-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
"Failed to find related managed instance SG. Was it deleted from AWS" error #236
Comments
emas80
added a commit
to emas80/alb-ingress-controller
that referenced
this issue
Oct 10, 2017
I fixed the issue our side, it was related to a wrong configuration of the security groups: while testing we have added a rule allowing access to our instances security group from the ALB security group, and this was causing the filter inside of the "DescribeSGByPermissionGroup" function to return 2 security groups instead of just one. |
Thanks for the work @emas80! |
bigkraig
pushed a commit
that referenced
this issue
Oct 1, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi, I am getting this error every couple of minutes.
I don't know exactly what caused this, the last thing we did was adding two annotations to the ingress to test the ssl redirect ( "ingress.kubernetes.io/ssl-redirect": "true" - I don't know if it would work or not, we were just testing it).
I already applied the previous configuration, but we keep having that error and there is no going back apparently.
It already happened before, and deleting the ALB from AWS fixed it - the new ALB was created automatically and everything was fine again.
I enabled the debug logs and I am also printing the AWS calls, it seems it's trying to describe the security group of the ALB, it's also printing the Security Group id.
The security group is there, it was not deleted.
I "fixed" the error message, it was not printing the "err" object.
The complete error message is "Found more than 1 matching (managed) instance SGs. Found 2".
(I will open a PR with the fix to print the error)
The text was updated successfully, but these errors were encountered: