haproxy status not captured in diagnostic snapshots

Bug #1570982 reported by Alex Schultz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Fix Released
Medium
Timmy Development Team
Mitaka
Fix Released
Medium
Timmy Development Team

Bug Description

Currently we do not capture the backend status as part of the diagnostic snapshot. This makes it hard to determine the status of the VIPs and backend services at the time the snapshot is created.

Steps to reproduce:
1) Generate diagnostic snapshot
2) Attempt to figure out backend status

Expected Results:
Snapshot should contain a captured output of haproxy-status.sh from the controllers

Actual Results:
No status is available.

Version: Any

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-web (master)

Fix proposed to branch: master
Review: https://review.openstack.org/306553

Changed in fuel:
assignee: nobody → Alex Schultz (alex-schultz)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-web (master)

Reviewed: https://review.openstack.org/306553
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=fef49fcd39a2f503f67ce2c30ec45c040fe20399
Submitter: Jenkins
Branch: master

commit fef49fcd39a2f503f67ce2c30ec45c040fe20399
Author: Alex Schultz <email address hidden>
Date: Fri Apr 15 11:26:31 2016 -0600

    Capture haproxy status in snapshots

    This change adds the haproxy status to the command output captured on
    the controllers. This will help in researching the status of the various
    services when the snapshot is generated.

    Change-Id: I0a7c83c21805dbd1182ea74692d76e9a49300bb8
    Closes-Bug: #1570982

Changed in fuel:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to fuel-web (stable/mitaka)

Fix proposed to branch: stable/mitaka
Review: https://review.openstack.org/337734

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to fuel-web (stable/mitaka)

Reviewed: https://review.openstack.org/337734
Committed: https://git.openstack.org/cgit/openstack/fuel-web/commit/?id=d839d231a24e32a83f0a22a42ead420901301d82
Submitter: Jenkins
Branch: stable/mitaka

commit d839d231a24e32a83f0a22a42ead420901301d82
Author: Alex Schultz <email address hidden>
Date: Fri Apr 15 11:26:31 2016 -0600

    Capture haproxy status in snapshots

    This change adds the haproxy status to the command output captured on
    the controllers. This will help in researching the status of the various
    services when the snapshot is generated.

    Change-Id: I0a7c83c21805dbd1182ea74692d76e9a49300bb8
    Closes-Bug: #1570982
    (cherry picked from commit fef49fcd39a2f503f67ce2c30ec45c040fe20399)

tags: added: on-verification
Revision history for this message
Alexey. Kalashnikov (akalashnikov) wrote :

Can't find any file with name haproxy_status.txt or any other contained output of haproxy-status.sh,
in snapshot generated by command 'fuel snapshot' or by UI from 'Support' page

May be I do something wrong, can someone tell me where I should find them exactly?

Checked On 9.1 snapshot #315
shotgun report:
http://paste.openstack.org/show/583106/

tags: removed: on-verification
Revision history for this message
Dmitry Pyzhov (dpyzhov) wrote :

We moved from Shotgun to Timmy. Moving the bug to corresponding team.

Changed in fuel:
status: Fix Committed → Confirmed
assignee: Alex Schultz (alex-schultz) → Timmy Development Team (timmy-core)
Revision history for this message
Dmitry Sutyagin (dsutyagin) wrote :

Dmitry, thank you for the submission. The fix is on review upstream - https://review.openstack.org/407094

Changed in fuel:
status: Confirmed → In Progress
Revision history for this message
Dmitry Sutyagin (dsutyagin) wrote :

The changes were merged to all branches.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.