Make CentOS ImageStream json actually based on CentOS containers#372
Make CentOS ImageStream json actually based on CentOS containers#372daveol wants to merge 1 commit intosclorg:masterfrom
Conversation
📝 WalkthroughWalkthroughUpdated nginx-centos ImageStream metadata: tag names and the Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning Review ran into problems🔥 ProblemsGit: Failed to clone repository. Please run the 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. Comment |
Pull Request validationFailed🔴 Failed or pending statuses:
🔴 Review - Missing review from a member (1 required) |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@imagestreams/imagestreams.yaml`:
- Around line 18-19: The imagestreams.yaml entry for "CentOS Stream 8" declares
app_versions: ["1.22", "1.24"] but there is no corresponding build (no
1.22/Dockerfile.c8s), which results in an unresolved image tag like
quay.io/sclorg/nginx-122-c8s:latest; either remove "1.22" from the app_versions
array for the CentOS Stream 8 entry in imagestreams.yaml, or add the missing
1.22 build definition (e.g., create the 1.22/Dockerfile.c8s and related build
metadata) so that the nginx-centos.json quay tag resolves correctly.
🪄 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: defaults
Review profile: CHILL
Plan: Pro
Run ID: 79ea335c-167f-4d79-ba3b-66bda66354ac
📒 Files selected for processing (2)
imagestreams/imagestreams.yamlimagestreams/nginx-centos.json
Signed-off-by: Dave Olsthoorn <dolsthoorn@esri.nl>
2876e2b to
822e715
Compare
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
imagestreams/nginx-centos.json (1)
1-147:⚠️ Potential issue | 🔴 CriticalUpdate tests and verify image availability on Quay.io.
Tests in
test/test_ocp_shared_helm_imagestreams.py(lines 26-33) still reference old UBI tag names (e.g.,1.26-ubi10,1.24-ubi9) andregistry.redhat.ioinstead of the newel*tags andquay.io/sclorgreferences.Additionally, the images referenced in
nginx-centos.jsonhave availability issues:
quay.io/sclorg/nginx-120-c9s:latestreturns 404 (image does not exist)quay.io/sclorg/nginx-122-c9s:latestreturns 401 (access denied)quay.io/sclorg/nginx-126-c9s:latestreturns 401 (access denied)Update the test parameters to match the new tag scheme and ensure all referenced images are published and accessible on Quay.io.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@imagestreams/nginx-centos.json` around lines 1 - 147, Tests still reference old UBI tags and registry names and the imagestream references contain unavailable Quay images; update test/test_ocp_shared_helm_imagestreams.py to use the new tag scheme (replace occurrences like "1.26-ubi10", "1.24-ubi9" with "1.26-el10", "1.24-el8"/"1.24-el9" as appropriate) and change registry.redhat.io references to quay.io/sclorg, and then update imagestream data in nginx-centos.json to only reference Quay images that are actually published (replace or remove the failing names quay.io/sclorg/nginx-120-c9s:latest, quay.io/sclorg/nginx-122-c9s:latest, quay.io/sclorg/nginx-126-c9s:latest with available tags such as the matching el* images or point to the correct ImageStreamTag entries like "1.26-el9"/"1.26-el10"), and verify each image URL via an HTTP HEAD/curl request or Quay API before committing.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@imagestreams/nginx-centos.json`:
- Around line 1-147: Tests still reference old UBI tags and registry names and
the imagestream references contain unavailable Quay images; update
test/test_ocp_shared_helm_imagestreams.py to use the new tag scheme (replace
occurrences like "1.26-ubi10", "1.24-ubi9" with "1.26-el10",
"1.24-el8"/"1.24-el9" as appropriate) and change registry.redhat.io references
to quay.io/sclorg, and then update imagestream data in nginx-centos.json to only
reference Quay images that are actually published (replace or remove the failing
names quay.io/sclorg/nginx-120-c9s:latest, quay.io/sclorg/nginx-122-c9s:latest,
quay.io/sclorg/nginx-126-c9s:latest with available tags such as the matching el*
images or point to the correct ImageStreamTag entries like
"1.26-el9"/"1.26-el10"), and verify each image URL via an HTTP HEAD/curl request
or Quay API before committing.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 5beb7055-17b0-4e9f-b874-164a98fadd10
📒 Files selected for processing (2)
imagestreams/imagestreams.yamlimagestreams/nginx-centos.json
🚧 Files skipped from review as they are similar to previous changes (1)
- imagestreams/imagestreams.yaml
It seems something went wrong when creating the file
imagestreams\nginx-centos.jsonsince they point to the UBI images instead of the images produced based off CentOS Stream. This fixes that.Summary by CodeRabbit
*-ubi*to*-el*(e.g.,1.26-ubi9→1.26-el9) and set the "latest" tag to1.26-el9.1.24.