Description of problem: Bird 2.0.9 unfortunately shipped with a bug in the Babel protocol which breaks the protocol on every reconfigure. We should probably backport the upstream fix for this: fcb4dd0c8313 ("Babel: Fix bug in iface reconfiguration") Since the likelihood of a new upstream release being tagged just for this bug is slim... See https://bird.network.cz/pipermail/bird-users/2022-February/015962.html for upstream discussion.
FEDORA-2022-eb87753cfd has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-eb87753cfd
FEDORA-2022-5591c23e90 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-5591c23e90
FEDORA-EPEL-2022-dfb03f1d29 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-dfb03f1d29
FEDORA-EPEL-2022-c6808a3b80 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-c6808a3b80
FEDORA-2022-5591c23e90 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-5591c23e90` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-5591c23e90 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-850254540b has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-850254540b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-850254540b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-dfb03f1d29 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-dfb03f1d29 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-c6808a3b80 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-c6808a3b80 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-9dad453e24 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-9dad453e24 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-eb87753cfd has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-eb87753cfd` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-eb87753cfd See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-c6808a3b80 has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2022-dfb03f1d29 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2022-9dad453e24 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-850254540b has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-5591c23e90 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-eb87753cfd has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.