[Bug 1665272] Fix merged to charm-cinder (master)
1665272 at bugs.launchpad.net
Thu Feb 23 16:53:42 UTC 2017
Author: Liam Young <liam.young at canonical.com>
Date: Wed Feb 22 09:48:08 2017 +0000
Add actions for renaming volume host attr
Add two new actions which are essentially wrappers around
cinder-manage volume update_host \
--currenthost CURRENTHOST \
In previous versions of the charm if block-device is set or the
legacy ceph relation is used (as opposed to storage-backend relation)
then the configuration of those backends is done in the [DEFAULT]
section of the cinder.conf. As of Ocata that is no longer supported
and backends need to be listed in their own sections and referenced
via enable_backends parameter. This change in config results in a
change of host name and existing volumes need to have their metadata
updated to point at the new hostname.
Old Hostname: <unit-name>
New Hostname: <unit-name>@<backend section name>#<volume-backend-name>
New Action: volume-backend-name
Used for updating the host attribute of volumes to add the driver
name. This is needed after an upgrade to Ocata if there are existing
volumes which have been configured prior to multi-backends
New Action: rename-volume-host
Used for updating the host attribute of volumes. This action is
a lower level action then volume-host-add-driver and simply passes
the old and new hosts verbatim to cinder-manage.
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