Last Modified: Nov 20, 2024
Affected Product(s):
F5OS F5OS
Known Affected Versions:
F5OS-A 1.3.0, F5OS-A 1.3.1, F5OS-A 1.3.2, F5OS-A 1.4.0, F5OS-A 1.5.0, F5OS-A 1.5.1, F5OS-A 1.5.2, F5OS-A 1.7.0, F5OS-A 1.8.0
Opened: Aug 29, 2023 Severity: 2-Critical
On r2x00/r4x00 related systems, tenant launch fails with an error in ConfD tenant status leaf: "[default/virt-launcher-bip1-1-9sblf:sriov-net3-bip1]: error adding container to network "sriov-net3-bip1": failed to set up pod interface "net7" from the device "x557_4": failed to set netlink MAC address to 00:94:a1:db:bd:0c: resource temporarily unavailable" Linux network manager udev rules and sriov cni try to access the VF and change the interface name of VF. During this process, VFs fail and unable to retrieve. Thus, resource temporarily unavailable error occurs.
Tenant launch is unsuccessful and unable to connect to the tenant console or tenants' management connection.
On r4x00 or r2x00 based systems: 1. In kubectl get pods -A output, the tenant pod goes into Init:0/1 state. default virt-launcher-bip1-1-t6rkh 0/1 Init:0/1 0 36s 2. And in kubectl events, "resource temporarily unavailable" occurs on one of the VFs. 3. In /sys/class/net folder unable to see the below VF interfaces. Instead, some interfaces point to ensp* names which are wrong. Actual result should be as follows: [root@appliance-1 ~]# ls /sys/class/net apigw-dummy-1 lcd sfp_7 sfp_p6v0503 veth0c09f23b veth6cec172f vethea3619d5 x557_p1v1100 x557_p3v1902 br_appliancenet lcd-intf sfp_8 sfp_p7v0900 veth2765115 veth80370796 vetheccdd5fb x557_p1v1101 x557_p3v1903 cni0 lo sfp_p5v0100 sfp_p7v0901 veth3f32fd86 veth82a8440b vethf4081a48 x557_p1v1103 x557_p4v1d00 default-intf mgmt sfp_p5v0101 sfp_p7v0903 veth4ab82fc6 veth8cda0b4d x557_1 x557_p2v1500 x557_p4v1d01 docker0 mgmt0-system sfp_p5v0102 sfp_p8v0d01 veth50d18b0 veth9e8b2e8c x557_2 x557_p2v1502 x557_p4v1d02 dummy0 sfp_5 sfp_p6v0500 sfp_p8v0d02 veth5fe12ffd vethac6590f8 x557_3 x557_p2v1503 flannel.1 sfp_6 sfp_p6v0502 sfp_p8v0d03 veth64783052 vethb688f03e x557_4 x557_p3v1901
1. Move tenants to configured state 2. Remove ice, iavf drivers using the following commands, a. "rmmod /lib/modules/3.10.0-1160.71.1.F5.el7_8.x86_64/updates/drivers/net/ethernet/intel/ice/ice.ko" b. "rmmod /lib/modules/3.10.0-1160.71.1.F5.el7_8.x86_64/updates/drivers/net/ethernet/intel/iavf/iavf.ko" 4. Load ice and iavf drivers using the following commands a. "insmod /lib/modules/3.10.0-1160.71.1.F5.1.el7_8.x86_64/updates/drivers/net/ethernet/intel/ice/ice.ko" b. "insmod /lib/modules/3.10.0-1160.71.1.F5.1.el7_8.x86_64/updates/drivers/net/ethernet/intel/iavf/iavf.ko" 5. Run config_ice_vfs.sh script present in /usr/omd/scripts/ folder using - "sh /usr/omd/scripts/config_ice_vfs.sh" 6. Wait until script is completed and VFs are created correctly. 6. Move tenants to running state and check the running state of tenant, after some time.
None