Editing role in xpack returns strict dynamic mapping exception


(Nick Erber) #1

Hi,

today I wanted to edit a role in Kibana.
When saving the role, kibana throws the following error:

[strict_dynamic_mapping_exception] mapping set to strict, dynamic introduction of [metadata] within [role] is not allowed

Trying the same by using a PUT /_xpack/security/role/rolename in the console gives me the same error:

{
  "error": {
    "root_cause": [
      {
        "type": "strict_dynamic_mapping_exception",
        "reason": "mapping set to strict, dynamic introduction of [metadata] within [role] is not allowed"
      }
    ],
    "type": "strict_dynamic_mapping_exception",
    "reason": "mapping set to strict, dynamic introduction of [metadata] within [role] is not allowed"
  },
  "status": 400
}

I am using ELK in it's 5.0 alpha5 version with a trial license of xpack.

Thanks in advance.


(Mark Walkom) #2

What are you trying to put?


(Nick Erber) #3

I'm trying to PUT the following, but it also throws the error when choosing other options.
When using the Management --> Elasticsearch --> Roles in Kibana it does the same error.

PUT /_xpack/security/role/test
{
    "cluster": [
      "all"
    ],
    "indices": [],
    "run_as": []
}

(Jay Modi) #4

Is this a cluster that you had upgraded from an earlier release?


(Ryan Young) #5

@jaymode - I'm experiencing the Same issue and it is a dev cluster that we upgraded from 2.3 -> 5.0 Alpha last week. Tried adding role from both Kibana and Sense and same exact error.


(Jay Modi) #6

Hi @Ryan_Young,

If you upgrade to beta1, which was just released a few minutes ago this issue should be fixed. Please let us know how it goes!

-Jay


(Nick Erber) #7

Hey @jaymode,

thanks, just updated to beta1 and it works.


(Jay Modi) #8

Awesome, great to hear that it is working now.


(system) #9