-
Bug
-
Resolution: Done
-
Critical
-
Logging 5.1
-
False
-
False
-
NEW
-
NEW
-
Undefined
-
-
Logging (LogExp) - Sprint 204
Known issue in 4.6. https://bugzilla.redhat.com/show_bug.cgi?id=1964532
Description:
When the kibana pods were restarted. the non-kubeadmin user can see their index. the kibana pattern throw message "Saved object is missing,Could not locate that index-pattern (id: 1a3361e0-db25-11eb-b9f7-7f39251b1356),
Version:
elasticsearch-operator.5.1.0-74
Step to reproduce:
1) deploy Logging 5.1
2) no-kubeadmin user create index pattern using UI
3) restart Kibana pods
4) Login kibana UI again.
Actual Result:
The UI throw error 'Saved object is missing,Could not locate that index-pattern (id: 1a3361e0-db25-11eb-b9f7-7f39251b1356' which click the index pattern name.
Expected Result:
users can discover logs via index pattern.
Additional info:
The workaround is to delete the .kibana indics and create pattern in UI again.
- is cloned by
-
LOG-1541 Saved object is missing after restart kibana-pods
- Closed