Bug 1964078 - EMC VMAX volume backend timeout during attachment_update
Summary: EMC VMAX volume backend timeout during attachment_update
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder
Version: 13.0 (Queens)
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Cinder Bugs List
QA Contact: Evelina Shames
Andy Stillman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-05-24 16:47 UTC by Luigi Tamagnone
Modified: 2023-07-10 19:48 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-10 19:48:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-4116 0 None None None 2021-11-17 09:33:29 UTC

Description Luigi Tamagnone 2021-05-24 16:47:53 UTC
Description of problem:
The instance creation fails with "Build of instance 8738645d-de56-4331-85e5-1decf756cd9c aborted: Unable to update the attachment. (HTTP 500)" The same volume on other compute nodes works.
This issue happens for every volume from VMAX backend
The issue could be bind with BUG 1942079. But I'm not sure.

Version-Release number of selected component (if applicable):
[redhat-release] Red Hat Enterprise Linux Server release 7.7 (Maipo)
[rhosp-release] Red Hat OpenStack Platform release 13.0.10 (Queens)

How reproducible:
The customer can reproduce the error every time they try to create an instance from a volume.

Steps to Reproduce:
1. create volume in VMAX backend from an image
2. Create an instance from that volume

Actual results:
Instance creation fails

Expected results:
instance creation succeed

Additional info:
From nova.log on cmpc24:
2021-05-21 16:32:14.043 8 ERROR nova.volume.cinder [req-1f0a046c-68ec-4a22-9007-487298d048ef ad9a17ce8088485ca950656ba84345b5 ff9c71872c20417e83e4387fccf85434 - default default] Update attachment failed for attachment 4 [details]bad0883-366a-4c53-811f-0314b89faa9a. Error: Unable to update the attachment. (HTTP 500) (Request-ID: req-c620442e-e659-4637-a34d-433231096a05) Code: 500: ClientException: Unable to update the attachment. (HTTP 500) (Request-ID: req-c620442e-e659-4637-a34d-433231096a05)
2021-05-21 16:32:14.064 8 ERROR nova.compute.manager [req-1f0a046c-68ec-4a22-9007-487298d048ef ad9a17ce8088485ca950656ba84345b5 ff9c71872c20417e83e4387fccf85434 - default default] [instance: 8738645d-de56-4331-85e5-1decf756cd9c] Instance failed block device setup: ClientException: Unable to update the attachment. (HTTP 500) (Request-ID: req-c620442e-e659-4637-a34d-433231096a05)

Comment 10 Lon Hohberger 2023-07-10 19:48:08 UTC
OSP13 support officially ended on 27 June 2023


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