Skip to content

[release-4.16] USHIFT-6687: Add aws templates for CI#6343

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.16from
pacevedom:USHIFT-6687-4.16
Mar 13, 2026
Merged

[release-4.16] USHIFT-6687: Add aws templates for CI#6343
openshift-merge-bot[bot] merged 1 commit intoopenshift:release-4.16from
pacevedom:USHIFT-6687-4.16

Conversation

@pacevedom
Copy link
Contributor

No description provided.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 12, 2026
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 12, 2026

@pacevedom: This pull request references USHIFT-6687 which is a valid jira issue.

Details

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.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 12, 2026
@coderabbitai
Copy link

coderabbitai bot commented Mar 12, 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: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 3af97490-809f-4d22-8814-e4d2bb72210b

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
  • Post copyable unit tests in a comment
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@openshift-ci openshift-ci bot requested review from ggiguash and kasturinarra March 12, 2026 12:43
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 12, 2026
@pacevedom pacevedom changed the base branch from main to release-4.16 March 12, 2026 12:45
@openshift-ci-robot
Copy link

openshift-ci-robot commented Mar 12, 2026

@pacevedom: This pull request references USHIFT-6687 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target either version "4.16." or "openshift-4.16.", but it targets "openshift-4.22" instead.

Details

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.

@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 12, 2026
@ggiguash
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 12, 2026
@pacevedom
Copy link
Contributor Author

/retest

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 13, 2026
@pmtk
Copy link
Member

pmtk commented Mar 13, 2026

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 13, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 13, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, pacevedom, pmtk

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

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [ggiguash,pacevedom,pmtk]

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
Contributor

openshift-ci bot commented Mar 13, 2026

@pacevedom: 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/verify-deps eaa9ece link true /test verify-deps
ci/prow/test-rpm eaa9ece link true /test test-rpm
ci/prow/ocp-full-conformance-serial-rhel-eus eaa9ece link true /test ocp-full-conformance-serial-rhel-eus
ci/prow/e2e-aws-tests-periodic-arm eaa9ece link true /test e2e-aws-tests-periodic-arm
ci/prow/test-unit eaa9ece link true /test test-unit
ci/prow/verify eaa9ece link true /test verify
ci/prow/e2e-aws-tests-cache-arm eaa9ece link true /test e2e-aws-tests-cache-arm
ci/prow/e2e-aws-tests-arm eaa9ece link true /test e2e-aws-tests-arm
ci/prow/e2e-aws-tests-bootc-periodic eaa9ece link true /test e2e-aws-tests-bootc-periodic
ci/prow/e2e-aws-tests eaa9ece link true /test e2e-aws-tests
ci/prow/e2e-aws-tests-bootc eaa9ece link true /test e2e-aws-tests-bootc
ci/prow/test-rebase eaa9ece link false /test test-rebase
ci/prow/e2e-aws-tests-bootc-periodic-arm eaa9ece link true /test e2e-aws-tests-bootc-periodic-arm
ci/prow/security eaa9ece link false /test security
ci/prow/e2e-aws-tests-cache eaa9ece link true /test e2e-aws-tests-cache
ci/prow/e2e-aws-tests-bootc-arm eaa9ece link true /test e2e-aws-tests-bootc-arm
ci/prow/e2e-aws-tests-periodic eaa9ece link true /test e2e-aws-tests-periodic
ci/prow/ocp-full-conformance-rhel-eus eaa9ece link true /test ocp-full-conformance-rhel-eus

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.

@pacevedom
Copy link
Contributor Author

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

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 13, 2026
@openshift-ci-robot
Copy link

@pacevedom: This PR has been marked as verified by CI.

Details

In response to this:

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

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.

@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. labels Mar 13, 2026
@openshift-merge-bot openshift-merge-bot bot merged commit b9661ec into openshift:release-4.16 Mar 13, 2026
13 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. 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. 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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants