Skip to content

Bump ubi9/ubi-minimal from 9.7-1773939694 to 9.7-1776833838 in /build#236

Open
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/docker/build/ubi9/ubi-minimal-9.7-1776833838
Open

Bump ubi9/ubi-minimal from 9.7-1773939694 to 9.7-1776833838 in /build#236
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/docker/build/ubi9/ubi-minimal-9.7-1776833838

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 1, 2026

Bumps ubi9/ubi-minimal from 9.7-1773939694 to 9.7-1776833838.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by CodeRabbit

  • Chores
    • Updated container base image to the latest patch version for improved stability and security patches.

Bumps ubi9/ubi-minimal from 9.7-1773939694 to 9.7-1776833838.

---
updated-dependencies:
- dependency-name: ubi9/ubi-minimal
  dependency-version: 9.7-1776833838
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added area/dependency Issues or PRs related to dependency changes ok-to-test Indicates a non-member PR verified by an org member that is safe to test. labels May 1, 2026
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 1, 2026

Walkthrough

Docker runtime base image tag updated from 9.7-1773939694 to 9.7-1776833838 in the Dockerfile, representing a patch/build version increment for the Red Hat UBI 9 minimal image. No functional changes to build steps, labels, or configuration.

Changes

Cohort / File(s) Summary
Docker Runtime Base Image
build/Dockerfile
Updated UBI 9 minimal base image tag from 9.7-1773939694 to 9.7-1776833838 in the runtime stage.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 12
✅ Passed checks (12 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: bumping the Docker base image tag from one version to another in the /build directory.
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 The custom check regarding stable and deterministic Ginkgo test names is not applicable to this pull request. The PR exclusively modifies the Docker base image tag in build/Dockerfile and does not modify any test files.
Test Structure And Quality ✅ Passed The custom check reviews Ginkgo test code quality, but this PR only modifies the Docker base image tag in build/Dockerfile without any test code changes.
Microshift Test Compatibility ✅ Passed This custom check is not applicable to this pull request. The MicroShift Test Compatibility check is designed to validate new Ginkgo e2e tests for compatibility with MicroShift APIs and features. This PR exclusively modifies the Docker base image tag in build/Dockerfile (line 10) from 9.7-1773939694 to 9.7-1776833838, with no changes to any test files. Since no new Ginkgo tests are added or modified, there are no tests to evaluate for MicroShift compatibility.
Single Node Openshift (Sno) Test Compatibility ✅ Passed PR updates Docker base image tag only; no new Ginkgo e2e tests added, so check is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed This PR only modifies a Docker base image tag in the Dockerfile. No deployment manifests, operator code, controllers, or scheduling constraints are added or modified.
Ote Binary Stdout Contract ✅ Passed OTE Binary Stdout Contract check not applicable; PR only updates Docker base image tag in build/Dockerfile with no executable Go code changes.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PR only modifies Docker base image tag in build/Dockerfile. No Ginkgo e2e tests or test code added, so custom check for IPv6/disconnected network assumptions is not applicable.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch dependabot/docker/build/ubi9/ubi-minimal-9.7-1776833838

Review rate limit: 8/10 reviews remaining, refill in 11 minutes and 59 seconds.

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

@openshift-ci openshift-ci Bot requested review from vaidehi411 and xiaoyu74 May 1, 2026 18:00
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 1, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
Once this PR has been reviewed and has the lgtm label, please assign ravitri for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

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 the current code and only fix it if needed.

Inline comments:
In `@build/Dockerfile`:
- Line 10: The Dockerfile's FROM line uses a non-existent UBI9 tag; replace the
tag in the FROM instruction (FROM
registry.access.redhat.com/ubi9/ubi-minimal:9.7-1776833838) with a valid,
pullable tag or digest — e.g., update to 9.7-1776104705 (or 9.7-1773939694) or
the documented digest
sha256:fe688da81a696387ca53a4c19231e99289591f990c904ef913c51b6e87d4e4df;
alternatively, if that original tag lives in a private registry, point the FROM
to that private registry or ensure the build environment has access to it.
🪄 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: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 1ea30239-bcba-485a-864f-efad31c33cef

📥 Commits

Reviewing files that changed from the base of the PR and between d7bd07a and 5d9d726.

📒 Files selected for processing (1)
  • build/Dockerfile

Comment thread build/Dockerfile
RUN make build

FROM registry.access.redhat.com/ubi9/ubi-minimal:9.7-1773939694
FROM registry.access.redhat.com/ubi9/ubi-minimal:9.7-1776833838
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

What is the current sha256 digest for registry.access.redhat.com/ubi9/ubi-minimal:9.7-1776833838, and is this tag still the latest 9.7 build?

💡 Result:

The SHA256 digest for registry.access.redhat.com/ubi9/ubi-minimal:9.7-1776833838 could not be found in any searched sources. No references to this specific tag exist across GitHub updates tracking UBI images, Docker Hub mirrors (redhat/ubi9-minimal tags), Red Hat Ecosystem Catalog pages, or other technical sites. It is likely either a non-existent tag, a private/internal build not publicly indexed, or a future/planned tag not yet released as of 2026-05-01. This tag is not the latest 9.7 build. Public sources show newer 9.7 tags like 9.7-1776104705 (updated April 18, 2026, digest sha256:fe688da81a696387ca53a4c19231e99289591f990c904ef913c51b6e87d4e4df) and Docker Hub lists tags up to ~1773939694 with digests like sha256:f5346fbb587b (pushed ~10 days ago). The tag number 1776833838 is higher than documented updates, but absent from lists.

Citations:


The specified base image tag does not exist in public registries and cannot be pulled.

The tag 9.7-1776833838 is not found in any public Red Hat UBI9 sources (Docker Hub, Red Hat Ecosystem Catalog, FTP, or GitHub tracking). This will cause the Docker build to fail.

Either verify this tag exists in a private registry accessible during the build, or update to a confirmed valid tag. The latest documented 9.7 release is 9.7-1776104705 (April 18, 2026, digest sha256:fe688da81a696387ca53a4c19231e99289591f990c904ef913c51b6e87d4e4df), or use 9.7-1773939694 from the previous build.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@build/Dockerfile` at line 10, The Dockerfile's FROM line uses a non-existent
UBI9 tag; replace the tag in the FROM instruction (FROM
registry.access.redhat.com/ubi9/ubi-minimal:9.7-1776833838) with a valid,
pullable tag or digest — e.g., update to 9.7-1776104705 (or 9.7-1773939694) or
the documented digest
sha256:fe688da81a696387ca53a4c19231e99289591f990c904ef913c51b6e87d4e4df;
alternatively, if that original tag lives in a private registry, point the FROM
to that private registry or ensure the build environment has access to it.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 1, 2026

@dependabot[bot]: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/lint 5d9d726 link true /test lint

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.

@codecov-commenter
Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 55.67%. Comparing base (d7bd07a) to head (5d9d726).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #236   +/-   ##
=======================================
  Coverage   55.67%   55.67%           
=======================================
  Files          23       23           
  Lines        1895     1895           
=======================================
  Hits         1055     1055           
  Misses        785      785           
  Partials       55       55           
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/dependency Issues or PRs related to dependency changes ok-to-test Indicates a non-member PR verified by an org member that is safe to test.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant