Bug 1969761 - sriov webhook not worked when upgrade from 4.7 to 4.8
Summary: sriov webhook not worked when upgrade from 4.7 to 4.8
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.8
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 4.9.0
Assignee: Peng Liu
QA Contact: zhaozhanqi
URL:
Whiteboard:
Depends On:
Blocks: 1977540
TreeView+ depends on / blocked
 
Reported: 2021-06-09 08:30 UTC by zhaozhanqi
Modified: 2021-10-18 17:33 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1977540 (view as bug list)
Environment:
Last Closed: 2021-10-18 17:33:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2021:3759 0 None None None 2021-10-18 17:33:39 UTC

Description zhaozhanqi 2021-06-09 08:30:13 UTC
Description of problem:
After upgrade sriov operator from 4.7 to 4.8

When deleting or new create one sriovnetworknodepolicy. Always met the error: 

Error from server (InternalError): error when creating "intel-netdevice.yaml": Internal error occurred: failed calling webhook "operator-webhook.sriovnetwork.openshift.io": the server rejected our request for an unknown reason

webhook pods logs:


0609 07:51:41.940086       1 start.go:75] handling request: {"kind":"AdmissionReview","apiVersion":"admission.k8s.io/v1beta1","request":{"uid":"46e50497-2985-46f9-8ef2-ef6c17835051","kind":{"group":"sriovnetwork.openshift.io","version":"v1","kind":"SriovNetworkNodePolicy"},"resource":{"group":"sriovnetwork.openshift.io","version":"v1","resource":"sriovnetworknodepolicies"},"requestKind":{"group":"sriovnetwork.openshift.io","version":"v1","kind":"SriovNetworkNodePolicy"},"requestResource":{"group":"sriovnetwork.openshift.io","version":"v1","resource":"sriovnetworknodepolicies"},"name":"mlx278-dpdk","namespace":"openshift-sriov-network-operator","operation":"CREATE","userInfo":{"username":"system:admin","groups":["system:masters","system:authenticated"]},"object":{"apiVersion":"sriovnetwork.openshift.io/v1","kind":"SriovNetworkNodePolicy","metadata":{"creationTimestamp":null,"managedFields":[{"apiVersion":"sriovnetwork.openshift.io/v1","fieldsType":"FieldsV1","fieldsV1":{"f:spec":{".":{},"f:isRdma":{},"f:mtu":{},"f:nicSelector":{".":{},"f:pfNames":{},"f:rootDevices":{},"f:vendor":{}},"f:nodeSelector":{".":{},"f:feature.node.kubernetes.io/sriov-capable":{}},"f:numVfs":{},"f:resourceName":{}}},"manager":"kubectl-create","operation":"Update","time":"2021-06-09T07:51:41Z"}],"name":"mlx278-dpdk","namespace":"openshift-sriov-network-operator"},"spec":{"isRdma":true,"mtu":1550,"nicSelector":{"pfNames":["ens3f1"],"rootDevices":["0000:5e:00.1"],"vendor":"15b3"},"nodeSelector":{"feature.node.kubernetes.io/sriov-capable":"true"},"numVfs":2,"resourceName":"mlx278dpdk"}},"oldObject":null,"dryRun":false,"options":{"kind":"CreateOptions","apiVersion":"meta.k8s.io/v1","fieldManager":"kubectl-create"}}}
E0609 07:51:41.940325       1 start.go:81] Request could not be decoded: no kind "AdmissionReview" is registered for version "admission.k8s.io/v1beta1" in scheme "github.com/k8snetworkplumbingwg/sriov-network-operator/pkg/webhook/scheme.go:14"
I0609 07:52:39.140624       1 start.go:181] watcher event: "/etc/tls/tls.crt": CHMOD
I0609 07:52:39.140677       1 start.go:185] modified file: /etc/tls/tls.crt


Version-Release number of selected component (if applicable):

sriov-network-operator.4.7.0-202106011747  --> 4.8.0-202106081938

How reproducible:


Steps to Reproduce:
1. launch 4.7 cluster and setup sriov operator
2.  Create one sriov policy to init the VF
3. upgrade cluster to 4.8 and upgrade sriov oprator to 4.8
4. After upgrade, try to delete the policy or create new one policy 

Actual results:


#oc create -f intel-netdevice.yaml 
Error from server (InternalError): error when creating "intel-netdevice.yaml": Internal error occurred: failed calling webhook "operator-webhook.sriovnetwork.openshift.io": the server rejected our request for an unknown reason

Expected results:

policy can be created or deleted

Additional info:

This issue can be workaround by disable webhook and enable it again.

Comment 5 zhaozhanqi 2021-06-30 03:11:09 UTC
Move this bug to verify 4.8 bugs firstly since there still no 4.9 build yet.

Comment 8 errata-xmlrpc 2021-10-18 17:33:22 UTC
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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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/RHSA-2021:3759


Note You need to log in before you can comment on or make changes to this bug.