Charmed Openstack does not support service user tokens

Bug #2008122 reported by Michael Quiniola
This bug report is a duplicate of:  Bug #1992840: Configure service tokens by default. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Nova Cloud Controller Charm
New
Undecided
Unassigned

Bug Description

During live migrations that are long-running the user token can expire causing the migration to fail. The exposure (or added in to the config file by default) of an option to enable service user tokens will allow the migrations to finish past the expiration of the user token. As seen here:

https://docs.openstack.org/nova/zed/admin/support-compute.html#user-token-times-out-during-long-running-operations

What would need to be done:
- Have charm create nova service user (as a superset of keystone_authtoken.service_token_roles)
- nova.conf template adjusted to above referenced link\

We have been seeing a lot of these issues in support and the go to solution as been to increase the token timeout.

Revision history for this message
Felipe Reyes (freyes) wrote :

Hi Michael, thanks for filing this bug. At the moment there is work in progress to support service tokens, progress can be tracked in the bug 1992840

I will mark this one as duplicated, please feel comment in the other bug any feedback you may have on the subject.

Best

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.