← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1867501] [NEW] System Information - Compute Services - wrong data

 

Public bug reported:

OS release: Train

I have some leftover compute services that are enabled but down.
OSC properly reports them:

$ openstack compute service list
+-----+------------------+-----------------+----------+---------+-------+----------------------------+
|  ID | Binary           | Host            | Zone     | Status  | State | Updated At                 |
+-----+------------------+-----------------+----------+---------+-------+----------------------------+
|   4 | nova-scheduler   | os-controller-3 | internal | enabled | up    | 2020-03-15T08:54:06.000000 |
|  85 | nova-scheduler   | os-controller-1 | internal | enabled | up    | 2020-03-15T08:54:15.000000 |
|  91 | nova-scheduler   | os-controller-2 | internal | enabled | up    | 2020-03-15T08:54:15.000000 |
|  60 | nova-scheduler   | os-controller-3 | internal | enabled | down  | 2020-02-07T20:35:03.000000 |
|  87 | nova-scheduler   | os-controller-2 | internal | enabled | down  | 2020-02-07T20:35:13.000000 |
| 111 | nova-scheduler   | os-controller-1 | internal | enabled | down  | 2020-02-07T20:35:12.000000 |

However, Horizon displays them twice, yet each time with State Up.

I guess it gets confused by duplicate (service name, host, zone) tuple
(possibly part of it) instead of differentiating based on ID.

** Affects: horizon
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1867501

Title:
  System Information - Compute Services - wrong data

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  OS release: Train

  I have some leftover compute services that are enabled but down.
  OSC properly reports them:

  $ openstack compute service list
  +-----+------------------+-----------------+----------+---------+-------+----------------------------+
  |  ID | Binary           | Host            | Zone     | Status  | State | Updated At                 |
  +-----+------------------+-----------------+----------+---------+-------+----------------------------+
  |   4 | nova-scheduler   | os-controller-3 | internal | enabled | up    | 2020-03-15T08:54:06.000000 |
  |  85 | nova-scheduler   | os-controller-1 | internal | enabled | up    | 2020-03-15T08:54:15.000000 |
  |  91 | nova-scheduler   | os-controller-2 | internal | enabled | up    | 2020-03-15T08:54:15.000000 |
  |  60 | nova-scheduler   | os-controller-3 | internal | enabled | down  | 2020-02-07T20:35:03.000000 |
  |  87 | nova-scheduler   | os-controller-2 | internal | enabled | down  | 2020-02-07T20:35:13.000000 |
  | 111 | nova-scheduler   | os-controller-1 | internal | enabled | down  | 2020-02-07T20:35:12.000000 |

  However, Horizon displays them twice, yet each time with State Up.

  I guess it gets confused by duplicate (service name, host, zone) tuple
  (possibly part of it) instead of differentiating based on ID.

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1867501/+subscriptions