Is systemd Predictable Interface Naming for NICs supported in VCFA?
Article ID: 449233
Updated On:
Products
Issue/Introduction
The systemd init system provides "Predictable Interface Names" which use udev rules to rename the kernel interface names like eth0 which are assigned in order of discovery.
The predictable names show the location of the devices (bus, slot) such as enp2s0 so that it is reliable across boots, as long as the device remains in the same physical position.
More information: systemd: PREDICTABLE_INTERFACE_NAMES
Environment
VCF Automation 9.x
Aria Automation 8.x
Cause
By default, the vmoperator CRD schema forces a default interface name of eth0 if the interfaces spec is omitted, or requires an explicit identifier mapping if configured.
This name is used by the bootstrap provider to explicitly rename the guest device to eth0, which suppresses systemd's consistent network device naming.
Resolution
This is not supported at present. If there are any issues with NIC naming, disable this for now such as creating this symlink as mentioned in the PREDICTABLE_INTERFACE_NAMES page:ln -s /dev/null /etc/systemd/network/99-default.link
By default, the vmoperator CRD schema forces a default interface name of eth0 if the interfaces spec is omitted, or requires an explicit identifier mapping if configured. This name is used by the bootstrap provider to explicitly rename the guest device to eth0, which suppresses systemd's consistent network device naming.
There is an open feature request for supporting systemd predictable naming. Please reach out to Broadcom Support quoting this article number (#449233) if you are interested:
Feedback
