Also, on the backup step a status of `mco ping` is serialized in an
upgrade tarball and on the restore step it is compared with the actual
status. All nodes that are not respond are logged.
In additional, the status of `mco ping` is archived on the backup step
and is compared on the restore step with the actual ones.
Reviewed: https:/ /review. openstack. org/358858 /git.openstack. org/cgit/ openstack/ fuel-octane/ commit/ ?id=f91ff40264c 257a8d3eb436ab5 e7c4c8272b27ce
Committed: https:/
Submitter: Jenkins
Branch: master
commit f91ff40264c257a 8d3eb436ab5e7c4 c8272b27ce
Author: Ilya Kharin <email address hidden>
Date: Mon Aug 22 23:17:00 2016 +0300
Restart mcollective on slave nodes after restore
Also, on the backup step a status of `mco ping` is serialized in an
upgrade tarball and on the restore step it is compared with the actual
status. All nodes that are not respond are logged.
In additional, the status of `mco ping` is archived on the backup step
and is compared on the restore step with the actual ones.
Change-Id: Ibba81102214998 d83614a42cdb21c 21bebd8284a
Related-Bug: #1561092