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.7.1-2.20211218004850.173edba.el8ost.noarch openstack-tripleo-common-containers-11.7.1-2.20211218004850.173edba.el8ost.noarch openstack-tripleo-heat-templates-11.6.1-2.20220116004910.el8ost.noarch openstack-tempest-26.1.0-2.20211013134917.271f820.el8ost.noarch python3-manila-tests-tempest-1.4.0-2.20210629204822.f083c71.el8ost.noarch RHOSP containers tag: 16.2_20220209.2 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 (Moderate: Red Hat OpenStack Platform 16.2 (openstack-tripleo-heat-templates) security update), 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/RHSA-2022:0995