cinder-volume fails to start with enabled_backends = cinder-ceph
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ceph Monitor Charm |
Fix Released
|
High
|
Frode Nordahl | ||
Ceph OSD Charm |
Fix Released
|
High
|
Frode Nordahl | ||
Ceph RADOS Gateway Charm |
Fix Released
|
High
|
Frode Nordahl | ||
OpenStack Ceph Charm (Retired) |
Fix Released
|
High
|
Frode Nordahl | ||
OpenStack Cinder Charm |
Fix Released
|
High
|
Liam Young |
Bug Description
maas version: 2.3.0~alpha3-
juju version: 2.2.4
openstack: cs:bundle/
My cinder unit is ending up blocked with message "Services not running that should be: cinder-volume".
In cinder-volume.log, this error repeats:
2017-09-22 05:24:29.242 49385 ERROR cinder.cmd.volume [-] Configuration for cinder-volume does not specify "enabled_backends". Using DEFAULT section to configure drivers is not supported since Ocata.
2017-09-22 05:24:29.242 49385 ERROR cinder.cmd.volume [-] No volume service(s) started successfully, terminating.
cinder.conf has "enabled_backends = cinder-ceph" in the DEFAULT section.
I've attached a crashdump of the deployment.
affects: | cinder (Juju Charms Collection) → charm-cinder |
Changed in charm-cinder: | |
assignee: | nobody → Liam Young (gnuoy) |
status: | New → In Progress |
Changed in charm-cinder: | |
importance: | Undecided → High |
Changed in charm-ceph-radosgw: | |
status: | New → In Progress |
Changed in charm-ceph-osd: | |
status: | New → In Progress |
Changed in charm-ceph-mon: | |
status: | New → In Progress |
Changed in charm-ceph: | |
status: | New → In Progress |
Changed in charm-ceph-radosgw: | |
assignee: | nobody → Frode Nordahl (fnordahl) |
Changed in charm-ceph-osd: | |
assignee: | nobody → Frode Nordahl (fnordahl) |
Changed in charm-ceph-mon: | |
assignee: | nobody → Frode Nordahl (fnordahl) |
Changed in charm-ceph: | |
assignee: | nobody → Frode Nordahl (fnordahl) |
Changed in charm-ceph: | |
status: | In Progress → Fix Committed |
Changed in charm-ceph-mon: | |
status: | In Progress → Fix Committed |
Changed in charm-ceph-osd: | |
status: | In Progress → Fix Committed |
Changed in charm-ceph-radosgw: | |
status: | In Progress → Fix Committed |
Changed in charm-ceph-radosgw: | |
importance: | Undecided → High |
Changed in charm-ceph-osd: | |
importance: | Undecided → High |
Changed in charm-ceph-mon: | |
importance: | Undecided → High |
Changed in charm-ceph: | |
importance: | Undecided → High |
Changed in charm-ceph: | |
milestone: | none → 17.11 |
Changed in charm-ceph-mon: | |
milestone: | none → 17.11 |
Changed in charm-ceph-osd: | |
milestone: | none → 17.11 |
Changed in charm-ceph-radosgw: | |
milestone: | none → 17.11 |
Changed in charm-cinder: | |
milestone: | none → 17.11 |
Changed in charm-cinder: | |
status: | Fix Committed → Fix Released |
Changed in charm-ceph-osd: | |
status: | Fix Committed → Fix Released |
Changed in charm-ceph-mon: | |
status: | Fix Committed → Fix Released |
Changed in charm-ceph: | |
status: | Fix Committed → Fix Released |
Changed in charm-ceph-radosgw: | |
status: | Fix Committed → Fix Released |
I haven't been able to reproduce this so far. How often are you seeing the bug ?
The only thing that look suspicious too me so far is that both cinder and cinder-ceph manage the cinder-volume service. Normally charms avoid this by sending a restart trigger down the relation so one charm can, in effect, request a service restart on another charm.
I think the error message from the cinder-volume.log is probably a red herring. This error is normal while the services are coming up. Once cinder-ceph has sent its relation data to cinder the config file is re-rendered with the correct backend set. The crash dump Jason provided shows the correctly rendered config.
It looks like cinder-volume is not being restarted after the cinder.conf is updated with the data from cinder-ceph but I can't see any code path that would lead to that behaviour.