Bug 2231893
Summary: | Networking-ovn-metadata-agent keeps restarting when some haproxy service can't be started | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Ihar Hrachyshka <ihrachys> |
Component: | openstack-neutron | Assignee: | Miro Tomaska <mtomaska> |
Status: | CLOSED DUPLICATE | QA Contact: | Eran Kuris <ekuris> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 17.1 (Wallaby) | CC: | bcafarel, chrisw, gregraka, gurpsing, jamsmith, jelynch, mariel, mtomaska, pgrist, scohen |
Target Milestone: | z2 | Keywords: | Triaged |
Target Release: | 17.1 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: |
The metadata service can become unavailable after the metadata agent fails in multiple attempts to start a malfunctioning HAProxy child container. The metadata agent logs an error message similar to: `ProcessExecutionError: Exit code: 125; Stdin: ; Stdout: Starting a new child container neutron-haproxy-ovnmeta-<uuid>”.
+
*Workaround:* Run `podman kill <_container name_>` to stop the problematic haproxy child container.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2023-10-11 17:26:37 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ihar Hrachyshka
2023-08-14 14:51:45 UTC
*** This bug has been marked as a duplicate of bug 2229779 *** |