Kibana 403 response for super user elastic

[Seenivasan_Gopalsamy]

Hello Team

We are getting a 403 response after adding the index patterns.

We are trying to move existing licenses to new servers due to disk space issue.

Elastic, kibana, x-pack 6.2.2

403 Response
Less Info
OK
Error: 403 Response
https://test-server/bundles/commons.bundle.js?v=16588:21:80798
processQueue@https://test-server/bundles/vendors.bundle.js?v=16588:116:132458
https://test-server/bundles/vendors.bundle.js?v=16588:116:133361
$digest@https://test-server/bundles/vendors.bundle.js?v=16588:116:144241
$apply@https://test-server/bundles/vendors.bundle.js?v=16588:116:147025
done@https://test-server/bundles/vendors.bundle.js?v=16588:116:100032
completeRequest@https://test-server/bundles/vendors.bundle.js?v=16588:116:104705
https://test-server/bundles/vendors.bundle.js?v=16588:116:105450

[Mikhail_Shustov]

@Seenivasan_Gopalsamy

We are getting a 403 response after adding the index patterns.

Did you fix your disk space issue before creating the new index? That 403 is originated from Elasticsearch Elasticsearch does not indicate retryability when flood stage is exceeded · Issue #49393 · elastic/elasticsearch · GitHub
This issue also provides some hints Kibana stays read only when ES high disk watermark has been exceeded and later gone beneath the limit · Issue #13685 · elastic/kibana · GitHub