k8s 1.25.0 #27490
k8s 1.25.0 #27490
Conversation
openshift-ci
bot
added
the
do-not-merge/hold
|
/payload 4.12 ci blocking |
|
@soltysh: trigger 4 job(s) of type blocking for the ci release of OCP 4.12
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/37f00a50-53a9-11ed-8a5b-47bb2f715871-0 |
openshift-ci
bot
added
e2e-images-update
|
/test lint |
|
/retest-required |
|
/payload 4.12 ci blocking |
|
@soltysh: trigger 4 job(s) of type blocking for the ci release of OCP 4.12
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/4ff36730-53d3-11ed-8ada-cae838cd733b-0 |
|
/payload 4.12 ci blocking Retesting for confirmation. We don't want to reintroduce this just yet since we got a streak of 6 rejected payloads and then it stopped once this was reverted, but the above payload command did succeed. The problems could've been something with infra... but I can't tell for sure from the logs. |
|
@stbenjam: trigger 4 job(s) of type blocking for the ci release of OCP 4.12
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/0b819600-5467-11ed-8b02-332ffce0dd4e-0 |
|
2x passed payload jobs. This is good to land after fixing the conflict. The only thing I can find in the failed jobs over the weekend is some failed ImagePullBackOffs, which must have contributed to the timeouts. |
openshift-merge-robot
added
the
needs-rebase
Following changes from openshift/library-go#1378
ExecuteTest was never executed anywhere, so not to confuse users how we run tests this is being removed.
setTestExclusion was matching against k8s.io/kubernetes/test/e2e/apps/disruption.go suffix, but since a while now, all packages vendored with go.mod report as: k8s.io/kubernetes@<version>/test/e2e/apps/disruption.go so this wasn't doing anything.
registry.k8s.io/pause:3.8 has problems with uncompressed windows layers which are not accepted by quay.io
…age tests The WaitForPod* methods has changed in kubernetes/kubernetes#109704 currently they are very strict about their expected state, so a quick run, like in most cases in these tests where we just print usage and complete won't likely catch running pod, so instead it's best to wait for it to finish.
soltysh
force-pushed
the
rebase-1.25.0
branch
from
2f6e13e to
209e426
Compare
openshift-merge-robot
removed
the
needs-rebase
|
/hold cancel |
openshift-ci
bot
removed
the
do-not-merge/hold
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: soltysh, stbenjam The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
|
@soltysh: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
This also broke all CSI tests. I can't even do a |
…e-1.25.0"" This reverts commit 1ec0eb3.
…e-1.25.0"" This reverts commit 1ec0eb3.
…e-1.25.0"" This reverts commit 1ec0eb3.
7 participants
This brings back #27416 which was reverted in #27489
/hold
until we solve problem with https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/aggregator-periodic-ci-openshift-release-master-ci-4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade/1583337789200535552