Description of problem: as of systemd 242, bridge interfaces no longer inherit the MAC of the first enslaved interface. This causes problems when using kickstart configurations like: network -device=br0 --onboot=yes --bootproto=dhcp --bridgeslaves=enp2s0 Kickstart begins the installation using enp2s0 and its MAC address, and the above line assumes in no small part that once the bridge is set up, it will keep using the same mac address from the standpoint of the external world. However, with the new systemd settings, the machine changes externally visible mac addresses part-way through installation, in a rather unpredictable way. Version-Release number of selected component (if applicable): as shipping with the Fedora 32 installer How reproducible: Specify a bridge interface during kickstart, e.g.: network -device=br0 --onboot=yes --bootproto=dhcp --bridgeslaves=enp2s0 Steps to Reproduce: 1. begin kickstart install Actual results: Software selection check fails (due to machine now having the wrong IP address, or failing to obtain a lease, because it's requesting one with a new mac address that may not be known to (and allowed by) the dhcp server. Expected results: Install proceeds normally, because the bridge mac address is the same as the physical MAC address already known to DHCP. Additional info: https://github.com/systemd/systemd/blob/efb536d0cbe2e58f80e501d19999928c75e08f6a/NEWS#L483 An additional `--inherit-physical-mac` option might set up systemd for both the installer (and probably the target system in /mnt/sysimage) to have ``` # /etc/systemd/network/98-bridge-inherit-mac.link [Match] Type=bridge [Link] MACAddressPolicy=none ```
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.