MySQL crashed after cluster reboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
High
|
Bogdan Dobrelya | ||
Mitaka |
Confirmed
|
High
|
Bogdan Dobrelya |
Bug Description
groups=
"""Shutdown of Neutron vlan, cinder/swift cluster
Scenario:
1. Create cluster with Neutron Vlan, cinder/swift
2. Add 3 controller, 2 compute, 1 cinder nodes
3. Verify Network
4. Deploy cluster
5. Verify networks
6. Run OSTF
7. Create 2 volumes and 2 instances with attached volumes
8. Fill cinder storage up to 30%(15% for each instance)
9. Shutdown of all nodes
10. Wait 5 minutes
11. Start cluster
12. Wait until OSTF 'HA' suite passes << Fail
13. Verify networks
14. Run OSTF tests
OSTF fails while trying to authenticate
In ostf.log:
Authorization Failed: Unable to establish connection to https:/
In keystone-all.log:
unavailable: [client 10.109.11.5:38056] mod_wsgi (pid=7481): Unable to connect to WSGI daemon process 'keystone_main' on '/var/run/
Unfortunately environment with this test was cleaned up
Build: 9.0-303 / mitaka-9.0 (May 09 2016)
Changed in fuel: | |
importance: | Undecided → High |
status: | New → Confirmed |
assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
milestone: | none → 10.0 |
tags: | added: area-library |
Changed in fuel: | |
assignee: | Fuel Sustaining (fuel-sustaining-team) → Kyrylo Galanov (kgalanov) |
status: | Confirmed → In Progress |
description: | updated |
Changed in fuel: | |
status: | In Progress → Confirmed |
Changed in fuel: | |
assignee: | Kyrylo Galanov (kgalanov) → Bogdan Dobrelya (bogdando) |
Apparently MySQL crashed. Unfortunately, I can see the log file of the last run only.
Could you please reproduce it on the environment and ping me?
---
2016-05-10 02:37:29 18550 [Note] InnoDB: 5.6.23 started; log sequence number 1625977
02:37:29 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.