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

AWS/GCP snapshot cleanup isn't working with builtin providers #2190

Closed
czunker opened this issue Oct 12, 2023 · 1 comment
Closed

AWS/GCP snapshot cleanup isn't working with builtin providers #2190

czunker opened this issue Oct 12, 2023 · 1 comment
Labels

Comments

@czunker
Copy link
Contributor

czunker commented Oct 12, 2023

Describe the bug
While debugging #2171 with builtin providers, I noticed that cleanup is not happening.

For ebs and gcp snapshot scanning, we call some cleanup after the scan is done. This cleanup is triggered via the provider shutdown. But builtin providers are added to the running providers, so they aren't shut down later:
https://github.com/mondoohq/cnquery/blob/main/providers/coordinator.go#L107-L117

This makes debugging harder.

To Reproduce
Steps to reproduce the behavior:

  1. Run a GCP or EBS snapshot scan with builtin providers for aws/gcp and os.
  2. Notice the scan finishing
  3. Note that the cloud console still shows created volumes and mountpoints are still present in the VM

Expected behavior
We should be able to execute this cleanup also with builtin providers.

@imilchev
Copy link
Member

imilchev commented Mar 1, 2024

this should now work with the new disconnect logic

@imilchev imilchev closed this as completed Mar 1, 2024
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

3 participants