OCPBUGS-42045: Add IBM Public Cloud PreSubmit E2E for Ingress Operator #56785
Conversation
openshift-ci-robot
added
jira/severity-important
|
@gcs278: This pull request references Jira Issue OCPBUGS-42045, 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. |
openshift-ci
bot
added
the
approved
|
/jira refresh |
openshift-ci-robot
added
jira/valid-bug
|
@gcs278: This pull request references Jira Issue OCPBUGS-42045, 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. |
|
/pj-rehearse |
|
@gcs278: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-openshift-cluster-ingress-operator-master-e2e-ibmcloud-operator |
|
@gcs278: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@gcs278: This pull request references Jira Issue OCPBUGS-42045, 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. |
gcs278
force-pushed
the
add-ibm-cloud-e2e
branch
2 times, most recently
from
bf97d35 to
2781cac
Compare
|
Not that bad first run, looks like the issue is Load Balancer HostName resolution. It's taking over 5 minutes for IBM Public Cloud. I think it's related to https://issues.redhat.com/browse/OCPBUGS-14966 |
|
/pj-rehearse pull-ci-openshift-cluster-ingress-operator-master-e2e-ibmcloud-operator |
|
@gcs278: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
CI infra issue: /pj-rehearse pull-ci-openshift-cluster-ingress-operator-master-e2e-ibmcloud-operator |
|
@gcs278: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
| @@ -1107,6 +1107,85 @@ presubmits: | |||
| secret: | |||
| secretName: result-aggregator | |||
| trigger: (?m)^/test( | .* )e2e-hypershift,?($|\s.*) | |||
| - agent: kubernetes | |||
| always_run: true | |||
There was a problem hiding this comment.
Can this be always_run: false, at least initially?
There was a problem hiding this comment.
Yes good idea to get started. We can always come back and update it. Done.
|
/assign |
gcs278
force-pushed
the
add-ibm-cloud-e2e
branch
from
2781cac to
6a0fafb
Compare
|
@gcs278: This pull request references Jira Issue OCPBUGS-42045, which is valid. 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. |
|
/hold Revision 0e2bb9b was retested 3 times: holding |
openshift-ci
bot
added
the
do-not-merge/hold
gcs278
force-pushed
the
add-ibm-cloud-e2e
branch
from
0e2bb9b to
3151642
Compare
|
@Miciah I think a recent update caused Could I get another LGTM please? |
gcs278
force-pushed
the
add-ibm-cloud-e2e
branch
from
3151642 to
d02c803
Compare
|
Whoops, did |
|
@gcs278: 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. |
openshift-ci-robot
removed
the
rehearsals-ack
|
/lgtm |
The Ingress Operator was lacking a presubmit E2E job for IBM Public Cloud. This change adds a IBM Public Cloud presubmit job as optional and always_run=false so that we can identify issues in CI.
gcs278
force-pushed
the
add-ibm-cloud-e2e
branch
from
d02c803 to
e8702da
Compare
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/unhold |
openshift-ci
bot
removed
the
do-not-merge/hold
|
Nothing changed since the last ack, and the CI job is expected to fail anyways. |
|
@gcs278: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
openshift-ci-robot
added
the
rehearsals-ack
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: gcs278, Miciah 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 |
|
@gcs278: Jira Issue OCPBUGS-42045: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-42045 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 openshift-eng/jira-lifecycle-plugin repository. |
openshift#56785) The Ingress Operator was lacking a presubmit E2E job for IBM Public Cloud. This change adds a IBM Public Cloud presubmit job as optional and always_run=false so that we can identify issues in CI.
The Ingress Operator was lacking a presubmit E2E job for IBM Public Cloud. This change adds a IBM Public Cloud presubmit job as optional and always_run=false so that we can identify issues in CI.