Incorrect start order of Cinder services in Mitaka

[Gorka Eguileor]

In Mitaka's Cinder Upgrade Notes [1] it is mentioned that the cinder-backup service should be the last to be upgraded and restarted:

"As cinder-backup was strongly reworked in this release, the recommended upgrade order when executing live (rolling) upgrade is c-api->c-sch->c-vol->c-bak."

But devstack starts Cinder Backup service before Cinder Volume, which can lead to problems during grenade jobs [2] where we see this error:

"ServiceTooOld: One of cinder-volume services is too old to accept such request. Are you running mixed Liberty-Mitaka cinder-volumes?"

[1]: http://docs.openstack.org/releasenotes/cinder/mitaka.html#id6
[2]: http://logs.openstack.org/58/350758/1/check/gate-grenade-dsvm-designate-powerdns/90b0f2d/logs/new/screen-c-bak.txt.gz?level=ERROR

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/355042

[OpenStack Infra (hudson-openstack)]

Change abandoned by Sean Dague (<email address hidden>) on branch: stable/mitaka
Review: https://review.openstack.org/355042
Reason: no update in 7 months

[Sean Dague (sdague)]

No open reviews found in this bug, unassigning. Please add a comment with active reviews before assigning an individual, or tag the bug in the gerrit review, which will do that automatically. We try not to assign bugs without patches as that discourages other folks from looking into bugs.

[Sean Dague (sdague)]

Automatically discovered version mitaka in description. If this is incorrect, please update the description to include 'devstack version: ...'

[Sean Dague (sdague)]

Devstack has upgraded all services before any are started, so this seems like invalid discovery logic on the cinder side.