[Bug 1665272] Fix merged to charm-cinder (master)
1665272 at bugs.launchpad.net
Tue Feb 21 10:54:42 UTC 2017
Author: Liam Young <liam.young at canonical.com>
Date: Thu Feb 16 12:13:03 2017 +0000
Move backends into their own sections
Using DEFAULT section to configure drivers is not supported since
Ocata. This change lists backends in enabled_backends.
Note: Using sectional config causes the os-vol-host-attr:host
volume attribute to change which invalidates existing volumes.
A subsequant change is needed to add an action for renaming
the host attribute of existing volumes *1
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to cinder in Juju Charms Collection.
Matching subscriptions: charm-bugs
cinder-volume fails to start in Ocata when no backend is connected
Status in cinder package in Juju Charms Collection:
When deploying the cinder charm using Ocata and no backend charm
connected, the cinder-volume service fails to start. Error from
Configuration for cinder-volume does not specify "enabled_backends". Using DEFAULT section to configure drivers is not supported since Ocata.
No volume service(s) started successfully, terminating.
The charm eventually reports the dead services via juju status:
Services not running that should be: cinder-volume
The easiest way to see this is to run the amulet test tests/gate-
basic-xenial-ocata. It fails with
2017-02-16 09:17:07,356 create_cinder_volume DEBUG: Creating cinder volume...
2017-02-16 09:17:14,114 resource_reaches_status DEBUG: Volume status wait status check: 0 [creating:available] 0974c72f-e88d-40c2-a00a-effa49abee9f
2017-02-16 09:17:18,304 resource_reaches_status DEBUG: Volume status wait status check: 1 [error:available] 0974c72f-e88d-40c2-a00a-effa49abee9f
2017-02-16 09:19:19,590 resource_reaches_status DEBUG: Volume status wait: expected, actual status = error, available
2017-02-16 09:19:19,590 resource_reaches_status DEBUG: 0974c72f-e88d-40c2-a00a-effa49abee9f never reached expected status: available
To manage notifications about this bug go to:
More information about the Ubuntu-openstack-bugs