Bug 1672751
Summary: | scan_cdn task failed while enabling red hat repositories from cdn | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Nikhil Kathole <nkathole> | ||||
Component: | Subscription Management | Assignee: | Justin Sherrill <jsherril> | ||||
Status: | CLOSED ERRATA | QA Contact: | Nikhil Kathole <nkathole> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 6.5.0 | CC: | jhutar, nkathole, zhunting | ||||
Target Milestone: | 6.5.0 | Keywords: | Regression, Triaged | ||||
Target Release: | Unused | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | tfm-rubygem-katello-3.10.0.19-1 | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2019-05-14 12:40:00 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: | 1653153 | ||||||
Attachments: |
|
Description
Nikhil Kathole
2019-02-05 18:59:24 UTC
Created attachment 1527265 [details]
screenshot of UI
Created redmine issue https://projects.theforeman.org/issues/25996 from this bug Does this impact enabling all repositories or only certain ones? Does the repo get enabled or is this just an error in the log? (In reply to Brad Buckingham from comment #8) > Does this impact enabling all repositories or only certain ones? This impact only enabling certain repos. > Does the repo get enabled or is this just an error in the log? No, repos won't get enabled. *** Bug 1673715 has been marked as a duplicate of this bug. *** VERIFIED Version tested: Satellite 6.5 snap 16 No failures in scan_cdn task and red hat repos are enabled successfully. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:1222 |