Back to bug 2218291
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Eduardo Olivares | 2023-06-28 15:22:42 UTC | Target Milestone | --- | z2 |
| Target Release | --- | 17.1 | ||
| Keywords | TestOnly, Triaged | |||
| Status | NEW | ASSIGNED | ||
| Assignee | rhos-maint | eolivare | ||
| RHEL Program Management | 2023-06-28 15:22:52 UTC | Target Release | 17.1 | --- |
| Red Hat One Jira (issues.redhat.com) | 2023-06-28 15:25:12 UTC | Link ID | Red Hat Issue Tracker OSP-26205 | |
| Eduardo Olivares | 2023-06-28 15:35:32 UTC | Doc Type | If docs needed, set a value | Known Issue |
| Doc Text | In Red Hat OpenStack Platform (RHOSP) 17.1 environments that use BGP dynamic routing, there is currently a known issue that may occur when the tripleo_frr service is restarted on any of the overcloud ndoes. + If the tripleo_frr is immediately restarted (systemctl restart tripleo_frr) on an overcloud nodes, the routes that this node was advertising via BGP may be lost on the peer nodes/routers. This is due to a known bug in the FRR package: https://bugzilla.redhat.com/show_bug.cgi?id=2193145 When this happens, it could take several minutes to recover those routes. + Workaround: This issue does not occur if the tripleo_frr service is restarted in this way: systemctl stop tripleo_frr; sleep 1; systemctl start tripleo_frr |
|||
| Eduardo Olivares | 2023-06-29 08:35:45 UTC | Priority | unspecified | high |
Back to bug 2218291