Upgrade Changes All The Ethernet Interface Names

[aaron.newsome]

Yes, I'm aware that I should have did a bunch of stuff prior to upgrading so that my interface names remain the same.

But I didn't. I simply upgraded and guess what, all my interface names were changed. For some reason I thought I'd be immune. I mean, I examined the posts carefully and I don't think I was running any of those brand of ethernets. After reboot, ceph was broken and all networks except the vmbr0 management network were down.

I was lucky that I had read about this issue affecting other people, and I know I was supposed to create a bunch of udev rules or whatever but I'm asking myself, should I have to?

Maybe I read somewhere that it's the kernel's fault or something like that. Wherever the issue stems from, it doesn't make it any less annoying.

Proxmox has generally been amazing software and I appreciate everything the team does, but this specific issue of interface names changing on upgrade seems like it could have been handled better.

Maybe the upgrade could recognize that "hey all your interface names are about to change, would you like me to make some udev rules so all your networks aren't broken after upgrade?". That would be nice.

 

[maxim.webster]

Maybe the upgrade could recognize that "hey all your interface names are about to change, would you like me to make some udev rules so all your networks aren't broken after upgrade?". That would be nice.

It's mentioned in the release notes for Proxmox 8.2 and you can (for further updates) change the automatism to predictable interfaces names. Link to https://pve.proxmox.com/pve-docs/pve-admin-guide.html#network_override_device_names is in the release notes, too.

 

[BobhWasatch]

Translation: I read the instructions and the forum posts but I ignored them and the things happened as described but it is someone else's fault.

 

[aaron.newsome]

That's one interpretation Bob. I'd like to think I'm helping some future upgrader avoid necessary downtime by learning from my laziness. I wasn't trying to blame anyone.

 

[maxim.webster]

That's one interpretation Bob. I'd like to think I'm helping some future upgrader avoid necessary downtime by learning from my laziness. I wasn't trying to blame anyone.

To late, been there already