We were using aliased interfaces (lo:1) on other OSs (cent/debian/etc)
as well as ubuntu to avoid overwriting the default lo interface
configuration files . We've tested cloud-init with lo and no mac
matching on ubuntu and non ubuntu OSs and it works, so we'll just change
our base CI data to work
To get you configuration working you need to remove the match and set-
name stanzas (which were never required really). Using the definition ID
as the interface name (the "lo" inside "ethernets") is enough to
configure an interface using its name. And by removing that it will work
on Jammy.
As
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055333
Title:
netplan.io 0.106.1-7ubuntu0.22.04.2 fails to manage
Mantic with 0.106.1 correctly configures the loopback interface so it
seems other package updates on the system aren't affected by the
permanent mac address changeset. I suspect it is something with systemd
but I haven't found anything definitive yet. The netplan file from
cloudinit and the
I was able to confirm that https://github.com/canonical/netplan/pull/278
is the breaking commit with git bisect. I tried to bisect forward to
0.107.1 to see if I could find the behavior change back to working but I
think my test setup is flawed or there's another factor at play here. I
did spin up
Ignore the github comment, I was looking at the
https://github.com/canonical/netplan.io repo which I incorrectly assumed
was the repo the package was being built from, I didn't even check the
code there when I didn't see any versioning tags (facepalm).
--
You received this bug notification
I can see the need for skipping most of, if not all non loopback,
virtual devices. lo would seem to be a special case imho. I'd like to
avoid differing cloudinit nocloud data between the various distros.
As an aside it also doesn't seem to handle subinterfaces (e.g. lo:1)
like other distributions
That's an interesting find, about it working in Mantic. It needs more
investigation.
Previous behavior was a bug that was inconsistent with the
NetworkManager backend and the documentation, that's why it got fixed in
the LTS, after plenty of testing:
Also, why is previous behavior allowed to change in an LTS release?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055333
Title:
netplan.io 0.106.1-7ubuntu0.22.04.2 fails to manage additional
If that is the case then why does it work on the newer version that is
present in mantic? Is there any source for this package besides github?
I can't find any tags, branching, release notes that would make it easy
to find/generate a changeset/changelog between specific versions or even
find which
This is probably related to the permanentMAC address matching, which was
invalid and got dropped in newer version of Netplan, as MAC address
matching is not supposed to be used on virtual interfaces (such as the
Loopback interface).
Could you please try removing the "match. macaddress:
11 matches
Mail list logo
