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
After upgrade from Sat 5.6 or 5.7 to 5.8, cdn-sync does not see channels that...
Status: MODIFIED
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Satellite Synchronization (Show other bugs)
580
Unspecified Unspecified
medium Severity medium
: ---
: ---
Assigned To: Jan Dobes
Red Hat Satellite QA List
:
Depends On:
Blocks: sat58-errata
  Show dependency treegraph
 
Reported: 2017-08-01 16:40 EDT by Candace Sheremeta
Modified: 2017-08-17 15:55 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Candace Sheremeta 2017-08-01 16:40:40 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):
5.8

How reproducible:
?

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

Actual results:
Output shows no channels synced

Expected results:
Channels that were synced prior to upgrade should be listed/synced

Additional info:
Comment 1 Candace Sheremeta 2017-08-01 16:42:14 EDT
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
Comment 3 Jan Dobes 2017-08-08 05:32:03 EDT
This is caused by change in spacewalk.git(master):

2f6327ba8b098a74d4d54493d5fb2b0fce947b2b

Basically it sees only channels with some CDN repositories already attached - after upgrade there are none, this needs to be enhanced.
Comment 4 Jan Dobes 2017-08-14 08:11:38 EDT
fixed in spacewalk.git(master):

833fc83cbbf2606d6dbb79fb125488822f3157e8

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.).

Note You need to log in before you can comment on or make changes to this bug.