M/N upgrades - Full HA -> HA NG migration might fail setting maintenance-mode
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Critical
|
Michele Baldessari |
Bug Description
[root@overcloud
{
"deploy_stdout": "mysql upgrade required: 0\nERROR: cluster remained unstable after setting maintenance-mode for more than 300 seconds, exiting.\n",
"deploy_stderr": "",
"deploy_
}
This is because we do the following:
pcs property set maintenance-
# We are making sure here that the property has propagated everywhere
if ! timeout -k 10 300 crm_resource --wait; then
echo_error "ERROR: cluster remained unstable after setting maintenance-mode for more than 300 seconds, exiting."
exit 1
fi
crm_resource --wait can actually take forever under certain conditions. Since we are going to shut
down the cluster later anyways, there is no point in using crm_resource --wait at this stage.
Fix proposed to branch: master /review. openstack. org/378317
Review: https:/