Description of problem: depolyed OSCP 3.10 and everything was working fine but after upgrading to 3.11 user with cluster-admin role is unable to view logs in kibana, just like in: https://github.com/openshift/origin-aggregated-logging/issues/1333 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. deploy 3.10 cluster 2. user with cluster-admin role login to kibana (everything is fine) 3. upgrade cluster 4. the same user can't view logs Expected results: Additional info:
Continuing to investigate but the short term fix would be to remove the kibana index for the particular user. I would recommend: 1. Export any custom index-patterns, visualizations, dashboards 2. Find the user's index pattern [1] 3. Delete the user's index pattern: oc exec -c elasticsearch $pod -- es_util --query=$KIBANA_INDEX -XDELETE [1] https://github.com/jcantrill/cluster-logging-tools/blob/master/scripts/kibana-index-name
Issue is because we skip [1] any additional logic if index already exists. Need to take into account version. Work around is #c4 [1] https://github.com/fabric8io/openshift-elasticsearch-plugin/blob/master/src/main/java/io/fabric8/elasticsearch/plugin/kibana/KibanaSeed.java#L63
Adding some clarification to Jeff's workaround: > 2. Find the user's index pattern [1] > [1] https://github.com/jcantrill/cluster-logging-tools/blob/master/scripts/kibana-index-name Make sure to add leading period to ".kibana.xxxxxx" when deleting the index. https://github.com/jcantrill/cluster-logging-tools/pull/3
Fixed in https://github.com/openshift/origin-aggregated-logging/pull/1478
Commits pushed to master at https://github.com/openshift/origin-aggregated-logging https://github.com/openshift/origin-aggregated-logging/commit/b275e32d7db20201e075d5435aeb7de650660c30 bug 1652224. Fix defaultIndex for Kibana uprade https://github.com/openshift/origin-aggregated-logging/commit/6d5d0b7e8d9fe4826b602f14489c21ad5ca14ea5 Merge pull request #1481 from openshift-cherrypick-robot/cherry-pick-1478-to-master [master] bug 1652224. Fix defaultIndex for Kibana uprade
The user continue to login Kibana once upgrade from v3.10 to v3.11.59
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-2019:0024