[system-tests] Test Mysql kill test wasn't wait enough on sync check
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Dmitry Tyzhnenko |
Bug Description
{
"build_id": "2015-01-
"ostf_sha": "95054878eff472
"build_number": "76",
"auth_
"api": "1.0",
"nailgun_sha": "e75ac13a46d6c4
"production": "docker",
"fuelmain_sha": "",
"astute_sha": "48829a27b8041c
"feature_
[
"mirantis"
],
"release": "6.1",
"release_versions":
{
"2014.2-6.1":
{
"VERSION":
{
"build_id": "2015-01-
"ostf_sha": "95054878eff472
"build_number": "76",
"api": "1.0",
"nailgun_sha": "e75ac13a46d6c4
"production": "docker",
"fuelmain_sha": "",
"astute_sha": "48829a27b8041c
"feature_
[
],
}
}
},
"fuellib_sha": "4c61bf87a96453
}
Steps:
1. Create next cluster - HA, CentOS, Neutron Vlan, 3 controllers, 2 compute nodes
2. Deploy cluster
3. After deployment ssh to first controller (node-1) and do:
pkill -9 -x "mysqld"
4. Wait until - crm resource status clone_p_mysql | grep -q "is running on: $HOSTNAME" return is Running
and galera state is synced
5. Ssh to next controller (node-4) and do:
pkill -9 -x "mysqld"
Actual result - after mysql killing on second controller mysql resiurce is stopped in pacemaker
Logs are attached
tags: | removed: to-be-covered-by-tests |
summary: |
- [system tests] Test Mysql kill test wasn't wait enough on sync check + [system-tests] Test Mysql kill test wasn't wait enough on sync check |
tags: | added: system-tests |
Changed in fuel: | |
importance: | Medium → High |
Do we have an automated test case for that running periodically?