Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error from deploying elasticsearch + security

See original GitHub issue

Chart version: elasticsearch-7.1.1 Kubernetes version: 1.13.0 Kubernetes provider: E.g. GKE (Google Kubernetes Engine) kubespray Helm Version: v2.13.0 helm get release output

e.g. helm get elasticsearch (replace elasticsearch with the name of your helm release)

Describe the bug: Run the ‘make’ from the security directory.

Steps to reproduce:

cd to the examples/security dir
type ‘make’, hit enter
install failed with “Error: release helm-es-security failed: timed out waiting for the condition” and “make: *** [install] Error 1”

Expected behavior:

Provide logs and/or server output (if relevant):

	$ make
	kubectl delete secrets elastic-credentials elastic-certificates elastic-certificate-pem || true && \
	vault read -field=value secret/devops-ci/helm-charts/elasticsearch/security/certificates | base64 --decode > elastic-certificates.p12 && \
	vault read -field=value secret/devops-ci/helm-charts/elasticsearch/security/certificate-pem | base64 --decode > elastic-certificate.pem && \
	kubectl create secret generic elastic-credentials  --from-literal=password=changeme --from-literal=username=elastic && \
	kubectl create secret generic elastic-certificates --from-file=elastic-certificates.p12 && \
	kubectl create secret generic elastic-certificate-pem --from-file=elastic-certificate.pem && \
	rm -f elastic-certificates.p12 elastic-certificate.pem
	Error from server (NotFound): secrets "elastic-credentials" not found
	Error from server (NotFound): secrets "elastic-certificates" not found
	Error from server (NotFound): secrets "elastic-certificate-pem" not found
	/bin/sh: line 1: vault: command not found
	/bin/sh: line 2: vault: command not found
	secret/elastic-credentials created
	secret/elastic-certificates created
	secret/elastic-certificate-pem created
	helm upgrade --wait --timeout=600 --install --values ./security.yml helm-es-security ../../ ; \

	Release "helm-es-security" does not exist. Installing it now.
	Error: release helm-es-security failed: timed out waiting for the condition
	make: *** [install] Error 1

Any additional context:

Issue Analytics

State:
Created 4 years ago
Comments:8 (4 by maintainers)

Top GitHub Comments

1reaction

bamb00commented, Jun 21, 2019

@Crazybus I forgot to list the steps,

Set the service.type to nodeport
Run ‘helm install . --name elasticsearch’
Create the ca and certificate
cd examples/security
Run ‘helm upgrade --wait --timeout=600 --install --values ./security.yml elasticsearch …/…/’

0reactions

bamb00commented, Jun 28, 2019

@Crazybus Yes. I have correct the mistake.

Top Results From Across the Web

Security Error When Deploying ElasticSearch Indexes

Symptoms. Multiple errors deploying all HCM ElasticSearch Indexes. Example. Unable to deploy\ index search definition HC_BEN_HEALTH_BENEFIT due ...

Common Security Error Messages | Curator Reference [5.8]

Elasticsearch ConnectionErroredit. Unable to create client connection to ; SNIMissingWarningedit. SNIMissingWarning: ; InsecurePlatformWarningedit.

Troubleshooting security | Elasticsearch Guide [8.5] | Elastic

Some settings are not returned via the nodes settings API · Authorization exceptions · Users command fails due to extra arguments · Users...

How do I resolve configuration change failures? - Elastic

Open the deployment Security page. In the Elasticsearch keystore section, check the Security keys list. The list is shown only if you currently...

Security settings in Elasticsearch - Elastic

security settings to enable anonymous access and perform message authentication, set up document and field level security, configure realms, encrypt ...