Description of problem: Elastic search operator fails to update from 4.5 to 4.6. Elastic search operator updation goes into the pending state with below error: ~~~ kind: ServiceAccount message: Policy rule not satisfied for service account name: elasticsearch-operator status: PresentNotSatisfied version: v1 ~~~ ~~~ kind: PolicyRule message: cluster rule:{"verbs":["*"],"apiGroups":[""],"resources":["pods","pods/exec","services","endpoints","persistentvolumeclaims","events","configmaps","secrets","serviceaccounts","services/finalizers"]} ~~~ with ElasticSearch subscription throwing error Error"error validating existing CRs agains new CRD's schema: elasticsearches.logging.openshift.io: error validating custom resource against new schema" Version-Release number of selected component (if applicable): 4.6 Expected results: Elastic search operator should update to 4.6
Closing this as a duplicate as it is a result of an issues with certs. Without further investigation the work around may be to delete the es pods and allow them to restart with the same certs "oc delete pods -l component=es" *** This bug has been marked as a duplicate of bug 1906641 ***
Reopen because of need for CSV update
@ewo I am able to reproduce the error with the following steps Platform: OCP 4.5.13 1. Install cluster logging and ES operator from the stable 4.5 CSV channel 2. Create a clo instance using the attached clo yaml 3. Manually delete the ES operator 4. Install the ES operator from the master branch and you will see the ES operator installation will fail After applying the PR (https://github.com/openshift/elasticsearch-operator/pull/630), I am able to install the 4.7 EO.
Created attachment 1749301 [details] clo yaml for reproduce the error
Sorry, I made a mistake in my above comment 12. The installation error was caused by two operatorGroups in the same namespace. After removing one, the upgrade from 4.5 to 4.6 succeeds. So I could not reproduce the error as reported by @Ashish.
I tested upgrade cluster from 4.5.28 to 4.6.13, then upgrade EO from elasticsearch-operator.4.5.0-202101140110.p0 to elasticsearch-operator.4.6.0-202101160934.p0, I was not able to reproduce the issue. $ oc get csv -n openshift-operators-redhat NAME DISPLAY VERSION REPLACES PHASE elasticsearch-operator.4.6.0-202101160934.p0 OpenShift Elasticsearch Operator 4.6.0-202101160934.p0 elasticsearch-operator.4.5.0-202101140110.p0 Succeeded
*** Bug 1918441 has been marked as a duplicate of this bug. ***
Closed. This has been moved to JIRA: https://issues.redhat.com/browse/LOG-1617