copilot-cli: One or more listeners not found

Hi,

I’ve been trying to move away from a manually-created network load balancer, to using copilot’s relatively new nlb feature. But, now I can’t get my services to deploy at all 😦

The failure is this step:

A custom resource assigning priority for HTTPS listener rules [delete complete] [1.9s] Received response status [FAILED] from custom resource. Message return ed: One or more listeners not found (Log: /aws/lambda/bitarb-prod-apac he-RulePriorityFunction-pllT8b0VP8gE/2022/06/12/[$LATEST]eb0c20e1b8914 c88bc2fbf974469e206) (RequestId: facc040d-bee8-4bb9-9c47-6bbb64396e03)

I’ve tried copilot svc delete and then re-init and re-deploy, but no luck. The CloudWatch log referred to above has just the same error message. I’m at a loss what to try next, any advice?

The service being deployed is is one that was using an existing application load balancer from a manifest. The service using the new nlb functionality is deploying fine, so somehow the moving around has broken an existing, supposedly unaffected service.

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 19 (10 by maintainers)

Most upvoted comments

Hello, @iamhopaul123 Thank you for advising me.

I added Parameter.dummyWorkloads and Outputs.dummyOutput into an env stack and update it:

Parameters:
  ...
  dummyWorkloads:
    Type: String

Outputs:
  ...
  dummyOutput:
    Value: !Sub '${dummyWorkloads}'

スクリーンショット 2022-08-05 23 34 40

Next I updated the service stack:

EnvControllerAction:
    Metadata:
      'aws:copilot:description': "Update your environment's shared resources"
    Type: Custom::EnvControllerFunction
    Properties:
      ServiceToken: !GetAtt EnvControllerFunction.Arn
      Workload: !Ref WorkloadName
      EnvStack: !Sub '${AppName}-${EnvName}'
      Parameters: [ALBWorkloads, dummyWorkloads] # this is the place to change

A service stack status is UPDATE_COMPLETE and drift status is IN_SYNC !

スクリーンショット 2022-08-05 23 40 51

Finally, I deployed with copilot deploy --name api --env stg --tag stg is NOW WORKING! ✔ Deployed service api.

I sincerely appreciate your support @iamhopaul123

You are free to close this issue and hope this helps others with the same problem.

rluisr on Aug 5, 2022