Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1108768

Summary: [Doc] yum-config-manager command doesn't change priority
Product: Red Hat OpenStack Reporter: Francesco Minafra <Francesco.Minafra>
Component: doc-Getting_Started_GuideAssignee: RHOS Documentation Team <rhos-docs>
Status: CLOSED CURRENTRELEASE QA Contact: ecs-bugs
Severity: high Docs Contact:
Priority: high    
Version: 4.0CC: ddomingo, mlopes, yeylon
Target Milestone: ---Keywords: Documentation, Triaged
Target Release: 5.0 (RHEL 7)   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Build Name: 22636, Getting Started Guide-4 Build Date: 25-03-2014 12:25:58 Topic ID: 29492-610000 [Latest]
Last Closed: 2015-02-08 22:44:20 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: 1040519    

Description Francesco Minafra 2014-06-12 14:14:51 UTC
Title: Red Hat Enterprise Linux OpenStack Platform Repository Configuration

Describe the issue:
Typing the command described in the text of the guide:

# yum-config-manager --enable rhel-6-server-openstack-4.0-rpms \
        --setopt="rhel-6-server-openstack-4.0-rpms.priority=1"

does not actually change the priority of the rhel-6-server-openstack-4.0-rpms
repository, which is still listed with priority = 99

Suggestions for improvement:

Probably it's a bug with yum-config-manager, and not with yum-plugin-priorities
because after I changed manually priority = 1 in /etc/yum/repos.d/redhat.repo
in the [rhel-6-server-openstack-4.0-rpms] stanza, the said repository is 
getting listed with the correct priority = 1 when I run again yum-config-manager (without arguments/options)

Additional information:

I'm using a freshly installed RHEL6.5 and followed the guide until the point above where it's suggested to run yum-config-manager to change priority.

Comment 2 Martin Lopes 2014-06-13 00:25:48 UTC
This bug is being assigned to Scott Radvan, who is now the designated docs specialist for RHEL integration.

Comment 3 Francesco Minafra 2014-06-13 07:43:12 UTC
Apparently this bug affects only the repository called:

rhel-6-server-openstack-4.0-rpms

If I use the command on another repository, e.g. 

yum-config-manager --setopt "rhel-6-server-rh-common-rpms.priority=1"

then the priority is set correctly.

Comment 4 Don Domingo 2014-06-19 00:56:46 UTC
I'm reassigning this to Bruce, as he has recently been studying that particular section for possible edits.

Bruce, this relates to your current work on BZ#1040519.

Comment 6 Andrew Dahms 2015-02-08 22:44:20 UTC
Dear Francesco,

Thank you for raising this bug.

The content surrounding the yum-config-manager command has since been updated several times, and should now be working correctly.

I am closing this bug at this time, but please let me know if you encounter this issue with other repositories and we will investigate this issue in the documentation for you.

Kind regards,

Andrew