read-only kibana user cannot use system after upgrade till index pattern is updated by a normal user

[elasticmachine]

Original comment by @jguay:

Kibana version:
Upgrade from 5.4 to 5.5 (or 6.0 alpha2)

Elasticsearch version:
Upgrade from 5.4 to 5.5 (or 6.0 alpha2)

Description of the problem including expected versus actual behavior:
After an upgrade, a read-only user has following behaviour:

• The user can browse to "Dashboard" page, when he tries to open dashboard I get the same error inside the dashboard
• The user can browse to "visualisation", when I click on the visualisation nothing happens
• cannot browse to Discover and get error "Request to Elasticsearch failed: "[security_exception] action [indices:data/write/index] is unauthorized for user [readonly]" and I cannot browse to discover data
  Browser network trace shows 403 request on a POST http://localhost:5601/es_admin/.kibana/index-pattern/myindexpattern*

Steps to reproduce:

1. Install 5.4 with one index pattern, one visualisation and one dashboard
2. Create a role with "read" and "view_index_metadata" to .kibana* and myindexpattern*
3. Create a user called "readonlyuser" and assign the role
4. login with readonlyuser and observe user can use Discover
5. Upgrade ES to 5.5
6. Login to kibana with readonlyuser and try to access Discover

Errors in browser console (if relevant):
"Request to Elasticsearch failed: "[security_exception] action [indices:data/write/index] is unauthorized for user [readonly]"

Provide logs and/or server output (if relevant):
Workaround is to login once with normal user to kibana and use the index patter

Describe the feature:
A great feature would be to update the index patterns upfront rather than on first usage of the index pattern

[elasticmachine]

Original comment by @Rasroh:

cc @elastic/kibana-management ?

[gingerwizard]

I believe this issue occurs whenever an index pattern exists but no matching indices for the pattern are present in ES. If those indices are then created and a read only user accesses a dashboard using the visuals, prior to the index patterns being refreshed in kibana, an attempt is made to modify the pattern through a PUT as indicated above.

I'm trying to produce a specific series of reproducible steps here. @alexfrancoeur this is a blocker for us.
This is occurring on 6.2.4.

[legrego]

Had a user come across this issue here: #51759 (comment)

[laurentmldev]

Yes indeed we got quite the same issue.

Is their any planification for a fix in coming weeks ?

Thanks!

[mattkime]

The index pattern field cache was removed in this PR which should resolve the problem - #83368