← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1449811] [NEW] nova lock/unlock api return code is not accurate

 

Public bug reported:

Currently, lock server api only returns 202(accepted) and 404(not found).    
The api return code is not accurate.                                           
                                                                               
The lock/unlock api in compute-api is a sync function, so the return code      
of nova-api should be:                                                         
                                                                               
* 200 : successfully lock/unlock an instance                                   
* 404 : instance not found                                                    
* 409 : locking/unlocking a locked/unlocked instance

** Affects: nova
     Importance: Undecided
     Assignee: Eli Qiao (taget-9)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => Eli Qiao (taget-9)

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

Title:
  nova lock/unlock api return code is not accurate

Status in OpenStack Compute (Nova):
  New

Bug description:
  Currently, lock server api only returns 202(accepted) and 404(not found).    
  The api return code is not accurate.                                           
                                                                                 
  The lock/unlock api in compute-api is a sync function, so the return code      
  of nova-api should be:                                                         
                                                                                 
  * 200 : successfully lock/unlock an instance                                   
  * 404 : instance not found                                                    
  * 409 : locking/unlocking a locked/unlocked instance

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


Follow ups

References