← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1453779] [NEW] Performing rescue operation on a volume backed instance fails.

 

Public bug reported:

When performing rescue operation on an instance booted from volume it gives error "Cannot rescue a volume-backed instance", "code": 400". 
Steps to reproduce
1. Boot a VM from volume
curl -g -i -X POST https://10.0.0.5:8774/v2/ee61323896a34bea9c9a5623fbb6f239/os-volumes_boot  -H "X-Auth-Token: <omitted>" -d '{"server": {"name": "TestVm", "imageRef": "", "block_device_mapping_v2": [{"boot_index": "0", "uuid": "5d246189-a666-470c-8cee-36ee489cbd9e", "volume_size": "6", "source_type": "image", "destination_type": "volume", "delete_on_termination": "1"}], "flavorRef": "da9ba7b5-be67-4a62-bb35-a362e05ba2f2", "max_count": 1, "min_count": 1, "networks": [{"uuid": "b5220eb2-e105-4ae0-8fc7-75a7cd468a40"}]}}'

{"server": {"security_groups": [{"name": "default"}], "OS-
DCF:diskConfig": "MANUAL", "id": "e436453d-5164-4f36-a7b0-617b63718759",
"links": [{"href":
"http://127.0.0.1:18774/v2/ee61323896a34bea9c9a5623fbb6f239/servers/e436453d-5164-4f36-a7b0-617b63718759";,
"rel": "self"}, {"href":
"http://127.0.0.1:18774/ee61323896a34bea9c9a5623fbb6f239/servers/e436453d-5164-4f36-a7b0-617b63718759";,
"rel": "bookmark"}], "adminPass": "6zGefA3nzNiv"}}


2. Run rescue operation on this instance.
curl -i 'https://10.0.0.5:8774/v2/ee61323896a34bea9c9a5623fbb6f239/servers/e436453d-5164-4f36-a7b0-617b63718759/action' -X POST -H 'X-Auth-Token: <omitted>'  -d '{"rescue": {"adminPass": "p8uQwFZ8qQan"}}'
HTTP/1.1 400 Bad Request
Date: Mon, 11 May 2015 05:20:57 GMT
Server: Apache/2.4.7 (Ubuntu)
Access-Control-Allow-Origin: *
Access-Control-Allow-Headers: Accept, Content-Type, X-Auth-Token, X-Subject-Token
Access-Control-Expose-Headers: Accept, Content-Type, X-Auth-Token, X-Subject-Token
Access-Control-Allow-Methods: GET POST OPTIONS PUT DELETE PATCH
Content-Length: 147
Content-Type: application/json; charset=UTF-8
X-Compute-Request-Id: req-6d671d9d-475c-41a3-894e-3e72676e1144
Via: 1.1 10.0.05:8774
Connection: close

{"badRequest": {"message": "Instance
e436453d-5164-4f36-a7b0-617b63718759 cannot be rescued: Cannot rescue a
volume-backed instance", "code": 400}}

The above issue is observed in Icehouse.

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  Performing rescue operation on a volume backed instance fails.

Status in OpenStack Compute (Nova):
  New

Bug description:
  When performing rescue operation on an instance booted from volume it gives error "Cannot rescue a volume-backed instance", "code": 400". 
  Steps to reproduce
  1. Boot a VM from volume
  curl -g -i -X POST https://10.0.0.5:8774/v2/ee61323896a34bea9c9a5623fbb6f239/os-volumes_boot  -H "X-Auth-Token: <omitted>" -d '{"server": {"name": "TestVm", "imageRef": "", "block_device_mapping_v2": [{"boot_index": "0", "uuid": "5d246189-a666-470c-8cee-36ee489cbd9e", "volume_size": "6", "source_type": "image", "destination_type": "volume", "delete_on_termination": "1"}], "flavorRef": "da9ba7b5-be67-4a62-bb35-a362e05ba2f2", "max_count": 1, "min_count": 1, "networks": [{"uuid": "b5220eb2-e105-4ae0-8fc7-75a7cd468a40"}]}}'

  {"server": {"security_groups": [{"name": "default"}], "OS-
  DCF:diskConfig": "MANUAL", "id":
  "e436453d-5164-4f36-a7b0-617b63718759", "links": [{"href":
  "http://127.0.0.1:18774/v2/ee61323896a34bea9c9a5623fbb6f239/servers/e436453d-5164-4f36-a7b0-617b63718759";,
  "rel": "self"}, {"href":
  "http://127.0.0.1:18774/ee61323896a34bea9c9a5623fbb6f239/servers/e436453d-5164-4f36-a7b0-617b63718759";,
  "rel": "bookmark"}], "adminPass": "6zGefA3nzNiv"}}

  
  2. Run rescue operation on this instance.
  curl -i 'https://10.0.0.5:8774/v2/ee61323896a34bea9c9a5623fbb6f239/servers/e436453d-5164-4f36-a7b0-617b63718759/action' -X POST -H 'X-Auth-Token: <omitted>'  -d '{"rescue": {"adminPass": "p8uQwFZ8qQan"}}'
  HTTP/1.1 400 Bad Request
  Date: Mon, 11 May 2015 05:20:57 GMT
  Server: Apache/2.4.7 (Ubuntu)
  Access-Control-Allow-Origin: *
  Access-Control-Allow-Headers: Accept, Content-Type, X-Auth-Token, X-Subject-Token
  Access-Control-Expose-Headers: Accept, Content-Type, X-Auth-Token, X-Subject-Token
  Access-Control-Allow-Methods: GET POST OPTIONS PUT DELETE PATCH
  Content-Length: 147
  Content-Type: application/json; charset=UTF-8
  X-Compute-Request-Id: req-6d671d9d-475c-41a3-894e-3e72676e1144
  Via: 1.1 10.0.05:8774
  Connection: close

  {"badRequest": {"message": "Instance
  e436453d-5164-4f36-a7b0-617b63718759 cannot be rescued: Cannot rescue
  a volume-backed instance", "code": 400}}

  The above issue is observed in Icehouse.

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


Follow ups

References