Skip to content

Wrong errormessage when passwords don't match #100

@widhalmt

Description

@widhalmt

For whatever reason, the collection used wrong passwords when connecting to the cluster. That's another issue, but we need to make sure that there's an error message that will send you the right way.

Ansible showed this:

TASK [netways.elasticstack.elasticsearch : Check for open port 9200/tcp] ********************************************
ok: [elastic801]
ok: [elastic802]

TASK [netways.elasticstack.elasticsearch : Fail if cluster is not ready yet] ****************************************
fatal: [elastic801]: FAILED! => {"changed": false, "msg": "Elasticsearch cluster is not ready (status:  , yet. Please rerun again later."}
fatal: [elastic802]: FAILED! => {"changed": false, "msg": "Elasticsearch cluster is not ready (status:  , yet. Please rerun again later."}

But the Elasticsearch logs showed this:

[2023-02-17T15:55:01,911][INFO ][o.e.x.s.a.RealmsAuthenticator] [elastic802] Authentication of [elastic] was terminated by realm [reserved] - failed to authenticate user [elastic]

The output of the status query was empty as you can see in the output of the fail task.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions