Description of problem: There are multiple tempest test failing with an error like this Details: (ServerActionsTestJSON:test_resize_server_revert_with_volume_attached) Server dfc0d66a-05ea-4733-8477-b8bc451329c9 failed to reach VERIFY_RESIZE status and task state "None" within the required time (300 s). Current status: ACTIVE. Current task state: None. An example of a failed tests: https://rhos-ci-jenkins.lab.eng.tlv2.redhat.com/view/custom/job/custom-17.1_compact-director-rhel-9.2-virthost-3cont_2comp_3ceph_1freeipa_4comprhel8-ipv4-geneve-ceph-tls-multirhel/2/testReport/junit/tempest.api.compute.servers.test_server_actions/ServerActionsTestJSON/test_resize_server_revert_id_c03aab19_adb1_44f5_917d_c419577e9e68_/ It is possible that perhaps this is no a product issue but maybe a test only issue. Regardless, I wanted to have it officially documented. Kashyap Chamarthy was already informed about this BZ. Version-Release number of selected component (if applicable): 17.1 How reproducible: 100% on a multirhel deployment Steps to Reproduce: 1. Deploy 17.1 multirhel, you can use Jenkins job for it https://rhos-ci-jenkins.lab.eng.tlv2.redhat.com/view/custom/job/custom-17.1_compact-director-rhel-9.2-virthost-3cont_2comp_3ceph_1freeipa_4comprhel8-ipv4-geneve-ceph-tls-multirhel/ 2. Run tempest.api.compute.* tests. 3. Notice they will fail with the error mentioned above Actual results: Expected results: Additional info:
Asking for blocker+ because migrations will not work until this is fixed.
submitted downstream patch before upstream got merged (low cores attention keep it pending)
*** Bug 2186553 has been marked as a duplicate of this bug. ***
A follow-up patch linked
A one more fix added upstream...
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 (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), 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/RHEA-2023:4577