commit 32f25307a69c69b002f3f7a220fa6bae2d4d110d
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/92766 /git.openstack. org/cgit/ stackforge/ fuel-library/ commit/ ?id=32f25307a69 c69b002f3f7a220 fa6bae2d4d110d
Committed: https:/
Submitter: Jenkins
Branch: master
commit 32f25307a69c69b 002f3f7a220fa6b ae2d4d110d
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