[Bug 1665272] Re: cinder-volume fails to start in Ocata when no backend is connected

[OpenStack Infra]

** Changed in: cinder (Juju Charms Collection)
       Status: Confirmed => In Progress

-- 
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
https://bugs.launchpad.net/bugs/1665272

Title:
  cinder-volume fails to start in Ocata when no backend is connected

Status in cinder package in Juju Charms Collection:
  In Progress

Bug description:
  When deploying the cinder charm using Ocata and no backend charm
  connected, the cinder-volume service fails to start. Error from
  cinder-volume.log:

  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:
https://bugs.launchpad.net/charms/+source/cinder/+bug/1665272/+subscriptions