[SOLVED] Web interface regression? - vmbrX naming convention being enforced again

[justinclift]

After upgrading our 2 trial Proxmox servers to PVE 8.2.2, the Linux bridges with naming that doesn't follow the (unhelpful) "vmbrX" convention are no longer shown in the web interface. They're still appearing via the standard linux cli tools as expected.

The allowing of useful bridge names was one of the items in the PVE 8.2 release notes:

Allow arbitrary names for bridges. Previously, bridges had to be named vmbrN to be recognized

The associated bug report isn't mentioning any kind of problems encountered, nor rollback of the capability:

https://bugzilla.proxmox.com/show_bug.cgi?id=545

Is this an unexpected regression in the webUI, or is something else probably going on?

 

[shanreich]

Can you post the output of the following commands (make sure to replace <nodename> with your actual node name)?

cat /etc/network/interfaces
ip -details -json -pretty l show type bridge
pvesh get nodes/<nodename>/network --output json-pretty

 

[justinclift]

@shanreich Found the problem. It looks like the Proxmox web interface is ignoring things defined under /etc/network/interfaces.d/.

After moving the bridge definitions from individual files in that directory to be inside the /etc/network/interfaces file itself, they're showing up again.

This probably isn't a regression after all, as moving the bridge definitions into that subdirectory was a recent process refinement on our end.

I've not been using Proxmox for long enough to know whether the webUI should be including files in that subdirectory or not.

If it should be, then a ticket will likely need to be filed somewhere.

 

[shanreich]

Makes sense, no we currently do not support showing interfaces from this folder, since the web UI only handles /etc/network/interfaces

 

[justinclift]

Thanks @shanreich. Looks like we'll need to update our process again to ignore the interfaces.d folder. No worries.