CI: Nova - SQL connection failed (pingtest)

[Emilien Macchi]

TripleO pingtest sometimes fails on testing Nova API:

Logstash query:
http://logstash.openstack.org/#dashboard/file/logstash.json?query=build_name%3A%20*tripleo-ci*%20AND%20build_status%3A%20FAILURE%20AND%20message%3A%20%5C%22504%20Gateway%20Time-out%5C%22

Error in pingtest logs:
http://logs.openstack.org/34/417134/2/check-tripleo/gate-tripleo-ci-centos-7-ovb-ha/ec58fc5/console.html#_2017-01-06_02_58_39_602254

Error in Nova logs:
http://logs.openstack.org/34/417134/2/check-tripleo/gate-tripleo-ci-centos-7-ovb-ha/ec58fc5/logs/overcloud-controller-1/var/log/nova/nova-api.txt.gz#_2017-01-06_02_47_04_754

"SQL connection failed"

[Thomas Herve (therve)]

Note that the error happens on successful runs as well. Eg:
http://logs.openstack.org/99/414099/7/check-tripleo/gate-tripleo-ci-centos-7-ovb-ha/e926d0c/logs/overcloud-controller-1/var/log/nova/nova-api.txt.gz

[Emilien Macchi (emilienm)]

The rate of failure is pretty low, I'm removing the tag alert and set the bug to High instead of Critical.

[Ben Nemec (bnemec)]

Moving to pike based on the rarity and the fact that nobody seems to be looking into it.

[Ben Nemec (bnemec)]

I'm skeptical that this is high priority since nobody has looked into it since January and it happens rarely. Dropping to medium and moving to Queens.

[Emilien Macchi (emilienm)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE