Skip to content

HYPERFLEET-1762 - openshift-hyperfleet: run verify-owners on architecture PRs that touch the ownership source - #86953

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
ciaranRoche:HYPERFLEET-1762-verify-owners
Oct 13, 2026
Merged

openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
ciaranRoche:HYPERFLEET-1762-verify-owners

Conversation

@ciaranRoche

@ciaranRoche ciaranRoche commented Oct 13, 2026 •

Copy link
Copy Markdown
Member

Adds a verify-owners presubmit for openshift-hyperfleet/architecture. It runs make verify-owners when a PR changes hyperfleet/docs/owners.yaml, hyperfleet/docs/owners.md, hyperfleet/docs/working-agreement.md, anything under hack/owners/ or the Makefile. The target checks the generated area table and the criteria copy are in sync with owners.yaml and that every path's approvers and reviewers match its area.

The build root gains make and python3-pyyaml so the target can run in the existing image.

Follow-up from review on openshift-hyperfleet/architecture#232.

Summary by CodeRabbit

The openshift-hyperfleet/architecture CI configuration now runs make verify-owners when a pull request changes the Makefile, files under hack/owners/, or specified ownership documentation. The project image now includes make and python3-pyyaml, which the check requires.

…h the ownership source

Adds a verify-owners presubmit for openshift-hyperfleet/architecture that
runs make verify-owners when a PR changes owners.yaml, owners.md, the
working agreement, the generator under hack/owners or the Makefile. The
target checks the generated area table and the criteria copy are in sync
with owners.yaml and that every path's approvers match its area. The
build root gains make and python3-pyyaml for it.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Oct 13, 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: Enterprise
  • Run ID: 5039afd0-67b0-4508-be19-6c6a9b4c594c
📥 Commits

Reviewing files that changed from the base of the PR and between 3b330f1 and 84e1e89.

⛔ Files ignored due to path filters (1)
  • ci-operator/jobs/openshift-hyperfleet/architecture/openshift-hyperfleet-architecture-main-presubmits.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (1)
  • ci-operator/config/openshift-hyperfleet/architecture/openshift-hyperfleet-architecture-main.yaml

Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 11 remain after this review.

Walkthrough

The HyperFleet architecture CI configuration installs make and python3-pyyaml and adds a verify-owners test for specified file changes.

Changes

Owner verification CI

Layer / File(s) Summary
Configure owner verification
ci-operator/config/openshift-hyperfleet/architecture/openshift-hyperfleet-architecture-main.yaml
The project image installs make and python3-pyyaml. A verify-owners test runs make verify-owners from the src container when the Makefile, hack/owners/, or listed documentation paths change.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~5 minutes

Change: Feature

Merge Risk: ⚪ Minimal · up to 84e1e

This adds a CI check for ownership files on architecture PRs. No concrete risk to production or merge readiness was identified.

Important

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

Failed Failed checks (1 error)

Check name Status Explanation Resolution
Container-Privileges Error The new verify-owners test runs from the src project image. That image is based on UBI and has no USER directive, so the test runs as root by default. The PR adds no non-root user or runtime sec… Run the project image as a non-root user, such as by creating or selecting an appropriate user after the package-installation step and adding USER <non-root-uid> to the Dockerfile. Alternatively, provide an explicit, security-reviewed jus…
Passed Passed checks (14 passed)
Check name Status Explanation
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 The pull request adds the static CI test name verify-owners. It does not add or change any Ginkgo It, Describe, Context, or When title. No dynamic test-title value is introduced.
Test Structure And Quality Passed The pull request changes only CI YAML configuration. It adds the verify-owners command, image packages, and generated presubmit job. It does not add or modify Ginkgo tests, cluster operations, asser…
Microshift Test Compatibility Passed The pull request changes only CI configuration and the generated presubmit job. It adds a verify-owners command and build dependencies; it does not add or modify Ginkgo e2e tests. The MicroShift tes…
Single Node Openshift (Sno) Test Compatibility Passed The pull request adds CI configuration and a verify-owners presubmit only. The authoritative diff contains no new Ginkgo e2e tests or test constructs such as It(), Describe(), Context(), or `W…
Topology-Aware Scheduling Compatibility Passed PASS: The pull request changes only CI configuration and generated presubmit job definitions. It adds build dependencies, a make verify-owners test, and a path-based trigger. It does not add or modi…
Ote Binary Stdout Contract Passed PASS: The pull request changes only CI YAML and generated presubmit configuration. It adds a make verify-owners job and build dependencies. It does not change an OTE binary, suite setup, or any proc…
Ipv6 And Disconnected Network Test Compatibility Passed PASS: The pull request changes only CI configuration and a generated presubmit job. It adds a verify-owners command, package installation, and path-based triggering. It does not add Ginkgo e2e tests…
No-Weak-Crypto Passed The pull request changes only CI configuration and a generated presubmit job. It adds build packages and a verify-owners test; it introduces no MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB usage, custom…
No-Sensitive-Data-In-Logs Passed The pull request adds a CI command and package dependencies. It does not add logging, secret interpolation, environment dumps, or output of passwords, tokens, API keys, PII, session IDs, hostnames, or…
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title clearly identifies the main change: adding the verify-owners check for OpenShift HyperFleet architecture pull requests that modify ownership sources.
Full details: Container-Privileges

Explanation

The new verify-owners test runs from the src project image. That image is based on UBI and has no USER directive, so the test runs as root by default. The PR adds no non-root user or runtime security context, and the description does not justify root execution. No privileged, host namespace, SYS_ADMIN, or allowPrivilegeEscalation setting was added.

Resolution

Run the project image as a non-root user, such as by creating or selecting an appropriate user after the package-installation step and adding USER &lt;non-root-uid&gt; to the Dockerfile. Alternatively, provide an explicit, security-reviewed justification for root execution and limit it to the build step where possible.

  • Fix all pre-merge checks with AI
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create a new PR

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

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@ciaranRoche: 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-hyperfleet-architecture-main-verify-owners openshift-hyperfleet/architecture presubmit Presubmit changed
pull-ci-openshift-hyperfleet-architecture-main-linkcheck openshift-hyperfleet/architecture presubmit Ci-operator config changed
pull-ci-openshift-hyperfleet-architecture-main-markdownlint openshift-hyperfleet/architecture presubmit Ci-operator config changed
pull-ci-openshift-hyperfleet-architecture-main-yamllint openshift-hyperfleet/architecture presubmit Ci-operator config changed

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.

@ciaranRoche

Copy link
Copy Markdown
Member Author

/pj-rehearse auto-ack

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@openshift-ci
openshift-ci Bot requested review from Mischulee and rafabene October 13, 2026 14:31
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 13, 2026
@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Oct 13, 2026
@openshift-ci

openshift-ci Bot commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

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

@pnguyen44

Copy link
Copy Markdown

Could you include the related ticket number in the PR title so this follow-up is traceable to the ownership rollout?

@ciaranRoche ciaranRoche changed the title openshift-hyperfleet: run verify-owners on architecture PRs that touch the ownership source HYPERFLEET-1762 - openshift-hyperfleet: run verify-owners on architecture PRs that touch the ownership source Oct 13, 2026
@pnguyen44

Copy link
Copy Markdown

/lgtm

@openshift-ci

openshift-ci Bot commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

@pnguyen44: changing LGTM is restricted to collaborators

Details

In response to this:

/lgtm

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.

@Mischulee

Copy link
Copy Markdown
Contributor

/lgtm

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

openshift-ci Bot commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ciaranRoche, Mischulee, pnguyen44

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-merge-bot
openshift-merge-bot Bot merged commit 4cdd511 into openshift:main Oct 13, 2026
22 checks passed
oharan2 pushed a commit to oharan2/release that referenced this pull request Oct 19, 2026
…h the ownership source (openshift#86953)

Adds a verify-owners presubmit for openshift-hyperfleet/architecture that
runs make verify-owners when a PR changes owners.yaml, owners.md, the
working agreement, the generator under hack/owners or the Makefile. The
target checks the generated area table and the criteria copy are in sync
with owners.yaml and that every path's approvers match its area. The
build root gains make and python3-pyyaml for it.

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
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. 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.

3 participants