yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1358155] Re: Using CLI I am able to stop server when it is locked

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Ghanshyam Mann <ghanshyam.mann@xxxxxxxxxxxxxxxxxx>
Date: Thu, 28 Aug 2014 02:06:56 -0000
Reply-to: Bug 1358155 <1358155@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

What was the Role? was it Admin.

I think you have performed this operation with Admin role (Please confirm). Server can be stopped only from two state ACTIVE or ERROR. If server is locked then only Admin can stop the server. Non admin user will get the conflict error if they try the same.
Tempest tests (api/compute/servers/test_server_actions.py:test_lock_unlock_server) confirm the same and validate this behavior. 

It nothing to do with Tempest, if there is any issue then it should be
Nova.

** Project changed: tempest => nova

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

Title:
  Using CLI I am able to stop server when it is locked

Status in OpenStack Compute (Nova):
  New

Bug description:
  I am using devstack + tempest -

  Operations are as -

  1.

  [raies@localhost devstack]$ nova list
  +--------------------------------------+-------------+--------+------------+-------------+-------------------+
  | ID                                   | Name        | Status | Task State | Power State | Networks          |
  +--------------------------------------+-------------+--------+------------+-------------+-------------------+
  | d44993fc-c81f-4e4c-9adf-09019859cb31 | test-server | ACTIVE | -          | Running     | public=172.24.4.7 |
  +--------------------------------------+-------------+--------+------------+-------------+-------------------+

  2.

  [raies@localhost devstack]$ nova lock d44993fc-c81f-4e4c-9adf-
  09019859cb31

  3.

  [raies@localhost devstack]$ nova stop d44993fc-c81f-4e4c-9adf-
  09019859cb31

  
  All the above commands are successful.

  But third command should raise exception (conflict) but all command
  are successful.

  
  Above can be confirmed from the API testing in tempest - 

  tempest/tempest/api/compute/servers/test_server_actions.py  ------>
  test_lock_unlock_server

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