Bug 1814919
| Summary: | SR-IOV Operator panic when numVfs set to 0 | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | zenghui.shi <zshi> | |
| Component: | Networking | Assignee: | Peng Liu <pliu> | |
| Networking sub component: | SR-IOV | QA Contact: | zhaozhanqi <zzhao> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | high | |||
| Priority: | high | |||
| Version: | 4.4 | |||
| Target Milestone: | --- | |||
| Target Release: | 4.5.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1814921 1815319 (view as bug list) | Environment: | ||
| Last Closed: | 2020-07-13 17:22:38 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 1814921, 1815319 | |||
|
Description
zenghui.shi
2020-03-19 02:31:59 UTC
Setting 'numVfs' set to 0 in the policy doesn't make sense. If users want to reset VF number to 0, they shall just remove the policy. So I will update the CRD to prevent users from setting 'numVfs' to 0 in the CR. Verified this bug on 4.5.0-202003250931
cat vfnum0
`
apiVersion: sriovnetwork.openshift.io/v1
kind: SriovNetworkNodePolicy
metadata:
name: without-netdevice
namespace: openshift-sriov-network-operator
spec:
mtu: 1500
nicSelector:
pfNames:
- ens3f1
rootDevices:
- '0000:5e:00.1'
vendor: '15b3'
nodeSelector:
feature.node.kubernetes.io/sriov-capable: 'true'
numVfs: 0
resourceName: withoutnetdevice
`
#oc create -f vfnum0
Error from server (numVfs(0) in CR without-netdevice is not allowed): error when creating "vfnum0": admission webhook "operator-webhook.sriovnetwork.openshift.io" denied the request: numVfs(0) in CR without-netdevice is not allowed
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:2409 |