Bug 1434787
Summary: | Channel mapping errors upon activation with new manifest | ||
---|---|---|---|
Product: | Red Hat Satellite 5 | Reporter: | Kenny Tordeurs <ktordeur> |
Component: | Other | Assignee: | Jan Dobes <jdobes> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Jan HutaĆ <jhutar> |
Severity: | low | Docs Contact: | |
Priority: | high | ||
Version: | 580 | CC: | ahumbe, ggainey, jhutar, ktordeur, lisas, rdrazny, shughes, tlestach, xdmoon |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | spacewalk-backend-2.5.3-110 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-06-21 12:11:16 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 465198, 1340444 |
Description
Kenny Tordeurs
2017-03-22 11:42:48 UTC
These are the inconsistencies between a manifest and embedded Sat 5.8 cert. One Q - has this manifest been generated from Prod (or from Stage)? Production These aren't inconsistencies - the messages are telling us that there are channel-families available to the org, for which there exists no mapping to a CDN content-set, which is a true statement. It's exacerbated when an org has, say, the Employee SKU associated with it - that SKU gives access to channel-families that haven't been available to actual customers in a decade or more, in some cases. That being said, a long list of loud ERROR messages is probably not useful. I would suggest the following: * change to WARNING (or even INFO) * log to a file, rather than stdout * Add a note, "some RHN channel-family content does not exist in CDN, and therefore cannot be accessed using cdn-sync". (I'm sure there is a better way to say this, but that's the gist of what we should add) Kenny - please attach the manifest you used in this case, so people have something to go on to verify my assumptions above. I don't see the justification for this being a high-sev issue. There is no failure here, what the code is reporting is true, and it doesn't block any functionality. High-severity implies broken-main-path, and nothing is broken here. Commit from bz1397762 makes these messages displayable only when -v parameter is specified, switching to MODIFIED. adding support for logging to file in spacewalk master: 34c3c5304d4e9ce6da5bcb18d78fb2dce544c85d 79fd790221d8ac87e3b80954d9f9626fe653a6f8 ec4d098350ca59677d79b2bbb06a8f85d36e1369 be26c485239a4dece779c22e8af4f0076ab433d0 dd7f8af9788a6d7df44247cab9fc9873df12d583 |