Skip to content

OCPBUGS-86733: [release-1.36] Persist image repo digest across CRI-O restarts#9984

Merged
openshift-merge-bot[bot] merged 1 commit into
cri-o:release-1.36from
openshift-cherrypick-robot:cherry-pick-9925-to-release-1.36
Jun 1, 2026
Merged

OCPBUGS-86733: [release-1.36] Persist image repo digest across CRI-O restarts#9984
openshift-merge-bot[bot] merged 1 commit into
cri-o:release-1.36from
openshift-cherrypick-robot:cherry-pick-9925-to-release-1.36

Conversation

@openshift-cherrypick-robot

Copy link
Copy Markdown

This is an automated cherry-pick of #9925

/assign bitoku

Fixed a bug where ImageRef in container status changed from a repo@digest to a raw image ID hash after CRI-O restart.

/cherrypick release-1.35 release-1.34 release-1.33

Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
@openshift-ci-robot

Copy link
Copy Markdown

@openshift-cherrypick-robot: Could not make automatic cherrypick of Jira Issue OCPBUGS-81273 for this PR as the target version is not set for this branch in the jira plugin config. Running refresh:
/jira refresh

Details

In response to this:

This is an automated cherry-pick of #9925

/assign bitoku

Fixed a bug where ImageRef in container status changed from a repo@digest to a raw image ID hash after CRI-O restart.

/cherrypick release-1.35 release-1.34 release-1.33

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 release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels May 29, 2026
@openshift-ci openshift-ci Bot requested review from QiWang19 and klihub May 29, 2026 10:17
@coderabbitai

coderabbitai Bot commented May 29, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 9dab198e-2d03-4138-baf3-84aebc614c39

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ 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 and usage tips.

@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. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 29, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@openshift-ci-robot: This pull request references Jira Issue OCPBUGS-81273, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED instead
  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-81273 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

@openshift-cherrypick-robot: Could not make automatic cherrypick of Jira Issue OCPBUGS-81273 for this PR as the target version is not set for this branch in the jira plugin config. Running refresh:
/jira refresh

In response to this:

This is an automated cherry-pick of #9925

/assign bitoku

Fixed a bug where ImageRef in container status changed from a repo@digest to a raw image ID hash after CRI-O restart.

/cherrypick release-1.35 release-1.34 release-1.33

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.

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.

@codecov

codecov Bot commented May 29, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 67.51%. Comparing base (28178a8) to head (a3d864b).

Additional details and impacted files
@@               Coverage Diff                @@
##           release-1.36    #9984      +/-   ##
================================================
+ Coverage         67.47%   67.51%   +0.03%     
================================================
  Files               215      215              
  Lines             29683    29691       +8     
================================================
+ Hits              20030    20046      +16     
- Misses             7943     7946       +3     
+ Partials           1710     1699      -11     
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@bitoku

bitoku commented May 29, 2026

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 29, 2026
@saschagrunert saschagrunert changed the title [release-1.36] OCPBUGS-81273: Persist image repo digest across CRI-O restarts OCPBUGS-86733: [release-1.36] Persist image repo digest across CRI-O restarts May 29, 2026
@openshift-ci-robot openshift-ci-robot removed the jira/severity-critical Referenced Jira bug's severity is critical for the branch this PR is targeting. label May 29, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-86733, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-86733 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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 is an automated cherry-pick of #9925

/assign bitoku

Fixed a bug where ImageRef in container status changed from a repo@digest to a raw image ID hash after CRI-O restart.

/cherrypick release-1.35 release-1.34 release-1.33

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.

@saschagrunert

Copy link
Copy Markdown
Member

/jira refresh

@openshift-ci-robot

Copy link
Copy Markdown

@saschagrunert: This pull request references Jira Issue OCPBUGS-86733, which is invalid:

  • expected Jira Issue OCPBUGS-86733 to depend on a bug in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

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.

@saschagrunert

Copy link
Copy Markdown
Member

/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 May 29, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@saschagrunert: This pull request references Jira Issue OCPBUGS-86733, which is valid. The bug has been moved to the POST state.

5 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-81273 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • bug has dependents
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 commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, saschagrunert

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 Jun 1, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit 9b267d9 into cri-o:release-1.36 Jun 1, 2026
56 of 59 checks passed
@openshift-ci-robot

Copy link
Copy Markdown

@openshift-cherrypick-robot: Jira Issue OCPBUGS-86733: All pull requests linked via external trackers have merged:

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

Details

In response to this:

This is an automated cherry-pick of #9925

/assign bitoku

Fixed a bug where ImageRef in container status changed from a repo@digest to a raw image ID hash after CRI-O restart.

/cherrypick release-1.35 release-1.34 release-1.33

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-cherrypick-robot

Copy link
Copy Markdown
Author

@openshift-cherrypick-robot: new pull request created: #9992

Details

In response to this:

This is an automated cherry-pick of #9925

/assign bitoku

Fixed a bug where ImageRef in container status changed from a repo@digest to a raw image ID hash after CRI-O restart.

/cherrypick release-1.35 release-1.34 release-1.33

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.

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. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. 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. release-note Denotes a PR that will be considered when it comes time to generate release notes.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants