Document URL: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.6/html/upgrading_and_updating_red_hat_satellite/index Describe the issue: Users always find creative ways to implement their patch management. This has broken many Satellite servers While foreman_protector (https://bugzilla.redhat.com/show_bug.cgi?id=1512600) is a wonderful addition, many customers are confused with the locked packages warnings and there seem to be no good document that would explain its purpose and doings. Suggestions for improvement: Could this be documented in some way? Does it make sense to clearly outline RH standpoint on doing "yum update/upgrade for underlying rhel" and "satellite-maintain upgrade" (do's and dont's) in the Upgrade guide linked above?
The Satellite Documentation Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product documentation. If you have any concerns about this, feel free to reach back out. If we do not hear from you, we will close this bug out. Thank you.