Skip to content

coreos/coreos-assembler: use fedora:latest build_root image - #82629

Open
dustymabe wants to merge 1 commit into
openshift:mainfrom
dustymabe:dusty-update-cosa
Open

coreos/coreos-assembler: use fedora:latest build_root image#82629
dustymabe wants to merge 1 commit into
openshift:mainfrom
dustymabe:dusty-update-cosa

Conversation

@dustymabe

@dustymabe dustymabe commented Jul 29, 2026

Copy link
Copy Markdown
Member

Use a moving tag for the build_root image so we never have to update it again and also stop using this build_root image to replace the FROM in the Dockerfile [1] since there is really no need and it means we have to update two places when we actually update the Dockerfile to a new Fedora version.

This also drops the findutils RPM add. As far as AI and I could tell this is not a documented requirement and we couldn't find any git history reasoning on why this is actually required. Let's find out!

[1] https://github.com/coreos/coreos-assembler/blob/0ace2f67a9cb1b0495cc0ecd06bc9ba4c0e7bc1d/Dockerfile#L3

Summary by CodeRabbit

Updates the CoreOS assembler CI build configuration in openshift/release to use the moving quay.io/fedora/fedora:latest tag for the build_root image (so it no longer needs periodic Fedora version bumps), simplifies the build root to install only git and create a writable /go directory, and stops overriding the Dockerfile’s FROM (by removing the from: root behavior) to avoid duplicate Fedora version updates.

@dustymabe

Copy link
Copy Markdown
Member Author

/pj-rehearse auto-ack

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@coderabbitai

coderabbitai Bot commented Jul 29, 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: Pro Plus

Run ID: 87985a8a-be0f-4181-ba0b-9bdc6f51bb30

📥 Commits

Reviewing files that changed from the base of the PR and between dd697c0 and f9e3d9e.

📒 Files selected for processing (1)
  • ci-operator/config/coreos/coreos-assembler/coreos-coreos-assembler-main.yaml

Walkthrough

The CoreOS assembler CI configuration now uses Fedora latest as its build root, installs only git, retains writable /go setup, expands explanatory comments, and removes the redundant from: root image mapping.

Changes

CoreOS assembler build configuration

Layer / File(s) Summary
Update build root and image mapping
ci-operator/config/coreos/coreos-assembler/coreos-coreos-assembler-main.yaml
The build root image changes to quay.io/fedora/fedora:latest, findutils is removed from installation, comments are expanded, and the image item no longer declares from: root.

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

🚥 Pre-merge checks | ✅ 15
✅ Passed checks (15 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the main change: switching the build_root image to fedora:latest.
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 PR only changes a ci-operator YAML; no Ginkgo test titles or test files are modified.
Test Structure And Quality ✅ Passed No Ginkgo test files changed; the PR only updates ci-operator YAML, so this test-quality check is not applicable.
Microshift Test Compatibility ✅ Passed Only a CI config YAML changed; no new Ginkgo tests or MicroShift-sensitive APIs/features were added.
Single Node Openshift (Sno) Test Compatibility ✅ Passed Only a ci-operator YAML changed; no Ginkgo e2e tests were added or modified, so SNO compatibility is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed Only build-root/image config changed; no affinity, nodeSelector, PDB, or replica logic was added.
Ote Binary Stdout Contract ✅ Passed Only a ci-operator YAML changed; no process-level binary code or stdout writes were introduced.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed Only ci-operator config changed; no new or modified Ginkgo e2e tests were added, so the IPv6/disconnected-network check is not applicable.
No-Weak-Crypto ✅ Passed Only a CI YAML config changed; no weak crypto, custom crypto, or secret comparisons appear in the diff.
Container-Privileges ✅ Passed No changed manifest sets privileged, hostPID/Network/IPC, allowPrivilegeEscalation, SYS_ADMIN, or explicit root settings; only kvm capability remains.
No-Sensitive-Data-In-Logs ✅ Passed No new logging or debug output was added; the patch only changes build-root image config and contains no passwords, tokens, or sensitive data in logs.
✨ 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.

Use a moving tag for the build_root image so we never have to update it
again and also stop using this build_root image to replace the FROM in
the Dockerfile [1] since there is really no need and it means we have
to update two places when we actually update the Dockerfile to a new
Fedora version.

This also drops the findutils RPM add. As far as AI and I could tell
this is not a documented requirement and we couldn't find any git
history reasoning on why this is actually required. Let's find out!

[1] https://github.com/coreos/coreos-assembler/blob/0ace2f67a9cb1b0495cc0ecd06bc9ba4c0e7bc1d/Dockerfile#L3

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

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
`@ci-operator/config/coreos/coreos-assembler/coreos-coreos-assembler-main.yaml`:
- Around line 4-9: Replace the mutable FROM image in the coreos-assembler
build-root definition with a tested, immutable Fedora release or digest. Keep
the existing git installation and build-root requirements unchanged, and ensure
future image updates occur through controlled, reviewable changes.
🪄 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: b83b5cb6-7ec9-498a-aa00-c67a7769df46

📥 Commits

Reviewing files that changed from the base of the PR and between 5480392 and dd697c0.

📒 Files selected for processing (1)
  • ci-operator/config/coreos/coreos-assembler/coreos-coreos-assembler-main.yaml

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 29, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@dustymabe: 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-coreos-coreos-assembler-main-images coreos/coreos-assembler presubmit Ci-operator config changed
pull-ci-coreos-coreos-assembler-main-rhcos coreos/coreos-assembler 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 c4rt0 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Thanks for this, it is much better indeed. No more bumping the Fedora version every release in here.

lgtm

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

openshift-ci Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: c4rt0, dustymabe

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

@dustymabe

Copy link
Copy Markdown
Member Author

/pj-rehearse auto-ack

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

@dustymabe: your /pj-rehearse request was not processed because the request waited in queue for longer than 5 minutes. Please retry in a few minutes.

@dustymabe

Copy link
Copy Markdown
Member Author

/pj-rehearse auto-ack

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@openshift-ci

openshift-ci Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

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

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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants