Bug 811796
Summary: | Protected Custom Repo Names Not Propagated to guest rh-cloud.repo file. | ||
---|---|---|---|
Product: | Red Hat Update Infrastructure for Cloud Providers | Reporter: | Matthew Mariani <mmariani> |
Component: | Tools | Assignee: | James Slagle <jslagle> |
Status: | CLOSED ERRATA | QA Contact: | James Slagle <jslagle> |
Severity: | low | Docs Contact: | |
Priority: | high | ||
Version: | 2.1 | CC: | achan, kbidarka, sghai, tsanders, vkuznets |
Target Milestone: | --- | ||
Target Release: | 2.1.1 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Previously, yum displayed the unique numeric identifier for custom repositories. Repositories were not immediately identifiable because of this convention. The fix appends the custom repository name instead of the unique numeric identifier to the yum repository configuration.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2013-02-27 16:58:57 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: |
Description
Matthew Mariani
2012-04-12 01:36:36 UTC
moving to version 2.1.1 commit 4ba710642a2ee655e12b760a3b6740313ba8848a One thing to note, since multiple custom repos might share the same entitlement path (custom repos just different by arch for example), we might not know which repo label to use in the yum config. So, we just go with the first one repo for the entitlement path in question. # rpm -q rh-rhui-tools rh-rhui-tools-2.1.15-1.el6_3.noarch On client: # yum repolist | grep cp_1 && echo SUCCESS Unable to read consumer identity rhui-custom-cp_1 Custom Repositories - cp_1 0 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. http://rhn.redhat.com/errata/RHBA-2013-0571.html |