[13:22] <p3lim> hey, when I set up a bond + slaves using netplan on networkd the bond gets a randomized MAC (which is fine), but it also sets this MAC on the two slace interfaces, making netplan matching against MAC broken
[13:22] <p3lim> was asked to ask this here instead
[13:22] <patdk-lap> what version are you using?
[13:23] <patdk-lap> ya, not seeing that issue here at all
[13:23] <patdk-lap> can you dump out 'ip link'
[13:25] <p3lim> sec, rebooting the box right now
[13:31] <p3lim> this was on 22.04, systemd 249, netplan 0.105
[13:36] <p3lim> patdk-lap: here's the before and after output from ip link, masked the MACs: https://paste.debian.net/1315837/
[13:36] <p3lim> (had to write it myself since I'm sitting in a virtual console)
[13:36] <p3lim> since the two slace interfaces suddenly have a different MAC from their original I cannot use match.macaddress in netplan any more
[13:37] <p3lim> and netplan complains about this when I first applied it; "bond0: (slave slave0): invalid new link 3 on slave"
[13:37] <p3lim> same error on both slave interfaces
[13:38] <patdk-lap> hmm, that wasn't the output of ip link
[13:38] <patdk-lap> the whole point of bond is they are suppose to have the same mac, if they do not, bond will not function
[13:38] <patdk-lap> and your switch will be really confused
[13:39] <p3lim> sure, I get that, but usually bond takes the MAC from one of the slave interfaces
[13:39] <p3lim> it doesn't mangle the slaves
[13:39] <p3lim> which makes it impossible for me now to manage them further with netplan
[13:39] <patdk-lap> I have no issues in netplan with my bonds
[13:40] <p3lim> I assume you don't use match.macaddress on your slaves
[13:40] <p3lim> which I have to use
[13:40] <patdk-lap> not since the bug was fixed, nope
[13:41] <p3lim> if netplan would use the "permaddr" mac this would be fine
[13:41] <p3lim> but it doesn't
[13:43] <p3lim> if I run netplan apply again now it complains "Cannot find unique matching interface for slaveX" and brings the whole bond down, and the state is so broken I need to reboot to fix it
[13:48] <p3lim> patdk-lap: which netplan version do you have?
[13:48] <patdk-lap> 0.106.1
[13:49] <p3lim> that's why it works for you :)
[13:49] <patdk-lap> why is yours so old?
[13:49] <p3lim> it was fixed in 0.106: https://launchpad.net/ubuntu/+source/netplan.io/0.106-0ubuntu1
[13:50] <p3lim> dunno, it's the latest I can get from the apt repos on jammy
[13:50] <patdk-lap> nope
[13:51] <patdk-lap> jammy only has 0.104
[13:51] <patdk-lap> jammy-updates has 0.106
[13:51] <patdk-lap> not sure where 0.105 came from
[13:51] <JanC> you should have 0.106.1 on jammy
[13:53] <p3lim> just did a full update, still only have 0.105
[13:53] <JanC> are you sure you have jammy-updates configured properly?  (with a working, up-to-date mirror!)
[13:53] <p3lim> using archive.ubuntu.com for jammy and jammy-updates
[13:54] <patdk-lap> hmm, released in sept, so, midly updated mirror :)
[13:58] <JanC> and "apt show -a netplan.io" doesn't show any newer versions?
[13:58] <p3lim> nope
[13:58] <p3lim> I'm just gonna bump this server to 24.04
[13:59] <JanC> and archive.ubuntu.com isn't pointed at some other (out-of-date) mirror using /etc/hosts or so?
[13:59] <patdk-lap> if you cannot locate netplan.io 0.106
[13:59] <patdk-lap> I'm not sure an upgrade will even work
[14:02] <JanC> (I hope no hosting companies hijack DNS to point people to their own outdated mirror or such?)
[14:03] <JanC> patdk-lap: certainly you want to know why it's not working first, because it could happen again...
[14:03] <p3lim> JanC: nope, verified with dig too
[14:03] <patdk-lap> hmm?
[14:03] <p3lim> maybe it's an outdated CDN, not sure
[14:04] <patdk-lap> if he cannot find the netplan package, it is unlikely to be able to find the packages needed to upgrade to 24.04
[14:04] <p3lim> do-release-upgrade seems to work fine
[14:04] <JanC> p3lim: when you run "apt update", does it actually check a jammy-updates repository
[14:04] <p3lim> yes
[14:05] <JanC> do-release-upgrade will fix your sources.list if it was wrong, I guess
[14:05] <JanC> during upgrade
[14:41] <p3lim> netplan on 24.04 works fine, on version 1.0
[14:41] <p3lim> well, almost fine
[14:41] <p3lim> while it's been updated to use PersistentMACAddress for creating the networkd configuration it still uses MACAddress to check if the link exists
[14:42] <p3lim> it doesn't seem to pose a real problem, just unnecessary log output that is false
[14:42] <p3lim> I will create a ticket about that
[14:43] <znf> I'll never understand why ubuntu-server depends on multipath.. 
[14:50] <patdk-lap> hmm, I dont have multipath installed
[14:51] <patdk-lap> ah, cause I only have minimal installed, not server
[14:58] <znf> yeah, still weird that it's a dependency 
[14:59] <JanC> seems like even 'ubuntu-server-minimal' has quite some (for many) unnecessary dependencies...   :-/
[15:09] <patdk-lap> I personally never understood os-prober, I get it's purpose, but seems useless on a server and really slows down kernel installs
[15:20] <trippeh> also it will fuck up your VM hosts :)
[15:37] <JanC> that seems to be a dependency of grub, calamares & ubiquity; after install I suppose only GRUB uses it...
[15:38] <JanC> and even there it's only recommended apaprently
[15:38] <JanC> so at least you can remove it if you want   :)
[15:39] <JanC> (and IIRC you can also disable its use?)
[15:49] <JanC> I think editing /etc/default/grub or creating (e.g.) /etc/default/grub.d/no-os-prober.cfg adding "GRUB_DISABLE_OS_PROBER=true" in it should do it?
[15:49] <patdk-lap> I always remove it
[15:50] <JanC> yeah, you can, because it's only a recommendation
[17:52] <Bombo> hi
[17:52] <Bombo> when i systemctl start nfs-kernel-server i get 'Condition check resulted in Kernel Module supporting RPCSEC_GSS being skipped.' in the syslog, how do i disable that check or rpcsec_gss?
[17:53] <jafa> question - can the full-disk-encryption support be configured to use TPM rather than a password? goal is to tied the disk to the hw, not prevent the server from working
[17:55] <Bombo> i guess its because /etc/krb5.keytab when i status rpc-gssd i get condition path exist was not met
[17:56] <Bombo> is that file part of any package?
[17:56] <patdk-lap> no, you have to create it, for your krb5 enviroment
[17:57] <Bombo> i don't have a krb5 environment
[17:57] <Bombo> i just want nfs
[17:58] <Bombo> (nfs-server)
[18:01] <Bombo> this is 20.04, does 22.04 or 24.04 provide that file?
[18:02] <Bombo> or does the nfs-server work without it?
[18:02] <JanC> is it a problem?
[18:02] <Bombo> well i cant start the nfs-server because of it
[19:10] <rfm> Bombo, I got that message last time I started nfs-server (on my new 24.04 instance) but despite the message nfs service started just fine
[19:16] <rfm> Bombo, and I see on my 20.04 server that message comes out at every boot
[19:51] <mybalzitch> how do I disable scanning for BTRFS filesystems on boot, or can I
[21:30] <Bombo> rfm: hm weird so there must be a different reason that it doesn't work, thx for that info