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

Instance profile is stuck in bad state if error occurs when initial role is attached #371

Open
backjo opened this issue May 18, 2022 · 0 comments · May be fixed by #372
Open

Instance profile is stuck in bad state if error occurs when initial role is attached #371

backjo opened this issue May 18, 2022 · 0 comments · May be fixed by #372
Labels
bug Something isn't working

Comments

@backjo
Copy link
Collaborator

backjo commented May 18, 2022

Is this a BUG REPORT or FEATURE REQUEST?:
BUG
What happened:
An Instance profile was created by IM, but it had no role attached. It is stuck in this state.
What you expected to happen:
IM should reconcile this error correctly, and attach a role to the profile if one does not exist on subsequent checks.
How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • Kubernetes version:
kubectl version -o yaml

Other debugging information (if applicable):

  • InstanceGroup status:
kubectl describe instancegroup <ig-name>
  • controller logs:
kubectl logs <instance-manager pod>
@backjo backjo added the bug Something isn't working label May 18, 2022
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
None yet
Development

Successfully merging a pull request may close this issue.

1 participant