Skip to content

OCPBUGS-99899: add os name exception for runc jobs - #31479

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
cpmeadors:fix/job-name-exception-for-runc-jobs
Aug 4, 2026
Merged

OCPBUGS-99899: add os name exception for runc jobs#31479
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
cpmeadors:fix/job-name-exception-for-runc-jobs

Conversation

@cpmeadors

@cpmeadors cpmeadors commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

[sig-ci] [Early] prow job name should match os version [Suite:openshift/conformance/parallel] test fails on runc jobs because 5.0 runc jobs use rhel-9 stream since runc is not in rhel-10. This adds another conditional for jobs with runc in their name to the check in validateStandaloneNodeOS().

Summary by CodeRabbit

  • Bug Fixes
    • Updated standalone node job detection so jobs containing -runc are correctly associated with the RHEL 9 operating system stream.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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 deads2k and p0lyn0mial August 3, 2026 15:45
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 3, 2026
@coderabbitai

coderabbitai Bot commented Aug 3, 2026

Copy link
Copy Markdown

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: Pro Plus

Run ID: c9571f1c-64d1-43d2-b57f-2d338b8f2df4

📥 Commits

Reviewing files that changed from the base of the PR and between b11a9a9 and 55a8cfb.

📒 Files selected for processing (1)
  • test/extended/ci/job_names.go
🚧 Files skipped from review as they are similar to previous changes (1)
  • test/extended/ci/job_names.go

Walkthrough

The standalone node OS validator now maps job names containing -runc to the rhel-9 OS stream.

Changes

Standalone node OS validation

Layer / File(s) Summary
Runc OS stream mapping
test/extended/ci/job_names.go
validateStandaloneNodeOS detects -runc in job names and assigns the rhel-9 target stream.

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

Suggested reviewers: deads2k, p0lyn0mial

🚥 Pre-merge checks | ✅ 14 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (14 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly identifies the runc job OS-name exception added by this pull request.
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 The commit changes only validateStandaloneNodeOS logic; all Ginkgo titles remain static descriptive strings with no dynamic values.
Test Structure And Quality ✅ Passed The patch adds only a target-stream conditional. It adds no It block, resource setup, cleanup, wait, or assertion, and it follows the existing validation pattern.
Microshift Test Compatibility ✅ Passed The patch adds only a -runc condition in validateStandaloneNodeOS; it adds no Ginkgo test declarations, so the new-test MicroShift compatibility check is not applicable.
Single Node Openshift (Sno) Test Compatibility ✅ Passed The PR adds only a -runc OS-stream condition in an existing helper; it adds no new Ginkgo tests or multi-node assumptions.
Topology-Aware Scheduling Compatibility ✅ Passed The patch changes only test/extended/ci/job_names.go, adding a job-name string check; it adds no manifests, operators, controllers, replicas, affinity, or scheduling constraints.
Ote Binary Stdout Contract ✅ Passed The patch only adds a strings.Contains branch inside validateStandaloneNodeOS, called from an It block; it adds no stdout or logging write.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed The patch adds only a -runc OS-stream condition in an existing helper; it adds no Ginkgo test and introduces no IPv4 or external-connectivity usage.
No-Weak-Crypto ✅ Passed The commit only adds a -runc job-name condition that selects rhel-9; it adds no cryptography, weak algorithms, custom crypto, or secret comparisons.
Container-Privileges ✅ Passed The PR changes only job-name matching logic in one Go file; the patch adds no privileged, host namespace, SYS_ADMIN, root, or allowPrivilegeEscalation configuration.
No-Sensitive-Data-In-Logs ✅ Passed The PR only adds a strings.Contains condition for -runc; it adds no logging or output and introduces no sensitive data exposure.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

@coderabbitai coderabbitai Bot 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.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@test/extended/ci/job_names.go`:
- Around line 276-277: Update the stream-selection logic around
validateStandaloneNodeOS so runc-rhcos10-guard is matched by the runc exception
before the rhcos10 condition, selecting rhel-9. Preserve the existing rhcos10
mapping for other job names.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Pro Plus

Run ID: fdb5a624-332b-4e61-9882-ca8634d50360

📥 Commits

Reviewing files that changed from the base of the PR and between e3c4a6b and b11a9a9.

📒 Files selected for processing (1)
  • test/extended/ci/job_names.go

Comment thread test/extended/ci/job_names.go Outdated
Comment on lines +276 to +277
} else if strings.Contains(jobName, "runc") {
targetStream = "rhel-9"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

rg -nP 'runc.*rhcos(?:9|10)|rhcos(?:9|10).*runc' .

Repository: openshift/origin

Length of output: 652


🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Inspect the relevant function and related job-name marker usage without running repository code.
wc -l test/extended/ci/job_names.go
sed -n '240,300p' test/extended/ci/job_names.go

printf '\n--- occurrences ---\n'
rg -n 'func .*jobName|targetStream|rhcos10|rhcos9|runc-rhcos10|container|rhcos10-guard|runc' test/extended/ci/job_names.go test/extended/node/runc_upgrade_cases.go

Repository: openshift/origin

Length of output: 11195


🏁 Script executed:

#!/bin/bash
set -euo pipefail

python3 - <<'PY'
from pathlib import Path
p = Path('test/extended/node/runc_upgrade_cases.go')
text = p.read_text()
for line in text.splitlines():
    if 'runcRHCOS10GuardPool' in line:
        print('Const line:', line.strip())
    if '"runc-rhcos10-guard"' in line:
        print('Job-name literal:', line.strip())

def target_stream(job_name: str) -> str:
    target_stream_var = "rhel-10"
    if "rhcos10" in job_name:
        target_stream_var = "rhel-10"
    elif "rhcos9" in job_name:
        target_stream_var = "rhel-9"
    elif "runc" in job_name:
        target_stream_var = "rhel-9"
    return target_stream_var

job = "runc-rhcos10-guard"
print("validateStandaloneNodeOS targetStream selected for", job, "=>", target_stream(job))
PY

Repository: openshift/origin

Length of output: 1667


Fix the job-name stream selection for runc-rhcos10-guard.

validateStandaloneNodeOS uses rhcos10 before runc, so runc-rhcos10-guard selects rhel-10 even though this guard pool is rhel-9 backed. Move the runc exception higher or handle this guard/job name explicitly.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@test/extended/ci/job_names.go` around lines 276 - 277, Update the
stream-selection logic around validateStandaloneNodeOS so runc-rhcos10-guard is
matched by the runc exception before the rhcos10 condition, selecting rhel-9.
Preserve the existing rhcos10 mapping for other job names.

@cpmeadors

Copy link
Copy Markdown
Contributor Author

/payload-job periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-serial-runc

@openshift-ci

openshift-ci Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

@cpmeadors: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-serial-runc

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/21ac6600-8f53-11f1-8ad8-61bf9eadfe34-0

@neisw

neisw commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

@cpmeadors since you have this open we may want to consult with @petr-muller as I'm seeing our 4.23 jobs now failing on this test

Comment thread test/extended/ci/job_names.go Outdated
targetStream = "rhel-10"
} else if strings.Contains(jobName, "rhcos9") {
targetStream = "rhel-9"
} else if strings.Contains(jobName, "runc") {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I wonder if we can do -runc- or at least -runc to avoid running into some weird unwanted component or test substring case

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

yes. that makes sense.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

done. I did some exploratory checking on jobs names with searches in sippy. "-runc" seemed the best choice.

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

@cpmeadors cpmeadors changed the title OCPBUGS-99899 - add os name exception for runc jobs OCPBUGS-99899: add os name exception for runc jobs Aug 3, 2026
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Aug 3, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@cpmeadors: This pull request references Jira Issue OCPBUGS-99899, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

[sig-ci] [Early] prow job name should match os version [Suite:openshift/conformance/parallel] test fails on runc jobs because 5.0 runc jobs use rhel-9 stream since runc is not in rhel-10. This adds another conditional for jobs with runc in their name to the check in validateStandaloneNodeOS().

Summary by CodeRabbit

  • Bug Fixes
  • Updated standalone node job detection so jobs containing runc are correctly associated with the RHEL 9 operating system stream.

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.

@cpmeadors
cpmeadors force-pushed the fix/job-name-exception-for-runc-jobs branch from b11a9a9 to 55a8cfb Compare August 3, 2026 17:42
@openshift-ci-robot

Copy link
Copy Markdown

@cpmeadors: This pull request references Jira Issue OCPBUGS-99899, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
Details

In response to this:

[sig-ci] [Early] prow job name should match os version [Suite:openshift/conformance/parallel] test fails on runc jobs because 5.0 runc jobs use rhel-9 stream since runc is not in rhel-10. This adds another conditional for jobs with runc in their name to the check in validateStandaloneNodeOS().

Summary by CodeRabbit

  • Bug Fixes
  • Updated standalone node job detection so jobs containing -runc are correctly associated with the RHEL 9 operating system stream.

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

Copy link
Copy Markdown
Contributor

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

@cpmeadors

Copy link
Copy Markdown
Contributor Author

/verified by "prow job name should match os version", specifically in https://pr-payload-tests.ci.openshift.org/runs/ci/21ac6600-8f53-11f1-8ad8-61bf9eadfe34-0

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Aug 3, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@cpmeadors: This PR has been marked as verified by "prow job name should match os version",specifically in https://pr-payload-tests.ci.openshift.org/runs/ci/21ac6600-8f53-11f1-8ad8-61bf9eadfe34-0.

Details

In response to this:

/verified by "prow job name should match os version", specifically in https://pr-payload-tests.ci.openshift.org/runs/ci/21ac6600-8f53-11f1-8ad8-61bf9eadfe34-0

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.

@petr-muller petr-muller left a comment

Copy link
Copy Markdown
Member

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 Aug 3, 2026
@openshift-ci

openshift-ci Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

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

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 [cpmeadors,petr-muller]

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

@neisw

neisw commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

/retest-required

@openshift-ci

openshift-ci Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

@cpmeadors: 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 45e45b5 into openshift:main Aug 4, 2026
22 checks passed
@openshift-ci-robot

Copy link
Copy Markdown

@cpmeadors: Jira Issue Verification Checks: Jira Issue OCPBUGS-99899
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-99899 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

[sig-ci] [Early] prow job name should match os version [Suite:openshift/conformance/parallel] test fails on runc jobs because 5.0 runc jobs use rhel-9 stream since runc is not in rhel-10. This adds another conditional for jobs with runc in their name to the check in validateStandaloneNodeOS().

Summary by CodeRabbit

  • Bug Fixes
  • Updated standalone node job detection so jobs containing -runc are correctly associated with the RHEL 9 operating system stream.

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.

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

4 participants