Operational Defect Database
BugZero found this defect 80 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
F5 | 1341701
Unable to launch tenant, as VF interface is getting incorrect name while attaching to tenant.
Last update date:
4/30/2024
Affected products:
F5OS
F5OS F5OS
Affected releases:
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
Fixed releases:
No fixed releases provided.
Description:
Bug ID 1341701: Unable to launch tenant, as VF interface is getting incorrect name while attaching to tenant. ... During this process, VFs fail and unable to retrieve. ... Thus, resource temporarily unavailable error occurs. ... Impact ... Tenant launch is unsuccessful and unable to connect to the tenant console or tenants' management connection. ... Conditions ... In kubectl get pods -A output, the tenant pod goes into Init:0/1 state. ... 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. ... Remove ice, iavf drivers using the following commands, a. ... Load ice and iavf drivers using the following commands a. ... 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.
