Description of problem: After upgrading RHOSP13 to RHOSP16.1z1, rhosp-release package is no longer installed in either undercloud node or overcloud nodes. This package is very often used to identify the maintenance release currently used in the deployment, so having this installed during upgrade would be very important and useful. Version-Release number of selected component (if applicable): RHOSP16.1z1 How reproducible: Always Steps to Reproduce: 1. Upgrade the deployment by following the upgrade documentation Actual results: rhosp-release package is not installed in either undercloud or overcloud Expected results: rhosp-release package is installed in both undercloud and overcloud Additional info:
From an OSP13 build: [stack@undercloud-0 ~]$ rpm -q --whatrequires rhosp-release rhosp-director-images-ipa-x86_64-13.0-20201112.1.el7ost.noarch octavia-amphora-image-x86_64-13.0-20201112.1.el7ost.noarch rhosp-director-images-x86_64-13.0-20201112.1.el7ost.noarch [stack@undercloud-0 ~]$ rpm -qa rhosp-director-images* rhosp-director-images-ipa-x86_64-13.0-20201112.1.el7ost.noarch rhosp-director-images-13.0-20201112.1.el7ost.noarch rhosp-director-images-x86_64-13.0-20201112.1.el7ost.noarch [stack@undercloud-0 ~]$ yumdb search reason user ... snip ... rhosp-director-images-13.0-20201112.1.el7ost.noarch reason = user rhosp-release-13.0.14-1.el7ost.noarch reason = user ... snip ... From this it would appear that rhosp-release was installed by the user, but it would have been installed as a dep by the installation of the rhosp-director-images package anyway. I'll verify the state post FFU and identify the root cause of the missing package in due course.
Changing this bug to low priority because the package is still installable and this is largely a cosmetic issue, not a functional one.
Part of the documented steps are to install the rhosp-director-images package, which will install rhosp-release as a dependency: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16.1/html-single/framework_for_upgrades_13_to_16.1/index#upgrading_the_overcloud_images If the package is not installed, then this step has been missed. As such, this is not a bug.
Sorry for updating this bug late. > If the package is not installed, then this step has been missed. As such, this is not a bug. Installing the rhos-director-images package installs rhosp-release in undercloud but the package is not installed in overcloud nodes. Currently rhosp-release package is included in overcloud images full and installed in overcloud nodes automatically. As I mentioned this is a useful information to identify the minor version installed I think it's still useful to implement a step to install rhosp-release package in overcloud nodes.
Hi, I would like to chime in a little bit. I run into the same issue with the lastest FFU from RHOSP13z16 to RHOSP16.1.6. 1. The rhosp-release-16.1.6-1.el8ost.noarch is install in undercloud during the "undercloud upgrade" phase. 2. However, the overcloud nodes the provided FFU upgraded steps did not installed the rhosp-release-16.1.6-1.el8ost.noarch. 3. We have to install the rhosp-release-16.1.6-1.el8ost.noarch manually to the overcloud nodes. 4. After FFU, adding new node will have the rhosp-release-16.1.6-1.el8ost.noarch (included in the overcloud-full.qcow2 Regards,
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 (Red Hat OpenStack Platform 16.1.7 (Train) bug fix and enhancement 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://access.redhat.com/errata/RHBA-2021:3762