Skip to content

Conversation

@bertinatto
Copy link
Member

No description provided.

k8s-ci-robot and others added 30 commits July 28, 2025 23:18
…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
…cycle

Fix prerelease-lifecycle for volumeattributesclass
…ding-conditions

Implement DRA Device Binding Conditions (KEP-5007)
* HPA support for pod-level resource specifications

* Add e2e tests for HPA support for pod-level resource specifications
Clear pod.Status.NominatedNodeName when pod is bound
…ation

Fix incorrect validation on the kubelet
…ssue_133249

test: fix TestStructuredAuthenticationConfigReload flake by handling expected network errors
When pod-level resources are detected, the cpu and memory manages
cannot engage because the feature is not yet compatible,
one of the main reasons being the managers only work at container level.

So, the managers has to detect if pod level resources are in use,
and turn themselves to no-operation skipping resource allocation
should that be the case.

We add an intentional loud log to inform the user, because
pods with pod-level resources landing on a node which cannot
actuate the desired spec is likely to be undesirable.

Signed-off-by: Francesco Romani <[email protected]>
Signed-off-by: Francesco Romani <[email protected]>
…nslator_WebSocketServerErrors

Deflake test stream translator web socket server errors
Add / update kubelet and DRA API owners
…_all_cases

KEP-5278 Stop clearing NominatedNodeName in all cases
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 15, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 15, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 15, 2025

@bertinatto: This pull request references OCPSTRAT-2371 which is a valid jira issue.

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.

@bertinatto
Copy link
Member Author

/retest

@bertinatto
Copy link
Member Author

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 15, 2025
@bertinatto
Copy link
Member Author

/retest

2 similar comments
@bertinatto
Copy link
Member Author

/retest

@bertinatto
Copy link
Member Author

/retest

@bertinatto
Copy link
Member Author

/verified by @bertinatto

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 16, 2025
@openshift-ci-robot
Copy link

@bertinatto: This PR has been marked as verified by @bertinatto.

In response to this:

/verified by @bertinatto

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.

@ardaguclu
Copy link
Member

/lgtm
feel free to unhold anytime

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 16, 2025
@bertinatto
Copy link
Member Author

/remove-label backports/unvalidated-commits

@openshift-ci openshift-ci bot removed the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Oct 16, 2025
@openshift-ci
Copy link

openshift-ci bot commented Oct 16, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ardaguclu, bertinatto

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@bertinatto
Copy link
Member Author

/test e2e-aws-ovn-hypershift

@bertinatto
Copy link
Member Author

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 16, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 00e7ec7 and 2 for PR HEAD 61114aa in total

@bertinatto
Copy link
Member Author

/retest

@bertinatto
Copy link
Member Author

/retest-required
This is a known DNS resolution problem in hypershift.

@bertinatto
Copy link
Member Author

/retest-required

@neisw
Copy link

neisw commented Oct 17, 2025

/override ci/prow/e2e-aws-ovn-hypershift

multi day infra outage still ongoing

@openshift-ci
Copy link

openshift-ci bot commented Oct 17, 2025

@neisw: Overrode contexts on behalf of neisw: ci/prow/e2e-aws-ovn-hypershift

In response to this:

/override ci/prow/e2e-aws-ovn-hypershift

multi day infra outage still ongoing

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.

@openshift-ci
Copy link

openshift-ci bot commented Oct 17, 2025

@bertinatto: The following test 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/okd-scos-e2e-aws-ovn 61114aa link false /test okd-scos-e2e-aws-ovn

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-merge-bot openshift-merge-bot bot merged commit 96593f3 into openshift:master Oct 17, 2025
23 of 24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. vendor-update Touching vendor dir or related files verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.