summaryrefslogtreecommitdiffstats
path: root/network
diff options
context:
space:
mode:
authorMichele Baldessari <michele@acksyn.org>2016-09-25 11:52:04 +0200
committerMichele Baldessari <michele@acksyn.org>2016-09-25 11:52:04 +0200
commitb70d6e6f34ea0d379b9a787da9f6f8909c179dc8 (patch)
tree49e36dc73889d7a42c335ef323161eab0b711df7 /network
parent5d49b75b6e8c608ede6fc7bd63b06055ce5f6317 (diff)
Disable openstack-cinder-volume in step1 and reenable it in step2
Currently we do not disable openstack-cinder-volume during our major-upgrade-pacemaker step. This leads to the following scenario. In major_upgrade_controller_pacemaker_2.sh we do: start_or_enable_service galera check_resource galera started 600 .... if [[ -n $(is_bootstrap_node) ]]; then ... cinder-manage db sync ... What happens here is that since openstack-cinder-volume was never disabled it will already be started by pacemaker before we call cinder-manage and this will give us the following errors during the start: 06:05:21.861 19482 ERROR cinder.cmd.volume DBError: (pymysql.err.InternalError) (1054, u"Unknown column 'services.cluster_name' in 'field list'") Change-Id: I01b2daf956c30b9a4985ea62cbf4c941ec66dcdf Closes-Bug: #1627470
Diffstat (limited to 'network')
0 files changed, 0 insertions, 0 deletions