origin
origin copied to clipboard
openshift
Bug 2070320: IBMCloud: Move oauth External check
Move the check for External topology (ROKS) for the oauth requestheaders test, prior to any test steps being performed, such as authentication.
Related: https://bugzilla.redhat.com/show_bug.cgi?id=2070320
@cjschaef: This pull request references Bugzilla bug 2070320, which is invalid:
- expected the bug to target the "4.11.0" release, but it targets "---" instead
Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.
In response to this:
Bug 2070320: IBMCloud: Move oauth External check
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.
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@cjschaef: This pull request references Bugzilla bug 2070320, 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
- bug is open, matching expected state (open)
- bug target release (4.11.0) matches configured target release for branch (4.11.0)
- bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
No GitHub users were found matching the public email listed for the QA contact in Bugzilla ([email protected]), skipping review request.
In response to this:
/bugzilla refresh
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.
Failing required tests are not related to this test change, they all appear to be due to other test failures or failures during install steps. Attempting to retrigger.
/retest-required
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: cjschaef, ibihim
To complete the pull request process, please assign stlaz after the PR has been reviewed.
You can assign the PR to them by writing /assign @stlaz in a comment when ready.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@cjschaef: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/e2e-aws-cgroupsv2 | 29d2c4eafb9f2b9dac3f7ad108911d34d56698ab | link | false | /test e2e-aws-cgroupsv2 |
| ci/prow/e2e-aws-ovn-single-node-upgrade | 29d2c4eafb9f2b9dac3f7ad108911d34d56698ab | link | false | /test e2e-aws-ovn-single-node-upgrade |
| ci/prow/e2e-aws-ovn-cgroupsv2 | 29d2c4eafb9f2b9dac3f7ad108911d34d56698ab | link | false | /test e2e-aws-ovn-cgroupsv2 |
| ci/prow/e2e-aws-ovn-single-node-serial | 29d2c4eafb9f2b9dac3f7ad108911d34d56698ab | link | false | /test e2e-aws-ovn-single-node-serial |
| ci/prow/e2e-agnostic-ovn-cmd | 29d2c4eafb9f2b9dac3f7ad108911d34d56698ab | link | false | /test e2e-agnostic-ovn-cmd |
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/test-infra repository. I understand the commands that are listed here.
@cjschaef: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/e2e-aws-cgroupsv2 | 29d2c4eafb9f2b9dac3f7ad108911d34d56698ab | link | false | /test e2e-aws-cgroupsv2 |
| ci/prow/e2e-aws-ovn-single-node-upgrade | 29d2c4eafb9f2b9dac3f7ad108911d34d56698ab | link | false | /test e2e-aws-ovn-single-node-upgrade |
| ci/prow/e2e-aws-ovn-cgroupsv2 | 29d2c4eafb9f2b9dac3f7ad108911d34d56698ab | link | false | /test e2e-aws-ovn-cgroupsv2 |
| ci/prow/e2e-aws-ovn-single-node-serial | 29d2c4eafb9f2b9dac3f7ad108911d34d56698ab | link | false | /test e2e-aws-ovn-single-node-serial |
| ci/prow/e2e-agnostic-ovn-cmd | 29d2c4eafb9f2b9dac3f7ad108911d34d56698ab | link | false | /test e2e-agnostic-ovn-cmd |
| ci/prow/e2e-gcp-ovn-image-ecosystem | 29d2c4eafb9f2b9dac3f7ad108911d34d56698ab | link | true | /test e2e-gcp-ovn-image-ecosystem |
| ci/prow/e2e-aws-ovn-image-registry | 29d2c4eafb9f2b9dac3f7ad108911d34d56698ab | link | true | /test e2e-aws-ovn-image-registry |
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/test-infra repository. I understand the commands that are listed here.
@cjschaef: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/e2e-aws-cgroupsv2 | 29d2c4eafb9f2b9dac3f7ad108911d34d56698ab | link | false | /test e2e-aws-cgroupsv2 |
| ci/prow/e2e-vsphere-ovn-etcd-scaling | 29d2c4eafb9f2b9dac3f7ad108911d34d56698ab | link | false | /test e2e-vsphere-ovn-etcd-scaling |
| ci/prow/e2e-agnostic-ovn-cmd | 29d2c4eafb9f2b9dac3f7ad108911d34d56698ab | link | false | /test e2e-agnostic-ovn-cmd |
| ci/prow/e2e-aws-ovn-single-node-serial | 29d2c4eafb9f2b9dac3f7ad108911d34d56698ab | link | false | /test e2e-aws-ovn-single-node-serial |
| ci/prow/e2e-azure-ovn-etcd-scaling | 29d2c4eafb9f2b9dac3f7ad108911d34d56698ab | link | false | /test e2e-azure-ovn-etcd-scaling |
| ci/prow/e2e-aws-ovn-single-node-upgrade | 29d2c4eafb9f2b9dac3f7ad108911d34d56698ab | link | false | /test e2e-aws-ovn-single-node-upgrade |
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/test-infra repository. I understand the commands that are listed here.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
@openshift-bot: Closed this PR.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen. Mark the issue as fresh by commenting/remove-lifecycle rotten. Exclude this issue from closing again by commenting/lifecycle frozen./close
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.