Comment 0 for bug 1365635

Deploy 5.0 master node

deploy 5.0 env

upgrade 5.1 to latest 5.1, e.g.

{"build_id": "2014-09-04_00-01-17", "ostf_sha": "4dcd99cc4bfa19f52d4b87ed321eb84ff03844da", "build_number": "496", "auth_required": true, "api": "1.0", "nailgun_sha": "3d965a7acd9361a361da92970d5bc5a1be77c969", "production": "docker", "fuelmain_sha": "435c43fe558898566ef8254ec09cc12bcb809c4b", "astute_sha": "8cc2c5b29d75ec2f60787e225564426a0508b3e4", "feature_groups": ["mirantis"], "release": "5.1", "fuellib_sha": "bc23f1359b35ec90d5c7bc9f33778b4f2922d409"}

apply https://review.openstack.org/#/c/118432/ to astute

start patching to 5.0.2
expected behaviour:

pacemaker should move failed resources (e.g. neutron agents) to other nodes

actual result:

resources stay on the node being patched