Load Balancer not creating after deleting

[saichaitanya11]

What happened?

I am trying to create a load balancer (ELB) using managed resource. The load balancer got created, but after deleting from the AWS Console, it is not creating again. The READY and SYNCED status remain true in the shell. Similarly, during a service deployment I have a load balancer created, but facing the same issue there also. Deleting the load balancer which got created during the service from the AWS Console is not creating again.

Load Balancer Script

`apiVersion: elb.aws.upbound.io/v1beta1 kind: ELB metadata: name: lb-03042023 spec: forProvider: availabilityZones:

• us-east-1b listener:
• instancePort: 8000 instanceProtocol: http lbPort: 80 lbProtocol: http region: us-east-1 providerConfigRef: name: default`

Service Script

`apiVersion: v1 kind: Service metadata: name: nginx-loadbalancer-api spec: type: LoadBalancer selector: app: nginxwebapp ports:

• protocol: TCP port: 80 targetPort: 80`

How can we reproduce it?

1. Create a service file or a managed resource file for an ELB.
2. Apply the file and verify under load balancers if the resource is created.
3. Delete the same from the Console and wait for some time.
4. Verify again if the resource is getting created.

What environment did it happen in?

• Universal Crossplane Version: v1.1.11
• Provider Version: xpkg.upbound.io/upbound/provider-aws:v0.21.0
• OS: Linux
• Kubernetes Version: v1.24

[svscheg]

The issue is reproducible on the latest master, using Load Balancer Script:

apiVersion: elb.aws.upbound.io/v1beta1
kind: ELB
metadata:
  name: examplesvetatesting
spec:
  forProvider:
    availabilityZones:
      - us-west-1b
    listener:
      - instancePort: 8000
        instanceProtocol: http
        lbPort: 80
        lbProtocol: http
    region: us-west-1

output with error:

 - lastTransitionTime: "2023-04-19T20:09:20Z"
    reason: Creating
    status: "False"
    type: Ready
  - lastTransitionTime: "2023-04-19T19:58:33Z"
    reason: ReconcileSuccess
    status: "True"
    type: Synced
  - lastTransitionTime: "2023-04-19T20:10:02Z"
    message: "apply failed: creating ELB Classic Load Balancer (examplesvetatesting):
      ValidationError: Only one of SubnetIds or AvailabilityZones may be specified\n\tstatus
      code: 400, request id: cbc9d9f6-61c3-47d3-841c-6f64cca7d3fd: "
    reason: ApplyFailure
    status: "False"
    type: LastAsyncOperation
  - lastTransitionTime: "2023-04-19T20:10:02Z"
    reason: Finished
    status: "True"
    type: AsyncOperation

[github-actions[bot]]

This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.

[github-actions[bot]]

This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.

[github-actions[bot]]

This issue is being closed since there has been no activity for 14 days since marking it as stale. If you still need help, feel free to comment or reopen the issue!