home page isn't sorting results by descending failure rate

Bug #1522200 reported by Anita Kuno
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Health
Fix Released
Undecided
Masayuki Igawa

Bug Description

When I am looking at http://status.openstack.org/openstack-health/#/ as I write this bug report, I see the top results sorted according to failure rate - as I am told I should expect.

Midway down the page however after several entries with 100% pass rate, I see zaqar with pass rate 0% and failure rate 0% then ironic-python-agent with failure rate 12.90% then taskflow with failure rate 4.76% then glance with failure rate 1.94% then back to entries with 100% pass rate.

Why are there some entries with non-zero failure rates in the middle of entries with 100% pass rates? Entries with non-zero failure rates should be rendered at the top of the page. I don't know where an entry with 0% pass rate 0% failure rate should be but I'm guessing not in the middle of the page.

References:
http://status.openstack.org/openstack-health/#/

Revision history for this message
Matthew Treinish (treinish) wrote :

So I just checked this again and I don't see the behavior anymore. I'm wondering if the recent refactor of the home page js controller in: https://review.openstack.org/#/c/245832/ fixed this issue. I'm gonna mark this as incomplete and if it comes back or we see more issues with the sorting here we can add the details and move this to confirmed.

As for the zaqar project, I still see the zaqar 0%/0% thing, but since we're sorting on failure percentage it's actually in the right place. :)

As for it's presence of 0% pass and 0% failed I've tracked that down to 2 bugs, 1 in the naming of zaqar functional jobs that didn't run tempest but included it in the name. Which has been fixed and after 10 days it will clear itself from the dashboard. The other is in the subunit-gearman worker script which should be fixed here: https://review.openstack.org/#/c/254382/ I'm debating also writing a cleanup script to remove these empty runs from the db because they're just eating space doing nothing.

Changed in openstack-health:
status: New → Incomplete
Revision history for this message
Anita Kuno (anteaya) wrote :

Okey dokey, and yes cleaning empty runs from the db sounds like a great idea.

Revision history for this message
Masayuki Igawa (igawa) wrote :

I've confirmed this bug now.

Changed in openstack-health:
assignee: nobody → Masayuki Igawa (igawa)
Revision history for this message
Masayuki Igawa (igawa) wrote :

I'll try to tackle with this.

Changed in openstack-health:
status: Incomplete → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to openstack-health (master)

Reviewed: https://review.openstack.org/269423
Committed: https://git.openstack.org/cgit/openstack/openstack-health/commit/?id=21eca6c9bb9225f27ad20c20017d8bb61b53c432
Submitter: Jenkins
Branch: master

commit 21eca6c9bb9225f27ad20c20017d8bb61b53c432
Author: Masayuki Igawa <email address hidden>
Date: Tue Jan 19 12:14:51 2016 +0900

    Fix sorting order on home page

    This commit fixes the sorting order on the home page. We should have a
    floating point value rounded to 4 digits after the decimal point at
    least. For example, 0.3333 would be 33% with the original rounding.
    However, this is not enough resolution for the home page. This should be
    33.33% at least.

    Closes-Bug: #1522200
    Change-Id: I2e57fce318256fcd6e9aee892706d21d5269b81c

Changed in openstack-health:
status: In Progress → 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.