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.
Reviewed: https:/ /review. openstack. org/522112 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=ca6daf148de bb9c9646fcf6db9 660c830da5a594
Committed: https:/
Submitter: Zuul
Branch: master
commit ca6daf148debb9c 9646fcf6db9660c 830da5a594
Author: lixipeng <email address hidden>
Date: Wed Nov 22 12:03:58 2017 +0800
Fix bug case by none token context
When set reclaim_ instance_ interval > 0, and then delete an on_termination` instance_ interval time pass,
instance which booted from volume with `delete_
set as true. After reclaim_
all volumes boot instance will with state: attached and in-use,
but attached instances was deleted.
This bug case as admin context from compute. manager. _reclaim_ queued_ deletes` did not have
`nova.
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: I3c35bba43fee81 baebe8261f546c1 424ce3a3383
Closes-Bug: #1733736
Closes-Bug: #1734025
Partial-Bug: #1736773