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: Thang Pham <thang.g.pham@xxxxxxxxx>
Date: Thu, 28 Aug 2014 03:17:47 -0000
Reply-to: Bug 1358155 <1358155@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

I cannot reproduce this bug based on the steps you listed above.  I get
the following error, which is correct:

$ nova stop test1
ERROR (Conflict): Instance f7961e90-29c8-4e5d-8e8e-34ad7e46b834 is locked (HTTP 409) (Request-ID: req-5193f0fb-3cd5-4603-80ea-74585caae612)

However, if I attempt to use the admin user to stop the instance, it
works, which is what I excepted.


** Changed in: nova
       Status: New => Invalid

-- 
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):
  Invalid

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