On 15/11/16 13:38, Sandro Bonazzola wrote:
On Sat, Nov 12, 2016 at 4:37 PM, Lamar Owen <lowen@pari.edu mailto:lowen@pari.edu> wrote:
On 11/12/2016 01:27 AM, Sandro Bonazzola wrote: Il 11/Nov/2016 22:03, "Mohammed Naser" <mnaser@vexxhost.com <mailto:mnaser@vexxhost.com> <mailto:mnaser@vexxhost.com <mailto:mnaser@vexxhost.com>>> ha scritto: > > Hi everyone! > > It seems that the latest released version of qemu-kvm-ev is > qemu-kvm-ev-2.3.0-31.el7_2.21.1 based on the following: > > https://cbs.centos.org/koji/packageinfo?packageID=539 <https://cbs.centos.org/koji/packageinfo?packageID=539> > > However, our systems are refusing to update to that package because > qemu-kvm-ev-2.3.0-31.el7.16.1 is installed. I believe the 16.1 is > making it seem that it is newer than 2.21.1 (16 > 2). Looks like dist tag is not considered in version computation. 21.1 is higher than 16.1 but el7 is considered higher than el7_2. Just to be sure, please try yum clean metadata, and then yum distro-sync. I can confirm this behavior here. In fact, it looks like we've missed two updates; el7_2.16.1 was released the day after el7.16.1 was, and that one didn't update my install, either. In checking, it appears that both have an epoch of 10. A yum distro-sync does not offer to reinstall qemu-$subpackage-ev for me, even after yum clean metadata or yum clean all.
karanbir any chance we can get the offending package removed from the repository? So at least rpm -Uvh --force to the newer release will work and yum won't try to downgrade it.
if we were to try and resolve this without removing rpms, what would that solution look like ?