commit 6de87343ddf5a939695c1178f9946d2d08c3e876
Author: Vladimir Sharshov <email address hidden>
Date: Thu May 8 07:44:30 2014 +0400
Set max avaliable TTL for Mcollective
We use virtual machine snapshots for CI. When we
up it from snapshots, we get error:
"MCollective agents '<ID>' didn't respond within
the allotted time.", but node is online. Big TTL
in Mcollective should solve this problem.
Reviewed: https:/ /review. openstack. org/96852 /git.openstack. org/cgit/ stackforge/ fuel-library/ commit/ ?id=6de87343ddf 5a939695c1178f9 946d2d08c3e876
Committed: https:/
Submitter: Jenkins
Branch: stable/4.1
commit 6de87343ddf5a93 9695c1178f9946d 2d08c3e876
Author: Vladimir Sharshov <email address hidden>
Date: Thu May 8 07:44:30 2014 +0400
Set max avaliable TTL for Mcollective
We use virtual machine snapshots for CI. When we
up it from snapshots, we get error:
"MCollective agents '<ID>' didn't respond within
the allotted time.", but node is online. Big TTL
in Mcollective should solve this problem.
Change-Id: Id3f2f5ddf26a9d 31de214e9d5596a 47f450b983f
Closes-Bug: #1316720