-
Notifications
You must be signed in to change notification settings - Fork 170
OCPBUGS-65951: [release-4.20]: Fix linter issues, add missing cheryy-pick bits of #2844 #2866
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
OCPBUGS-65951: [release-4.20]: Fix linter issues, add missing cheryy-pick bits of #2844 #2866
Conversation
|
@ormergi: This pull request references Jira Issue OCPBUGS-64697, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
@ricky-rav @jcaamano could you please have a look? |
ricky-rav
left a comment
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
ricky-rav
left a comment
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.
Actually, when we add or modify code that involves ocp hacks, we should prefix the commit with CARRY:. Let's do it here too please.
Relax linter CI job by adding the missing bits of cherry-pick conflicts introduced by openshift#2844 Signed-off-by: Or Mergi <[email protected]>
ef663d4 to
85fa1bb
Compare
Done |
|
@ricky-rav tide is not happy with the spesified OCPBUG, do we really need another one or can we replace it to NO-JIRA? |
|
/retitle NO-JIRA: [release-4.20]: Fix linter issues, add missing cheryy-pick bits of #2844 |
|
@ormergi: This pull request explicitly references no jira issue. 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 openshift-eng/jira-lifecycle-plugin repository. |
ricky-rav
left a comment
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
No need for a jira ticket here, especially since 4.21 is not affected. (somehow my (Jira automation would work with a brand new 4.21 bug that we close as done right away and then a separate 4.20 bug linked to this...) |
|
/retest |
|
/retest-required |
|
/retest |
|
/override ci/prow/e2e-aws-ovn-windows |
|
/verified by ci/prow/lint |
|
@kyrtapz: This PR has been marked as verified by 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/retitle OCPBUGS-65951: [release-4.20]: Fix linter issues, add missing cheryy-pick bits of #2844 |
|
@ormergi: This pull request references Jira Issue OCPBUGS-65951, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/jira refresh |
|
@jluhrsen: This pull request references Jira Issue OCPBUGS-65951, 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/jira refresh |
|
@jluhrsen: This pull request references Jira Issue OCPBUGS-65951, which is valid. The bug has been moved to the POST state. 7 validation(s) were run on this bug
Requesting review from QA contact: 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 openshift-eng/jira-lifecycle-plugin repository. |
|
/retest-required |
|
@ormergi: The following test failed, say
Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
|
/retest-required |
|
this is a linter fix not affecting logic |
|
@kyrtapz: Overrode contexts on behalf of kyrtapz: ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-local-gw 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-sigs/prow repository. |
ecb7aac
into
openshift:release-4.20
|
@ormergi: Jira Issue Verification Checks: Jira Issue OCPBUGS-65951 Jira Issue OCPBUGS-65951 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓 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 openshift-eng/jira-lifecycle-plugin repository. |
📑 Description
Release-4.20 wont pass CI linter job causing PRs to fail on CI e.g.: #2827
This PR add the missing bits for the cherry-pick that introduced by #2844
Fixes #
Additional Information for reviewers
✅ Checks
How to verify it