ca6daf148d
When set reclaim_instance_interval > 0, and then delete an instance which booted from volume with `delete_on_termination` set as true. After reclaim_instance_interval time pass, all volumes boot instance will with state: attached and in-use, but attached instances was deleted. This bug case as admin context from `nova.compute.manager._reclaim_queued_deletes` did not have any token info, then call cinder api would be failed. So add user/project CONF with admin role at cinder group, and when determine context is_admin and without token, do authenticaion with user/project info to call cinder api. Change-Id: I3c35bba43fee81baebe8261f546c1424ce3a3383 Closes-Bug: #1733736 Closes-Bug: #1734025 Partial-Bug: #1736773
20 lines
1.0 KiB
YAML
20 lines
1.0 KiB
YAML
---
|
|
fixes:
|
|
- |
|
|
It is now possible to configure the ``[cinder]`` section of nova.conf to
|
|
allow setting admin-role credentials for scenarios where a user token is
|
|
not available to perform actions on a volume. For example, when
|
|
``reclaim_instance_interval`` is a positive integer, instances are
|
|
soft deleted until the nova-compute service periodic task removes them.
|
|
If a soft deleted instance has volumes attached, the compute service needs
|
|
to be able to detach and possibly delete the associated volumes, otherwise
|
|
they will be orphaned in the block storage service. Similarly, if
|
|
``running_deleted_instance_poll_interval`` is set and
|
|
``running_deleted_instance_action = reap``, then the compute service will
|
|
need to be able to detach and possibly delete volumes attached to
|
|
instances that are reaped. See `bug 1733736`_ and `bug 1734025`_ for more
|
|
details.
|
|
|
|
.. _bug 1733736: https://bugs.launchpad.net/nova/+bug/1733736
|
|
.. _bug 1734025: https://bugs.launchpad.net/nova/+bug/1734025
|