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

Ephemeral ec2 security groups are not cleaned up #6

Open
syndr opened this issue Apr 18, 2024 · 1 comment · May be fixed by #16
Open

Ephemeral ec2 security groups are not cleaned up #6

syndr opened this issue Apr 18, 2024 · 1 comment · May be fixed by #16
Assignees
Labels
bug Something isn't working

Comments

@syndr
Copy link
Collaborator

syndr commented Apr 18, 2024

As part of the "destroy" step, security groups used by the ec2_platform role are supposed to be cleaned up. This does not appear to be happening.

image

@syndr syndr added the bug Something isn't working label Apr 18, 2024
@syndr syndr self-assigned this Apr 18, 2024
@syndr
Copy link
Collaborator Author

syndr commented Oct 14, 2024

I believe this is caused when multiple instances are generated as part of one test -- the later one either doesn't respect or doesn't read the test id that was generated by the first.

Likely caused by variable definition that generates the unique id.

syndr added a commit that referenced this issue Jan 23, 2025
Fix the `docker_platform` role so that it works correctly when
more than one platform is specified in molecule.yml.

Move non-provider-specific platform configuration to a `platform` role. This is a breaking change for this version, as functions of `docker_platform` are now provided by platform.

Replace any references to `docker_platform` in playbooks using this collection with `platform`, options stay the same.
@syndr syndr linked a pull request Jan 23, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant