+++ This bug was initially created as a clone of Bug #2010940 +++ Description of problem: After the FFU procedure, the ceph-nfs container doesn't work and the old reference is still running on the overcloud. ceph-ansible is supposed to update the unit, but it doesn't run any handler to restart it, because ceph-nfs is owned by pcmk (and there's also the VIP constraint). There's no task in tripleo-heat-templates that restart the ceph-nfs resource. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
ceph-nfs is now properly updated during the upgrade and the tempest tests from manila-tempest-plugin, which were mostly failing before, now pass correctly. The undercloud used: openstack-tripleo-common-11.4.1-1.20211201113403.75bd92a.el8ost.noarch openstack-tripleo-common-containers-11.4.1-1.20211201113403.75bd92a.el8ost.noarch openstack-tripleo-heat-templates-11.3.2-1.20220114223343.29a02c1.el8ost.noarch openstack-tempest-24.0.0-1.20210925123311.c73e6b1.el8ost.noarch python3-manila-tests-tempest-1.1.0-1.20211117153357.eba8fa9.el8ost.noarch RHOSP containers tag: 16.1_20220210.1 Ceph containers tag: 4-59
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.8 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-2022:0986