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

Feat: Extend resource_wait_for_uninstall #18

Draft
wants to merge 12 commits into
base: main
Choose a base branch
from
Draft

Feat: Extend resource_wait_for_uninstall #18

wants to merge 12 commits into from

Conversation

svteb
Copy link
Collaborator

@svteb svteb commented Feb 24, 2025

Description

The resource_wait_for_uninstall function is to be used in a pull request that will resolve #2194, but in its previous state it did not check that the associated resources (pods) were properly deleted. In some scenarios, such as a pod being stuck due to a finalizer, the function would not detect anything.

Related testsuite pull request: #XXXX

Pull request is currently based on #17 and will need to be rebased after #17 is merged.

Issues:

Refs: #2194

How has this been tested:

  • Covered by existing integration testing
  • Added integration testing to cover
  • Verified all A/C passes
    • develop
    • master
    • tag/other branch
  • Test environment
    • Shared Packet K8s cluster
    • New Packet K8s cluster
    • Kind cluster
  • Have not tested

Types of changes:

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update

Checklist:

Documentation

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • No updates required.

Code Review

  • Does the test handle fatal exceptions, ie. rescue block

Issue

  • Tasks in issue are checked off

@svteb svteb force-pushed the wait_for_pods branch 2 times, most recently from 97190bf to 3113035 Compare February 24, 2025 09:51
Refs: #2194
- Change allows for a deep check that will verify if associated
resources (pods) of some core resource were deleted.
- In some cases a pod finalizer may be stuck which would force the
user to manually cancel cnf_uninstall and not be informed of what is
happening.
- Changes to the delete module were warranted since --wait=true flag
is set by default, thus this parameter never affected anything. The
change is also necessary since the waiting will be done through
resource_wait_for_uninstall instead (the default value will be false).

Signed-off-by: svteb <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] Cleanup not waiting for resources to remove
2 participants