Make ostf error about haproxy more informative

Bug #1587063 reported by Alexandr Kostrikov on 2016-05-30
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Alexandr Kostrikov

Bug Description

It is hard to understand what exact cause of haproxy backend to quickly sort errors by type.

  - Check state of haproxy backends on controllers (failure) Some haproxy backend has down state.. Please refer to OpenStack logs for more details.

We have information in ostf error log at what level (L3,L4,L7) and on which service failure has been detected.

We need to add more information to error which is reported to jenkins

Fix proposed to branch: master

Changed in fuel:
status: New → In Progress

Example of what is accessible in logs:
2016-05-30 00:32:20 DEBUG (test_haproxy) Dead backends ['ceilometer node-1 Status: DOWN/L4CON Sessions: 0 Rate: 0 ', 'ceilometer node-4 Status: DOWN/L4CON Sessions: 0 Rate: 0 ', 'ceilometer node-5 Status: DOWN/L4CON Sessions: 0 Rate: 0 ']

tags: added: area-ostf
removed: area-qa
Changed in fuel:
milestone: 9.0 → 10.0

Submitter: Jenkins
Branch: master

commit afc374aa9efc6e9f363d6e4211607bfd9f121b43
Author: Alexandr Kostrikov <email address hidden>
Date: Mon May 30 17:57:40 2016 +0300

    Detailed haproxy failure message

    That is aimed to make debug easier and

    Change-Id: I5aa633b954e4cd8c6bb7291339c1c5806925c8c9
    Related-bug: #1570805
    Closes-bug: #1587063

Changed in fuel:
status: In Progress → Fix Committed

Messages are look like
"Dead backends ['mysqld node-1 Status: DOWN/L7STS Sessions: 0 Rate: 0 ']. Please refer to OpenStack logs for more details."

Changed in fuel:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers