Bug 1313882

Summary:	nova - multiple block_device_mapping records
Product:	Red Hat OpenStack	Reporter:	Simon Reber <sreber>
Component:	openstack-nova	Assignee:	Lee Yarwood <lyarwood>
Status:	CLOSED WONTFIX	QA Contact:	Joe H. Rahme <jhakimra>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.0 (Juno)	CC:	afariasa, aguetta, bschmaus, dasmith, eglynn, fahmed, fan-wxa, hfukumot, kchamart, ltamagno, lyarwood, mas-hatada, mfuruta, mschuppe, mzheng, pablo.iranzo, sbauza, sclewis, sgordon, sreber, srevivo, tvignaud, vromanso
Target Milestone:	---	Keywords:	Triaged, ZStream
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-05-12 13:02:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1581780, 1235795, 1273812

Comment 3 Nikola Dipanov 2016-03-04 13:44:28 UTC

This bug seems like a likely duplicate of BZ 1305408, but will not mark it as such yet before we are sure.

We will need to get the logs to investigate further, preferably from the time when the stress testing happened that leads to the bug.

Additionally - we would also want _exact_ commands used to do the stress testing as opposed to just descriptions.

Comment 8 Nikola Dipanov 2016-03-09 11:11:11 UTC

Ok so I spent some time digging into the already reported bugs and it seems that this has been reported already:

  https://bugs.launchpad.net/nova/+bug/1427060

The proposed patch:

  https://review.openstack.org/#/c/163177/

seems outdated though, so I'll try to work on a more up-to-date one.

Comment 19 Lee Yarwood 2016-11-16 15:39:46 UTC

Opening this bug up so that other duplicates can be closed out.

Comment 20 Lee Yarwood 2016-11-16 15:41:13 UTC

*** Bug 1342347 has been marked as a duplicate of this bug. ***

Comment 21 Lee Yarwood 2016-11-16 15:41:15 UTC

*** Bug 1341937 has been marked as a duplicate of this bug. ***

Comment 22 Lee Yarwood 2016-11-16 15:41:17 UTC

*** Bug 1340996 has been marked as a duplicate of this bug. ***

Comment 25 Lee Yarwood 2017-01-21 16:48:26 UTC

*** Bug 1305408 has been marked as a duplicate of this bug. ***

Comment 28 Lee Yarwood 2018-01-08 14:48:22 UTC

*** Bug 1376818 has been marked as a duplicate of this bug. ***

Comment 31 Lee Yarwood 2018-03-22 12:53:25 UTC

Moving back to ON_DEV, the current plan is to remove duplicate BDMs in 14/R with an online migration before then introducing a new constraint around volume_id and instance_uuid on the table in 15/S. While this doesn't fix the underlying race it will ensure duplicate records are not left in the DB.

Comment 33 melanie witt 2018-07-27 15:19:49 UTC

*** Bug 1608221 has been marked as a duplicate of this bug. ***

Comment 39 Andre 2019-08-01 14:47:39 UTC

Hi,

Is this issue already fixed on a newer version? If yes, since which version?

Comment 40 Andre 2019-08-01 14:47:51 UTC

Hi,

Is this issue already fixed on a newer version? If yes, since which version?

Comment 44 Lee Yarwood 2020-12-11 15:53:59 UTC

*** Bug 1906485 has been marked as a duplicate of this bug. ***

Comment 45 Lee Yarwood 2021-05-12 13:02:23 UTC

While this remains something that I'd like to eliminate through a reworking the attach volume flow [1] to automatically create and update BDMs within the API we've not seen any additional hits of this recently and so for the time being we will be closing this out as WONTFIX.

[1] https://docs.openstack.org/nova/latest/reference/attach-volume.html