Skip to content

[release-4.22] Release Testing 4.22.0-rc.3#6678

Open
agullon wants to merge 1 commit into
release-4.22from
release-testing-4.22.0-rc.3
Open

[release-4.22] Release Testing 4.22.0-rc.3#6678
agullon wants to merge 1 commit into
release-4.22from
release-testing-4.22.0-rc.3

Conversation

@agullon
Copy link
Copy Markdown
Contributor

@agullon agullon commented May 14, 2026

Release testing PR for MicroShift 4.22.0-rc.3. Do not merge.

Created by /microshift-release:automated-testing

pre-commit.check-secrets: ENABLED
@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 May 14, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 14, 2026

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

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 14, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: 98dd88f6-3cfa-4dd5-9b3f-3b7c0405904b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release-testing-4.22.0-rc.3

Comment @coderabbitai help to get the list of available commands and usage tips.

@agullon
Copy link
Copy Markdown
Contributor Author

agullon commented May 14, 2026

/test e2e-aws-tests-release
/test e2e-aws-tests-release-arm
/test e2e-aws-tests-bootc-release-el9
/test e2e-aws-tests-bootc-release-el10
/test e2e-aws-tests-bootc-release-arm-el9
/test e2e-aws-tests-bootc-release-arm-el10

@agullon
Copy link
Copy Markdown
Contributor Author

agullon commented May 15, 2026

/test e2e-aws-tests-bootc-release-el9
/test e2e-aws-tests-bootc-release-el10

@agullon
Copy link
Copy Markdown
Contributor Author

agullon commented May 15, 2026

/test e2e-aws-tests-bootc-release-el9
/test e2e-aws-tests-bootc-release-el10

2 similar comments
@agullon
Copy link
Copy Markdown
Contributor Author

agullon commented May 15, 2026

/test e2e-aws-tests-bootc-release-el9
/test e2e-aws-tests-bootc-release-el10

@agullon
Copy link
Copy Markdown
Contributor Author

agullon commented May 15, 2026

/test e2e-aws-tests-bootc-release-el9
/test e2e-aws-tests-bootc-release-el10

@agullon
Copy link
Copy Markdown
Contributor Author

agullon commented May 15, 2026

/test e2e-aws-tests-bootc-release-el9

3 similar comments
@agullon
Copy link
Copy Markdown
Contributor Author

agullon commented May 15, 2026

/test e2e-aws-tests-bootc-release-el9

@agullon
Copy link
Copy Markdown
Contributor Author

agullon commented May 17, 2026

/test e2e-aws-tests-bootc-release-el9

@agullon
Copy link
Copy Markdown
Contributor Author

agullon commented May 18, 2026

/test e2e-aws-tests-bootc-release-el9

@agullon agullon marked this pull request as ready for review May 18, 2026 09:17
@agullon
Copy link
Copy Markdown
Contributor Author

agullon commented May 18, 2026

/label backport-risk-assessed
/label jira/valid-bug
/verified by CI/lgtm

@openshift-ci openshift-ci Bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. labels May 18, 2026
@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label May 18, 2026
@openshift-ci-robot
Copy link
Copy Markdown

@agullon: This PR has been marked as verified by CI/lgtm.

Details

In response to this:

/label backport-risk-assessed
/label jira/valid-bug
/verified by CI/lgtm

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.

@agullon
Copy link
Copy Markdown
Contributor Author

agullon commented May 18, 2026

/lgtm

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 18, 2026

@agullon: you cannot LGTM your own PR.

Details

In response to this:

/lgtm

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
Copy Markdown
Contributor

openshift-ci Bot commented May 18, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: agullon

The full list of commands accepted by this bot can be found here.

Details 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

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 18, 2026

@agullon: all tests passed!

Full PR test history. Your PR dashboard.

Details

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

backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants