[swarm] mysql service does not start after termination
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
High
|
Fuel QA Team | ||
Mitaka |
Invalid
|
High
|
Fuel QA Team |
Bug Description
Detailed bug description:
Mysql service does not start after termination within 2 minutes. It looks like the box where it's running is a bit slow. All services are OK after restoring from the snapshot: all controllers run mysql services, no errors in logs. It can be considered as performance issue though.
Traceback: http://
Increasing the timeout might help a little bit for slow boxes, however it's not the best way to go.
Steps to reproduce:
1. Terminate mysql
2. Wait while it is being restarted
3. Verify it is restarted
4. Go to another controller
5. Run OSTF
Expected results:
mysql service gets up after termination withing 2 minutes
Actual result:
mysql service is down
Impact:
swarm failure
Description of the environment:
9.1 snapshot #90
[root@nailgun log]# shotgun2 short-report
cat /etc/fuel_build_id:
495
cat /etc/fuel_
495
cat /etc/fuel_release:
9.0
cat /etc/fuel_
mitaka-9.0
rpm -qa | egrep 'fuel|astute|
python-
fuelmenu-
fuel-release-
fuel-bootstrap
fuel-openstack
fuel-ostf-
shotgun-
python-
fuel-9.
fuel-misc-
fuel-provision
fuel-utils-
fuel-setup-
network-
fuel-agent-
fuel-ui-
fuel-library9.
nailgun-
rubygem-
fuel-nailgun-
fuel-notify-
fuel-mirror-
fuel-migrate-
MOS_CENTOS_
MOS_CENTOS_
MOS_CENTOS_
MOS_CENTOS_
MOS_CENTOS_
MOS_UBUNTU_
UBUNTU_MIRROR_ID: ubuntu-
CENTOS_MIRROR_ID: centos-
Logs: https:/
Changed in fuel: | |
milestone: | none → 9.1 |
assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
tags: | added: area-library |
Changed in fuel: | |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in fuel: | |
milestone: | 9.1 → 10.0 |
tags: |
added: area-qa removed: area-library |
Changed in fuel: | |
assignee: | Fuel Sustaining (fuel-sustaining-team) → Fuel QA Team (fuel-qa) |
Hi,
We have a grace period of 10 minutes to reassemble cluster after it was broken. Could you please increase timeout in tests?
--
Kyrylo