Bug 1854997
| Summary: | Cannot access logs in kibana with the managed deployment orchestrated by the cluster logging operator | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | OpenShift BugZilla Robot <openshift-bugzilla-robot> |
| Component: | Logging | Assignee: | Jeff Cantrill <jcantril> |
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.3.z | CC: | aos-bugs, bgottfri, brian_mckeown, brueckner, cewong, decarr, ewolinet, ikarpukh, jason.greene, jcantril, jtpape, nbziouec, periklis, pweil, rkonuru, smerrow, tnakajo, wili, yhuang |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | 4.3.z | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-08-05 10:54:08 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: | 1835396 | ||
| Bug Blocks: | 1854304 | ||
|
Comment 3
Anping Li
2020-07-13 11:32:29 UTC
Verified on IBM ROKS with CI build 4.3.0-0.ci-2020-07-13-135117 @Cesar Wong One of customers in IBM Cloud tried but it doesn't work. Can you help this? >I see https://bugzilla.redhat.com/show_bug.cgi?id=1854997 that said Verified on IBM ROKS with CI build 4.3.0-0.ci-2020-07-13-135117 >But I see the latest Operator version for 4.3 is 4.3.29-202007061006.p0 provided by Red Hat, Inc >It's update on 0706, I have tried again, it's not work. > >And I found an error when build ES pod: >Elasticsearch node is not ready to accept HTTP requests yet [503] >And the kibana still show that error. @tnakajo I verified with a build from our CI system because the build cannot become official until it's verified first (chicken/egg). If you notice the date of the build that I verified with (Jul 13) and the build that the customer is trying to test with (Jul 06), the build they are trying does not have the fix yet. An official build with the fix will have to be later than Jul 13. @Cesar Wong Thank you for the quick resonse. I wonder today is July 27. Did you mean the official build with the fix has been released already?? @Cesar Wong The customer tested last friday. But we want to know now is how to obtain the fix for IBM ROKS with CI build 4.3.0-0.ci-2020-07-13-135117. The fix will be published to the marketplace as a new version of the logging/elasticsearch operator. However, all I can see is that the fix is merged and verified, I don't know when it will be published. @jcantril can you help? @jcantril @Cesar Wong Another customer reported that their ROKS version is 4.3.28 and they can not use the 2 operator image as below: Channel 4.3 Elasticsearch Operator Version: elasticsearch-operator.4.3.29-202007061006.p0 Channel 4.5 Elasticsearch Operator Version: elasticsearch-operator.4.5.0-202007172106.p0 Could you tell us when it will be published? how to get the fixed elasticsearch-operator with ROKS 4.3.28? and tell us the the name/new version of the logging/elasticsearch operator? @jcantril @Cesar Wong Could you update asap? I have 4 customers waiting for the information. Could you tell us asap when the new version of the logging/elasticsearch operator will be published for 4.3.x Marketplace? @jcantril @Cesar Wong Could you respond to me with any updates? (In reply to tnakajo from comment #10) > @jcantril @Cesar Wong > Channel 4.3 Elasticsearch Operator Version: > elasticsearch-operator.4.3.29-202007061006.p0 You should only ever use the 4.3 operator on a 4.3 cluster. > Could you tell us when it will be published? how to get the fixed > elasticsearch-operator with ROKS 4.3.28? and tell us the the name/new > version of the logging/elasticsearch operator? I am a member of the engineering team and do not control the schedule of the releases. This change will be shipped with the errata defined https://bugzilla.redhat.com/show_bug.cgi?id=1854997#c2 and looks to target "Release date 2020-Aug-05" Thank you. We expact see the new version of the logging/elasticsearch operator in the market place on 2020-Aug05. 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.3.31 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-2020:3180 |