-
Notifications
You must be signed in to change notification settings - Fork 4k
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
(awselasticloadbalancingv2): No load balancers found with NetworkLoadBalancer lookup method after 2.167.0 #32161
Comments
Working hypothesis: the load balancer context provider is now requiring that the load balancer have the same set of tags as the query:
whereas before it only required that the query was a subset of the load balancer's tags. @rishi-kulkarni can you please confirm that this is your case? |
Aha, very interesting. Yes, I can confirm that looking up all tags resolves the NLB, but looking up any subset does not. Thanks for the quick investigation and PR! |
… a subset of tags (#32164) There was a regression in the load balancer lookup, in which we started requiring that the set of tags in the query is strictly the same as the set of tags in the load balancer (rather than merely a subset of it). Remove the length equality constraint and also simplify the code to make the intent clearer. Fixes #32161. ### Checklist - [ ] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license* Co-authored-by: Momo Kornher <kornherm@amazon.co.uk>
Comments on closed issues and PRs are hard for our team to see. |
… a subset of tags (#32164) There was a regression in the load balancer lookup, in which we started requiring that the set of tags in the query is strictly the same as the set of tags in the load balancer (rather than merely a subset of it). Remove the length equality constraint and also simplify the code to make the intent clearer. Fixes #32161. ### Checklist - [ ] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license* Co-authored-by: Momo Kornher <kornherm@amazon.co.uk>
Describe the bug
I had three CI pipelines fail with the following error starting today using both Go and Python cdk:
Pinning the
aws-cdk
CLI tonpm install -g aws-cdk@2.166.0
resolved the issue in all pipelines. Perhaps could be related to the new Zonal Shift feature?Regression Issue
Confirmed Regression
Last Known Working CDK Version
2.166.0
Expected Behavior
Looking up a still-existing Network Load Balancer by tag should work.
Current Behavior
The Network Load Balancer lookup fails to resolve.
Reproduction Steps
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.167.1
Framework Version
No response
Node.js Version
22
OS
Linux
Language
Python, Go
Language Version
Python 3.11 | Go 1.23.2
Other information
No response
The text was updated successfully, but these errors were encountered: