diff options
| author |   Michele Baldessari <michele@acksyn.org> | 2016-09-28 09:41:30 +0200 |
|---|---|---|
| committer | Michele Baldessari <michele@acksyn.org> | 2016-09-28 12:28:39 +0200 |
| commit | 35da6af8bd1629ea823aecdd0e15b73fcbccf7b0 (patch) | |
| tree | 0df805377b8d182f5b8f4da7826918140ebb2f13 /network/management_v6.yaml | |
| parent | 7c39f66d1c7a68d46e9cc116e8985b9d1650afb9 (diff) | |
Full HA->HA NG migration might fail setting maintenance-mode
Currently we do the following in the migration path:
pcs property set maintenance-mode=true
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.
The property will be set atomically across the cluster nodes so we should be good
without this.
Change-Id: I8f531d63479b81d65b572c4431c9db6f610f7e04
Closes-Bug: #1628393
Diffstat (limited to 'network/management_v6.yaml')
0 files changed, 0 insertions, 0 deletions