Bug ID 1188821: FIPS partition configuration is not removed even after the chassis partition is detached from tenant

Last Modified: Apr 28, 2025

Affected Product(s):
F5OS Velos(all modules)

Fixed In:
F5OS-A 1.4.0

Opened: Nov 11, 2022

Severity: 3-Major

Symptoms

FIPS partition configuration is not removed even after the FIPS partition is detached from the tenant.

Impact

appliance-1# show tenants tenants tenant synctenant1 state unit-key-hash wtlsoWPAXj/CxXQJleNTR4aYuaQ10qNulxBWnppQmEOebQLphkh6nPN1ogkFpSSsoiNdoy9zMzwfmV8cCeZWAQ== state type BIG-IP state image BIGIP-tmos-tier2-17.1.0-0.0.1574.ALL-F5OS.qcow2.zip.bundle state mgmt-ip 10.238.160.66 state prefix-length 24 state gateway 10.238.160.254 state cryptos enabled state vcpu-cores-per-node 30 state memory 108032 state storage size 82 state running-state deployed state appliance-mode disabled state status Running state primary-slot 1 state image-version "BIG-IP 17.1.0 0.0.1574" state mac-data base-mac 14:a9:d0:15:3d:24 state mac-data mac-pool-size 1 MAC ------------------- 14:a9:d0:15:3d:24 state cpu-allocations cpu-allocation 1 cpus [ 6 7 8 11 12 13 14 15 17 18 19 20 21 22 23 30 31 32 35 36 37 38 39 41 42 43 44 45 46 47 ] state instances instance 1 synctenant1-1 instance-id 1 phase Running creation-time 2022-11-11T06:39:22Z ready-time 2022-11-11T06:39:49Z status "Started tenant instance" 4. Check ENV details after removing FIPS partition from tenant >> [root@appliance-1 IMAGES]# kubectl get pods -A NAMESPACE NAME READY STATUS RESTARTS AGE kube-system kube-multus-ds-amd64-75ckg 1/1 Running 2 107m kube-system kube-flannel-ds-t2llf 1/1 Running 2 107m kube-system coredns-6786db45bd-5r2j4 1/1 Running 2 107m kube-system klipper-lb-vknsd 2/2 Running 4 107m kube-system local-path-provisioner-5d99c5c99b-9vpxr 1/1 Running 2 107m kube-system pause-7b5dc98878-vwb7m 1/1 Running 2 107m kube-system metrics-server-68fddb5cb7-bxdq4 1/1 Running 2 107m kubevirt virt-operator-7b8b67d494-2c9nx 1/1 Running 2 106m kubevirt virt-operator-7b8b67d494-rp9kv 1/1 Running 2 106m kubevirt virt-controller-6b8c7d95dd-sjw8g 1/1 Running 2 105m kubevirt virt-api-6f779c8f89-7vn2c 1/1 Running 2 104m kubevirt virt-controller-6b8c7d95dd-9wbmf 1/1 Running 2 105m kubevirt virt-handler-j5xfv 1/1 Running 2 106m kubevirt virt-api-6f779c8f89-q2977 1/1 Running 2 104m default virt-launcher-synctenant1-1-2cg6r 1/1 Running 0 2m20s >> kubectl describe vmi synctenant1-1 Name: hnet-conf-synctenant1 Env: Name: TMM_DESCSOCK_SVC_ID Value: 10 Name: TENANT_ID Value: 2 Name: KVM_OPERATION Value: 4 Name: KVM_MEMORY Value: 113279762432 Name: TENANT_OP Value: BIGIP Name: HA_IP Value: BIGIP Name: HA_MASK Value: BIGIP Name: FIPS_PARTITION >> we didnt attach FIPS partition to tenant, still its there in config Value: syncpart1 Name: TENANT_NAME Value: synctenant1 Name: TENANT_TYPE Value: BIGIP Name: TENANT_SIZE Value: 82 Name: VLOG_INFO Value: sevbound Name: SLOT_NUM Value: 1 Actual Results: FIPS partition configuration is not removing even after de-attach the FIPS partition from tenant Expected Results: FIPS partition name should not display in describe command.

Conditions

If the tenant is created again with the same name.

Workaround

N/A

Fix Information

Fips_partition is cleared when the tenant is deleted before the delete thread handles it.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips