Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2022596

Summary: ServiceAccount in manifests conflicts with OLM
Product: OpenShift Container Platform Reporter: OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component: NetworkingAssignee: Ben Nemec <bnemec>
Networking sub component: kubernetes-nmstate-operator QA Contact: Aleksandra Malykhin <amalykhi>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: aos-bugs, mifiedle
Version: 4.8   
Target Milestone: ---   
Target Release: 4.9.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2023529 (view as bug list) Environment:
Last Closed: 2021-11-22 21:47:05 UTC Type: ---
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: 2022447, 2030117    
Bug Blocks: 2023529    

Description OpenShift BugZilla Robot 2021-11-12 06:16:11 UTC
+++ This bug was initially created as a clone of Bug #2022447 +++

Description of problem: In our OLM manifests we define the service account to be used for the operator. This is no longer allowed by OLM as it wants to manage the service account itself and having it defined in the manifests causes a conflict. We need to remove the service account on our side and let OLM handle it.


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


How reproducible: Always


Steps to Reproduce:
1. Attempt to build the operator in Brew
2.
3.

Actual results: Build fails


Expected results: Build succeeds


Additional info:

--- Additional comment from bnemec on 2021-11-11 21:04:08 UTC ---

*** Bug 2022489 has been marked as a duplicate of this bug. ***

Comment 3 Aleksandra Malykhin 2021-11-18 09:04:38 UTC
Verified on OCP Cluster version is 4.9.0-0.nightly-2021-11-18-000209

Nmstate operator build 4.9.0-202111151129 was succeeded

For additional check I installed it from brew:

Steps to verify:
1. Install the cluster
2. Check the version of the nmstate in UI  ( it is 4.9.0-202111020858, doesn't have the fix)
3. Follow the instructions to get the brew build available https://hackmd.io/0vbbJdZ7RXem69vCWI61ug?view
3.1. Change the image id number from the last step to the latest or the one containing the fix (134817 in my case)
'image: registry-proxy.engineering.redhat.com/rh-osbs/iib:<image-id>'

4. Go to the UI OCP platform and install Nmstate https://access.redhat.com/documentation/en-us/openshift_container_platform/4.9/html/networking/kubernetes-nmstate#installing-the-kubernetes-nmstate-operator_k8s-nmstate-operator
 Note: Check that the version is correct

The result: 
In the installing page I see that the namespace is pre-configured, no need to create it manually
"Operator recommended Namespace: openshift-nmstate

Info alert:
Namespace creation
Namespace openshift-nmstate does not exist and will be created."


5. Create the instance https://console-openshift-console.apps.ocp-edge-cluster-0.qe.lab.redhat.com/k8s/ns/openshift-nmstate/operators.coreos.com~v1alpha1~ClusterServiceVersion/kubernetes-nmstate-operator.4.9.0-202111151129/
6. Verify that the nmstate is installed on the cluster 
[kni@provisionhost-0-0 ~]$ oc get pods -n openshift-nmstate -w
NAME                                    READY   STATUS    RESTARTS   AGE
nmstate-cert-manager-7bd498f5b8-6h84c   1/1     Running   0          2m1s
nmstate-handler-94thx                   1/1     Running   0          2m
nmstate-handler-cztbp                   1/1     Running   0          2m
nmstate-handler-nst7x                   1/1     Running   0          2m
nmstate-handler-qk7fc                   1/1     Running   0          2m
nmstate-handler-wl42n                   1/1     Running   0          2m
nmstate-operator-6b5b64d797-jtn9n       1/1     Running   0          12m
nmstate-webhook-7b75874c59-j67v5        1/1     Running   0          2m
nmstate-webhook-7b75874c59-w7sph        1/1     Running   0          2m1s

[kni@provisionhost-0-0 ~]$ oc get nns worker-0-0 -o yaml

Comment 5 errata-xmlrpc 2021-11-22 21:47:05 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 (OpenShift Container Platform 4.9.8 bug fix 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/RHBA-2021:4712