Skip to content

UPSTREAM: <carry>: OCPBUGS-101774: Update registry.access.redhat.com/ubi9/ubi-minimal:latest Docker digest to 8eb2830 - #198

Merged
openshift-merge-bot[bot] merged 1 commit into
masterfrom
konflux/mintmaker/master/registry.access.redhat.com-ubi9-ubi-minimal-latest
Aug 18, 2026
Merged

UPSTREAM: <carry>: OCPBUGS-101774: Update registry.access.redhat.com/ubi9/ubi-minimal:latest Docker digest to 8eb2830#198
openshift-merge-bot[bot] merged 1 commit into
masterfrom
konflux/mintmaker/master/registry.access.redhat.com-ubi9-ubi-minimal-latest

Conversation

@red-hat-konflux-kflux-prd-rh03

@red-hat-konflux-kflux-prd-rh03 red-hat-konflux-kflux-prd-rh03 Bot commented Aug 4, 2026

Copy link
Copy Markdown

This PR contains the following updates:

Package Type Update Change
registry.access.redhat.com/ubi9/ubi-minimal final digest 2a98ec38eb2830

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "after 5am on tuesday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

To execute skipped test pipelines write comment /ok-to-test.


Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

@openshift-ci openshift-ci Bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Aug 4, 2026
@openshift-ci

openshift-ci Bot commented Aug 4, 2026

Copy link
Copy Markdown

Hi @red-hat-konflux-kflux-prd-rh03[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@gcs278

gcs278 commented Aug 5, 2026

Copy link
Copy Markdown

/assign @grzpiotrowski

@red-hat-konflux-kflux-prd-rh03
red-hat-konflux-kflux-prd-rh03 Bot force-pushed the konflux/mintmaker/master/registry.access.redhat.com-ubi9-ubi-minimal-latest branch from 7fbb2ad to 51e7a43 Compare August 11, 2026 08:02
@red-hat-konflux-kflux-prd-rh03 red-hat-konflux-kflux-prd-rh03 Bot changed the title UPSTREAM: <carry>: Update registry.access.redhat.com/ubi9/ubi-minimal:latest Docker digest to 48fa5d8 UPSTREAM: <carry>: Update registry.access.redhat.com/ubi9/ubi-minimal:latest Docker digest to 7c37290 Aug 11, 2026
@grzpiotrowski

grzpiotrowski commented Aug 13, 2026

Copy link
Copy Markdown

/retitle NE-2847: UPSTREAM: : Update registry.access.redhat.com/ubi9/ubi-minimal:latest Docker digest to 7c37290

@openshift-ci openshift-ci Bot changed the title UPSTREAM: <carry>: Update registry.access.redhat.com/ubi9/ubi-minimal:latest Docker digest to 7c37290 NE-2847: UPSTREAM: <carry>: Update registry.access.redhat.com/ubi9/ubi-minimal:latest Docker digest to 7c37290 Aug 13, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 13, 2026
@openshift-ci-robot

openshift-ci-robot commented Aug 13, 2026

Copy link
Copy Markdown

@red-hat-konflux-kflux-prd-rh03[bot]: This pull request references NE-2847 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

This PR contains the following updates:

Package Type Update Change
registry.access.redhat.com/ubi9/ubi-minimal final digest 2a98ec37c37290

Configuration

📅 Schedule: (UTC)

  • Branch creation
  • "after 5am on tuesday"
  • Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

To execute skipped test pipelines write comment /ok-to-test.


Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

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.

…:latest Docker digest to 8eb2830

Signed-off-by: red-hat-konflux-kflux-prd-rh03 <206760901+red-hat-konflux-kflux-prd-rh03[bot]@users.noreply.github.com>
@red-hat-konflux-kflux-prd-rh03
red-hat-konflux-kflux-prd-rh03 Bot force-pushed the konflux/mintmaker/master/registry.access.redhat.com-ubi9-ubi-minimal-latest branch from 51e7a43 to 3936eec Compare August 18, 2026 08:02
@red-hat-konflux-kflux-prd-rh03 red-hat-konflux-kflux-prd-rh03 Bot changed the title NE-2847: UPSTREAM: <carry>: Update registry.access.redhat.com/ubi9/ubi-minimal:latest Docker digest to 7c37290 UPSTREAM: <carry>: Update registry.access.redhat.com/ubi9/ubi-minimal:latest Docker digest to 8eb2830 Aug 18, 2026
@openshift-ci-robot openshift-ci-robot removed the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 18, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@red-hat-konflux-kflux-prd-rh03[bot]: No Jira issue is referenced in the title of this pull request.
To reference a jira issue, add 'XYZ-NNN:' to the title of this pull request and request another refresh with /jira refresh.

Details

In response to this:

This PR contains the following updates:

Package Type Update Change
registry.access.redhat.com/ubi9/ubi-minimal final digest 2a98ec38eb2830

Configuration

📅 Schedule: (UTC)

  • Branch creation
  • "after 5am on tuesday"
  • Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

To execute skipped test pipelines write comment /ok-to-test.


Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

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.

@grzpiotrowski

Copy link
Copy Markdown

/ok-to-test

@openshift-ci openshift-ci Bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Aug 18, 2026
@grzpiotrowski

Copy link
Copy Markdown

/retitle UPSTREAM: : OCPBUGS-101774: Update registry.access.redhat.com/ubi9/ubi-minimal:latest Docker digest to 8eb2830

@openshift-ci openshift-ci Bot changed the title UPSTREAM: <carry>: Update registry.access.redhat.com/ubi9/ubi-minimal:latest Docker digest to 8eb2830 UPSTREAM: <carry>: OCPBUGS-101774: Update registry.access.redhat.com/ubi9/ubi-minimal:latest Docker digest to 8eb2830 Aug 18, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. labels Aug 18, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@red-hat-konflux-kflux-prd-rh03[bot]: This pull request references Jira Issue OCPBUGS-101774, which is invalid:

  • expected the vulnerability to target either version "5.1.0." or "openshift-5.1.0.", but it targets "5.0.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

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

Details

In response to this:

This PR contains the following updates:

Package Type Update Change
registry.access.redhat.com/ubi9/ubi-minimal final digest 2a98ec38eb2830

Configuration

📅 Schedule: (UTC)

  • Branch creation
  • "after 5am on tuesday"
  • Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

To execute skipped test pipelines write comment /ok-to-test.


Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

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-ci-robot openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Aug 18, 2026

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

/lgtm
/approve

@grzpiotrowski

Copy link
Copy Markdown

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 18, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@grzpiotrowski: This pull request references Jira Issue OCPBUGS-101774, which is valid.

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

In response to this:

/jira refresh

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-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 18, 2026
@openshift-ci

openshift-ci Bot commented Aug 18, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: grzpiotrowski

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-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 18, 2026
@openshift-ci

openshift-ci Bot commented Aug 18, 2026

Copy link
Copy Markdown

@red-hat-konflux-kflux-prd-rh03[bot]: 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 c0da8cc into master Aug 18, 2026
5 checks passed
@openshift-ci-robot

Copy link
Copy Markdown

@red-hat-konflux-kflux-prd-rh03[bot]: Jira Issue OCPBUGS-101774: Some pull requests linked via external trackers have merged:

The following pull request, linked via external tracker, has not merged:

All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-101774 has not been moved to the MODIFIED state.

Details

In response to this:

This PR contains the following updates:

Package Type Update Change
registry.access.redhat.com/ubi9/ubi-minimal final digest 2a98ec38eb2830

Configuration

📅 Schedule: (UTC)

  • Branch creation
  • "after 5am on tuesday"
  • Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

To execute skipped test pipelines write comment /ok-to-test.


Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

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.

@red-hat-konflux-kflux-prd-rh03
red-hat-konflux-kflux-prd-rh03 Bot deleted the konflux/mintmaker/master/registry.access.redhat.com-ubi9-ubi-minimal-latest branch August 18, 2026 20:02
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/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. 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. 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.

3 participants