Skip to content

DO NOT MERGE: ocp-next #2148

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Draft
wants to merge 2,423 commits into
base: master
Choose a base branch
from
Draft

DO NOT MERGE: ocp-next #2148

wants to merge 2,423 commits into from

Conversation

bertinatto
Copy link
Member

No description provided.

@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Nov 28, 2024
@openshift-ci-robot
Copy link

@bertinatto: 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 openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Nov 28, 2024
@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Nov 28, 2024

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 openshift-ci bot added vendor-update Touching vendor dir or related files approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Nov 28, 2024
@openshift-ci-robot
Copy link

@bertinatto: 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.

@bertinatto
Copy link
Member Author

/test verify

@openshift-ci-robot
Copy link

@bertinatto: 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.

@bertinatto
Copy link
Member Author

/test verify
/test images

@openshift-ci-robot
Copy link

@bertinatto: 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.

@bertinatto
Copy link
Member Author

/test all

@openshift-ci-robot
Copy link

@bertinatto: 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.

@bertinatto
Copy link
Member Author

/test all

@openshift-ci-robot
Copy link

@bertinatto: 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

@bertinatto: 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.

@bertinatto
Copy link
Member Author

/test k8s-e2e-gcp-ovn
/test k8s-e2e-gcp-serial
/test integration

@openshift-ci-robot
Copy link

@bertinatto: 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.

@bertinatto
Copy link
Member Author

/test all

@openshift-ci-robot
Copy link

@bertinatto: 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.

@bertinatto
Copy link
Member Author

/test k8s-e2e-gcp-ovn
/test k8s-e2e-gcp-serial

@openshift-ci-robot
Copy link

@bertinatto: 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.

@bertinatto
Copy link
Member Author

/test all

jsafrane and others added 11 commits June 12, 2025 14:04
@jsafrane @bertinatto
UPSTREAM: 131236: RWX tests should create RWX volumes
0f82ff7 
The test that checks that a volume can be accessed from multiple nodes
should create ReadWriteMany volume and not ReadWriteOnce.
@bertinatto
UPSTREAM: 131249: Kubelet: Randomize ClusterRole name in e2e
f723259
@bertinatto
UPSTREAM: 131361: Wait for resource quota status to be populated
f5eb2d2
@bertinatto
UPSTREAM: 131409: test/e2e/node/kubelet_authz.go: fix SAR to include …
5d97114 
…SA groups
@bertinatto
UPSTREAM: 131518: Don't reinitialize test framework during each test …
2a39671 
…case
@bertinatto
UPSTREAM: 131852: test/e2e/apimachinery/namespace.go: make OrderedNam…
8d4e686 
…espaceDeletion test serial
@haircommander @bertinatto
UPSTREAM: 132035: e2e: fix userns test
bff281c 
After creating two pods, we need to ensure we wait on each to be ready before we collect their logs
@bertinatto
UPSTREAM: <carry>: Add OpenShift tooling, images, configs and docs
37fff46
@bertinatto
UPSTREAM: <drop>: hack/update-vendor.sh
bbb7f19
@bertinatto
UPSTREAM: <drop>: make update
2743ce9
@bertinatto
UPSTREAM: <drop>: hack/update-vendor.sh
6dca016
@bertinatto
Copy link
Member Author

/payload-job periodic-ci-openshift-release-master-ci-4.20-e2e-azure-ovn-upgrade

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Jun 12, 2025

@bertinatto: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.20-e2e-azure-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/541b5c80-47d9-11f0-868b-f71c01c51862-0

@openshift-ci-robot
Copy link

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

The following commits are valid:

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.

@bertinatto
Copy link
Member Author

/test integration

@openshift-ci-robot
Copy link

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

The following commits are valid:

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.

@bertinatto
Copy link
Member Author

/test integration

10 similar comments
@bertinatto
Copy link
Member Author

/test integration

@bertinatto
Copy link
Member Author

/test integration

@bertinatto
Copy link
Member Author

/test integration

@bertinatto
Copy link
Member Author

/test integration

@bertinatto
Copy link
Member Author

/test integration

@bertinatto
Copy link
Member Author

/test integration

@bertinatto
Copy link
Member Author

/test integration

@bertinatto
Copy link
Member Author

/test integration

@bertinatto
Copy link
Member Author

/test integration

@bertinatto
Copy link
Member Author

/test integration

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. 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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.