=== TheCaptain8983 is now known as TheCaptain898
=== ShadowLabs2072 is now known as ShadowLabs207
=== ahasenack__ is now known as ahasenack
[19:39] <frickler> upgrading the hwe kernel on 22.04 from 6.5.x to 6.8.x has lead to interface renames, which was a bit surprising for me, is this expected? seems to affect at least the i40e driver
[19:40] <frickler> result was loss of connectivity since the supposedly "persistent" interface names were being used in the netplan config
[19:41] <ravage> I think that's at least in the kernel release notes and the noble releases notes
[19:42] <ravage> Which has the same version 
[19:42] <ravage> Not sure if there is anything on the HWE package notes
[19:48] <frickler> ravage: do you happen to have a pointer? at least I cannot find anything related in https://discourse.ubuntu.com/t/ubuntu-24-04-lts-noble-numbat-release-notes/39890
[19:48] <ravage> Probably because upgrades from 22.04 are not enabled yet
[19:49] <ravage> But it's a good reminder to put that in the upgrade notes
[19:51] <frickler> well I didn't do an upgrade to 24.04, just an update of linux-image-generic-hwe-22.04 on a 22.04 server
[19:51] <ravage> Yes which does the same kernel upgrade 
[19:52] <ravage> And for the release upgrade that will bite many more users in the backside
[19:53] <frickler> but isn't that a bit unstable for a stable LTS setup even now? or is that to be expected if one opts in for the hwe series?
[19:53] <frickler> anyway I'm out for today, thx for your updates
[19:54] <ravage> I guess you could add something to apt news yes
[20:06] <arraybolt3> frickler: if you're still around, are you able to say what the interface name was before the kernel upgrade and what it is now?
[20:06] <arraybolt3> (I know I just joined and shouldn't be able to see things before I joined but ravage pulled me in since I have Ubuntu developer connections to help fix things)
[20:07] <ravage> he said he is out for today but hopefully can get some more information soon
[20:07] <arraybolt3> Also are you absolutely, 100% sure it's the kernel change that triggered it? I get that you may not be able to just reboot the server a bunch of times for debugging, but if it is possible to boot into the older kernel, record the interface name, then boot back into the newer kernel and see if that triggers a deterministic interface name change to the new name, that would be very helpful.
[20:07] <arraybolt3> ravage: kk, I'll stick around
[20:08] <ravage> but it may explicitly be a problem with that driver
[20:09] <ravage> so that would be mainly a server problem
[20:09] <ravage> i dont think a lot of workstations have a 40 gbit port
[20:12] <ravage> https://github.com/D4M4EVER/Proxmox_Preserve_Network_Names
[20:12] <ravage> has some of the name changes
[20:13] <ravage> also maybe the script could be nice to be used in an upgrade
[20:13] <ravage> but have not looked into it. creates some systemd files with the mac addresses