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

Improve CI to prevent any orphaned resources #498

Closed
prashanth26 opened this issue Aug 17, 2020 · 1 comment · Fixed by #550
Closed

Improve CI to prevent any orphaned resources #498

prashanth26 opened this issue Aug 17, 2020 · 1 comment · Fixed by #550
Assignees
Labels
kind/enhancement Enhancement, improvement, extension needs/tests Needs (more) tests priority/2 Priority (lower number equals higher priority) status/in-progress Issue is in progress/work

Comments

@prashanth26
Copy link
Contributor

prashanth26 commented Aug 17, 2020

What would you like to be added:
Improve the CI script to prevent any orphaned resources

Why is this needed:
We have in the past observed orphaned volumes on the deletion of machines due to new API changes. Shall regressions must be checked by double-checking on infra resources (VMs. Disks, NICs) before CI tests terminate.

@prashanth26 prashanth26 added kind/enhancement Enhancement, improvement, extension needs/tests Needs (more) tests priority/critical Needs to be resolved soon, because it impacts users negatively labels Aug 17, 2020
@hardikdr
Copy link
Member

/assign

@gardener-robot gardener-robot added the status/in-progress Issue is in progress/work label Oct 22, 2020
@gardener-robot gardener-robot added priority/2 Priority (lower number equals higher priority) and removed priority/critical Needs to be resolved soon, because it impacts users negatively labels Mar 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement Enhancement, improvement, extension needs/tests Needs (more) tests priority/2 Priority (lower number equals higher priority) status/in-progress Issue is in progress/work
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants