After lock/unlock the controller, ACC100 behavior was like you commented, without any status info in the "system host-device-show" and I can check the status and info using "kubectl get sriovfecnodeconfigs.sriovfec.intel.com -n sriov-fec-system controller-0 -o yaml".
I opened this launchpad because for N3000 after lock/unlock, the status info appear in the "system host-device-show".
I configured both ACC100 and N3000 using sriov-fec-operator method following this document https:/ /docs.starlingx .io/node_ management/ kubernetes/ hardware_ acceleration_ devices/ configure- sriov-fec- operator- to-enable- hw-accelerators -for-hosted- vran-containari zed-workloads. html
After lock/unlock the controller, ACC100 behavior was like you commented, without any status info in the "system host-device-show" and I can check the status and info using "kubectl get sriovfecnodecon figs.sriovfec. intel.com -n sriov-fec-system controller-0 -o yaml".
I opened this launchpad because for N3000 after lock/unlock, the status info appear in the "system host-device-show".
So the wrong behavior is populate device status info for N3000, I think this https:/ /bugs.launchpad .net/starlingx/ +bug/1996109 can be used to fix it.