Cinder volume service is not managed by Pacemaker on BlockStorage

[Raoul Scarazzini]

Last TripleO deployments failed at this step:

2016-09-29 00:42:57Z [AllNodesDeploySteps]: CREATE_FAILED Error: resources.AllNodesDeploySteps.resources.BlockStorageDeployment_Step5.resources[0]: Deployment to server failed: deploy_status_code: Deployment exited with non-zero status code: 1

And specifically with this message:

exception: connect failed Error: Could not find dependency Exec[wait-for-settle] for Pacemaker::Resource::Systemd[openstack-cinder-volume]

Making some verifications the broke element is openstack-cinder-volume, and specifically its inclusion in overcloud_volume.pp. The faulty code/assumption seems to be ./roles_data.yaml:

- name: BlockStorage
  ServicesDefault:
    - OS::TripleO::Services::CACerts
    - OS::TripleO::Services::CinderVolume
    - OS::TripleO::Services::Kernel
    - OS::TripleO::Services::Ntp
    - OS::TripleO::Services::Timezone
    - OS::TripleO::Services::Snmp
    - OS::TripleO::Services::TripleoPackages
    - OS::TripleO::Services::TripleoFirewall
    - OS::TripleO::Services::SensuClient
    - OS::TripleO::Services::FluentdClient
    - OS::TripleO::Services::VipHosts

By default we have in environments/puppet-pacemaker.yaml

  OS::TripleO::Services::CinderVolume: ../puppet/services/pacemaker/cinder-volume.yaml

So the above BlockStorage won't work with pacemaker

[Michele Baldessari (michele)]

Not sure why LP is not picking this up, but Giulio's fix is tracked here: https://review.openstack.org/379410

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/379410
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=7822c9756a80f0d49a25c668e70628fa051fbdf9
Submitter: Jenkins
Branch: master

commit 7822c9756a80f0d49a25c668e70628fa051fbdf9
Author: Giulio Fidente <email address hidden>
Date: Thu Sep 29 14:05:46 2016 +0200

    Cinder volume service is not managed by Pacemaker on BlockStorage

    We do not want cinder-volume to be managed by Pacemaker on
    BlockStorage nodes, where Pacemaker is not running at all.

    This change adds a new BlockStorageCinderVolume service name
    which can (and is, by default) mapped to the non Pacemaker
    implementation of the service.

    The error was:
    Could not find dependency Exec[wait-for-settle] for
    Pacemaker::Resource::Systemd[openstack-cinder-volume]

    Also moves cinder::host setting into the Pacemaker specific service
    definition because we only want to set a shared host= string when
    the service is managed by Pacemaker.

    Closes-Bug: #1628912
    Change-Id: I2f7e82db4fdfd5f161e44d65d17893c3e19a89c9

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/381240

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/381240
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=582bb8af050bde8b86947f03ab7ebed935d0b22f
Submitter: Jenkins
Branch: stable/newton

commit 582bb8af050bde8b86947f03ab7ebed935d0b22f
Author: Giulio Fidente <email address hidden>
Date: Thu Sep 29 14:05:46 2016 +0200

    Cinder volume service is not managed by Pacemaker on BlockStorage

    We do not want cinder-volume to be managed by Pacemaker on
    BlockStorage nodes, where Pacemaker is not running at all.

    This change adds a new BlockStorageCinderVolume service name
    which can (and is, by default) mapped to the non Pacemaker
    implementation of the service.

    The error was:
    Could not find dependency Exec[wait-for-settle] for
    Pacemaker::Resource::Systemd[openstack-cinder-volume]

    Also moves cinder::host setting into the Pacemaker specific service
    definition because we only want to set a shared host= string when
    the service is managed by Pacemaker.

    Closes-Bug: #1628912
    Change-Id: I2f7e82db4fdfd5f161e44d65d17893c3e19a89c9
    (cherry picked from commit 7822c9756a80f0d49a25c668e70628fa051fbdf9)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 5.0.0.0rc3 release candidate.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 5.0.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 6.0.0.0b1 development milestone.