Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

devops: disks are being accumulated for temporal and long-live instances #9169

Open
gustavovalverde opened this issue Jan 27, 2025 · 0 comments
Assignees
Labels
A-devops Area: Pipelines, CI/CD and Dockerfiles A-infrastructure Area: Infrastructure changes C-bug Category: This is a bug C-cleanup Category: This is a cleanup P-High 🔥 S-needs-triage Status: A bug report needs triage

Comments

@gustavovalverde
Copy link
Member

Describe the issue or request

We need to cleanup disks that are being left behind when replacing an old instance with a new one

Expected Behavior

On deletion, existing disks should be deleted if we're mounting an cached state, and be kept if we're re-mounting the same disk

Current Behavior

We don't have a workflow or logic that handles this differentiation

Possible Solution

A cleanup job

Additional Information/Context

No response

Is this happening on PRs?

No

Is this happening on the main branch?

Yes

@gustavovalverde gustavovalverde added A-devops Area: Pipelines, CI/CD and Dockerfiles A-infrastructure Area: Infrastructure changes C-bug Category: This is a bug C-cleanup Category: This is a cleanup P-High 🔥 S-needs-triage Status: A bug report needs triage labels Jan 27, 2025
@gustavovalverde gustavovalverde self-assigned this Jan 27, 2025
@github-project-automation github-project-automation bot moved this to New in Zebra Jan 27, 2025
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
A-devops Area: Pipelines, CI/CD and Dockerfiles A-infrastructure Area: Infrastructure changes C-bug Category: This is a bug C-cleanup Category: This is a cleanup P-High 🔥 S-needs-triage Status: A bug report needs triage
Projects
Status: New
Development

No branches or pull requests

1 participant