Hide Forgot
Description of problem: Note: Customer is using EMCDell VNX as a cinder driver. But we'd like to make sure this issue is not raised from OpenStack side Volume attachment is failing, on Cinder it shows as available but nova shows it as attached. I'll post more information and logs on the next comment as private, since it may contain customer sensitive information. We're expecting a RCA from this issue. Version-Release number of selected component (if applicable): dellemc/openstack-cinder-volume-dellemc-rhosp16:latest rhosp-rhel8/openstack-cinder-scheduler:16.1-49 rhosp-rhel8/openstack-cinder-api:16.1-49 rhosp-rhel8/openstack-nova-compute:16.1-52.1602000860 rhosp-rhel8/openstack-nova-libvirt:16.1-56.1602000855 rhosp-rhel8/openstack-nova-api:16.1-55 rhosp-rhel8/openstack-nova-novncproxy:16.1-54 rhosp-rhel8/openstack-nova-scheduler:16.1-53 rhosp-rhel8/openstack-nova-conductor:16.1-53 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: sosreport are available on supportshell under /cases/02791747
Do we currently have any workaround for this issue? Or maybe just to mitigate, like increasing some timeout?
(In reply to Andre from comment #7) > Do we currently have any workaround for this issue? Or maybe just to > mitigate, like increasing some timeout? There's no workaround at present, we have spoken about removing this initial RPC call entirely and creating the bdm record in the DB from within the API for sometime to avoid the fallout we are seeing here from the timeout. That said the underlying issue here seems to be more of a RPC issue so lets address that and I might spawn a separate bug to track the additional rework/refactor in openstack-nova.
(In reply to Lee Yarwood from comment #9) > I might spawn a separate bug to track the additional rework/refactor in openstack-nova. Apologies, I had already done this in bug #1899581.
Fix submitted on master upstream: https://review.opendev.org/c/openstack/oslo.messaging/+/764776
All the fixes have been cherry-picked from upstream train into OSP 16.1 Build successfully completed https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=35535009 Generated version python-oslo-messaging-10.2.1-1.20201114001303.el8ost
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.6 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:2097