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

[Feature Request] modify OPENSEARCH_INITIAL_ADMIN_PASSWORD as it breaks automation #4965

Open
jgrammen-agilitypr opened this issue Dec 10, 2024 · 4 comments
Labels
enhancement New feature or request

Comments

@jgrammen-agilitypr
Copy link

Is your feature request related to a problem? Please describe

the new OPENSEARCH_INITIAL_ADMIN_PASSWORD (2.12) break automation (puppet) as it every difficult to pass ENV vars.
it also appears to conflict with debian packaging policies (https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#introduction-to-package-maintainer-scripts )

Describe the solution you'd like

an alternative solution to allow the passing of the required variables to the installer script. Maybe via install_options

Related component

Other

Describe alternatives you've considered

No response

Additional context

installing the package via puppet fails as passing the required ENV var is not possible

@jgrammen-agilitypr jgrammen-agilitypr added enhancement New feature or request untriaged Require the attention of the repository maintainers and may need to be prioritized labels Dec 10, 2024
@reta reta transferred this issue from opensearch-project/OpenSearch Dec 10, 2024
@TheMeier
Copy link

A well defined path containing the credentials would a viable solution

@cwperks cwperks removed the untriaged Require the attention of the repository maintainers and may need to be prioritized label Dec 16, 2024
@cwperks
Copy link
Member

cwperks commented Dec 16, 2024

[Triage] @jgrammen-agilitypr OPENSEARCH_INITIAL_ADMIN_PASSWORD is only enforced when using the demo security configuration. Have you tried supplying custom yaml files for the security configuration and installing the appropriate certs?

I'm not familiar with puppet, how are env variable supplied?

@jgrammen-agilitypr
Copy link
Author

Ok, I must not be understanding something. if you just install the opensearch package it won't fail to install? if that is true, then I must be sequencing something wrong and deploying configuration for opensearch at the wrong time.

puppet does not let you supply ENV variables during package installation.

@TheMeier
Copy link

sudo dpkg  -i opensearch-2.18.0-linux-x64.deb 
Selecting previously unselected package opensearch.
(Reading database ... 53356 files and directories currently installed.)
Preparing to unpack opensearch-2.18.0-linux-x64.deb ...
Running OpenSearch Pre-Installation Script
Unpacking opensearch (2.18.0) ...
Setting up opensearch (2.18.0) ...
Running OpenSearch Post-Installation Script
ERROR: Something went wrong during demo configuration installation. Please see the logs in /var/log/opensearch/install_demo_configuration.log
dpkg: error processing package opensearch (--install):
 installed opensearch package post-installation script subprocess returned error exit status 1
Processing triggers for libc-bin (2.36-9+deb12u9) ...
Errors were encountered while processing:
 opensearch

this still fails. The log says:

No custom admin password found. Please provide a password via the environment variable OPENSEARCH_INITIAL_ADMIN_PASSWORD.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants