Description of problem: When set the numVfs more than total num. After a while, the sriov-network-config-daemon become Crash Version-Release number of selected component (if applicable): quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.2.0-201908041300-ose-sriov-dp-admission-controller quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.2.0-201908051019-ose-sriov-network-config-daemon How reproducible: always Steps to Reproduce: 1. install sriov operator 2. Add SriovNetworkNodePolicy and set numVfs more than total num 3. Check the sriov-network-config-daemon Actual results: 3. sriov-network-config-daemon become crash Expected results: network-resources-injector can block this Additional info:
The validation of user config data needs to happen during custom resource creation, which requires an admission controller for SriovNetworkNodePolicy API. Since it's a new feature, we plan to support this feature in 4.3.
Solved by this Jira story https://jira.coreos.com/browse/SDN-514
Verified this bug with new added webhook image
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0062