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 1731222: unwarranted SARs on foreground GC of objects with owner refs #102
Bug 1731222: unwarranted SARs on foreground GC of objects with owner refs #102
Conversation
@gabemontero: An error was encountered adding this pull request to the external tracker bugs for bug 1731222 on the Bugzilla server at https://bugzilla.redhat.com:
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. |
/bugzilla refresh |
@gabemontero: This pull request references Bugzilla bug 1731222, which is valid. 3 validation(s) were run on this bug
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. |
note for reviewers - I've confirmed this changes is not needed prior to 4.5, at least for templates I confirmed all the way back to 4.2 |
/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.
Nit on the commit & PR title:
- Reference the bug in the title line of the git commit
- Leave a shorter title that makes sense to a customer
You should continue to reference the upstream PR in the details of the commit.
6556e17
to
418f0ce
Compare
@gabemontero: This pull request references Bugzilla bug 1731222, which is valid. 3 validation(s) were run on this bug
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. |
both PR title and commit updated @adambkaplan |
all green tests again @deads2k @dmage @adambkaplan |
@gabemontero: This pull request references Bugzilla bug 1731222, which is valid. 3 validation(s) were run on this bug
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 cancel |
/lgtm |
/hold move the package to where you use it please |
…refs copy/use kubernetes/kubernetes#90534 for IsMutationForGC check
418f0ce
to
894f585
Compare
per slack conversation with @deads2k we put versions of the new mutating GC check in both packages |
/hold cancel |
/lgtm this duplication makes sense because these are logically distinct resources that are unlikely to live together long term. The upstream reference and the reflective test ensure they will stay in sync. This also eliminates a k/k dep. Good PR. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, gabemontero 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 |
@gabemontero: Some pull requests linked via external trackers have merged: openshift/openshift-apiserver#102. The following pull requests linked via external trackers have not merged:
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. |
See https://coreos.slack.com/archives/CB48XQ4KZ/p1588008887095400 for history
/assign @deads2k
@deads2k - I could not find any official guideline on how to (a presumably temporary until a rebase pulls it in) copy of k8s in lieu of vendoring; please advise if code changes / commit wording etc. need modification
/assign @dmage
@dmage if possible minimally pls make sure this change catches your instance of the problem
@openshift/openshift-team-developer-experience @bparees FYI
/hold
since the upstream PR kubernetes/kubernetes#90534 has not merged yet ... however, if during review we think it is just a matter of when I'll unhold