[BM-IPI] The effect of this bug are the same of: https://bugzilla.redhat.com/show_bug.cgi?id=2094090 
In this case using a custom VLAN name rather then the "name.number" standard leave again the VM in provisiong state.

OCP 4.12.z

Install a new cluster using a VLAN on top of a bond without a 'dot' in the name.

Machines keeps the Provisoned State

Machines move on Running state

The workaround described on https://access.redhat.com/solutions/6964105 works also on our scenario.

Looking at: https://review.opendev.org/c/openstack/ironic-python-agent/+/848866/1/ironic_python_agent/hardware.py

The blow funcion seems only contemplate a VLAN with a ('.') in it:
======================================
    def _is_vlan(self, interface_name):
        # A VLAN interface does not have /device, check naming convention
        # used when adding VLAN interface
        interface, sep, vlan = interface_name.partition('.') <---------- THIS
        return vlan.isdigit()
======================================