heat api and api cfn containers are showing up as unhealthy

Bug #1772492 reported by Alex Schultz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Medium
Alex Schultz

Bug Description

[centos@undercloud ~]$ sudo docker ps -f health=unhealthy
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
6c82c4664dc0 docker.io/tripleomaster/centos-binary-heat-api-cfn:20b99f6998c088650b0c0cb066cc6aac3e5f9312_b333f915 "kolla_start" 42 minutes ago Up 42 minutes (unhealthy) heat_api_cfn
193a0ebf7329 docker.io/tripleomaster/centos-binary-heat-api:20b99f6998c088650b0c0cb066cc6aac3e5f9312_b333f915 "kolla_start" 42 minutes ago Up 42 minutes (unhealthy) heat_api

These containers are marked as unhealthy because the healthcheck url is returning 401 which curl considers as an error. Since heat-api does not have a healthcheck url, we need to update the healthcheck scripts to check for the 401

Tags: containers
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-common (master)

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

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

Reviewed: https://review.openstack.org/569852
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=db47c12099414836227d13d609af3f4a5556c4df
Submitter: Zuul
Branch: master

commit db47c12099414836227d13d609af3f4a5556c4df
Author: Alex Schultz <email address hidden>
Date: Mon May 21 13:59:01 2018 -0600

    Update heat api healtchecks

    The heat-api and heat-api-cfn containers need to check for 401 which is
    what the api will return when it is up. There is not currently a
    specific healthcheck url for heat that would return 200 so we need to
    update the container healthcheck to look for the 401.

    Change-Id: Ib0ac8847a47a42e7e0d73b699236df3355f58dcd
    Closes-Bug: #1772492

Changed in tripleo:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-common (master)

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-common (master)

Reviewed: https://review.openstack.org/571173
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=ed760d71717c7115f9a505ff0aa3229b2165075a
Submitter: Zuul
Branch: master

commit ed760d71717c7115f9a505ff0aa3229b2165075a
Author: Alex Schultz <email address hidden>
Date: Wed May 30 05:05:54 2018 -0600

    Fix heat api cfn healthcheck

    The heat-api-cfn returns a 400 instead of a 401.

    Change-Id: I8c82119037e976c92d6313dac17b4f0601ab96fe
    Closes-Bug: #1772492

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tripleo-common 9.1.0

This issue was fixed in the openstack/tripleo-common 9.1.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-common (stable/queens)

Fix proposed to branch: stable/queens
Review: https://review.openstack.org/612327

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on tripleo-common (stable/queens)

Change abandoned by Martin Mágr (<email address hidden>) on branch: stable/queens
Review: https://review.openstack.org/612327

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Change abandoned by James Slagle (<email address hidden>) on branch: stable/queens
Review: https://review.opendev.org/612327
Reason: Abandoning this patch per the TripleO Patch Abandonment guidelines (https://specs.openstack.org/openstack/tripleo-specs/specs/policy/patch-abandonment.html). If you wish to have this restored and cannot do so yourself, please reach out via #tripleo on freenode or the OpenStack Dev mailing list.

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.