Bug 2127965
| Summary: | Frr container does not come up after a reboot because /run/frr directory is gone | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Luca Miccini <lmiccini> |
| Component: | openstack-tripleo-heat-templates | Assignee: | Luca Miccini <lmiccini> |
| Status: | CLOSED ERRATA | QA Contact: | Joe H. Rahme <jhakimra> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 17.0 (Wallaby) | CC: | erpeters, gregraka, mburns |
| Target Milestone: | z1 | Keywords: | Triaged |
| Target Release: | 17.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-tripleo-heat-templates-14.3.1-0.20220922100710.feca772.el9ost | Doc Type: | Known Issue |
| Doc Text: |
There is currently a known issue in RHOSP 17.0 where the Free Range Router (FRR) container does not start after the host on which it resides is rebooted. This issue is caused by a missing file in the BGP configuration. Workaround: Create the file, `/etc/tmpfiles.d/run-frr.conf`, and add the following line:
+
----
d /run/frr 0750 root root - -
----
+
After you make this change, `tmpfiles` recreates `/run/frr` after each reboot and the FRR container can start.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-01-25 12:29:22 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
Luca Miccini
2022-09-19 13:30:07 UTC
[root@ctrl-1-0 ~]# ll /etc/tmpfiles.d/ total 12 -rw-r--r--. 1 root root 30 Dec 7 08:12 run-frr.conf -rw-r--r--. 1 root root 34 Dec 7 08:12 run-octavia.conf -rw-r--r--. 1 root root 38 Dec 7 08:12 var-tmp-horizon.conf [root@ctrl-1-0 ~]# cat /etc/tmpfiles.d/run-frr.conf d /run/frr 0750 root root - - 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 (Red Hat OpenStack Platform 17.0.1 bug fix and enhancement 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-2023:0271 |