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

Bug 2031669

Summary:	16.1 repos has higher version for some packages as compare to 16.2 repos
Product:	Red Hat OpenStack	Reporter:	Khomesh Thakre <kthakre>
Component:	tripleo-ansible	Assignee:	Martin Magr <mmagr>
Status:	CLOSED DUPLICATE	QA Contact:	David Rosenfeld <drosenfe>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	16.2 (Train)	CC:	astupnik, jjoyce, sshnaidm
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-12-17 20:01:53 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 Khomesh Thakre 2021-12-13 08:00:21 UTC

Description of problem:

After upgrading from 16.1 to 16.2, some packages are not upgraded and still coming from the 16.1 repositories. 

~~~
[root@undercloud mistral]# sudo yum list installed | grep openstack-16.1 | grep -v image
ansible-tripleo-ipsec.noarch                  9.3.0-1.20201113193132.0c8693c.el8ost              @openstack-16.1-for-rhel-8-x86_64-rpms
puppet-datacat.noarch                         0.6.3-1.20201113161038.5cce8f2.el8ost              @openstack-16.1-for-rhel-8-x86_64-rpms
puppet-kibana3.noarch                         0.0.5-1.20201113191144.6ca9631.el8ost              @openstack-16.1-for-rhel-8-x86_64-rpms
puppet-nssdb.noarch                           1.0.2-1.20201113160106.2ed2a2d.el8ost              @openstack-16.1-for-rhel-8-x86_64-rpms
puppet-snmp.noarch                            3.9.1-1.20201113161906.5d73485.el8ost              @openstack-16.1-for-rhel-8-x86_64-rpms
puppet-staging.noarch                         1.0.5-1.20201113145155.b466d93.el8ost              @openstack-16.1-for-rhel-8-x86_64-rpms
puppet-sysctl.noarch                          0.0.13-1.20201113145324.a3d160d.el8ost             @openstack-16.1-for-rhel-8-x86_64-rpms
puppet-timezone.noarch                        5.1.2-0.20200228222931.21b4a58.el8ost              @openstack-16.1-for-rhel-8-x86_64-rpms
python3-ansible-runner.noarch                 1.4.0-1.el8ost                                     @openstack-16.1-for-rhel-8-x86_64-rpms
[root@undercloud mistral]#
~~~

After taking a deeper look, I found that we have a 16.2 repo that has a lower version available and thus DNF doesn't upgrade these packages.  

~~~
[root@undercloud mistral]# yum list --showduplicates puppet-datacat                                                                                                                          
Updating Subscription Management repositories.
Last metadata expiration check: 0:59:20 ago on Tue 09 Nov 2021 02:08:55 AM EST.
Installed Packages
puppet-datacat.noarch                                              0.6.3-1.20201113161038.5cce8f2.el8ost                                                @openstack-16.1-for-rhel-8-x86_64-rpms
Available Packages
puppet-datacat.noarch                                              0.6.2-2.20210528040724.5cce8f2.el8ost.2                                              openstack-16.2-for-rhel-8-x86_64-rpms

[root@undercloud mistral]# yum list --showduplicates ansible-tripleo-ipsec
Updating Subscription Management repositories.
Last metadata expiration check: 1:00:08 ago on Tue 09 Nov 2021 02:08:55 AM EST.
Installed Packages
ansible-tripleo-ipsec.noarch                                          9.3.0-1.20201113193132.0c8693c.el8ost                                             @openstack-16.1-for-rhel-8-x86_64-rpms
Available Packages
ansible-tripleo-ipsec.noarch                                          9.2.0-2.20210527201530.ffe104c.el8ost.2                                           openstack-16.2-for-rhel-8-x86_64-rpms
[root@undercloud mistral]#
~~~

Is this behavior expected? And will it have any adverse effect on the environment?

Comment 4 Jason Joyce 2021-12-17 20:01:53 UTC


*** This bug has been marked as a duplicate of bug 2031142 ***