Proxmox set Device identifier as NIC identifier in interfaces when creating host in Foreman. Operating system should set the Device Identifier during its network configuration and if the user, in this case proxmox itself, specifies a distinct name then it is important that this name works for the corresponding OS and compute resource.
The snippet `preseed_netplan_generic_interface (which is part of the Ubuntu provisioning process) results in a different config depending on whether the Device Identifier is given or not. Since the default value put by Proxmox is same as nic identifier (generally net0) results in incorrect network configuration.
How reproducible:
Deploy an Ubuntu 22.04 host with Proxmox as compute resource.
Steps to Reproduce:
Create a new Ubuntu 22.04 host
Choose Proxmox as compute resource
In the network configuration, leave the Device Identifier field blank (as it is the default)
Actual results:
After the host performs its network configuration, it cannot retrieve the finish template due to an incorrect network setup (resulting in DNS issues).
Expected results:
The host does not run into a DNS issue and is able to successfully build the host with correct network configuration and DNS resultion.
Additional info:
With the same setup on vSphere, it results in a different (working) network configuration.
Proxmox set Device identifier as NIC identifier in interfaces when creating host in Foreman. Operating system should set the Device Identifier during its network configuration and if the user, in this case proxmox itself, specifies a distinct name then it is important that this name works for the corresponding OS and compute resource.
The snippet `preseed_netplan_generic_interface (which is part of the Ubuntu provisioning process) results in a different config depending on whether the Device Identifier is given or not. Since the default value put by Proxmox is same as nic identifier (generally net0) results in incorrect network configuration.
How reproducible: Deploy an Ubuntu 22.04 host with Proxmox as compute resource.
Steps to Reproduce:
Actual results: After the host performs its network configuration, it cannot retrieve the finish template due to an incorrect network setup (resulting in DNS issues).
Expected results: The host does not run into a DNS issue and is able to successfully build the host with correct network configuration and DNS resultion.
Additional info: With the same setup on vSphere, it results in a different (working) network configuration.