-
Bug
-
Resolution: Duplicate
-
Normal
-
None
-
None
-
False
-
None
-
False
-
NEW
-
NEW
-
Bug Fix
-
-
-
Log Storage - Sprint 242, Log Storage - Sprint 244
Description of problem:
When elasticsearch is deployed on the Openshift 4.14 hypershift management cluster, the kibana normal user can not fetch any data from elasticsearch.
No such issue on the other non-hypershift 4.14 cluster.
No such issue on Openshift 4.13 hypershift management cluster
Cluster-admin can display the app logs
Version-Release number of selected component (if applicable):
Openshift 4.14
How reproducible:
On the Openshift 4.14 hypershift management cluster, the kibana normal user can not fetch any data from elasticsearch.
No such issue on the other non-hypershift 4.14 cluster.
No such issue on Opensihft 4.13 hypershift management cluster
Cluster-admin can display the app logs
Steps to Reproduce:
1. Deploy Logging 5.8 on Openshift 4.14 hypershift management cluster
2. Forward logs to elasticsearch.
3. testuser1 create some pods
$oc get pods -n test-log-user1-1692848093
centos-logtest-hz2jg 1/1 Running 0 4h25m
4. testuser1 login kibana to create an index pattern.
5. cluster-admin login kibana to create index patterns.
Actual results:
testuser1 can not display logs of pod centos-logtest-hz2jg.
Expected results:
testuser1 can display logs of pod centos-logtest-hz2jg.
Additional info:
$ kubectl auth can-i get pods/log -n test-log-user1-1692848093
yes
$ kubectl auth can-i get pods --subresource=log -n test-log-user1-1692848093
yes