RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1073626 - Setting priority for repo doesn't print out a confirmation that the priority was set to a certain value
Summary: Setting priority for repo doesn't print out a confirmation that the priority ...
Keywords:
Status: CLOSED DUPLICATE of bug 1024111
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: yum-utils
Version: 6.6
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Packaging Maintenance Team
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks: 1099559
TreeView+ depends on / blocked
 
Reported: 2014-03-06 20:15 UTC by Liz
Modified: 2014-06-13 13:07 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-26 10:43:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Liz 2014-03-06 20:15:49 UTC 
Description of problem:
Setting priority for repo doesn't print out a confirmation that the priority was set to a certain value

Running:
yum-config-manager --enable REPO_NAME --setopt="REPO_NAME.priority=1"

Unsure if this actually did change the priority. Would be great to see in output.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Run yum-config-manager --enable REPO_NAME --setopt="REPO_NAME.priority=1"
2. View output
3.

Actual results:
Priority isn't seen in output.

Expected results:
Add new priority value to output for confirmation to the user.

Additional info:
Comment 2 Valentina Mukhamedzhanova 2014-03-10 15:52:02 UTC 
Hello, I have a few questions about this report.
1. Do you have yum-plugin-priorities installed? If yes, how did you install it?
2. What output do you currently get?
Comment 3 Liz 2014-03-10 17:22:59 UTC 
Hi Valentina,

Thanks very much for following up on this. As soon as I installed yum-plugin-priorities, the value did actually start showing up in the output.

The issue I recently faced is that when I tried to change the priority from 99 to 1, it didn't seem to update. Should I update this bug to reflect this new state?

Thanks!
Liz
Comment 4 Valentina Mukhamedzhanova 2014-03-11 08:19:15 UTC 
Before updating the bug report, let's make sure we do indeed have a bug. Could you please provide the following information:
1. When you *don't* have the yum-plugin-priorities installed what output do you get?
2. When you *don't* have the yum-plugin-priorities installed does the priority option get updated?
3. When you *have* the yum-plugin-priorities installed what output do you get?
4. When you *have* the yum-plugin-priorities installed does the priority option get updated?

Please make sure you provide the entire output for 'yum-config-manager --enable REPO_NAME --setopt="REPO_NAME.priority=1"'.

Thank you!
Comment 5 Matt Reid 2014-03-21 20:06:57 UTC 
Answering for Liz:

1. Output with no yum-plugin-priorities 
[root@cf-rhos-uxd ~]# yum-config-manager --enable rhel-6-server-openstack-4.0-rpms --setopt=rhel-6-server-openstack-4.0-rpms.priority=1
Loaded plugins: product-id
==================== repo: rhel-6-server-openstack-4.0-rpms ====================
[rhel-6-server-openstack-4.0-rpms]
bandwidth = 0
base_persistdir = /var/lib/yum/repos/x86_64/6Server
baseurl = https://cdn.redhat.com/content/dist/rhel/server/6/6Server/x86_64/openstack/4.0/os
cache = 0
cachedir = /var/cache/yum/x86_64/6Server/rhel-6-server-openstack-4.0-rpms
cost = 1000
enabled = 1
enablegroups = True
exclude = 
failovermethod = priority
gpgcadir = /var/lib/yum/repos/x86_64/6Server/rhel-6-server-openstack-4.0-rpms/gpgcadir
gpgcakey = 
gpgcheck = True
gpgdir = /var/lib/yum/repos/x86_64/6Server/rhel-6-server-openstack-4.0-rpms/gpgdir
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
hdrdir = /var/cache/yum/x86_64/6Server/rhel-6-server-openstack-4.0-rpms/headers
http_caching = all
includepkgs = 
keepalive = True
mdpolicy = group:primary
mediaid = 
metadata_expire = 86400
metalink = 
mirrorlist = 
mirrorlist_expire = 86400
name = Red Hat OpenStack 4.0 (RPMs)
old_base_cache_dir = 
password = 
persistdir = /var/lib/yum/repos/x86_64/6Server/rhel-6-server-openstack-4.0-rpms
pkgdir = /var/cache/yum/x86_64/6Server/rhel-6-server-openstack-4.0-rpms/packages
proxy = 
proxy_dict = 
proxy_password = 
proxy_username = 
repo_gpgcheck = False
retries = 10
skip_if_unavailable = False
ssl_check_cert_permissions = True
sslcacert = /etc/rhsm/ca/redhat-uep.pem
sslclientcert = /etc/pki/entitlement/2802263051537174663.pem
sslclientkey = /etc/pki/entitlement/2802263051537174663-key.pem
sslverify = True
throttle = 0
timeout = 30.0
username = 


2. No, the priority doesn't seem to have been updated, it's not even listed in the output.
yum-config-manager --enable rhel-6-server-openstack-4.0-rpms --setopt=rhel-6-server-openstack-4.0-rpms.priority=1 | grep priority
failovermethod = priority

3. Here's the output when I have yum-plugin-priorities installed.
[root@cf-rhos-uxd ~]# rpm -qa yum-plugin-priorities
yum-plugin-priorities-1.1.30-14.el6.noarch
[root@cf-rhos-uxd ~]# yum-config-manager --enable rhel-6-server-openstack-4.0-rpms --setopt="rhel-6-server-openstack-4.0-rpms.priority=1"
Loaded plugins: priorities, product-id
==================== repo: rhel-6-server-openstack-4.0-rpms ====================
[rhel-6-server-openstack-4.0-rpms]
bandwidth = 0
base_persistdir = /var/lib/yum/repos/x86_64/6Server
baseurl = https://cdn.redhat.com/content/dist/rhel/server/6/6Server/x86_64/openstack/4.0/os
cache = 0
cachedir = /var/cache/yum/x86_64/6Server/rhel-6-server-openstack-4.0-rpms
cost = 1000
enabled = True
enablegroups = True
exclude = 
failovermethod = priority
gpgcadir = /var/lib/yum/repos/x86_64/6Server/rhel-6-server-openstack-4.0-rpms/gpgcadir
gpgcakey = 
gpgcheck = True
gpgdir = /var/lib/yum/repos/x86_64/6Server/rhel-6-server-openstack-4.0-rpms/gpgdir
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
hdrdir = /var/cache/yum/x86_64/6Server/rhel-6-server-openstack-4.0-rpms/headers
http_caching = all
includepkgs = 
keepalive = True
mdpolicy = group:primary
mediaid = 
metadata_expire = 86400
metalink = 
mirrorlist = 
mirrorlist_expire = 86400
name = Red Hat OpenStack 4.0 (RPMs)
old_base_cache_dir = 
password = 
persistdir = /var/lib/yum/repos/x86_64/6Server/rhel-6-server-openstack-4.0-rpms
pkgdir = /var/cache/yum/x86_64/6Server/rhel-6-server-openstack-4.0-rpms/packages
priority = 99
proxy = 
proxy_dict = 
proxy_password = 
proxy_username = 
repo_gpgcheck = False
retries = 10
skip_if_unavailable = False
ssl_check_cert_permissions = True
sslcacert = /etc/rhsm/ca/redhat-uep.pem
sslclientcert = /etc/pki/entitlement/2802263051537174663.pem
sslclientkey = /etc/pki/entitlement/2802263051537174663-key.pem
sslverify = True
throttle = 0
timeout = 30.0
username = 

4. As you can see above, I specified priority=1 with --setopt, and in the output, priority is still 99, but here's the grepped version to be concise.
[root@cf-rhos-uxd ~]# yum-config-manager --enable rhel-6-server-openstack-4.0-rpms --setopt=rhel-6-server-openstack-4.0-rpms.priority=1 | grep priority
failovermethod = priority
priority = 99

That's what the docs tell me should work, and I can't find a way that makes priority anything other than the default 99. Am I missing something? 

The Getting Started Guide for OpenStack tells me to '# yum-config-manager --enable REPO_NAME --setopt="REPO_NAME.priority=1"'
Comment 6 Valentina Mukhamedzhanova 2014-03-24 09:21:24 UTC 
Hello, Matt, thank you for the provided information. I cannot reproduce this problem on my test system, so I need some more details.

1. What version of yum and yum-utils are you using?
2. How did you install yum-plugin-priorities?
3. Could you list your /etc/yum.repos.d/rhel-6-server-openstack-4.0-rpms.repo file?
4. Does setting any other option work for you? For example '# yum-config-manager --enable rhel-6-server-openstack-4.0-rpms --setopt="rhel-6-server-openstack-4.0-rpms.gpgcheck=0"'
Comment 7 Matt Reid 2014-03-24 13:49:05 UTC 
1. Version info:
[root@cf-rhos-uxd ~]# rpm -qa yum
yum-3.2.29-43.el6_5.noarch
[root@cf-rhos-uxd ~]# rpm -qa yum-utils
yum-utils-1.1.30-17.el6_5.noarch

2. I installed it after enabling the openstack repository, on a system that had been registered and subscribed through subscription manager. Normally, I think this package is pulled from the Server Optional repo (which is not enabled on my system), but is also included in the Openstack repo, I don't know if they're different versions.

3. I don't have a /etc/yum.repos.d/rhel-6-server-openstack-4.0-rpms file, in that directory, I just have redhat.repo and rhel-source.repo. In redhat.repo, the openstack repo has the following information:
[rhel-6-server-openstack-4.0-rpms]
name = Red Hat OpenStack 4.0 (RPMs)
baseurl = https://cdn.redhat.com/content/dist/rhel/server/6/$releasever/$basearch/openstack/4.0/os
enabled = 1
gpgcheck = 1
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
sslverify = 1
sslcacert = /etc/rhsm/ca/redhat-uep.pem
sslclientkey = /etc/pki/entitlement/2802263051537174663-key.pem
sslclientcert = /etc/pki/entitlement/2802263051537174663.pem
metadata_expire = 86400
ui_repoid_vars = releasever basearch

4. It doesn't look like I can modify any options through setopt. That gpgcheck command doesn't change it from "gpgcheck = True", and trying to change other things, those do not get modified either.
Comment 8 Valentina Mukhamedzhanova 2014-03-26 10:08:20 UTC 
Matt, thank you, with your help I have managed to reproduce the problem. It seems that it is caused by the dot in the repo id, so the root cause of the problem is probably the same as for bug 1024111. I will check if the suggested patch fixes the problem.
Comment 9 Valentina Mukhamedzhanova 2014-03-26 10:43:33 UTC 

*** This bug has been marked as a duplicate of bug 1024111 ***
Note You need to log in before you can comment on or make changes to this bug.