Skip to content
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

serverless did not remove alb target group #11726

Open
4 tasks done
shuangqiu123 opened this issue Feb 6, 2023 · 1 comment
Open
4 tasks done

serverless did not remove alb target group #11726

shuangqiu123 opened this issue Feb 6, 2023 · 1 comment
Assignees
Labels

Comments

@shuangqiu123
Copy link

shuangqiu123 commented Feb 6, 2023

Are you certain it's a bug?

  • Yes, it looks like a bug

Is the issue caused by a plugin?

  • It is not a plugin issue

Are you using the latest v3 release?

  • Yes, I'm using the latest v3 release

Is there an existing issue for this?

  • I have searched existing issues, it hasn't been reported yet

Issue description

I first ran the serverless deploy and I got the access denied error as I didn't have permission for elasticloadbalancing: RegisterTargets.
I then added the missing permission so all permissions are added for the deployment.
After this, I ran serverless remove and it went successfully.
However, when I ran serverless deploy again, it gave me the error:
Resource of type 'AWS::ElasticLoadBalancingV2::TargetGroup' with identifier '' already exists.
The serverless remove command did not remove the target group, while all permissions were added.

Service configuration (serverless.yml) content

service: hello-world

frameworkVersion: '3'

provider:
  name: aws
  runtime: nodejs18.x
  stage: staging

functions:
  hello:
    handler: index.js
    events:
      - alb:
          listenerArn: 
          priority: 99
          targetGroupName: hello-world-tg
          conditions:
            path: /lambda

Command name and used flags

serverless deploy

Command output

N/A

Environment information

Framework Core: 3.27.0
Plugin: 6.2.3
SDK: 4.3.2
@medikoo
Copy link
Contributor

medikoo commented Feb 6, 2023

@shuangqiu123 this looks as an issue on AWS side. Framework delegates stack removal to AWS, and it's AWS that's responsible for removing the stack with all the resources that were created in its capacity.

Have you tried contacting AWS support about that, by chance?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants