Some haproxy backend has down state during mysql one-by-one termination
Bug #1654276 reported by
Alexandr Kostrikov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
High
|
Fuel QA Team | ||
Mitaka |
Fix Committed
|
High
|
Vladimir Jigulin | ||
Newton |
Confirmed
|
High
|
Fuel QA Team | ||
Ocata |
Confirmed
|
High
|
Fuel QA Team |
Bug Description
During swarm[0] run there were failure on scenario:
Scenario:
1. Terminate mysql
2. Wait while it is being restarted
3. Verify it is restarted
4. Go to another controller
5. Run OSTF
fuel_health.
Additional information:
There is no env available, need to wait for reproduce
2017-01-04 05:07:11 FAILURE Check state of haproxy backends on controllers (fuel_health. tests.ha. test_haproxy. HAProxyCheck. test_001_ check_state_ of_backends) Some haproxy backend has down state..
Jan 04 05:07:10 [4897] node-1. test.domain. local pengine: info: clone_print: Clone Set: clone_p_mysqld [p_mysqld] test.domain. local pengine: info: short_print: Started: [ node-1. test.domain. local node-4. test.domain. local node-5. test.domain. local ]
Jan 04 05:07:10 [4897] node-1.