We should increase time to live for messages and queues for max value in mcollective

[Tatyanka]

{"build_id": "2014-05-06_01-31-29", "mirantis": "yes", "build_number": "183", "ostf_sha": "fe718434f88f2ab167779770828a195f06eb29f8", "nailgun_sha": "c61100f34a12c597df32f7498697acd84035957f", "production": "docker", "api": "1.0", "fuelmain_sha": "185fac4a937b970fc82aa48a9c31c7981f8f7659", "astute_sha": "3cffebde1e5452f5dbf8f744c6525fc36c7afbf3", "release": "5.0", "fuellib_sha": "edaecb643f34ca73be3716c5a722bfdd40e06128"}

Steps to Reproduce:
1. Deploy one node cluster using KVM
2. Delete it
3. Deploy neutron gre cluser with 4 nodes (1controller 2 computes 1 cinder+ mongo) with murano/savanna/ceilometer

Expected
Deployment pass , cluster ready, ostf pass

Actual:
deployment of controller fail with message [7ff473ade700] (receiver) Node slave-01_controller not answered by RPC, removing from db

Info: Dima P comment: need to set ttl to max value for mcollective

[Tatyanka (tatyana-leontovich)]

we have failed tests on CI especially for ha with a very similar problem. We marked node with error status with 2014-05-06T14:56:36 err: [394] MCollective agents '1' didn't respond within the allotted time.
 and do not wait a little bit more , but than we can see in logs that node is responsible and online

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/92766

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/92766
Committed: https://git.openstack.org/cgit/stackforge/fuel-library/commit/?id=32f25307a69c69b002f3f7a220fa6bae2d4d110d
Submitter: Jenkins
Branch: master

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.

    Change-Id: Id3f2f5ddf26a9d31de214e9d5596a47f450b983f
    Closes-Bug: #1316720

[Aleksey Kasatkin (alekseyk-ru)]

Problem is repeated on #199.

2014-05-13 14:24:12 ERR [416] Timeout of deployment is exceeded.
2014-05-13 14:24:12 ERR [416] MCollective agents '1' didn't respond within the allotted time.

[Vladimir Sharshov (vsharshov)]

Aleksey, problem with "Timeout of deployment" is another bug: https://bugs.launchpad.net/fuel/+bug/1312443. Thanks for the report.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/4.1
Review: https://review.openstack.org/96852

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/96852
Committed: https://git.openstack.org/cgit/stackforge/fuel-library/commit/?id=6de87343ddf5a939695c1178f9946d2d08c3e876
Submitter: Jenkins
Branch: stable/4.1

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.

    Change-Id: Id3f2f5ddf26a9d31de214e9d5596a47f450b983f
    Closes-Bug: #1316720

[Meg McRoberts (dreidellhasa)]

Documented as fixed in 4.1.1

[Tatyanka (tatyana-leontovich)]

verifiy 6.1 rc3