Red Hat Bugzilla – Bug 1265016
Do We Need Sentence About Syncing Proxy Channel After Upgrade?
Last modified: 2017-07-23 20:25:41 EDT
Description of problem:
Customer upgraded Satellite & Satellite proxy months ago. It is unknown whether the customer did something wrong or if instructions were not explicit enough, but the proxy never got subscribed to the rhel-5-server-satellite-proxy-5.6-rpms. More importantly, the Satellite was not syncing the rhel-5-server-satellite-proxy-5.6-rpms channel, so even if the proxy was subscribed, it would not have gotten updates.
This reporter does not know whether the configure-proxy.sh script, as shown in the proxy installation guide:
...should have subscribed the proxy to the new channel & started the Satellite syncing it or not. If it does, then this bug ticket can be closed as the customer apparently did something wrong. If it does not, then a note needs added to the documentation that the customer must manually subscribe the proxy to the new rhel-5-server-satellite-proxy-5.X-rpms channel and manually cause the Satellite to start syncing it.
Version-Release number of selected component (if applicable):
Customer encountered this when upgrading from Satellite 5.4 to 5.6. This reporter imagines the customer would have also had the problem had they gone to 5.7
Moving to the default assignee to be triaged as the schedule allows.
I agree on all counts. Particularly given the imminent end of RHN, I think we can go ahead and close this.