DefangLabs / DefangLabs/defang

Compose Down error: Dependency Violation

Open
#366 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

ai-debugging aws byoc pulumi
Dominant language
Go
Stars
166
Forks
24
Avg merge
10h 8m
Merged PRs (30d)
33

Description

➜  hasura git:(hasura-rds-example) ✗ defang compose down
 # Using AWS provider
 * Deleted services, deployment ID 078d26107c5c4024be0bf15132b4efd2
 * Press V to toggle verbose mode
2024-05-10T07:21:27.357000-07:00 cd  ** Destroy started for stack beta
2024-05-10T07:21:33.440000-07:00 cd  ** Refresh succeeded in 3.0s
 * Verbose mode on
2024-05-10T07:36:35.975000-07:00 cd pulumi  -  aws:ec2:SecurityGroup hasura-rds_hasura-sg deleting (900s) error: deleting urn:pulumi:beta::hasura-rds::defang-mvp:cd/tenant_stack:TenantStack$defang-mvp:shared/fargate_service:FargateService$aws:ec2/securityGroup:SecurityGroup::hasura-rds_hasura-sg: 1 error occurred:
2024-05-10T07:36:35.975000-07:00 cd pulumi  -  aws:ec2:SecurityGroup hasura-rds_hasura-sg **deleting failed** error: deleting urn:pulumi:beta::hasura-rds::defang-mvp:cd/tenant_stack:TenantStack$defang-mvp:shared/fargate_service:FargateService$aws:ec2/securityGroup:SecurityGroup::hasura-rds_hasura-sg: 1 error occurred:
2024-05-10T07:36:36.315000-07:00 cd pulumi     pulumi:pulumi:Stack hasura-rds-beta  error: update failed
2024-05-10T07:36:36.334000-07:00 cd pulumi     pulumi:pulumi:Stack hasura-rds-beta **failed** 1 error
2024-05-10T07:36:36.334000-07:00 cd pulumi Diagnostics:
2024-05-10T07:36:36.334000-07:00 cd pulumi   aws:ec2:SecurityGroup (hasura-rds_hasura-sg):
2024-05-10T07:36:36.334000-07:00 cd pulumi     error: deleting urn:pulumi:beta::hasura-rds::defang-mvp:cd/tenant_stack:TenantStack$defang-mvp:shared/fargate_service:FargateService$aws:ec2/securityGroup:SecurityGroup::hasura-rds_hasura-sg: 1 error occurred:
2024-05-10T07:36:36.334000-07:00 cd pulumi      * deleting Security Group (sg-025eedd0f01caa245): DependencyViolation: resource sg-025eedd0f01caa245 has a dependent object
2024-05-10T07:36:36.334000-07:00 cd pulumi      status code: 400, request id: 66fea10c-d355-4157-a2db-a23903c21443
2024-05-10T07:36:36.334000-07:00 cd pulumi   pulumi:pulumi:Stack (hasura-rds-beta):
2024-05-10T07:36:36.334000-07:00 cd pulumi     error: update failed
2024-05-10T07:36:36.334000-07:00 cd pulumi Resources:
2024-05-10T07:36:36.334000-07:00 cd pulumi Duration: 15m2s
2024-05-10T07:36:36.685000-07:00 cd pulumi  ** CommandError
Error: EssentialContainerExited: Essential container in task exited with code 255

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported defang compose down failure and inspect the AWS Security Group deletion error showing a DependencyViolation. Trace which dependent object prevents deletion; done means the compose environment can be removed without the Security Group error or the subsequent command failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, docker-compose
Domain
cli, cloud, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.