Comment 8 for bug 1695904

Fresh results available at http://logs.openstack.org/76/461076/2/check/gate-tripleo-ci-centos-7-scenario002-multinode-upgrades/cc1f341/ confirm Sofer's observation.

It looks like puppet-cinder is requesting a restart after the config changes (as a result of the upgrade), but the pacemaker stuff responsble for monitoring the resource_restart_flag is no longer present. And that's because the ControllerPostPuppetRestart heat resource was deleted during the update/upgrade.

Jun 08 18:57:09 - Upgrade initiated [0]
Jun 08 19:06:19 - ControllerPostPuppetRestart resource was deleted [1]
Jun 08 19:19:35 - cinder-volume restarted [2]
Jun 08 19:34:14 - "openstack-cinder-volume resource restart flag" issued [3]
Jun 08 19:37:59 - "openstack-cinder-volume resource restart flag" issued [4]
Jun 08 19:43:20 - Upgrade complete [5]

[0] http://logs.openstack.org/76/461076/2/check/gate-tripleo-ci-centos-7-scenario002-multinode-upgrades/cc1f341/console.html#_2017-06-08_18_57_09_104134
[1] http://logs.openstack.org/76/461076/2/check/gate-tripleo-ci-centos-7-scenario002-multinode-upgrades/cc1f341/console.html#_2017-06-08_19_06_19_963287
[2] http://logs.openstack.org/76/461076/2/check/gate-tripleo-ci-centos-7-scenario002-multinode-upgrades/cc1f341/logs/subnode-2/var/log/journal-text.txt.gz#_Jun_08_19_19_35_211321
[3] http://logs.openstack.org/76/461076/2/check/gate-tripleo-ci-centos-7-scenario002-multinode-upgrades/cc1f341/logs/subnode-2/var/log/journal-text.txt.gz#_Jun_08_19_34_14_205820
[4] http://logs.openstack.org/76/461076/2/check/gate-tripleo-ci-centos-7-scenario002-multinode-upgrades/cc1f341/logs/subnode-2/var/log/journal-text.txt.gz#_Jun_08_19_37_59_218360
[5] http://logs.openstack.org/76/461076/2/check/gate-tripleo-ci-centos-7-scenario002-multinode-upgrades/cc1f341/console.html#_2017-06-08_19_43_20_692680