Bug 1498360 - OPS Tools | Availability Monitoring | Health checks representation in Uchiwa should be redone because of containers introduction in osp12.
Summary: OPS Tools | Availability Monitoring | Health checks representation in Uchiwa ...
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: opstools-ansible
Version: 12.0 (Pike)
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Lars Kellogg-Stedman
QA Contact: Leonid Natapov
URL:
Whiteboard:
Keywords: Tracking
: 1505321 1510408 1510409 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-04 06:51 UTC by Leonid Natapov
Modified: 2019-05-20 18:02 UTC (History)
10 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2019-05-20 18:02:59 UTC


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
RDO 10731 None None None 2017-11-29 07:55 UTC

Description Leonid Natapov 2017-10-04 06:51:03 UTC
Health checsk representation in Uchiwa should be redone because of containers introduction in osp12.

In OSP11 we had checks for each service and each service was shown in Uchiwa along with its status (active,not active,etc).

In OSP12 with introduction of the containers we have one single check docker_health_check that shows unhealthy containers under its "output" which looks very user unfriendly and really hard to understand what is going on.

Here is the example of how it looks like: 

--------------
output:
/nova_vnc_proxy (71529e4ffa5e): There is no nova-novncproxy process with opened RabbitMQ ports (5671,5672) running in the container /ceilometer_agent_central (3493da8311b5): There is no ceilometer-poll process with opened RabbitMQ ports (5671,5672) running in the container /aodh_evaluator (00fa97538ae5): There is no aodh-evaluator process with opened RabbitMQ ports (5671,5672) running in the container
-------------

We have to show in Uchiwa a list of containers each one shows its status (healthy/unhealthy)

Comment 1 Martin Magr 2017-11-08 11:46:24 UTC
*** Bug 1505321 has been marked as a duplicate of this bug. ***

Comment 2 Martin Magr 2017-11-08 11:49:39 UTC
*** Bug 1510409 has been marked as a duplicate of this bug. ***

Comment 3 Martin Magr 2017-11-22 18:30:49 UTC
*** Bug 1510408 has been marked as a duplicate of this bug. ***

Comment 4 Martin Magr 2019-05-20 18:02:59 UTC
opstools-ansible patch has been merged upstream for some time already. Closing this BZ.


Note You need to log in before you can comment on or make changes to this bug.