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
Bug 1982046: lib/resourcedelete: Always check delete progress #629
Bug 1982046: lib/resourcedelete: Always check delete progress #629
Conversation
@jottofar: This pull request references Bugzilla bug 1982046, which is invalid:
Comment In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
9024d17
to
711d079
Compare
/bugzilla refresh |
@jottofar: This pull request references Bugzilla bug 1982046, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Bugzilla (yanyang@redhat.com), skipping review request. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/hold |
/test images |
5ce2fcd
to
a961ed8
Compare
/retitle Bug 1982046: lib/resourcedelete: Always check delete progress |
@jottofar: This pull request references Bugzilla bug 1982046, which is valid. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Bugzilla (yanyang@redhat.com), skipping review request. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
a961ed8
to
ac2f54d
Compare
/unhold |
/retest |
ac2f54d
to
0c482d5
Compare
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/hold
/cc @wking @LalatenduMohanty
Loots fine to me (except the comment below to improve the diff), feel free to pull the hold
} | ||
existing, err := client.CustomResourceDefinitions().Get(ctx, required.Name, metav1.GetOptions{}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's no real reason to move this higher, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not required but I did it so this matches resourcedelete
delete methods. Also, a minor thing, but now resource
is declared closer to where it's used.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/hold cancel |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/lgtm cancel
Must be a bad rebase |
0c482d5
to
19fa33e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jottofar, LalatenduMohanty, vrutkovs The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@jottofar: All pull requests linked via external trackers have merged: Bugzilla bug 1982046 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Previously delete methods would simply return when not in UpdateMode. This meant that if a delete was started in UpdateMode but had not completed while in UpdateMode the delete would never be marked as completed and minor upgrades would remain blocked. With this change deletes are continuously checked which also means a deleted resource that is recreated is logged as such by CVO even when not in UpdateMode. Deletes are still only requested when in UpdateMode.