OpenStack Nova Cloud Controller Charm

Cannot create volume-backed instances

Bug #2031694 reported by Michael Quiniola
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Nova Cloud Controller Charm
Invalid
Undecided
Unassigned

Bug Description

Focal/Ussuri

After updating the charm to a newer revision in which service tokens are enabled by default, we could no longer create volume backed instances. This also includes creating a volume from an image (which worked) and then attempting to create an instance from that volume.

The workaround was to comment out the [service_user] section in nova.conf in all nova-cloud-controller and nova-compute units. Then we could create volume backed instances.

To add to this, we can no longer attach volumes to already created instances.

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

Can you provide us the output of "juju status" and make sure you have no pending updates in the system (apt-get update; apt-get upgrade)?

Changed in charm-nova-cloud-controller:
status: New → Incomplete
Revision history for this message
Felipe Reyes (freyes) wrote :

The other option (if you can) would be to provide us a test case so we can reproduce the issue ourselves.

Revision history for this message
Michael Quiniola (qthepirate) wrote :

This bug can be closed.

After upgrade from a non service token based environment to the newest charm version which implemented service tokens nova was looking for an expired trust.

This can be solved with:
keystone-manage trust_flush --project-id <services project in service_domain id>

Revision history for this message
Alex Kavanagh (ajkavanagh) wrote :

Thanks for the confirmation and clean-up info, Michael!

Changed in charm-nova-cloud-controller:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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