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] Vault fails to install after changing helm to use localhost #1729

Closed
przemyslavic opened this issue Oct 2, 2020 · 8 comments
Closed
Assignees
Labels
Milestone

Comments

@przemyslavic
Copy link
Collaborator

Describe the bug
Vault installation fails after recent changes to helm and kubectl now executed locally.

To Reproduce
Deploy a new cluster from develop branch with the configuration given below: epicli apply -f test.yml
Config files

---
kind: configuration/vault
title: Vault Config
name: default
provider: aws
specification:
  vault_enabled: true

Expected behavior
The cluster with Vault enabled has been deployed successfully

OS (please complete the following information):

  • OS: [all]

Cloud Environment (please complete the following information):

  • Cloud Provider [all]

Additional context
The installation fails on TASK [vault : Run configuration script] returning an error ERROR: There was an error during checking if Vault Agent Helm Chart is already installed. Exit status: 127".
Command called: helm list | grep vault; but now there is no helm on kubernetes master vm.
The role should be refactored according to the latest changes to use local helm and local kubectl.

@mkyc
Copy link
Contributor

mkyc commented Oct 2, 2020

@erzetpe
Copy link
Contributor

erzetpe commented Oct 2, 2020

Yes, this is dependend on PR #1713.

@ar3ndt
Copy link
Contributor

ar3ndt commented Oct 2, 2020

installation of Vault Helm chart needs helm binary installed on kubernetes master. I will add it.
it doesn't require helm repository itself as installation uses download_file task independently though it uses docker image from repository
quick fix already tested

@mkyc
Copy link
Contributor

mkyc commented Oct 6, 2020

@rpudlowski93 isn't that task in some way already tested by you? I've seen comment in related PR.

@rpudlowski93
Copy link
Contributor

rpudlowski93 commented Oct 7, 2020

@mkyc Yes, we tested it but as I noticed today morning, not enough. I found bug related to the PR and reported it here #1745.
With the change reported in the bug I tested it and it works properly, @ar3ndt should fixed it very fast (small change)

I will wait for the PR related to the #1745, and I will test finally vault using the scenario: link. If everything goes fine, I will move the task to DoD

@atsikham atsikham self-assigned this Oct 7, 2020
@atsikham
Copy link
Contributor

atsikham commented Oct 7, 2020

@rpudlowski93 could you please add correct dependencies to this task in dependencies section and move to correct state? It's not ready for test.

@atsikham atsikham removed their assignment Oct 7, 2020
@rpudlowski93
Copy link
Contributor

@atsikham - sure! It will be ready to test after marge the PR realted to #1745 :)

@rpudlowski93
Copy link
Contributor

rpudlowski93 commented Oct 7, 2020

PR #1748 merged

Using the following configuation with enabled vault:

---
kind: configuration/vault
title: Vault Config
name: default
provider: azure
specification:
  vault_enabled: true

installation process finished without any errors. Helm was installed properly on master node and all necessary files were downloaded correctly from separated repository.

Tested on Azure and single master node.

@mkyc mkyc closed this as completed Oct 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants