Red Hat Bugzilla – Bug 1477344
After upgrade from Sat 5.6 or 5.7 to 5.8, cdn-sync does not see channels that were synced prior to upgrade
Last modified: 2017-08-17 15:55:34 EDT
Description of problem:
Many customers have been running into the problem where, after upgrading from Satellite 5.6 or 5.7 to Satellite 5.8, running a full cdn-sync shows there is nothing to do as no channels are synced, and running # cdn-sync -l shows no channels synced (nothing marked with "p").
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Have a Sat 5.6 or 5.7 built with channels synced
2. Upgrade to Satellite 5.8
3. Run cdn-sync or cdn-sync -l
Output shows no channels synced
Channels that were synced prior to upgrade should be listed/synced
Forgot to mention: syncing the channels individually with # cdn-sync -c <channel-label> works and does get the channels to show up when running # cdn-sync -l or a full # cdn-sync
This is caused by change in spacewalk.git(master):
Basically it sees only channels with some CDN repositories already attached - after upgrade there are none, this needs to be enhanced.
fixed in spacewalk.git(master):
It now adds all null-org channels and all custom-org channels with associated null-org repositories to synced_channels set. Running cdn-sync without parameters will now try to sync channels which were previously ignored (previously, only channels synced at least once manually were attempted) - however, it's possible this sync will fail for some channels if there is something missing for them (error in channel mapping, entitlement error etc.).