yahoo-eng-team team mailing list archive

[Mathew Odden <mrodden@xxxxxxxxxx>]

Public bug reported:

Sending a soft reboot request to the Nova API while an instance is in
the stopped state results in the following response:


Status
409 Conflict

{
conflictingRequest: {
message: "Cannot 'reboot' while instance is in vm_state stopped"
code: 409
}
-
}

Since we support a hard reboot on certain states it would be better to
indicate the type of reboot in the error message that isn't supported.
e.g. return message: "Cannot 'soft reboot' while instance is in vm_state
stopped"

** Affects: nova
     Importance: Low
     Assignee: Mathew Odden (locke105)
         Status: In Progress

** Changed in: nova
   Importance: Undecided => Low

** Changed in: nova
     Assignee: (unassigned) => Mathew Odden (locke105)

** Changed in: nova
       Status: New => In Progress

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

Title:
  API error message reports incorrect state for unavailable soft reboot

Status in OpenStack Compute (Nova):
  In Progress

Bug description:
  Sending a soft reboot request to the Nova API while an instance is in
  the stopped state results in the following response:

  
  Status
  409 Conflict

  {
  conflictingRequest: {
  message: "Cannot 'reboot' while instance is in vm_state stopped"
  code: 409
  }
  -
  }

  Since we support a hard reboot on certain states it would be better to
  indicate the type of reboot in the error message that isn't supported.
  e.g. return message: "Cannot 'soft reboot' while instance is in
  vm_state stopped"

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