Skip to content

SREP-4053: Add rosa-e2e cluster profile#5034

Merged
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
dustman9000:rosa-e2e-profile
Mar 21, 2026
Merged

SREP-4053: Add rosa-e2e cluster profile#5034
openshift-merge-bot[bot] merged 1 commit intoopenshift:mainfrom
dustman9000:rosa-e2e-profile

Conversation

@dustman9000
Copy link
Member

@dustman9000 dustman9000 commented Mar 19, 2026

Summary

Register rosa-e2e as a cluster profile for the rosa-e2e nightly CI jobs.

  • Add ClusterProfileROSAE2E constant (rosa-e2e)
  • Add to AWS profile lists
  • Map to rosa-e2e-quota-slice boskos resource

The cluster profile secret (cluster-secrets-rosa-e2e) and boskos quota slices are already registered in openshift/release (PR #76494, merged).

The nightly periodic job PR (openshift/release#76427) depends on this profile being available.

Jira: https://redhat.atlassian.net/browse/SREP-4053

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 19, 2026

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

@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 19, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 19, 2026 •
edited by openshift-ci bot
Loading

@dustman9000: This pull request references SREP-4053 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 task to target the "4.22.0" version, but no target version was set.

Details

In response to this:

Summary

Register rosa-e2e as a cluster profile for the rosa-e2e nightly CI jobs.

  • Add ClusterProfileROSAE2E constant (rosa-e2e)
  • Add to AWS profile lists
  • Map to rosa-e2e-quota-slice boskos resource

The cluster profile secret (cluster-secrets-rosa-e2e) and boskos quota slices are already registered in openshift/release (PR #76494, merged).

The nightly periodic job PR (openshift/release#76427) depends on this profile being available.

Jira: https://redhat.atlassian.net/browse/SREP-4053

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.

@coderabbitai
Copy link

coderabbitai bot commented Mar 19, 2026 •
edited
Loading

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e1d40c9e-893f-407c-84b4-12eaf9c7296a

📥 Commits

Reviewing files that changed from the base of the PR and between 328c993 and 05b84d9.

📒 Files selected for processing (1)
  • pkg/api/types.go

Walkthrough

Added a new cluster profile ClusterProfileROSAE2E ("rosa-e2e") to the ClusterProfile enum and integrated it into ClusterProfiles(), ClusterType() (maps to AWS), and LeaseType() (returns "rosa-e2e-quota-slice").

Changes

Cohort / File(s) Summary
Cluster Profile Enumeration
pkg/api/types.go		 Added ClusterProfileROSAE2E constant and updated ClusterProfiles() to include it; mapped it to CloudAWS in ClusterType() and to "rosa-e2e-quota-slice" in LeaseType().

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@openshift-ci openshift-ci bot requested review from bear-redhat and smg247 March 19, 2026 21:30
@dustman9000
Copy link
Member Author

dustman9000 commented Mar 19, 2026

/override breaking-changes
breaking-changes failure is unrelated to this PR - AWS credential issue in cluster-init for build07. Same failure on PR #5032.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 19, 2026

@dustman9000: dustman9000 unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-release-oversight openshift-staff-engineers openshift-sustaining-engineers.

Details

In response to this:

/override breaking-changes
breaking-changes failure is unrelated to this PR - AWS credential issue in cluster-init for build07. Same failure on PR #5032.

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.

@dustman9000
Copy link
Member Author

dustman9000 commented Mar 20, 2026

/retest

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 20, 2026

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e

@bear-redhat
Copy link
Contributor

bear-redhat commented Mar 20, 2026

/lgtm

@bear-redhat
Copy link
Contributor

bear-redhat commented Mar 20, 2026

/lgtm cancel

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. and removed lgtm Indicates that a PR is ready to be merged. labels Mar 20, 2026
@dustman9000
SREP-4053: Add rosa-e2e cluster profile
05b84d9 
Register ClusterProfileROSAE2E with quota slice rosa-e2e-quota-slice
for the rosa-e2e nightly CI jobs. Secret maps to cluster-secrets-rosa-e2e
via the standard naming convention.
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 20, 2026

Tests from second stage were triggered manually. Pipeline can be controlled only manually, until HEAD changes. Use command to trigger second stage.

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Mar 20, 2026

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e

@bear-redhat
Copy link
Contributor

bear-redhat commented Mar 20, 2026

/test breaking-changes

@bear-redhat
Copy link
Contributor

bear-redhat commented Mar 20, 2026

/override breaking-changes

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 20, 2026

@bear-redhat: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • breaking-changes

Only the following failed contexts/checkruns were expected:

  • CodeRabbit
  • ci/prow/breaking-changes
  • ci/prow/checkconfig
  • ci/prow/codegen
  • ci/prow/e2e
  • ci/prow/format
  • ci/prow/frontend-checks
  • ci/prow/images
  • ci/prow/integration
  • ci/prow/lint
  • ci/prow/security
  • ci/prow/unit
  • ci/prow/validate-vendor
  • pull-ci-openshift-ci-tools-main-breaking-changes
  • pull-ci-openshift-ci-tools-main-checkconfig
  • pull-ci-openshift-ci-tools-main-codegen
  • pull-ci-openshift-ci-tools-main-e2e
  • pull-ci-openshift-ci-tools-main-format
  • pull-ci-openshift-ci-tools-main-frontend-checks
  • pull-ci-openshift-ci-tools-main-images
  • pull-ci-openshift-ci-tools-main-integration
  • pull-ci-openshift-ci-tools-main-lint
  • pull-ci-openshift-ci-tools-main-security
  • pull-ci-openshift-ci-tools-main-unit
  • pull-ci-openshift-ci-tools-main-validate-vendor
  • tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

Details

In response to this:

/override breaking-changes

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.

@bear-redhat
Copy link
Contributor

bear-redhat commented Mar 20, 2026

/override ci/prow/breaking-changes

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 20, 2026

@bear-redhat: Overrode contexts on behalf of bear-redhat: ci/prow/breaking-changes

Details

In response to this:

/override ci/prow/breaking-changes

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.

@bear-redhat
Copy link
Contributor

bear-redhat commented Mar 20, 2026

/lgtm

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

openshift-ci bot commented Mar 20, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bear-redhat, dustman9000

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:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 20, 2026
@dustman9000
Copy link
Member Author

dustman9000 commented Mar 21, 2026

/retest ci/prow/images

@dustman9000
Copy link
Member Author

dustman9000 commented Mar 21, 2026

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 21, 2026

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

@openshift-merge-bot openshift-merge-bot bot merged commit 14f4ba0 into openshift:main Mar 21, 2026
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@bear-redhat bear-redhat Awaiting requested review from bear-redhat

@smg247 smg247 Awaiting requested review from smg247

Assignees

@bear-redhat bear-redhat

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.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@dustman9000 @openshift-ci-robot @bear-redhat