Created attachment 1806980 [details] screenshot with bz Description of problem: After installing the operator I want to define a network attachment definition, and I cannot do so as it says the operator is missing. Version-Release number of selected component (if applicable): 4.8.2 of OCP and 4.8.0 of the operator. How reproducible: This is during the hackathon and was confirmed by others. Steps to Reproduce: 1. Fresh cluster. Install and configure the operator. 2. Then, in the GUI, click on Networking/Network Attachment definitions. (There should be none) 3. Click on create network attachment definition. 4. It states, under network type: Warning alert:Missing installed operators OpenShift Virtualization Operator or SR-IOV Network Operator needs to be installed on the cluster, in order to pick the Network Type. Actual results: Cannot create nad Expected results: Can create nad Additional info:
Thanks for reporting it. It seems to me like a UI bug, but before we move it one, I'd like to clarify few things: By "operator" you mean OpenShift Virtualization? This happens during the installation or once it is completed? Does this recover after a while? Could you list net-attach-def objects through `oc`? So we confirm it is available on the backend.
I can confirm this does not resolve over time (at least overnight). In my case, I installed 4.7.19, updated to candidate-4.8.rc3, then to 4.8.2. I ensured the OpenShift Virtualization operator updated successfully to 4.8.2. Now after having successfully deployed a VM in the cluster, I want to create a Network Attachment Definition, but the UI says the operator is not installed. The resources are available, it does just appear to be a UI issue that prevents creation. [root@ocp4-bastion artifacts]# oc get net-attach-def -A No resources found [root@ocp4-bastion artifacts]# oc api-resources | grep net-attach network-attachment-definitions net-attach-def k8s.cni.cncf.io/v1 true NetworkAttachmentDefinition
(In reply to Petr Horáček from comment #1) > Thanks for reporting it. It seems to me like a UI bug, but before we move it > one, I'd like to clarify few things: > > By "operator" you mean OpenShift Virtualization? > This happens during the installation or once it is completed? > Does this recover after a while? > Could you list net-attach-def objects through `oc`? So we confirm it is > available on the backend. Yes, the openshift virtualization operator. It installs, I setup a template, spin up a virtual machine. I have not checked the backend... You mean like this, @phoracek ? [root@ocp4-bastion nfs]# oc get net-attach-def --all-namespaces No resources found
That's what I meant, thanks. It seems to be an issue with the UI's detection of available features. Moving to the UI component. Feel free to move it back if this ends up being a backend issue.
verified on master
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