Attached volumes fail to migrate

[Torin Woltjer]

If a volume is not attached, migration works as suspected. However, an attached volume will fail.

[Sean McGinnis (sean-mcginnis)]

Check that you have the [nova] section in cinder.conf set right? From the log it appears this fails since we are unable to figure out where nova is, which is required in order to move a volume that is attached.

[Torin Woltjer (woltjert)]

The configuration file did not come with a [nova] section and I cant find a [nova] in any of the reference configuration files. Can you link to documentation on this section or provide an example configuration file that includes it?

[Sean McGinnis (sean-mcginnis)]

I'm still looking for documentation describing it, but you can search for the [nova] section in the sample config to find the available options:

https://docs.openstack.org/cinder/latest/sample_config.html

[Torin Woltjer (woltjert)]

Thank for providing that for me. I'll take a look at what I can accomplish with that. I look forward to seeing that extra documentation, if you can find it.

[Torin Woltjer (woltjert)]

I don't know if this is in the direction of a solution but, adding the [nova] section with interface = admin changes the error to what is in the attached log. Commenting out the following lines in my cinder.conf returns the old error during migration.

nova_endpoint_admin_template = http://UBNTU-OSTACK-CONTROL2:8774/v2.1/%(tenant_id)s
nova_endpoint_template = http://UBNTU-OSTACK-CONTROL2:8774/v2.1/%(tenant_id)s