Bug 1899581 - MessagingTimeout while in nova.compute.api.API._create_volume_bdm can leave orphaned BDM records in the database
Summary: MessagingTimeout while in nova.compute.api.API._create_volume_bdm can leave o...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-nova
Version: 17.0 (Wallaby)
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: OSP DFG:Compute
QA Contact: OSP DFG:Compute
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-19 15:42 UTC by Lee Yarwood
Modified: 2024-10-01 17:06 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-23 15:19:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-5503 0 None None None 2022-01-04 11:05:30 UTC

Description Lee Yarwood 2020-11-19 15:42:27 UTC 
Description of problem:

Bug #1898578 details a failure to attach a volume to an instance where n-cpu raises MessageUndeliverable after creating a BDM record. This results in n-api eventually raising MessagingTimeout and the overall request failing.

This leaves a BDM record in the database suggesting that the volume is attached to the instance when in fact it is not. n-api should rollback and remove any BDM records created by n-cpu when it encounters MessagingTimeout.

This issue was previously raised in bug #1752734 but assumed resolved by other fixes to oslo.messaging that landed later in Rocky.

Version-Release number of selected component (if applicable):
17 / master

How reproducible:
Always

Steps to Reproduce:
1. Cause MessagingTimeout to be raised from calls to reserve_block_device_name


Actual results:
BDM records created by n-cpu are not cleaned up by n-api.


Expected results:
BDM records created by n-cpu are cleaned up by n-api.

Additional info:
Note You need to log in before you can comment on or make changes to this bug.