"The use case is to remove the root volume of an instance while this
being powered off. A different volume will then be attached. This keeps
the whole configuration (especially MAC addresses of network ports)
while changing the software."

This isn't a use case we are trying to support, this goes against the
'cloud' model etc.

** Changed in: nova
       Status: New => Won't Fix

-- 
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/1391196

Title:
  Cannot detach root volume from instance (to attach a different volume)

Status in OpenStack Compute (Nova):
  Won't Fix

Bug description:
  In objection of https://review.openstack.org/#/c/75552/ I have use
  cases to be able to detach the (none-ephemeral) root volume from an
  instance/ a server to be able to attach a different volume.

  Using the following (undocumented?) request to replace the volume
  attachment isn't successful either:

   curl -i 
'http://10.47.52.20:8774/v2/35c70d4fc1414f708a547a9a6ee179ad/servers/6ae98f88-e706-44de-91f3-8756f9ba7ef6/os-volume_attachments/f5e5e5f6-61ce-4601-a7c5-c09cf2392425'
 -X PUT -H "X-Auth-Project-Id: Demo" -H "User-Agent: python-novaclient" -H 
"Content-Type: application/json" -H "Accept: application/json" -H 
"X-Auth-Token: xxx" -d '{"volumeAttachment": {"volumeId": 
"401c6474-5d41-4bb7-a461-b20f64014003"}}'
  HTTP/1.1 202 Accepted
  Content-Type: text/html; charset=UTF-8
  Content-Length: 0

  in spite of the empty response not reporting any error. This request
  also doesn't work for non-boot volumes.

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to