← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1971408] Re: server cannot reboot after multi-attach volume retyping

 

[Expired for OpenStack Compute (nova) because there has been no activity
for 60 days.]

** Changed in: nova
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1971408

Title:
  server cannot reboot after multi-attach volume retyping

Status in OpenStack Compute (nova):
  Expired

Bug description:
  Description
  ===========
  The server will fail to hard reboot after an retype operation
  is performed on the multi-attach volume of it.
  With multiattach the nova will call to volume api to get volume
  according to connection_info in block device mappings of nova.
  However, the volume id may become name_id after retyping
  operation and server will fail to hard reboot since volume
  cannot be find.

  Expected result
  ===============
  The server will succedd in hard reboot after an retype operation
  is performed on the multi-attach volume of it.

  The server will fail to hard reboot after an retype operation
  is performed on the multi-attach volume of it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1971408/+subscriptions



References