Skip to content

Add ROSA stage/integration/production dashboards#3316

Open
vkumar51 wants to merge 1 commit intoopenshift:mainfrom
vkumar51:add-rosa-dashboards
Open

Add ROSA stage/integration/production dashboards#3316
vkumar51 wants to merge 1 commit intoopenshift:mainfrom
vkumar51:add-rosa-dashboards

Conversation

@vkumar51
Copy link

@vkumar51 vkumar51 commented Mar 7, 2026

Summary

  • Add three ROSA dashboard entries (rosa-stage, rosa-integration, rosa-production) to Sippy, modeled after the existing ARO dashboard pattern (aro-integration, aro-stage, aro-production)
  • rosa-stage includes all 22 actively running ROSA and OSD-AWS osde2e periodic jobs from Prow (all run against stage environment)
  • rosa-integration and rosa-production are empty placeholders for future expansion

Jobs included in rosa-stage

Category Jobs Versions
ROSA Classic/STS nightly 7 4.16–4.22
ROSA HCP nightly 1 4.21
ROSA BYO-VPC proxy tests 2 latest
OSD-AWS nightly 7 4.16–4.22
OSD-AWS upgrades 4 z-stream + y-stream
OSD-AWS informing 1 latest

All job names verified against https://prow.ci.openshift.org/configured-jobs/openshift/osde2e

Context

ROSA (Red Hat OpenShift Service on AWS) currently has no Sippy dashboard visibility. Test results are scattered across Prow with no unified view. This PR brings ROSA in line with how ARO tracks its E2E test health via Sippy.

Expected dashboards after merge

  • sippy.dptools.openshift.org/sippy-ng/tests/rosa-stage
  • sippy.dptools.openshift.org/sippy-ng/tests/rosa-integration (empty, future use)
  • sippy.dptools.openshift.org/sippy-ng/tests/rosa-production (empty, future use)

Test plan

  • Verify rosa-stage dashboard appears on Sippy after next data refresh
  • Verify job results populate correctly (dependent on jUnit artifacts in GCS)
  • Verify rosa-integration and rosa-production dashboards appear as empty

🤖 Generated with Claude Code

Add three ROSA dashboard entries (rosa-stage, rosa-integration,
rosa-production) modeled after the existing ARO dashboard pattern.

rosa-stage includes all actively running ROSA and OSD-AWS osde2e
periodic jobs from Prow, all of which run against the stage
environment:
- ROSA Classic/STS nightly jobs (4.16-4.22)
- ROSA HCP nightly (4.21)
- ROSA BYO-VPC proxy tests
- OSD-AWS nightly jobs (4.16-4.22)
- OSD-AWS upgrade jobs (z-stream and y-stream)
- OSD-AWS informing suite

rosa-integration and rosa-production are empty placeholders for
future expansion when integration and production test jobs are added.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@openshift-ci-robot
Copy link

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 openshift-ci bot requested review from dgoodwin and smg247 March 7, 2026 17:51
@openshift-ci-robot
Copy link

Scheduling required tests:
/test e2e

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 7, 2026

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

Copy link
Member

@petr-muller petr-muller left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rosa-integration and rosa-production are empty placeholders for future expansion

Specific near future or just speculative? May be worth adding only once needed. No big deal either way, feel free to unhold as needed. LGTM otherwise.

/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 Mar 7, 2026
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 7, 2026
@petr-muller
Copy link
Member

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 7, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: petr-muller, vkumar51

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 7, 2026
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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants