Open lajchon opened 3 weeks ago
Hi @lajchon,
Thank you for the report, is the issue also reproducible in provider v1.7.0?
@turkenf , it appears to still be an issue after updating the provider to v1.7.0.
Adding voice to this issue. It also occurs in 1.6.0 and 1.6.1 as well.
In our scenario, the LBListener can cause it to crash within 5sec or so.
Is there an existing issue for this?
Affected Resource(s)
elbv2.aws.upbound.io/v1beta1, Kind=LBListener
Resource MRs required to reproduce the bug
Steps to Reproduce
Deploy elbv2.aws.upbound.io/v1beta1 LB, LBTargetGroup and LBListener with v1.4.0 is successful. Bump elbv2 Provider version to v1.5.0 or v1.6.0, an
Observed a panic: value is null
is loggedWhat happened?
After bumping version from v1.4.0 to v1.5.0+, the following is logged for existing LBListener:
When attempting to create a new Listener with elbv2 v1.5.0, Listeners are created correctly and associated with Load-Balancer, but the following status is eventually returned:
Relevant Error Output Snippet
No response
Crossplane Version
1.16.0
Provider Version
1.5.0
Kubernetes Version
No response
Kubernetes Distribution
No response
Additional Info
No response