openshift
WIP OCPBUGS-22413: Use Centos 8 Stream mysql image in tests
@vrutkovs: This pull request references Jira Issue OCPBUGS-22413, which is invalid:
- expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED instead
Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.
The bug has been updated to refer to the pull request using the external bug tracker.
In response to this:
Reverts openshift/origin#28367
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.
Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: vrutkovs Once this PR has been reviewed and has the lgtm label, please assign bparees for approval. For more information see the Kubernetes Code Review Process.
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
/jira refresh /test e2e-gcp-ovn /test okd-e2e-gcp /payload-job periodic-ci-openshift-release-master-ci-4.15-upgrade-from-stable-4.14-e2e-aws-ovn-upgrade
@vrutkovs: trigger 1 job(s) for the /payload-(job|aggregate) command
- periodic-ci-openshift-release-master-ci-4.15-upgrade-from-stable-4.14-e2e-aws-ovn-upgrade
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/4be49bb0-7889-11ee-8587-7e4ac99345e0-0
@vrutkovs: This pull request references Jira Issue OCPBUGS-22413, which is valid. The bug has been moved to the POST state.
3 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target version (4.15.0) matches configured target version for branch (4.15.0)
- bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
In response to this:
/jira refresh /test e2e-gcp-ovn /test okd-e2e-gcp /payload-job periodic-ci-openshift-release-master-ci-4.15-upgrade-from-stable-4.14-e2e-aws-ovn-upgrade
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.
/test e2e-gcp-ovn /test okd-e2e-gcp /payload-job periodic-ci-openshift-release-master-ci-4.15-upgrade-from-stable-4.14-e2e-aws-ovn-upgrade
@vrutkovs: trigger 1 job(s) for the /payload-(job|aggregate) command
- periodic-ci-openshift-release-master-ci-4.15-upgrade-from-stable-4.14-e2e-aws-ovn-upgrade
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/bb9fe5b0-7896-11ee-8709-dfb3f54e9c87-0
/test e2e-gcp-ovn /test okd-e2e-gcp /payload-job periodic-ci-openshift-release-master-ci-4.15-upgrade-from-stable-4.14-e2e-aws-ovn-upgrade
@vrutkovs: trigger 1 job(s) for the /payload-(job|aggregate) command
- periodic-ci-openshift-release-master-ci-4.15-upgrade-from-stable-4.14-e2e-aws-ovn-upgrade
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/268220a0-78b5-11ee-9ca9-361f64afee57-0
/test e2e-gcp-ovn /test okd-e2e-gcp /payload-job periodic-ci-openshift-release-master-ci-4.15-upgrade-from-stable-4.14-e2e-aws-ovn-upgrade
@vrutkovs: trigger 1 job(s) for the /payload-(job|aggregate) command
- periodic-ci-openshift-release-master-ci-4.15-upgrade-from-stable-4.14-e2e-aws-ovn-upgrade
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/3d21b580-78e4-11ee-975a-ebfec2594e06-0
/test e2e-gcp-ovn /test okd-e2e-gcp /payload-job periodic-ci-openshift-release-master-ci-4.15-upgrade-from-stable-4.14-e2e-aws-ovn-upgrade
@vrutkovs: trigger 1 job(s) for the /payload-(job|aggregate) command
- periodic-ci-openshift-release-master-ci-4.15-upgrade-from-stable-4.14-e2e-aws-ovn-upgrade
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/e3207b60-7952-11ee-96c8-6cc509032d05-0
/test e2e-gcp-ovn /test okd-e2e-gcp /payload-job periodic-ci-openshift-release-master-ci-4.15-upgrade-from-stable-4.14-e2e-aws-ovn-upgrade
@vrutkovs: trigger 1 job(s) for the /payload-(job|aggregate) command
- periodic-ci-openshift-release-master-ci-4.15-upgrade-from-stable-4.14-e2e-aws-ovn-upgrade
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/168f5b90-7a45-11ee-9b01-2ca3ce4046a0-0
@vrutkovs: trigger 8 job(s) of type blocking for the nightly release of OCP 4.15
- periodic-ci-openshift-release-master-nightly-4.15-e2e-aws-sdn-upgrade
- periodic-ci-openshift-release-master-ci-4.15-e2e-azure-ovn-upgrade
- periodic-ci-openshift-release-master-ci-4.15-upgrade-from-stable-4.14-e2e-gcp-ovn-rt-upgrade
- periodic-ci-openshift-hypershift-release-4.15-periodics-e2e-aws-ovn-conformance
- periodic-ci-openshift-release-master-nightly-4.15-e2e-aws-ovn-serial
- periodic-ci-openshift-release-master-ci-4.15-e2e-aws-ovn-upgrade
- periodic-ci-openshift-release-master-nightly-4.15-e2e-metal-ipi-ovn-ipv6
- periodic-ci-openshift-release-master-nightly-4.15-e2e-metal-ipi-sdn-bm
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/d25cc400-7d4e-11ee-8c82-e19b6f5725a2-0
@vrutkovs: all tests passed!
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
@vrutkovs: This pull request references Jira Issue OCPBUGS-22413. The bug has been updated to no longer refer to the pull request using the external bug tracker.
In response to this:
Reverts openshift/origin#28367
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-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-sigs/prow repository.