Comment 14 for bug 1323277

Revision history for this message
Aleksandr Didenko (adidenko) wrote : Re: vip__management recovered with error

Tested on 4.1
{
    "astute_sha": "55df06b2e84fa5d71a1cc0e78dbccab5db29d968",
    "build_id": "2014-06-18_00-41-14",
    "build_number": "367",
    "fuellib_sha": "245b99f3733fa1b24208c2d732236d404e79abd1",
    "fuelmain_sha": "6baad98fc95334b6a7c1f4b69ba0cfa3a266481c",
    "mirantis": "yes",
    "nailgun_sha": "bdc747cd70721874d1e8af36181fd4179cce4fce",
    "ostf_sha": "2b7b39e4b6ea89751b65171f24a8e80b5cac56aa",
    "release": "4.1.1"
}

VIPs moved OK:

Online: [ node-2.test.domain.local node-3.test.domain.local ]
OFFLINE: [ node-1.test.domain.local ]

 vip__management_old (ocf::mirantis:ns_IPaddr2): Started node-2.test.domain.local
 vip__public_old (ocf::mirantis:ns_IPaddr2): Started node-3.test.domain.local

Env is operational, OSTF is ok, I can launch instances, browse Horizon, etc.