Hello Raman, after some internal discussions, we consider this as an edge case.
We think it's rare that a NIC of a guest is manually changed post install (for example, by destroying and recreating the same) and if so the two (actually three) line changes: two lines: match: macaddress: 52:54:00:54:10:8b (actually three, with: set-name: enp0s1 ) could likely be done at the same time. Control over the matching rules is a bit limited, for example globs are not possible for the macaddress themselves. However, in cases where similar or even equal system are setup often (by tearing them down / destroy and setting them up again - potentially in test environments), a convenient solution could be to use the non-interactive 'autoinstall' for the installation (which works fine with KVM guests). (https://canonical-subiquity.readthedocs-hosted.com/en/latest/howto/autoinstall-quickstart.html) autoinstall allows you to define and use your own netplan.yaml configuration (it's actually a separate section in the autoinstall.yaml), hence the above 3 lines can simply be omitted. Btw. and autoinstall (yaml) file (will is the user-data for the autoinstall process) usually does not need to be written from scratch, since an interactive installation auto generates such an autoinstall yaml file for you and places it at /var/log/installer/autoinstall-user-data. This can be taken as a base (for a user-data file) and the three lines can be removed (hence will not be used anymore for all future autoinstalls attempts). Would that make sense? ** Changed in: ubuntu-power-systems Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2138794 Title: [Ubuntu26.04] [FW1110] : Guest network is going down, as MAC address mismatches! To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2138794/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
