yahoo-eng-team team mailing list archive

[John Garbutt <john@xxxxxxxxxxxxxxx>]

The owner of the instance should not be able to reset state, that is
totally as intended.

A policy issue will never make an instance go to error, I think you are
hitting a different issue here. Please double check the logs, I suspect
if you are using KVM, you are missing the qemu agent from your image, or
similar.

** Changed in: nova
       Status: In Progress => 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/1525196

Title:
  change default policy for password and resetstate

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  all cases from devstack, git head commit
  4474dce9e6b847a7691fc3f01d0c594061570d73

  I created an instance with admin tenant then use set-password with demo user, it make the instance ERROR
  this kind of operations should not disabled by default

  jichen@devstack1:~$ export OS_USERNAME=demo
  jichen@devstack1:~$ nova set-password t5
  New password:
  Again:
  ERROR (Conflict): Failed to set admin password on d3485187-779c-441f-8394-4e3d31234a9f because error setting admin password (HTTP 409) (Request-ID: req-96b69164-e353-44f8-82a1-ecd20200173b)
  jichen@devstack1:~$ nova list
  +--------------------------------------+------+--------+------------+-------------+-------------------+
  | ID                                   | Name | Status | Task State | Power State | Networks          |
  +--------------------------------------+------+--------+------------+-------------+-------------------+
  | d3485187-779c-441f-8394-4e3d31234a9f | t5   | ERROR  | -          | Running     | private=10.0.0.10 |
  +--------------------------------------+------+--------+------------+-------------+-------------------+

  
  Also, after the instance become ERROR state, I can't change it to ACTIVE state even if I am the owner of the instance

  jichen@devstack1:~$ nova list
  +--------------------------------------+--------+---------+------------+-------------+------------------+
  | ID                                   | Name   | Status  | Task State | Power State | Networks         |
  +--------------------------------------+--------+---------+------------+-------------+------------------+
  | 380e55e3-9726-4928-a44c-a206bc656f48 | t2     | ERROR   | -          | Running     | private=10.0.0.8 |
  | c426c3d0-a981-4839-969a-50d828e05459 | t4  é | SHUTOFF | -          | Shutdown    | private=10.0.0.2 ||
  +--------------------------------------+--------+---------+------------+-------------+------------------+
  jichen@devstack1:~$ nova reset-state --active t2
  Reset state for server t2 failed: Policy doesn't allow os_compute_api:os-admin-actions:reset_state to be performed. (HTTP 403) (Request-ID: req-e7669a3c-3075-4a63-a7a6-f646013a5428)
  ERROR (CommandError): Unable to reset the state for the specified server(s)

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