Bug 1890825 - Kibana Route not recreated after deletion
Summary: Kibana Route not recreated after deletion
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.5
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.7.0
Assignee: Hui Kang
QA Contact: Anping Li
Rolfe Dlugy-Hegwer
URL:
Whiteboard: logging-exploration
Depends On:
Blocks: 1926276
TreeView+ depends on / blocked
 
Reported: 2020-10-22 23:59 UTC by Robert Bost
Modified: 2023-09-18 00:23 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
* Previously, if you deleted a Kibana route, the Cluster Logging Operator (CLO) could not recover or recreate it. The current release fixes this issue by letting the CLO watch the route. Now, if you delete the route, the route, the Elasticsearch operator can reconcile or recreate it. (link:https://bugzilla.redhat.com/show_bug.cgi?id=1890825[*BZ#1890825*])
Clone Of:
: 1926276 (view as bug list)
Environment:
Last Closed: 2021-02-24 11:21:19 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift elasticsearch-operator pull 549 0 None closed Bug 1890825: watch route deletion in kibana controller 2021-02-19 08:56:34 UTC
Red Hat Knowledge Base (Solution) 5528881 0 None None None 2021-01-11 11:09:39 UTC
Red Hat Product Errata RHBA-2021:0652 0 None None None 2021-02-24 11:22:12 UTC

Description Robert Bost 2020-10-22 23:59:07 UTC 
Description of problem:

User deletes Route for Kibana but it is not reconciled by the Cluster Logging Operator. 

Version-Release number of selected component (if applicable): clusterlogging.4.5.0-202010090328.p0

How reproducible: Always when user deletes Route

Actual results: Route lost until user follows workaround below.

Expected results: I'd expect the Route to be reconciled. This seems to have been the behaviour before after reading the resolution in https://bugzilla.redhat.com/show_bug.cgi?id=1822152 


Additional info:
A workaround is to edit ClusterLogging resource, removing visualization section and re-add it. This results in Kibana being reinstalled.
Comment 1 Qiaoling Tang 2020-10-23 00:48:53 UTC 
I can reproduce this issue with elasticsearch-operator.4.6.0-202010221124.p0, I don't see any logs related to the route/kibana in the EO.

reproduce steps:
1. deploy logging
2. wait until all the EFK pods become Running
3. delete route/kibana

delete the kibana/kibana, and wait for the EO to recreate it, then the route/kibana back
Comment 3 Anping Li 2020-11-03 08:24:45 UTC 
Verified on elasticsearch-operator.4.7.0-202011030448.p0,clusterlogging.4.7.0-202011021919.p0
Comment 8 Oscar Casal Sanchez 2021-02-08 08:38:26 UTC 
Hello,

Is this going to be backported to 4.5 or 4.6? I can see that the bug is in VERIFIED status, but, I was not able to find the related Bugs for that versions. Could you let us about this question?

Best regards,
Oscar
Comment 9 Hui Kang 2021-02-08 14:36:16 UTC 
Hi, Oscar, yes, I will do the cherry-pick to 4.6 and 4.5
Comment 16 errata-xmlrpc 2021-02-24 11:21:19 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 (Errata Advisory for Openshift Logging 5.0.0), 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:0652
Comment 18 Red Hat Bugzilla 2023-09-18 00:23:07 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.