Bug 1701180
Summary: | [OSP15] failed healthcheck for heat_engine container | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Artem Hrechanychenko <ahrechan> |
Component: | openstack-tripleo-heat-templates | Assignee: | Emilien Macchi <emacchi> |
Status: | CLOSED ERRATA | QA Contact: | Artem Hrechanychenko <ahrechan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 15.0 (Stein) | CC: | athomas, emacchi, ltomasbo, mburns, sbaubeau, scollier |
Target Milestone: | ga | Keywords: | Triaged, ZStream |
Target Release: | 15.0 (Stein) | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | openstack-tripleo-heat-templates-10.5.1-0.20190619000409.eff8376.el8ost | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-09-21 11:21:11 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Artem Hrechanychenko
2019-04-18 10:02:56 UTC
VERIFIED [stack@undercloud-0 ~]$ sudo systemctl status tripleo_heat_engine_healthcheck.service ● tripleo_heat_engine_healthcheck.service - heat_engine healthcheck Loaded: loaded (/etc/systemd/system/tripleo_heat_engine_healthcheck.service; disabled; vendor preset: disabled) Active: inactive (dead) since Thu 2019-06-20 11:37:03 EDT; 45s ago Process: 382179 ExecStart=/usr/bin/podman exec heat_engine /openstack/healthcheck 5672 (code=exited, status=0/SUCCESS) Main PID: 382179 (code=exited, status=0/SUCCESS) Jun 20 11:37:03 undercloud-0.redhat.local systemd[1]: Starting heat_engine healthcheck... Jun 20 11:37:03 undercloud-0.redhat.local systemd[1]: Started heat_engine healthcheck. openstack-tripleo-heat-templates-10.5.1-0.20190614201227.9fee07b.el8ost.noarch 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/RHEA-2019:2811 |