OCPBUGS-39315: remove ingress operator exclusion #29093
Conversation
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: kannon92 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
kannon92
changed the title
openshift-ci-robot
added
the
jira/valid-reference
|
@kannon92: 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. |
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
|
@kannon92: The following tests 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. |
|
@kannon92 I investigated the logs here and I don't see any issues for cluster-ingress. Do you? |
|
/payload 4.18 informing |
yea, i think we gotta search for a job that actually triggers this. Not sure if it is covered in the default presubmits. |
|
/payload 4.18 nightly informing |
|
@kannon92: trigger 72 job(s) of type informing for the nightly release of OCP 4.18
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/708127f0-7111-11ef-8a2a-3bc56ba8cbf2-0 |
|
/payload 4.18 nightly blocking |
|
@kannon92: trigger 9 job(s) of type blocking for the nightly release of OCP 4.18
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/538d1480-7128-11ef-8c0b-e7390bea2fd0-0 |
|
If we can't find any failures, I'm happy to merge this PR. And we can monitor the CI to see if this failure occurs again. |
|
@kannon92 let me know if there's anything else I can do. It's not clear to me how to find issues in the payload tests you ran. |
|
@kannon92, I don't see any restarts for cluster-ingress-operator in CI. @openshift/openshift-team-network-edge is fine with the change. Do you want to remove the "wip" from the commit message and link this to OCPBUGS-39315? |
openshift-merge-robot
added
the
needs-rebase
kannon92
force-pushed
the
remove-ingress-operator-exception
branch
from
4375a9e
to
f409bd2
Compare
openshift-merge-robot
removed
the
needs-rebase
kannon92
changed the title
openshift-ci-robot
added
the
jira/invalid-bug
|
@kannon92: This pull request references Jira Issue OCPBUGS-39315, 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 |
|
@kannon92: This pull request references Jira Issue OCPBUGS-39315, 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 |
openshift-ci-robot
added
the
jira/valid-bug
|
@kannon92: This pull request references Jira Issue OCPBUGS-39315, which is valid. The bug has been moved to the POST state. 3 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. |
openshift-ci-robot
removed
the
jira/invalid-bug
done! |
cc @candita