Skip to content

Conversation

jacobsee
Copy link
Member

No description provided.

HirazawaUi and others added 30 commits July 29, 2025 00:02
…e-devices

KEP-127 - validation: Return an error if user namespaces are used with volumeDevices
fix: handle corner cases in the async preemption
ContainerRestartRules feature gate should work with probes
Reset metrics per status code also allow to  log the particular status
code that flake, in case the problem comes from an specific one.

Change-Id: I29f67d4c5d76449350f45049f45ce8325a2d0ddd
Test that assert on metrics use the returned status to sync the test, if
the metric is updated AFTER the state is returned the test will flake
because the assertion on the metric will race.

Change-Id: I317708a22cb47256c37dac3cab0463a2f925ad6b
The metrics assertion race with the metric update, and since this
happens at the serverside, we use an active look to check the metrics
instead of expecting to be updated immidiatly.

Change-Id: I9a64b66301d5f4ac3df0c0a01de10602a20f89ea
Also, fix its conformance description, which appears to have
accidentally been filled in with the description of the wrong test.
…d-image-pulling

remove broken test that depends on expired credential, remove hardcoded credential, add TODOs
…2e-failure

[PodLevelResources] Add missing label to Downward API test
Turned up during manual end-to-end testing of the Pod Certificates
feature.  This issue prevents podCertificate projected volumes from
successfully mounting.  Would have been caught by a feature e2e test.

After this fix, podCertificate volumes function correctly in a Kind
cluster.

Additionally, fix logging from podcertificatemanager.  In order for
projectionKey to have sensible logging output, its fields need to be
exported.
Adding check for nil pod resources in huge pages test
…flake

Fix apiserver service proxying e2e test flakiness
…expected network errors

Signed-off-by: Anish Ramasekar <[email protected]>
feat: trigger PreBindPreFlight in the binding cycle
smg247 and others added 17 commits August 24, 2025 15:24
Add featuregate for performantsecuritypolicy for storage
…teOncePodOnly

Tests with [Feature:SELinuxMountReadWriteOncePodOnly] must be skipped if
SELinuxMount feature gate is set to true. See
https://github.com/kubernetes/kubernetes/blob/1ce98e3c093e6c2eea794737de894394683c9ffb/test/e2e/storage/csimock/csi_selinux_mount.go#L50
for details how the SELinux tests use FeatureGate: / Feature: to test
various combinations of the gates.
Ensure that we remove the SELinuxMount check when the feature gate is
removed from k/k.

The code will fail to compile + the rebase person will find helpful
comments around.
…required to make build scripts work in our env

doot
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 24, 2025
@openshift-ci-robot
Copy link

@jacobsee: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci-robot
Copy link

@jacobsee: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci-robot
Copy link

@jacobsee: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@jacobsee
Copy link
Member Author

/retest

@openshift-ci-robot
Copy link

@jacobsee: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci-robot
Copy link

@jacobsee: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

Copy link

openshift-ci bot commented Aug 26, 2025

@jacobsee: 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-azure ec058a3 link false /test e2e-azure
ci/prow/k8s-e2e-gcp-five-control-plane-replicas ec058a3 link false /test k8s-e2e-gcp-five-control-plane-replicas
ci/prow/e2e-metal-ipi-ovn-dualstack ec058a3 link false /test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-openstack-csi-cinder ec058a3 link false /test e2e-openstack-csi-cinder
ci/prow/e2e-aws-ovn ec058a3 link false /test e2e-aws-ovn
ci/prow/e2e-aws-single-node ec058a3 link false /test e2e-aws-single-node
ci/prow/e2e-vsphere ec058a3 link false /test e2e-vsphere
ci/prow/e2e-aws-disruptive ec058a3 link false /test e2e-aws-disruptive
ci/prow/e2e-openstack-csi-manila ec058a3 link false /test e2e-openstack-csi-manila
ci/prow/k8s-e2e-aws ec058a3 link false /test k8s-e2e-aws
ci/prow/e2e-aws ec058a3 link false /test e2e-aws
ci/prow/e2e-metal-ipi-ovn-ipv6 e56627e link false /test e2e-metal-ipi-ovn-ipv6
ci/prow/unit 8f00372 link true /test unit
ci/prow/e2e-gcp 8f00372 link true /test e2e-gcp
ci/prow/k8s-e2e-aws-ovn-serial 8f00372 link false /test k8s-e2e-aws-ovn-serial
ci/prow/e2e-aws-ovn-techpreview-serial 8f00372 link false /test e2e-aws-ovn-techpreview-serial
ci/prow/e2e-aws-ovn-crun 8f00372 link true /test e2e-aws-ovn-crun
ci/prow/e2e-aws-ovn-cgroupsv2 8f00372 link true /test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-aws-ovn-serial 8f00372 link true /test e2e-aws-ovn-serial
ci/prow/e2e-aws-ovn-fips 8f00372 link true /test e2e-aws-ovn-fips
ci/prow/verify 8f00372 link true /test verify
ci/prow/e2e-aws-crun-wasm 8f00372 link true /test e2e-aws-crun-wasm
ci/prow/integration 8f00372 link true /test integration
ci/prow/e2e-aws-ovn-runc 8f00372 link true /test e2e-aws-ovn-runc
ci/prow/e2e-aws-ovn-techpreview 8f00372 link false /test e2e-aws-ovn-techpreview
ci/prow/k8s-e2e-gcp-ovn 8f00372 link true /test k8s-e2e-gcp-ovn
ci/prow/okd-scos-e2e-aws-ovn 8f00372 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-downgrade 8f00372 link true /test e2e-aws-ovn-downgrade
ci/prow/k8s-e2e-gcp-serial 8f00372 link true /test k8s-e2e-gcp-serial

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. vendor-update Touching vendor dir or related files
Projects
None yet
Development

Successfully merging this pull request may close these issues.