Description of problem:
While performing the minor update of OSP, it would be good if we can check which repositories are enabled on the overcloud nodes.
If there are some extra repositories enabled like EPEL, there should be a error displayed and the update process should abort.
On one of our setup, we faced this issue. We had EPEL repository enabled on controller nodes, which updated the packages on a controller node and galara went down because of package mismatch on the controllers.
No warning / error displayed if any extra repository enabled on overcloud nodes.
Operation should abort immediately with an error.
Verified in: openstack-tripleo-validations-8.4.0-2.el7ost.noarch
This only checks if EPEL is enabled (and fails if it is), and checks that there is at least 1 repo enabled. It doesn't guarantee that the *correct* repos are enabled for the upgrade.
Chaitanya, if you would like to additionally verify that the needed repos are not missing, please specify what those repos are. You can re-open this bug or file a new one.
I think there should be a verification of those repositories which should commonly be enabled on all the overcloud nodes (be it controllers, computes or ceph nodes).
There are some scenarios where we have ceph nodes in the overcloud stack for which we will have to enable the mon and osd repos on controllers and ceph nodes, otherwise these repos are not required.
Would this be doable here? If not, I think we can only verify the common repos as stated earlier. Let me know and I will raise a separate bug for it.
It's definitely doable - we can have a list of 'mandatory' and a list of 'forbidden' repos. Please open another bug with as much detail as possible as to what these repos should be.
I have opened another bug to validate the necessary repositories required ahead of beginning a minor update / major upgrade: https://bugzilla.redhat.com/show_bug.cgi?id=1575946
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.