Bug 1269147
| Summary: | Incorrect gpgcheck value set when 'repos --list' command pulls updated content | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Filip Nguyen <fnguyen> |
| Component: | subscription-manager | Assignee: | candlepin-bugs |
| Status: | CLOSED NOTABUG | QA Contact: | John Sefler <jsefler> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.3 | CC: | bcourt |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-11-20 15:58:33 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: | 1207433 | ||
What you are observing is the gap between when the certificate is updated on Candlepin and when those updates are pulled down to the machine by the rhsmcertd. |
Content may be updated by [1]. Then issuing [2] will trigger regeneration of the entitlement certificate to pull updated content and will update [3]. The problem is that when [1] updates gpgUrl to null then operation [2] will incorrectly leave gpgcheck in [3] to value '1'. Note that doing [1] with gpgUrl=null and then doing [4] will correctly set gpgcheck in [3] to '0'. [1] POST to /candlepin/owners/{owner}/content/{content_id} [2] repos --list [3] /etc/yum.repos.d/redhat.repo [4] remove --all && attach --pool <pool that has the content updated by [1]>