How to add new RPMs to a Content View without pushing updates for the existing repositories in Red Hat Satellite 6

Solution Verified - Updated -

Issue

  • When adding new packages or a new repository to a Content View, a new version has to be published, this inadvertently pushes updates for the existing repositories in the Content View.
  • Is it possible to maintain the existing repositories at the same version, while adding new packages or repositories to a Content View?

Environment

  • Red Hat Satellite 6.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In