Bug 1768771

Summary: [sriov] sriovnetworknodepolicies CR cannot be shown in 'Provided APIs' from Webconsole
Product: OpenShift Container Platform Reporter: zhaozhanqi <zzhao>
Component: Management ConsoleAssignee: Cyril <cajieh>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: high Docs Contact:
Priority: high    
Version: 4.3.0CC: aos-bugs, jokerman, pliu, spadgett, yanpzhan
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-01-23 11:10:52 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:
Attachments:
Description Flags
picture from console none

Description zhaozhanqi 2019-11-05 08:52:22 UTC 
Description of problem:
Given the cluster and setup with sriov-network-operator subscribed. Check the webconsole installed Operators-->SR-IOV Network Operator -->Overriew-->Provided APIs, the CR sriovnetworknodepolicies did not be shown.  it works well in cli:


oc get sriovnetworknodepolicies.sriovnetwork.openshift.io
NAME              AGE
default           4d4h
intel-netdevice   3d21h

Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2019-10-31-003134
quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.3.0-201911010555-ose-sriov-network-operator

How reproducible:
always

Steps to Reproduce:
1. Given the baremetal cluster is setup
2. installed the sriov-network-operator with registry 'redhat-operators-art'
3. Check the overriew from installed operator from webconsole

Actual results:
The sriovnetworknodepolicies CR cannot be shown. so it also cannot create new CR from webconsole

Sriov Network and Sriov Network Node State can be shown.

Expected results:
should be able to show sriovnetworknodepolicies and create new CR.

Additional info:
Comment 1 zhaozhanqi 2019-11-05 08:53:34 UTC 
Created attachment 1632873 [details]
picture from console
Comment 3 Samuel Padgett 2019-11-06 20:12:09 UTC 
This issue only exists in 4.3.
Comment 5 Samuel Padgett 2019-11-09 15:23:24 UTC 
No doc update needed as this was never in a shipped release. Clearing needinfo as we were able to reproduce.
Comment 6 Yanping Zhang 2019-11-13 07:06:08 UTC 
Payload: 4.3.0-0.nightly-2019-11-13-004353
Tested on OCP 4.3 env with above version. Install the sriov-network-operator with registry 'redhat-operators-art', then check the overview page of the installed operator "SR-IOV Network Operator", there is Sriov Network Node Policy with "Create Instance" button, and could create instance successfully.
Comment 8 errata-xmlrpc 2020-01-23 11:10:52 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, 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