Per call w/ Lenovo - after adding the netplan yaml, the machine is put into a reboot loop (just issuing a reboot from within the OS in a loop and then testing the device is up on each subsequent boot) so If I understood:
1: Install 24.04 on the machine (one with several network ports) 2: Add the netplan yaml (and configure static IPs for all NIC ports) 3: implement a reboot loop where the machine is rebooted periodically over 24 or 48 hours 4: after each reboot check that all the NICs have IPs and the IPs are expected ones. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2083129 Title: [Lenovo Ubuntu 22.04.4 Bug] netplan static IP address assignment use NetworkManager as renderer would be lost static ip Status in netplan.io package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Invalid Status in netplan.io source package in Jammy: New Status in network-manager source package in Jammy: Invalid Bug description: On Ubuntu 22.04.4, to configure a system to use static address assignment, create a netplan configuration in the file, like /etc/netplan/00-installer-config.yaml. After assigning the network configuration abstraction renderer to NetworkManager not networkd in /etc/netplan/00-installer-config.yaml, then we do warm reboot test, some of the NIC interface lost their static ip in some reboot cycles when the rendered is NetworkManager, but networkd as a renderer is works well, all NIC interfaces can get their corresponding IP that configured in netplan confile file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2083129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
