# Kibana won't start after 8.2.0 upgrade

**URL:** <https://discuss.elastic.co/t/kibana-wont-start-after-8-2-0-upgrade/304881>\
**Category:** Kibana\
**Created:** [May 17, 2022, 12:42am UTC](https://discuss.elastic.co/t/kibana-wont-start-after-8-2-0-upgrade/304881 "2022-05-17T00:42:14Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ibra\_013](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ibra_013/32/104827_2.png) [@ibra\_013](https://discuss.elastic.co/u/ibra_013)\
**Post date:** [May 17, 2022, 8:24pm UTC](https://discuss.elastic.co/t/kibana-wont-start-after-8-2-0-upgrade/304881/3 "2022-05-17T20:24:16Z")

</div>

Hi @elasticforme

Check this [thread](https://discuss.elastic.co/t/cannot-delete-index-with-superuser/303249/3) same issue as yours.

> <https://github.com/elastic/kibana/issues/127881>
>
> \*\*Kibana version:\*\* 8.0+
> 
> \*\*Elasticsearch version:\*\* aligned with Kibana
> 
> \*\*…Describe the bug:\*\*
> 
> On versions \< 8.0, \`.reporting\*\` indices could be deleted at least by the \`superuser\` or anyone who had \`reporting\_user\` permissions.
> 
> On 8.0+, due to the fact \`.reporting\*\` indices are considered system indices, even a \`superuser\` do not have the permission to delete them (as \`superuser\` doesn't have the permission to delete restricted indices starting 8.0).
> 
> \*\*Steps to reproduce:\*\*
> 1. Create report
> 2. Try to delete any \`.reporting-\*\` index
> 
> \*\*Expected behavior:\*\*
> 
> A user should have the permission to delete reports and/or clean up old reports without having to use workarounds.
> 
> The current workaround is to create a dedicated role and a user assigned to it which grants:
> \`\`\`
> {
> "names" : \[
> ".reporting\*"
> \],
> "privileges" : \[
> "monitor",
> "read",
> "view\_index\_metadata",
> "read\_cross\_cluster",
> "delete\_index"
> \],
> "allow\_restricted\_indices" : true
> }
> \`\`\`
> 
> The problem occurs also when granting both \`reporting\_user\` and \`superuser\` permissions.
> \`\`\`
> {
> "error" : {
> "root\_cause" : \[
> {
> "type" : "security\_exception",
> "reason" : "action \[indices:admin/delete\] is unauthorized for user \[lucalucaluca\] with roles \[reporting\_user,superuser\] on indices \[.reporting-2022-03-13\], this action is granted by the index privileges \[delete\_index,manage,all\]"
> }
> \],
> "type" : "security\_exception",
> "reason" : "action \[indices:admin/delete\] is unauthorized for user \[lucalucaluca\] with roles \[reporting\_user,superuser\] on indices \[.reporting-2022-03-13\], this action is granted by the index privileges \[delete\_index,manage,all\]"
> },
> "status" : 403
> }
> \`\`\`
> 
> The same problem occurs when using the new Kibana permissions.
> Even granting the following to a given user, still blocks the removal of \`.reporting\*\` indices.
> \`\`\`
> {
> "reporting\_my" : {
> "cluster" : \[
> "all"
> \],
> "indices" : \[
> {
> "names" : \[
> "kibana\_sample\_data\_logs"
> \],
> "privileges" : \[
> "all"
> \],
> "field\_security" : {
> "grant" : \[
> "\*"
> \],
> "except" : \[\]
> },
> "allow\_restricted\_indices" : false
> }
> \],
> "applications" : \[
> {
> "application" : "kibana-.kibana",
> "privileges" : \[
> "feature\_discover.minimal\_all",
> "feature\_discover.url\_create",
> "feature\_discover.store\_search\_session",
> "feature\_discover.generate\_report",
> "feature\_dashboard.minimal\_all",
> "feature\_dashboard.url\_create",
> "feature\_dashboard.store\_search\_session",
> "feature\_dashboard.generate\_report",
> "feature\_dashboard.download\_csv\_report"
> \],
> "resources" : \[
> "\*"
> \]
> }
> \],
> "run\_as" : \[\],
> "metadata" : { },
> "transient\_metadata" : {
> "enabled" : true
> }
> }
> }
> 
> \`\`\`
> 
> \*\*Any additional context:\*\*
> 
> As \`.reporting\*\` documents contains both the job/task definition and the "result" of the report, maybe we could decouple them into 2 separate indices? Also the \`.reporting\` index could become a "workspace" index (like \`.async-search\` index) where we keep only the jobs to be done and store the generated reports in a separate index.
> 
> Or otherwise we should provide a dedicated API to manage reports \`\_reporting\` at ES or Kibana level and allow to delete specific reports or whole groups of reports.
> 
> ~I would consider it a bug as it is a regression on features of reporting~
> \> This as an effect of the breaking change made by ES security to no longer allow the superuser role to manage system indices by default.
> 
> \*\*PLEASE BE AWARE\*\* that it is possible to auto-delete old Reporting indices modifying the ILM Policy \`kibana-reporting\`, adding a Delete phase.
> So, this problem affects only users who are interested in deleting a specific reporting index.

---

_[View the full topic](https://discuss.elastic.co/t/kibana-wont-start-after-8-2-0-upgrade/304881)._