+++ This bug was initially created as a clone of Bug #1637739 +++ Description of problem: nova_metadata container is in unhealthy state on undercloud and overcloud nodes: [root@undercloud-0 stack]# docker ps | grep nova_metadata 2ee724246dec 192.168.24.1:8787/rhosp14/openstack-nova-api:2018-10-08.4 "kolla_start" 4 hours ago Up 4 hours (unhealthy) nova_metadata [root@controller-0 heat-admin]# docker ps | grep nova_metadata 0e3143263535 192.168.24.1:8787/rhosp14/openstack-nova-api:2018-10-08.4 "kolla_start" 2 hours ago Up 42 minutes (unhealthy) nova_metadata Version-Release number of selected component (if applicable): 14 -p 2018-10-08.4 How reproducible: 100% Steps to Reproduce: 1. Deploy OSP14 undercloud and overcloud 2. Check nova_metadata container status Actual results: It reports unhealthy state Expected results: It reports healthy state. Additional info: Attaching job artifacts --- Additional comment from Martin Schuppert on 2018-11-21 11:12:26 EST --- Since there were ongoing upstream tripleo ci issues and we could not land the fix and added a temporary down-stream only patch to unblock the situation. This BZ is to track the revert of the downstream-only patch.
If this bug requires doc text for errata release, please set the 'Doc Type' and provide draft text according to the template in the 'Doc Text' field. The documentation team will review, edit, and approve the text. If this bug does not require doc text, please set the 'requires_doc_text' flag to -.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0446