Why does a VNI attachment fail?

Virtual Private Cloud 4.20 and later Bare metal worker nodes only RHCOS only

You try to attach a virtual network interface (VNI) for OpenShift Virtualization, but the attachment does not succeed.

A VNI attachment can fail if the VNI does not exist, if it is created in a different zone than the worker node, or if the account does not have the required permissions to manage cluster and VPC resources.

To resolve the issue,

verify that the VNI exists, confirm the zone placement, and review the IAM permissions and attachment status.

1. Verify that the VNI exists in your VPC.

   ibmcloud is virtual-network-interfaces
   

2. Check the VNI zone and compare it with the worker node zone.

   ibmcloud is virtual-network-interface <vni_id>
   oc get node <node_name> -L topology.kubernetes.io/zone
   

3. Review the IAM permissions for the user or service ID that you are using.

   ibmcloud iam user-policies <user_email>
   

4. Check the VNI attachment status for the cluster.

   ibmcloud ks vni ls --cluster-id <cluster_id>
   

5. Review the prerequisites and zone requirements in Managing virtual network interfaces for OpenShift Virtualization.