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/375382 /git.openstack. org/cgit/ openstack/ fuel-octane/ commit/ ?id=298428cc40e fa5be6b6cb5c8c0 6d063f50028af7
Committed: https:/
Submitter: Jenkins
Branch: stable/mitaka
commit 298428cc40efa5b e6b6cb5c8c06d06 3f50028af7
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