Skip to content

NVIDIA-1170: Add signed job(s) - #84324

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
josecastillolema:nvidiaci-signed
Sep 1, 2026
Merged

NVIDIA-1170: Add signed job(s)#84324
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
josecastillolema:nvidiaci-signed

Conversation

@josecastillolema

@josecastillolema josecastillolema commented Aug 31, 2026

Copy link
Copy Markdown
Member

Summary by CodeRabbit

  • Added a signed NVIDIA GPU Operator end-to-end job for the OpenShift 4.22 stable CI configuration.
  • Enabled AWS Secure Boot and precompiled NVIDIA drivers for the signed job.
  • Updated the AWS workflow to accept NVIDIAGPU_USE_PRECOMPILED_DRIVER.

Signed-off-by: Jose Castillo Lema <josecastillolema@gmail.com>

    gitleaks.version: 8.30.0
    gitleaks.check-secrets: ENABLED
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 31, 2026
@openshift-ci-robot

openshift-ci-robot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

@josecastillolema: This pull request references NVIDIA-1170 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.1.0" version, but no target version was set.

Details

In response to this:

Signed-off-by: Jose Castillo Lema josecastillolema@gmail.com

gitleaks.version: 8.30.0
gitleaks.check-secrets: ENABLED

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 the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 31, 2026
@coderabbitai

coderabbitai Bot commented Aug 31, 2026

Copy link
Copy Markdown
Contributor

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: Team

Run ID: 1b527497-9e95-4f6c-8740-6945cf5b62b7

📥 Commits

Reviewing files that changed from the base of the PR and between da194f4 and 4e24ae9.

⛔ Files ignored due to path filters (1)
  • ci-operator/jobs/rh-ecosystem-edge/nvidia-ci/rh-ecosystem-edge-nvidia-ci-main-presubmits.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (2)
  • ci-operator/config/rh-ecosystem-edge/nvidia-ci/rh-ecosystem-edge-nvidia-ci-main__4.22-stable.yaml
  • ci-operator/step-registry/nvidia-gpu-operator/e2e-aws/nvidia-gpu-operator-e2e-aws-workflow.yaml

Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review.


Walkthrough

The AWS workflow now accepts a precompiled-driver setting. The 4.22 stable configuration adds a signed NVIDIA GPU Operator test job with secure boot and precompiled drivers enabled.

Changes

Signed NVIDIA GPU Operator end-to-end test

Layer / File(s) Summary
Signed test workflow wiring
ci-operator/step-registry/nvidia-gpu-operator/e2e-aws/nvidia-gpu-operator-e2e-aws-workflow.yaml, ci-operator/config/rh-ecosystem-edge/nvidia-ci/rh-ecosystem-edge-nvidia-ci-main__4.22-stable.yaml
The AWS workflow accepts NVIDIAGPU_USE_PRECOMPILED_DRIVER. The 4.22 stable configuration adds the nvidia-gpu-operator-e2e-26-3-x-signed job with secure boot and precompiled drivers enabled.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Merge Risk: ⚪ Minimal · up to 4e24a

The change adds signed NVIDIA CI job configuration and workflow wiring, with no actionable merge-blocking risk remaining; it is merge-ready after normal checks and review.

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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 PASS. The pull request changes CI YAML only. It adds the static target nvidia-gpu-operator-e2e-26-3-x-signed and the static environment variable NVIDIAGPU_USE_PRECOMPILED_DRIVER. No Ginkgo It, `…
Test Structure And Quality ✅ Passed PASS: The pull request changes only CI YAML configuration and generated Prow job YAML. The diff adds a signed NVIDIA GPU Operator job and declares NVIDIAGPU_USE_PRECOMPILED_DRIVER; it does not add o…
Microshift Test Compatibility ✅ Passed PASS: The pull request adds CI configuration and one workflow environment variable, not new Ginkgo test declarations. The exact diff contains only YAML files; it adds the `nvidia-gpu-operator-e2e-26-3…
Single Node Openshift (Sno) Test Compatibility ✅ Passed PASS — The pull request adds CI YAML only. The diff adds the nvidia-gpu-operator-e2e-26-3-x-signed job, generated presubmit configuration, and the NVIDIAGPU_USE_PRECOMPILED_DRIVER workflow variabl…
Topology-Aware Scheduling Compatibility ✅ Passed PASS: The pull request changes only CI job configuration, a generated presubmit job, and a workflow environment-variable declaration. The diff adds no deployment manifest, operator code, controller, o…
Ote Binary Stdout Contract ✅ Passed PASS. The commit changes only three YAML files. It adds a signed CI job, a generated presubmit entry, and an environment-variable declaration. The diff contains no OTE source, main or suite setup code…
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PASS. The pull request adds CI YAML only: a signed variant of the existing nvidia-gpu-operator-e2e-26-3-x job and one optional workflow environment variable. The diff adds no Ginkgo test declaration…
No-Weak-Crypto ✅ Passed The pull request adds CI YAML for a signed Secure Boot job and declares NVIDIAGPU_USE_PRECOMPILED_DRIVER. The commit adds no MD5, SHA1, DES, 3DES, RC4, Blowfish, or ECB usage. It adds no crypto implem…
Container-Privileges ✅ Passed PASS. The pull request adds one CI job and one optional environment variable. The exact diff introduces no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, allowPrivilegeEscalation, o…
No-Sensitive-Data-In-Logs ✅ Passed PASS. The pull request adds a CI job, environment values, a workflow parameter declaration, and generated Prow configuration. It does not add logging code or log interpolation of secrets, tokens, cred…
Title check ✅ Passed The title clearly identifies the main change: adding signed NVIDIA GPU Operator CI job configuration. This matches the new secure-boot and precompiled-driver test job.
Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

Full details: Stable And Deterministic Test Names

Explanation

PASS. The pull request changes CI YAML only. It adds the static target nvidia-gpu-operator-e2e-26-3-x-signed and the static environment variable NVIDIAGPU_USE_PRECOMPILED_DRIVER. No Ginkgo It, Describe, Context, or When title is added or changed. The generated job contains a pod-IP field for CI infrastructure, not a test title.

Full details: Test Structure And Quality

Explanation

PASS: The pull request changes only CI YAML configuration and generated Prow job YAML. The diff adds a signed NVIDIA GPU Operator job and declares NVIDIAGPU_USE_PRECOMPILED_DRIVER; it does not add or modify Ginkgo test code. No new It, Eventually, Consistently, BeforeEach, AfterEach, or assertion code is present, so the listed test-structure requirements are not violated by this change.

Full details: Microshift Test Compatibility

Explanation

PASS: The pull request adds CI configuration and one workflow environment variable, not new Ginkgo test declarations. The exact diff contains only YAML files; it adds the nvidia-gpu-operator-e2e-26-3-x-signed job and passes NVIDIAGPU_USE_PRECOMPILED_DRIVER to the existing make run-tests step. Therefore, this check has no changed Ginkgo test to assess for unavailable MicroShift APIs or features.

Full details: Single Node Openshift (Sno) Test Compatibility

Explanation

PASS — The pull request adds CI YAML only. The diff adds the nvidia-gpu-operator-e2e-26-3-x-signed job, generated presubmit configuration, and the NVIDIAGPU_USE_PRECOMPILED_DRIVER workflow variable. It adds no Ginkgo test source and no It(), Describe(), Context(), or When() declarations. Therefore, the SNO multi-node assumption check is not applicable.

Full details: Topology-Aware Scheduling Compatibility

Explanation

PASS: The pull request changes only CI job configuration, a generated presubmit job, and a workflow environment-variable declaration. The diff adds no deployment manifest, operator code, controller, or scheduling constraint. The existing workflow replica settings remain unchanged, and the added job uses the existing nvidia-gpu-operator-e2e-aws workflow. No explicit topology-compatibility failure condition is introduced.

Full details: Ote Binary Stdout Contract

Explanation

PASS. The commit changes only three YAML files. It adds a signed CI job, a generated presubmit entry, and an environment-variable declaration. The diff contains no OTE source, main or suite setup code, logging calls, or stdout writes. The new job invokes the existing make run-tests workflow, so this pull request does not introduce the stated stdout contract violation.

Full details: Ipv6 And Disconnected Network Test Compatibility

Explanation

PASS. The pull request adds CI YAML only: a signed variant of the existing nvidia-gpu-operator-e2e-26-3-x job and one optional workflow environment variable. The diff adds no Ginkgo test declarations, Go files, IPv4 literals, URL downloads, public hostnames, or registry endpoints. The generated job uses the existing nvidia-gpu-operator-e2e-aws workflow and an internal quay-proxy.ci.openshift.org image reference. The custom check is therefore not triggered.

Full details: No-Weak-Crypto

Explanation

The pull request adds CI YAML for a signed Secure Boot job and declares NVIDIAGPU_USE_PRECOMPILED_DRIVER. The commit adds no MD5, SHA1, DES, 3DES, RC4, Blowfish, or ECB usage. It adds no crypto implementation or secret/token comparison. The added job only selects existing Secure Boot steps and a precompiled-driver option.

Full details: Container-Privileges

Explanation

PASS. The pull request adds one CI job and one optional environment variable. The exact diff introduces no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, allowPrivilegeEscalation, or security-context fields. The new job only sets AWS_SECUREBOOT_ENABLED, NVIDIAGPU_SUBSCRIPTION_CHANNEL, and NVIDIAGPU_USE_PRECOMPILED_DRIVER; the workflow change only documents the latter variable.

Full details: No-Sensitive-Data-In-Logs

Explanation

PASS. The pull request adds a CI job, environment values, a workflow parameter declaration, and generated Prow configuration. It does not add logging code or log interpolation of secrets, tokens, credentials, PII, or customer data. The new reporter template is identical to the existing template and reports only job status and a log URL. The added environment values are the literals "true", "v26.3", and an existing base domain; none is logged by the changed files.

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

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

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@josecastillolema: 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-rh-ecosystem-edge-nvidia-ci-main-4.22-stable-nvidia-gpu-operator-e2e-26-3-x-signed rh-ecosystem-edge/nvidia-ci presubmit Presubmit changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-5.0-stable-nvidia-gpu-operator-e2e-master rh-ecosystem-edge/nvidia-ci presubmit Registry content changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-5.0-stable-nvidia-gpu-operator-e2e-25-10-x rh-ecosystem-edge/nvidia-ci presubmit Registry content changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-5.0-stable-nvidia-gpu-operator-e2e-26-3-x rh-ecosystem-edge/nvidia-ci presubmit Registry content changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-5.0-stable-nvidia-gpu-operator-e2e-arm64 rh-ecosystem-edge/nvidia-ci presubmit Registry content changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-4.16-stable-nvidia-gpu-operator-e2e-master rh-ecosystem-edge/nvidia-ci presubmit Registry content changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-4.16-stable-nvidia-gpu-operator-e2e-25-10-x rh-ecosystem-edge/nvidia-ci presubmit Registry content changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-4.16-stable-nvidia-gpu-operator-e2e-26-3-x rh-ecosystem-edge/nvidia-ci presubmit Registry content changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-4.16-stable-nvidia-gpu-operator-e2e-arm64 rh-ecosystem-edge/nvidia-ci presubmit Registry content changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-4.22-stable-nvidia-gpu-operator-e2e-master rh-ecosystem-edge/nvidia-ci presubmit Registry content changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-4.22-stable-nvidia-gpu-operator-e2e-25-10-x rh-ecosystem-edge/nvidia-ci presubmit Registry content changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-4.22-stable-nvidia-gpu-operator-e2e-26-3-x rh-ecosystem-edge/nvidia-ci presubmit Registry content changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-4.22-stable-nvidia-gpu-operator-e2e-arm64 rh-ecosystem-edge/nvidia-ci presubmit Registry content changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-4.15-stable-nvidia-gpu-operator-e2e-master rh-ecosystem-edge/nvidia-ci presubmit Registry content changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-4.15-stable-nvidia-gpu-operator-e2e-25-10-x rh-ecosystem-edge/nvidia-ci presubmit Registry content changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-4.15-stable-nvidia-gpu-operator-e2e-26-3-x rh-ecosystem-edge/nvidia-ci presubmit Registry content changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-4.15-stable-nvidia-gpu-operator-e2e-arm64 rh-ecosystem-edge/nvidia-ci presubmit Registry content changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-4.14-stable-nvidia-gpu-operator-e2e-master rh-ecosystem-edge/nvidia-ci presubmit Registry content changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-4.14-stable-nvidia-gpu-operator-e2e-25-10-x rh-ecosystem-edge/nvidia-ci presubmit Registry content changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-4.14-stable-nvidia-gpu-operator-e2e-26-3-x rh-ecosystem-edge/nvidia-ci presubmit Registry content changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-4.14-stable-nvidia-gpu-operator-e2e-arm64 rh-ecosystem-edge/nvidia-ci presubmit Registry content changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-4.19-stable-nvidia-gpu-operator-e2e-master rh-ecosystem-edge/nvidia-ci presubmit Registry content changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-4.19-stable-nvidia-gpu-operator-e2e-25-10-x rh-ecosystem-edge/nvidia-ci presubmit Registry content changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-4.19-stable-nvidia-gpu-operator-e2e-26-3-x rh-ecosystem-edge/nvidia-ci presubmit Registry content changed
pull-ci-rh-ecosystem-edge-nvidia-ci-main-4.19-stable-nvidia-gpu-operator-e2e-arm64 rh-ecosystem-edge/nvidia-ci presubmit Registry content changed

A total of 46 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs.

A full list of affected jobs can be found here
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

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.

@josecastillolema

Copy link
Copy Markdown
Member Author

/pj-rehearse pull-ci-rh-ecosystem-edge-nvidia-ci-main-4.22-stable-nvidia-gpu-operator-e2e-26-3-x-signed

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@josecastillolema

Copy link
Copy Markdown
Member Author

/pj-rehearse ack

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@josecastillolema: 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 Sep 1, 2026

@vtruhpon vtruhpon left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

looks good

@vtruhpon

vtruhpon commented Sep 1, 2026

Copy link
Copy Markdown

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Sep 1, 2026
@openshift-ci

openshift-ci Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: josecastillolema, vtruhpon

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 commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

@josecastillolema: 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 4fdf569 into openshift:main Sep 1, 2026
19 checks passed
@nikitabugrovsky

Copy link
Copy Markdown

I think we should go with the newest GPU Operator version 26.7. Otherwise, LGTM.

@josecastillolema

Copy link
Copy Markdown
Member Author

I think we should go with the newest GPU Operator version 26.7. Otherwise, LGTM.

Totally @nikitabugrovsky , this PR was just for validating the e2e workflow, will open a new one including all the missing targets from OCP 4.20 onward.

@josecastillolema

Copy link
Copy Markdown
Member Author

@nikitabugrovsky continued in #84407

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. 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