+++ This bug was initially created as a clone of Bug #1809498 +++ We are likely still awaiting proper images from ART since this is trying to boot an ES5 node. ES6 will be used in 4.5. What images does the EO say it should be using? What images does the CLO say it should be using? --- Additional comment from Anping Li on 2020-03-10 03:04:39 UTC --- Yes, there isn't 4.5 channel in operator-registry redhat-operatrors-art. Waiting art. --- Additional comment from Jeff Cantrill on 2020-04-14 20:08:20 UTC --- Please retest now there are available images for 4.5. One suspicion I have is if you upgrade CLO before EO that records will be written to an index with a '-write' suffix and thus the new indexmanagement will be broken
I tested upgrade from 4.4 to 4.5 again, still hit the issue in https://bugzilla.redhat.com/show_bug.cgi?id=1809498#c0. For the issue in https://bugzilla.redhat.com/show_bug.cgi?id=1809498#c4, it didn't appear. I checked the logging 4.4, the env var `POD_IP` was added to the elasticsearch when deploying logging 4.4. I also tested upgrade from 4.3 to 4.5, the issue in https://bugzilla.redhat.com/show_bug.cgi?id=1809498#c4 didn't appear, but I hit the same issue in https://bugzilla.redhat.com/show_bug.cgi?id=1809498#c0. The env var `POD_IP` wasn't added to the elasticsearch when deploying logging 4.3. It seems the fix PR https://github.com/openshift/elasticsearch-operator/pull/316 only fixes the issue in https://bugzilla.redhat.com/show_bug.cgi?id=1809498#c4. @IgorKarpukhin, is my understanding correct? 4.5 logging images are from 4.5.0-0.ci-2020-04-22-212726.
Yes, that's correct. This fix isn't backported to 4.4 yet. I'm working on it.
Qiaoling Tang could you please post the logs from catalog operator during the upgrade from 4.3 to 4.4? Ex: oc logs -f catalog-operator-7648d9cff4-rqx9j -n openshift-operator-lifecycle-manager
Catalog operator logs: http://pastebin.test.redhat.com/858655 Cluster version: 4.4.0-0.nightly-2020-04-23-192521
Moving to ON_QA. Qiaoling if you feel it is reasonable to move this bug to Verified please do so.,
Per the discussions in the above, I move this to VERIFIED. Feel free to reopen this bz if you have any problems related to this issue.
*** Bug 1829971 has been marked as a duplicate of this bug. ***
This issue has been fixed by this PR: https://github.com/openshift/elasticsearch-operator/pull/316. Not a bug anymore.
moving back to verified. the release process will close this when appropriate.
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:2409