Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1211390

Summary: yum does not work consistently with RPMs with '0:' in the name
Product: Red Hat Enterprise Linux 6 Reporter: Dave Sullivan <dsulliva>
Component: yumAssignee: Valentina Mukhamedzhanova <vmukhame>
Status: CLOSED ERRATA QA Contact: Eva Mrakova <emrakova>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.8CC: emrakova, ffesti, james.antill
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: yum-3.2.29-71.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-10 21:29:52 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: 1172231    
Attachments:
Description Flags
patch none

Description Dave Sullivan 2015-04-13 20:54:47 UTC
Description of problem:

Installing RPMs with the '0:' in the name works, but doing a 'yum list installed rpm_name' fails if the name has a '0:' in it.

PKGNAME=$(repoquery "ypserv*" | sort -n  | tail -1)
 yum -y install $PKGNAME
yum list installed $PKGNAME

The package will be installed and can be viewed in 'rpm -qa | grep ypserv'.  The 'yum list installed PKGNAME' or 'rpm -q PKGNAME' does not show it.  If you search for the name without the '0:', then both the yum list installed and rpm -q command work.



Fails on RHEL5.11 and 6.5


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

Any yum version on rhel5/rhel6

rhel7 not tested


How reproducible:


See description above

Actual results:


Expected results:


Additional info:

Interesting that we see epochnum

[root@seaking openssh-clients]# rpm -qa ypserv --qf '%{epochnum}:%{name}-%{version}-%{release}.%{arch}\n'
0:ypserv-2.19-26.el6_4.2.x86_64
[root@seaking openssh-clients]# uname -a
Linux seaking.sullyvon.com 2.6.32-504.3.3.el6.x86_64 #1 SMP Fri Dec 12 16:05:43 EST 2014 x86_64 x86_64 x86_64 GNU/Linux

Looks like yum list works fine

[root@seaking openssh-clients]# echo $PKGNAME
ypserv-0:2.19-26.el6_4.2.x86_64
[root@seaking openssh-clients]# yum list $PKGNAME
Loaded plugins: product-id, refresh-packagekit, rhnplugin, security, subscription-manager
This system is not registered with RHN Classic or RHN Satellite.
You can use rhn_register to register.
RHN Satellite or RHN Classic support will be disabled.
Available Packages
ypserv.x86_64                                                                                  2.19-26.el6_4.2                                                                                   rhel-6-server-rpms


But yum list installed doesn't

[root@seaking openssh-clients]# yum list installed $PKGNAME
Loaded plugins: product-id, refresh-packagekit, rhnplugin, security, subscription-manager
This system is not registered with RHN Classic or RHN Satellite.
You can use rhn_register to register.
RHN Satellite or RHN Classic support will be disabled.
Error: No matching Packages to list

Some what odd

repoquery seems to show an epoch

[root@seaking openssh-clients]# repoquery --qf '%{epoch}:%{name}-%{version}-%{release}.%{arch}\n' "ypserv*"
0:ypserv-2.19-26.el6_4.2.x86_64

But rpm only sees epochnum

[root@seaking openssh-clients]# rpm -qa ypserv --qf '%{epochnum}:%{name}-%{version}-%{release}.%{arch}\n'
0:ypserv-2.19-26.el6_4.2.x86_64


[root@seaking openssh-clients]# rpm -qa ypserv --qf '%{epoch}:%{name}-%{version}-%{release}.%{arch}\n'
(none):ypserv-2.19-26.el6_4.2.x86_64

[root@seaking openssh-clients]# repoquery --querytags | grep epoch
epoch

[root@seaking openssh-clients]# rpm --querytags | grep -i epoch
EPOCH
EPOCHNUM

EPOCHNUM (epoch of header, returns 0 for no epoch) 

So I think our bug here on yum list installed <pkg> can't handle the default format returned by repoquery.

If you use the --envra flag you can get this to work just fine

[root@seaking ypserv]# PKGNAME=$(repoquery --envra "ypserv*" | sort -n  | tail -1)
[root@seaking ypserv]# yum list installed $PKGNAME
Loaded plugins: product-id, refresh-packagekit, rhnplugin, security, subscription-manager
This system is not registered with RHN Classic or RHN Satellite.
You can use rhn_register to register.
RHN Satellite or RHN Classic support will be disabled.
Installed Packages
ypserv.x86_64

Comment 3 Valentina Mukhamedzhanova 2015-09-30 20:49:03 UTC
Created attachment 1078821 [details]
patch

Comment 9 errata-xmlrpc 2016-05-10 21:29:52 UTC
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://rhn.redhat.com/errata/RHEA-2016-0836.html