Skip to content

COS-4080: openshift/os: add RHCOS 10 node image build#78929

Open
c4rt0 wants to merge 2 commits intoopenshift:mainfrom
c4rt0:add_rhel-10.2
Open

COS-4080: openshift/os: add RHCOS 10 node image build#78929
c4rt0 wants to merge 2 commits intoopenshift:mainfrom
c4rt0:add_rhel-10.2

Conversation

@c4rt0
Copy link
Copy Markdown
Contributor

@c4rt0 c4rt0 commented May 6, 2026

Add RHEL 10.2 node image build alongside the existing RHEL 9.8 in the openshift/os CI configs. Currently only the RHEL 9.8 node image is built.

Adds a second base_images entry (rhel-coreos-base:10.2) and a second images entry to build rhel-coreos-10 in:

  • openshift-os-master.yaml
  • openshift-os-release-5.0.yaml
  • openshift-os-release-5.1.yaml

Aditionally disabling 5.1 in the second commit.

Overview

This PR updates OpenShift CI configs in the openshift/os area to add RHEL CoreOS (RHCOS) / RHEL 10.2 node image builds so CI will validate el10 node images alongside the existing el9 builds.

Practical changes

  • Adds a new base_images entry rhel-coreos-base-10 (tag 10.2) and wires it into image builds.
  • Introduces image build pipelines:
    • rhel-coreos-10 (Containerfile; IMAGE_NAME openshift/ose-rhel-coreos-10; IMAGE_CPE set for el10)
    • rhel-coreos-10-extensions (extensions/Containerfile consuming rhel-coreos-10)
  • Updates promotion settings to exclude the new images from automatic promotion. For release branches (release-5.0 and release-5.1) promotion for the coreos images is disabled.
  • Adds the new coreos/rhel-coreos-base:10.2 entry to core-services/image-mirroring/_config.yaml so CI can mirror the base image.

Files changed (CI/config + mirroring):

  • ci-operator/config/openshift/os/openshift-os-master.yaml
  • ci-operator/config/openshift/os/openshift-os-release-5.0.yaml
  • ci-operator/config/openshift/os/openshift-os-release-5.1.yaml
  • core-services/image-mirroring/_config.yaml

Impact / notes for reviewers

  • CI will now build and test RHEL CoreOS 10.2 node images and their extensions in addition to RHEL 9.8, closing the previous el10 testing gap.
  • pj-rehearse runs failed for the author due to an import timeout for quay.io/openshift/ci:coreos_rhel-coreos-base_10.2 in the CI imagestream (missing tag), and the author could not inspect the coreos imagestream due to permission errors. Reviewers should verify the mirrored base image is available and that mirroring/import is succeeding for the new 10.2 tag before merging.
  • The author indicated intent to squash commits; travier suggested ensuring the image-mirroring config is updated (the mirroring entry for coreos/rhel-coreos-base:10.2 is present in this PR).

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 6, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 098a8776-3e75-4b7f-983f-7c2f5935375c

📥 Commits

Reviewing files that changed from the base of the PR and between be94f72 and 1cf23ac.

⛔ Files ignored due to path filters (1)
  • ci-operator/jobs/openshift/os/openshift-os-release-5.1-presubmits.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (4)
  • ci-operator/config/openshift/os/openshift-os-master.yaml
  • ci-operator/config/openshift/os/openshift-os-release-5.0.yaml
  • ci-operator/config/openshift/os/openshift-os-release-5.1.yaml
  • core-services/image-mirroring/_config.yaml
🚧 Files skipped from review as they are similar to previous changes (3)
  • ci-operator/config/openshift/os/openshift-os-release-5.0.yaml
  • ci-operator/config/openshift/os/openshift-os-master.yaml
  • ci-operator/config/openshift/os/openshift-os-release-5.1.yaml

Walkthrough

Adds RHEL CoreOS 10 to CI configs: a new base image rhel-coreos-base-10 (tag 10.2), two image builds (rhel-coreos-10, rhel-coreos-10-extensions), updates promotion exclusions, and adds the base to image-mirroring supplemental images.

Changes

RHEL CoreOS 10 Support

Layer / File(s) Summary
Base Image Declaration
ci-operator/config/openshift/os/openshift-os-master.yaml, ci-operator/config/openshift/os/openshift-os-release-5.0.yaml, ci-operator/config/openshift/os/openshift-os-release-5.1.yaml
Adds base_images.rhel-coreos-base-10 (namespace coreos, name rhel-coreos-base, tag 10.2).
Image Build Definitions
ci-operator/config/openshift/os/.../openshift-os-master.yaml, .../openshift-os-release-5.0.yaml, .../openshift-os-release-5.1.yaml
Adds images.items entries: rhel-coreos-10 (root Containerfile, build args including IMAGE_NAME and IMAGE_CPE, inputs from rhel-coreos-base-10) and rhel-coreos-10-extensions (extensions/Containerfile, inputs from rhel-coreos-10).
Promotion / Promotion Exclusions
ci-operator/config/openshift/os/.../openshift-os-master.yaml, .../openshift-os-release-5.0.yaml, .../openshift-os-release-5.1.yaml
Extends promotion.to.excluded_images to include rhel-coreos-10 and rhel-coreos-10-extensions; release-5.1 records these in a disabled promotion.to entry.
Image Mirroring Mapping
core-services/image-mirroring/_config.yaml
Adds coreos/rhel-coreos-base:10.2 to supplementalCIImages (namespace coreos, name rhel-coreos-base, tag 10.2).

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 12
✅ Passed checks (12 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically describes the main change: adding a RHEL CoreOS 10 (RHCOS 10) node image build to the openshift/os CI configurations.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed This PR modifies only YAML configuration files, not test code. The custom check for Ginkgo test name stability is not applicable to YAML CI operator and image-mirroring configuration changes.
Test Structure And Quality ✅ Passed PR contains only YAML configuration files. The custom check for Ginkgo test quality is not applicable as no test code is present.
Microshift Test Compatibility ✅ Passed No Ginkgo e2e tests are added in this PR. All changes are YAML CI configuration files. The check is not applicable to CI configuration changes.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR only modifies YAML configuration files. No Ginkgo e2e tests are added, so the SNO compatibility check does not apply.
Topology-Aware Scheduling Compatibility ✅ Passed The PR modifies CI infrastructure configuration files, not deployment manifests, operator code, or controllers. No scheduling constraints affecting topology are introduced.
Ote Binary Stdout Contract ✅ Passed PR modifies only YAML CI configuration files. No Go code changes, so OTE Binary Stdout Contract check is not applicable.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed Custom check is not applicable. The PR only modifies CI/CD configuration YAML files and does not add any Ginkgo e2e tests. Check specifically requires "new Ginkgo e2e tests" to be added.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

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

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started


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-merge-bot
Copy link
Copy Markdown
Contributor

@c4rt0, pj-rehearse: unable to determine affected jobs. This could be due to a branch that needs to be rebased. ERROR:

could not determine changed registry steps: could not load step registry: load cluster profile list: unmarshal file /var/tmp/gitrepo2290977441/ci-operator/step-registry/cluster-profiles/cluster-profiles-config.yaml: error unmarshaling JSON: while decoding JSON: json: cannot unmarshal array into Go value of type api.ClusterProfilesList
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 6, 2026
@openshift-ci openshift-ci Bot requested review from Rolv-Apneseth and jbtrystram May 6, 2026 16:23
@c4rt0 c4rt0 changed the title ci: add RHCOS 10 node image build for openshift/os [COS-4080]openshift/os: add RHCOS 10 node image build May 6, 2026
@c4rt0
Copy link
Copy Markdown
Contributor Author

c4rt0 commented May 6, 2026

/retest

Copy link
Copy Markdown
Contributor

@joelcapitao joelcapitao left a comment

Choose a reason for hiding this comment

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

We should also build the rhel-coreos-10-extensions like rhel-coreos-extensions (RHEL9).
Also, you need to run make jobs to re-generate the Prow jobs and commit the diff. It will clear the ci/prow/generated-config failure

@travier
Copy link
Copy Markdown
Member

travier commented May 7, 2026

Title should likely be in this format for the bot: COS-4080: openshift/os: add RHCOS 10 node image build

@travier
Copy link
Copy Markdown
Member

travier commented May 7, 2026

/retitle COS-4080: openshift/os: add RHCOS 10 node image build

@openshift-ci openshift-ci Bot changed the title [COS-4080]openshift/os: add RHCOS 10 node image build COS-4080: openshift/os: add RHCOS 10 node image build May 7, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented May 7, 2026

@c4rt0: This pull request references COS-4080 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 story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Add RHEL 10.2 node image build alongside the existing RHEL 9.8 in the openshift/os CI configs. Currently only the RHEL 9.8 node image is built.

Adds a second base_images entry (rhel-coreos-base:10.2) and a second images entry to build rhel-coreos-10 in:

  • openshift-os-master.yaml
  • openshift-os-release-5.0.yaml
  • openshift-os-release-5.1.yaml

Aditionally disabling 5.1 in the second commit.

Overview

This PR extends the OpenShift OS repository's CI pipeline to test RHEL 10.2-based node images alongside the existing RHEL 9.8 testing. Previously, CI only validated packages against RHEL 9.8 images, leaving RHEL 10-specific package changes untested.

Changes

The PR updates CI job configurations for the openshift/os repository across three branches:

  • openshift-os-master.yaml: Adds a new RHEL 10.2 base image (rhel-coreos-base-10) and introduces a corresponding build job for rhel-coreos-10 images
  • openshift-os-release-5.0.yaml: Adds the same RHEL 10.2 base image and build job
  • openshift-os-release-5.1.yaml: Adds the RHEL 10.2 base image and build job, with promotion rules disabled

Each configuration file also updates promotion rules to handle the new RHEL 10 image appropriately for its respective branch.

Impact

This change enables the CI pipeline to validate that package changes in the openshift/os repository work correctly for both RHEL 9.8 and RHEL 10.2 node images, closing a testing gap that previously allowed RHEL 10-specific issues to go undetected.

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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 7, 2026
@c4rt0
Copy link
Copy Markdown
Contributor Author

c4rt0 commented May 7, 2026

/pj-rehearse

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

@c4rt0: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@c4rt0
Copy link
Copy Markdown
Contributor Author

c4rt0 commented May 7, 2026

Thanks for the above comments @joelcapitao && @travier

The pj/rehearse is looking for coreos_rhel-coreos-base_10.2 on quay.io/openshift/ci which is not there.

ERRO[2026-05-07T12:46:49Z] 
  * could not run steps: step [input:rhel-coreos-base-10] failed: failed to wait for importing imagestreamtags on ci-op-nghvyg44/pipeline:rhel-coreos-base-10: failed to reimport the tag ci-op-nghvyg44/pipeline:rhel-coreos-base-10: unable to import tag ci-op-nghvyg44/pipeline:rhel-coreos-base-10 with message Internal error occurred: [dockerimage.image.openshift.io "quay.io/openshift/ci:coreos_rhel-coreos-base_10.2" not found, dockerimage.image.openshift.io "quay-proxy.ci.openshift.org/openshift/ci:coreos_rhel-coreos-base_10.2" not found] on the image stream even after (6) imports: timed out waiting for the condition 

AFAIK this isn't something related to tis PR. I tried finding current tags in the CI image stream but failed due to permission restrictions

oc get imagestream rhel-coreos-base -n coreos

Error from server (Forbidden): imagestreams.image.openshift.io "rhel-coreos-base" is forbidden: User "apiaseck" cannot get resource "imagestreams" in API group "image.openshift.io" in the namespace "coreos"

@c4rt0
Copy link
Copy Markdown
Contributor Author

c4rt0 commented May 7, 2026

Just to add to the above - I will squash the first and last commit of this PR once I clarify what else needs to be addressed here.

@travier
Copy link
Copy Markdown
Member

travier commented May 7, 2026

I think you need to add it to

coreos/rhel-coreos-base:9.8:

c4rt0 added 2 commits May 7, 2026 16:30
Add RHEL 10.2 node image and extensions build to CI for
openshift/os master, release-5.0, and release-5.1. Also add
rhel-coreos-base:10.2 to the CI image mirroring config.

Assisted-by: Claude Opus 4.6 <noreply@anthropic.com>
@c4rt0 c4rt0 force-pushed the add_rhel-10.2 branch from be94f72 to 1cf23ac Compare May 7, 2026 15:51
@openshift-ci openshift-ci Bot removed the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 7, 2026
@openshift-merge-bot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@c4rt0: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name Repo Type Reason
pull-ci-openshift-os-release-5.1-images openshift/os presubmit Presubmit changed
pull-ci-openshift-os-release-5.0-e2e-aws openshift/os presubmit Ci-operator config changed
pull-ci-openshift-os-release-5.0-images openshift/os presubmit Ci-operator config changed
pull-ci-openshift-os-master-e2e-aws openshift/os presubmit Ci-operator config changed
pull-ci-openshift-os-master-images openshift/os presubmit Ci-operator config changed
pull-ci-openshift-os-master-okd-scos-e2e-aws-ovn openshift/os presubmit Ci-operator config changed
pull-ci-openshift-os-master-okd-scos-images openshift/os presubmit Ci-operator config changed
pull-ci-openshift-os-release-5.1-e2e-aws openshift/os presubmit Ci-operator config changed
Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@c4rt0
Copy link
Copy Markdown
Contributor Author

c4rt0 commented May 7, 2026

/pj-rehearse more

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

@c4rt0: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@c4rt0
Copy link
Copy Markdown
Contributor Author

c4rt0 commented May 7, 2026

/retest-required

@c4rt0
Copy link
Copy Markdown
Contributor Author

c4rt0 commented May 7, 2026

/pj-rehearse

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

@c4rt0: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

Copy link
Copy Markdown
Contributor

@joelcapitao joelcapitao left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 7, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 7, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: c4rt0, joelcapitao
Once this PR has been reviewed and has the lgtm label, please assign deepsm007 for approval. For more information see the Code Review Process.

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

@c4rt0
Copy link
Copy Markdown
Contributor Author

c4rt0 commented May 7, 2026

/pj-rehearse pull-ci-openshift-os-release-5.0-images

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

@c4rt0: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@c4rt0
Copy link
Copy Markdown
Contributor Author

c4rt0 commented May 7, 2026

/pj-rehearse pull-ci-openshift-os-master-images

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

@c4rt0: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@c4rt0
Copy link
Copy Markdown
Contributor Author

c4rt0 commented May 7, 2026

/pj-rehearse pull-ci-openshift-os-release-5.1-images

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

@c4rt0: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@c4rt0
Copy link
Copy Markdown
Contributor Author

c4rt0 commented May 7, 2026

/pj-rehearse auto-ack

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

@c4rt0: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@c4rt0
Copy link
Copy Markdown
Contributor Author

c4rt0 commented May 7, 2026

I feel like the e2e-aws rehearsals are irrelevant here (triggered probably by the auto-ack) - I will ignore their results.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 7, 2026

@c4rt0: 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/rehearse/openshift/os/release-5.1/images 1cf23ac link unknown /pj-rehearse pull-ci-openshift-os-release-5.1-images
ci/rehearse/openshift/os/release-5.0/e2e-aws 1cf23ac link unknown /pj-rehearse pull-ci-openshift-os-release-5.0-e2e-aws
ci/rehearse/openshift/os/release-5.0/images 1cf23ac link unknown /pj-rehearse pull-ci-openshift-os-release-5.0-images
ci/rehearse/openshift/os/master/images 1cf23ac link unknown /pj-rehearse pull-ci-openshift-os-master-images
ci/rehearse/openshift/os/master/e2e-aws 1cf23ac link unknown /pj-rehearse pull-ci-openshift-os-master-e2e-aws

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.

@c4rt0
Copy link
Copy Markdown
Contributor Author

c4rt0 commented May 7, 2026

Hmmm, all of the rehearsals fail. Am I correct in thinking that this will only suceed after this PR merges? Does the rehearsal run against the cluster, which doesn't know about 10.2 yet?

INFO[2026-05-07T16:57:50Z] Tagging rhel-coreos-extensions into stable   
INFO[2026-05-07T16:57:50Z] Ran for 13m46s                               
ERRO[2026-05-07T16:57:50Z] Some steps failed:                           
ERRO[2026-05-07T16:57:50Z] 
  * could not run steps: step [input:rhel-coreos-base-10] failed: failed to wait for importing imagestreamtags on ci-op-lb187m71/pipeline:rhel-coreos-base-10: failed to reimport the tag ci-op-lb187m71/pipeline:rhel-coreos-base-10: unable to import tag ci-op-lb187m71/pipeline:rhel-coreos-base-10 with message Internal error occurred: [dockerimage.image.openshift.io "quay.io/openshift/ci:coreos_rhel-coreos-base_10.2" not found, dockerimage.image.openshift.io "quay-proxy.ci.openshift.org/openshift/ci:coreos_rhel-coreos-base_10.2" not found] on the image stream even after (6) imports: timed out waiting for the condition 
INFO[2026-05-07T16:57:50Z] Reporting job state 'failed' with reason 'executing_graph:step_failed:tagging_input_image' 

@c4rt0
Copy link
Copy Markdown
Contributor Author

c4rt0 commented May 8, 2026

I believe that's a valid assumption (based on some feedback)

/pj-rehearse ack

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

@c4rt0: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label May 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants