Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG][opensearch] #120

Open
tibz7 opened this issue Mar 14, 2023 · 2 comments
Open

[BUG][opensearch] #120

tibz7 opened this issue Mar 14, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@tibz7
Copy link

tibz7 commented Mar 14, 2023

Describe the bug
running the playbook fails because user logstash password is not defined.

To Reproduce
Steps to reproduce the behavior:

  1. Run the playbook with the given example in the readme
  2. Delete the logstash user and run the playbook,
  3. It works.

Expected behavior
Playbook work out of the box, providing only the admin and kibanaserver password in the --extra-vars
Maybe it is just the documentation which was not very clear to me, but that case, the logstash user should be provided as well, as part of the example.

@tibz7 tibz7 added bug Something isn't working untriaged labels Mar 14, 2023
@prudhvigodithi
Copy link
Member

[Triage]
Hey @tibz7 thats for bringing this up, I do see there is a way to change the admin user directly during the install, similar way we should add for logstash user, can you please contribute with the fix?
Thank you
@gaiksaya @bbarani @peterzhuamazon

@bbarani
Copy link
Member

bbarani commented Jan 22, 2024

@tibz7 Can you confirm if this PR has addressed this documentation gap?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: 📦 Backlog
Development

No branches or pull requests

3 participants