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:
Version-Release number of selected component (if applicable):
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
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 
3. Delete the user's index pattern:
oc exec -c elasticsearch $pod -- es_util --query=$KIBANA_INDEX -XDELETE
Issue is because we skip  any additional logic if index already exists. Need to take into account version. Work around is #c4
Adding some clarification to Jeff's workaround:
> 2. Find the user's index pattern 
>  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.
Fixed in https://github.com/openshift/origin-aggregated-logging/pull/1478
Commits pushed to master at https://github.com/openshift/origin-aggregated-logging
bug 1652224. Fix defaultIndex for Kibana uprade
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.