[Satellite 6] When to publish Red Hat Satellite Content View Versions?

Environment

• Red Hat Satellite 6

Issue

• In which scenarios do we need to publish Red Hat Satellite Content View Versions ?
• When a new version of Content View is published and if the previous version is deleted, then why the count grows?
• It is also not clear why the numbers of the old versions are kept, since the old versions are deleted but still the numbers continue forward, losing the initial numbers?

Resolution

• Need to publish a new version of Content View is in the following cases:

  • If a new repository is added.
  • If a repository on Red Hat Satellite is updated and want it to get reflected on the servers.
  • If a new package is added/synced to a repository.
  • If broken symlink issue has occurred for a repository that is added to the content view.
  • If a filter has been created to exclude or Include any packages from the content view.
  • If Composite Content Views are in use, one must publish individual Content Views that are part of the Composite Content View before publishing a new version of the Composite Content View.

• The previous count of Content View version is kept to avoid conflicts between the various versions of Content Views, as many things are linked with version numbers. Thus, the Content View version number will always grow.

• The publication of Content View is immutable in nature.

For more KB articles/solutions related to Red Hat Satellite 6.x Content View Issues, please refer to the Red Hat Satellite Consolidated Troubleshooting Article for Red Hat Satellite 6.x Content View Issues

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.