3.9. Content Management Issues
- BZ 1182481: Possible to delete ContentViewVersion used by Composite Content View Components
- Issue
The relationship between a Composite Content View and the used ContentViewVersion is not strict. If you re-publish a ContentView and delete the old ContentViewVersion, the list of Composite Content View components is empty.
WorkaroundNone at this time.
- BZ 1207642: Race condition on enabling repositories or promoting to the same environment
- Issue
A race condition could exist if you try to create, enable, publish, or promote different content views to the same environment. As a result, not all of the repositories that should be visible in the environment are actually visible.
WorkaroundTo work around this issue, re-enable the repository or promote the Content View again.
- BZ 1118271: The
Remove repositoriesoption does not delete associated packages from the file system - Issue
If you remove the repositories from a specific product, Red Hat Satellite does not automatically remove the associated packages from the file system, even though the repositories themselves are successfully removed.
WorkaroundNo supported workaround for this issue currently exists. If you encounter this issue, contact Red Hat Support or visit https://access.redhat.com/solutions/1295653 "How to deploy and use pulp-admin."
- BZ 1223568: Unregistering a Content Host shows an error in the Content Host's log file
- Issue
If you unregister a Content Host from Satellite, the process completes successfully but displays an error in the
/var/log/messagesfile. For example:May 20 17:50:19 cloud-10 goferd: [ERROR][Thread-3] katelloplugin:148 - send enabled report failed: [Errno 2] No such file or directory: '/etc/pki/consumer/key.pem'
Other error messages may also appear but in this scenario they appear not to affect the successful completion of the operation.WorkaroundNone required.
- BZ 1227064: Unregistering a Content Host shows an error in the Content Host's log file
- Issue
If you see messages similar to the following in
/var/log/foreman/production.loglog file, they can be ignored. The underlying error does not affect Satellite 6's operation and will be resolved in a future release.[F] no manager for d587f86a-5287-4369-b71a-fe4e7dc10582:3 (Dynflow::Error)
WorkaroundNone required.
- BZ 1184853: [RFE] Don't publish the same repositories over and over again
- Issue
Publishing and promoting Content View performance is not optimal and will be improved in future releases. Currently the publish and promotion process operates on all the repositories in the Content View, not only those repositories whose content had been changed.
WorkaroundNone at this time.
- BZ 1250716: Duplicate content view entries are shown in composite content view -> Add page
- Issue
If you navigate to → → , enter a name for the view and check the Composite View? checkbox, you may find the list of content views contains duplicates. This issue is cosmetic only and does not affect the operation of views.
WorkaroundNavigate to another screen, then navigate again to → and the duplicates will no longer be visible.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.