Bug 1942608
| Summary: | crictl cannot list the images with an error: error locating item named "manifest" for image with ID | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Vinu K <vkochuku> |
| Component: | Node | Assignee: | Qi Wang <qiwan> |
| Node sub component: | CRI-O | QA Contact: | Weinan Liu <weinliu> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | unspecified | CC: | aos-bugs, dwalsh, jokerman, qiwan, saniyer |
| Version: | 4.5 | Keywords: | Reopened |
| Target Milestone: | --- | ||
| Target Release: | 4.8.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Cause: When list the image, kubelet will try to get the satus of the image that hasn't done pulling.
Consequence: Hit the error `error locating item named "manifest"`.
Fix: Keep a list of imaegs that haven't finished pulling. When traverse throught the images, skip those images.
Result: Should not get error when list images.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-07-27 22:55:12 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Vinu K
2021-03-24 15:54:35 UTC
Hello Team, Any update on this? Thanks, Vinu K Hello Team, Do we have any temporary workaround for this to stop the continuous error reporting? Thanks, Vinu K Did not get completed this sprint. Change to MODIFIED since https://github.com/cri-o/cri-o/pull/4726 merged to crio:master. Hello Team, Thanks for the progress on this. Could you please confirm that if there is any workaround for the time being to stop the error alert or is it okay to ignore the error on the node with its missing manifest? Thanks, Vinu K Hello Team, CU has upgraded the cluster to 4.6.26 and still, the problem persists in the same master node. --- [core@master2 ~]$ sudo crictl images -q FATA[0000] listing images: rpc error: code = Unknown desc = error locating item named "manifest" for image with ID "9e11cc7364c9791ebf68949c852bf121cb4ae5829c925a1da6546be6f63b3536": file does not exist --- Should we bring the cluster to 4.8 to get rid of this error? The event log keeps reporting the error and CU expects a workaround. Thanks, Vinu K Hi Vine K, The fix is not included in 4.6.26. They can bring in the 4.8 clusters. And after re-pulling images, the data will be restored to the same place, as long as the ID of the image didn't change (i.e., a different image wasn't pushed to the same location that's specified using a tag). Thanks, Qi Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2438 Hello Team, CU has observed the same issue even after upgrading to 4.10. master2.ocpdev.stantec.com failed to get image stats: rpc error: code = Unknown desc = error locating item named "manifest" for image with ID "9e11cc7364c9791ebf68949c852bf121cb4ae5829c925a1da6546be6f63b3536": file does not exist Thanks, Vinu K Hi @vkochuku, thanks for the update. I will take a look later. Hello @qi wang, that you for your update. I have a question. Do we need to open a new Jira for this to track? Yes. It'd be better to have a new Jira bug to track this. You can assign it to me when you create that bug. Thanks. |