upgrades to pike: cinder-volumes fails to start

Bug #1691851 reported by Emilien Macchi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Alan Bishop
Revision history for this message
Gorka Eguileor (gorka) wrote :
Revision history for this message
Alan Bishop (alan-bishop) wrote :

I see cinder's db sync occurring, but looking at subnode's /var/log/messages [1] I don't see any signs of cinder-volume's upgrade tasks ever running. Also, the cinder-volume log also shows signs of the service starting just once, whereas cinder-api and cinder-scheduler both show signs of stopping, and then being started again after the upgrade.

I suspect the problem is related to cinder-volume being run under pacemaker, but I don't understand the details of how pacemaker upgrades are supposed to work.

[1] http://logs.openstack.org/67/462667/3/check/gate-tripleo-ci-centos-7-multinode-upgrades-nv/51759ea/logs/subnode-2/var/log/messages

Changed in tripleo:
assignee: nobody → Alan Bishop (alan-bishop)
Changed in tripleo:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-heat-templates (master)

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

commit c4e3bbe039135f32f0e198365e704b3dbfd00290
Author: Alan Bishop <email address hidden>
Date: Tue May 23 10:42:24 2017 -0400

    Handle upgrading cinder-volume under pacemaker

    Add upgrade tasks for cinder-volume when it's controlled by pacemaker:

    o Stop the service before the entire pacemaker cluster is stopped.
      This ensures the service is stopped before infrastructure services
      (e.g. rabbitmq) go away.
    o Migrate the cinder DB prior to restarting the service. This covers
      the situation when puppet-cinder (who otherwise would handle the db
      sync) isn't managing the service.
    o Start the service after the rest of the pacemaker cluster has been
      started.

    Closes-Bug: #1691851
    Change-Id: I5874ab862964fadb68320d5c4de39b20f53dc25c

Changed in tripleo:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-heat-templates (stable/ocata)

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/470354

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-heat-templates (stable/ocata)

Reviewed: https://review.openstack.org/470354
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=862585bbbcf5a8b9bd171ada44cda90d3600f2d5
Submitter: Jenkins
Branch: stable/ocata

commit 862585bbbcf5a8b9bd171ada44cda90d3600f2d5
Author: Alan Bishop <email address hidden>
Date: Tue May 23 10:42:24 2017 -0400

    Handle upgrading cinder-volume under pacemaker

    Add upgrade tasks for cinder-volume when it's controlled by pacemaker:

    o Stop the service before the entire pacemaker cluster is stopped.
      This ensures the service is stopped before infrastructure services
      (e.g. rabbitmq) go away.
    o Migrate the cinder DB prior to restarting the service. This covers
      the situation when puppet-cinder (who otherwise would handle the db
      sync) isn't managing the service.
    o Start the service after the rest of the pacemaker cluster has been
      started.

    Closes-Bug: #1691851
    Change-Id: I5874ab862964fadb68320d5c4de39b20f53dc25c
    (cherry picked from commit c4e3bbe039135f32f0e198365e704b3dbfd00290)

tags: added: in-stable-ocata
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 7.0.0.0b2

This issue was fixed in the openstack/tripleo-heat-templates 7.0.0.0b2 development milestone.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-heat-templates 6.2.0

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.