Bug: Invalid role definition [null]

I was asked to move a bug report here (https://github.com/elastic/elasticsearch/issues/26053):

Elasticsearch version (bin/elasticsearch --version): 5.5.1

Plugins installed: [x-pack]

JVM version (java -version): Java SE Runtime 1.7.0_151-b15

OS version (uname -a if on a Unix-like system): Red Hat Enterprise Linux Server release 7.4 (Maipo)

Description of the problem including expected versus actual behavior:

Steps to reproduce:

  1. Add --- in first line of /x-pack/roles.yml to apply to convention of valid yaml file (see: http://yaml.org/)
  2. Restart elasticsearch

Expected behavior:
Elasticsearch will start without errors.

Actual behavior.
Elasticsarch fails with error. "invalid role"

Provide logs (if relevant):
[2017-08-04T09:20:14,940][ERROR][o.e.x.s.a.s.FileRolesStore] [POC_loghost_node_1] invalid role definition [null] in roles file [/usr/share/elasticsearch/config/x-pack/roles.yml]. skipping role...

I think all of the Elastic products only support one single document inside yml files., so it does fail when using the document separator in YAML.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.