[9.2][SWARM] RabbitMQ OSTF fail after exit maintenance_mode: can not set proxy

[Vladimir Jigulin]

Steps to reproduce:
1. Create cluster
2. Add 3 node with controller and mongo roles
3. Add 2 node with compute and cinder roles
4. Deploy the cluster
5. Unexpected reboot
6. Wait until controller is switching in maintenance mode
7. Exit maintenance mode
8. Check the controller become available
9. Run OSTF << -- fail

Catched on 9.2 MU-1 iso #03/20/17 20:07

Expected results: OSTF passed
Actual result:
- RabbitMQ availability (fuel_health.tests.ha.test_rabbit.RabbitSanityTest.test_002_rabbitmqctl_status_ubuntu). Test status: failure, message: Can not set proxy for Health Check.Make sure that network configuration for controllers is correct

Errors:
http://paste.openstack.org/show/603762/
Trying to authenticate at "https://10.109.13.6:5000/v2.0/" using HTTP proxy "http://10.109.10.4:8888"
AuthorizationFailure: Authorization Failed: Service Unavailable (HTTP 503)
Can not set proxy for Health Check.Make sure that network configuration for controllers is correct

[Anton Chevychalov (achevychalov)]

Unable to confirm problem on lab. Besides it is green now on SWARM. Looks like we have issue with timeout on pacemaker or incorrect detection on step 8.

I mark that as Won't Fix.

[Vladimir Jigulin (vjigulin)]

All 3 "Controller Maintenance Mode" jobs catch this bug in 04/01/17 run

snapshots:
https://drive.google.com/file/d/0Bw7ZahkM7_sJN1c4bFp0ZFVNQzg/view?usp=sharing
https://drive.google.com/file/d/0Bw7ZahkM7_sJUHlvbnJUMS1qOTQ/view?usp=sharing