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

jenkins-x-vault IAM user not auto created with terraform module #40

Closed
rckclmbr-bot opened this issue May 4, 2020 · 5 comments
Closed

Comments

@rckclmbr-bot
Copy link

rckclmbr-bot commented May 4, 2020

Summary

When going through "Getting started" on AWS and using terraform, the docs indicate you can optionally not create an IAM user for vault, and the user should be autocreated, however it fails.

Steps to reproduce the behavior

Follow Step 1 in https://jenkins-x.io/docs/getting-started/

Expected behavior

terraform apply works successfully

Actual behavior

Provisioning fails with

Error: error getting user: NoSuchEntity: The user with name jenkins-x-vault cannot be found.

Operating system / Environment

Fedora 31 -> AWS

@hferentschik hferentschik transferred this issue from jenkins-x/jx May 6, 2020
@hferentschik hferentschik transferred this issue from jenkins-x/terraform-aws-eks-jx May 6, 2020
@hferentschik hferentschik transferred this issue from jenkins-x/jx May 6, 2020
@hferentschik
Copy link
Contributor

Can you provide some more context? I am not able to reproduce this atm. How does your Terraform configuration look like? Can you post the more of the error and/or the output of terraform apply (watch out for any sensitive information).

@jenkins-x-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

@jenkins-x-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten

@jenkins-x-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

@jenkins-x-bot
Copy link

@jenkins-x-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Provide feedback via https://jenkins-x.io/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants