Bug 1603240 - Health checks for containerized services: octavia_health_manager & octavia_housekeeping
Summary: Health checks for containerized services: octavia_health_manager & octavia_ho...
Keywords:
Status: CLOSED DUPLICATE of bug 1517500
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-octavia
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Assaf Muller
QA Contact: Alexander Stafeyev
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-19 14:02 UTC by rlopez
Modified: 2019-09-10 14:07 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-20 14:41:21 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description rlopez 2018-07-19 14:02:47 UTC
Description of problem:

On the latest OSP13 GA.

After successful overcloud deployment the container health check shows unhealthy state for : octavia_health_manager / octavia_housekeeping  -  it seems that there are no open ports for the services in the containers or the ports are wrong or the health check is wrong. Honestly I'm not sure.

Seeing the following errors when running `sudo docker ps | grep -i unhealthy` within a controller:

822257473b99        192.168.24.1:8787/rhosp13/openstack-octavia-health-manager:13.0-38      "kolla_start"            16 hours ago        Up 16 hours (unhealthy)                       octavia_health_manager
f28fe412d711        192.168.24.1:8787/rhosp13/openstack-octavia-housekeeping:13.0-38        "kolla_start"            16 hours ago        Up 16 hours (unhealthy)                       octavia_housekeeping

sudo docker inspect ocatvia_health_manager shows:

"Output": "There is no octavia-health- process with opened RabbitMQ ports (5671,5672) running in the container\n"

sudo docker inspect octavia_housekeeping shows:

"Output": "There is no octavia-houseke process with opened RabbitMQ ports (5671,5672) running in the container\n"


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