Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/Installation_Guide/chap-Red_Hat_Satellite-Installation_Guide-Upgrading_Red_Hat_Satellite_Server_and_Capsule_Server.html#sect-Red_Hat_Satellite-Installation_Guide-Upgrading_Red_Hat_Satellite_Server_and_Capsule_Server-Upgrading_Red_Hat_Satellite There was a consultant working on a customer upgrade from 6.0 to 6.1. While not directly related to upgrade, there was an issue with content filters behaving differently after the system was upgrade. The consultant was said that he was told (in 6.0 docs? by engineering? in the 6.1 doc? TBD) to have "include all the packages without errata" as part of the content filter. However, with that setting, the original exclude rule was overridden, which broke the customer SOE.
Mass re-assign of all content / lifecycle related bugs to Dan MacPherson for the new content management guide.
++++ IMPORTANT +++++ These bugs are being reassigned to Dan MacPherson as part of his work on creating a content management guide. ///////////////////////////// DO NOT REASSIGN TO THE QUEUE. /////////////////////////////
I've tried to expand on how content filters work, especially the order of include and exclude: http://file.bne.redhat.com/~dmacpher/Sat6/Content_Management/#Creating_Content_Views-Defining_Content_Filters The following note sums it up: === Note === If using a combination of Include and Exclude filters, publishing a content view triggers the Include filters first, then the exclude filters. In this situation, select which content to include, then which content to exclude from the inclusive subset. Deon, does that suit the requirements of this BZ?
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
The bugs were included as part of technical review of the full guide. In addition, the guide has been peer reviewed. Setting the QA contact to adahms and flipping the status to ON_QA.
Peer reviewed performed in BZ#1326123. This content is now live on the Customer Portal. Closing.