Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1992863

Summary: [OSP 16.2] Avoid duplicate BDMs during reserve_block_device_name
Product: Red Hat OpenStack Reporter: Lee Yarwood <lyarwood>
Component: openstack-novaAssignee: Lee Yarwood <lyarwood>
Status: CLOSED ERRATA QA Contact: OSP DFG:Compute <osp-dfg-compute>
Severity: medium Docs Contact:
Priority: medium    
Version: 17.0 (Wallaby)CC: alifshit, dasmith, eglynn, jhakimra, kchamart, nova-maint, sbauza, sgordon, vromanso
Target Milestone: z2Keywords: Patch, Triaged
Target Release: 16.2 (Train on RHEL 8.4)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: openstack-nova-20.6.2-2.20210812144825.1aa5711.el8ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1992858 Environment:
Last Closed: 2022-03-23 22:11:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Lee Yarwood 2021-08-11 20:23:23 UTC 
+++ This bug was initially created as a clone of Bug #1992858 +++

Description of problem:

Duplicate BlockDeviceMapping if attaching volumes too fast 
https://launchpad.net/bugs/1937375

When attaching a volume to a running instance the nova-api validates that
the volume is not already attached to the instance. However nova-compute
is responsible for actually creating the BDM entry in the database.
If sending attach requests fast enough it can be possible that the same
"attach_volume" request can be sent to nova-compute for the same
volume/instance combination.
Comment 14 errata-xmlrpc 2022-03-23 22:11:12 UTC 
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 16.2.2), 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:1001