Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2240252

Summary: container image inspections fails when performing a minor update from 17.0 to 17.1
Product: Red Hat OpenStack Reporter: David Hill <dhill>
Component: openstack-tripleo-commonAssignee: Brendan Shephard <bshephar>
Status: CLOSED DUPLICATE QA Contact: David Rosenfeld <drosenfe>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 17.1 (Wallaby)CC: ariveral, bshephar, ipanova, jbeaudoi, jmarti, jpretori, lbezdick, mburns, mitr, nalmond, obulatov, slinaber, visinha, ykarel
Target Milestone: ---Keywords: Reopened, Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-09 03:17:45 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 David Hill 2023-09-22 17:52:12 UTC
Description of problem:
container image inspections fails when performing a minor update from 17.0 to 17.1 ... all downloaded images fails inspection with:
~~~
Error: readObjectStart: expect { or n, but found , error found in #0 byte of ...||..., bigger context ...||...
Error: readObjectStart: expect { or n, but found , error found in #0 byte of ...||..., bigger context ...||...
Error: readObjectStart: expect { or n, but found , error found in #0 byte of ...||..., bigger context ...||...
Error: readObjectStart: expect { or n, but found , error found in #0 byte of ...||..., bigger context ...||...
Error: readObjectStart: expect { or n, but found , error found in #0 byte of ...||..., bigger context ...||...
~~~

If I manually pull the image from the CDN I can succesffully inspect the images.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 7 Ina Panova 2023-09-22 22:30:38 UTC
Adding @obulatov in case he hot any insights or recommendations to this situation.

Comment 11 Oleg Bulatov 2023-09-25 11:04:08 UTC
`podman inspect` interacts with local entities and shouldn't interact with remote registries, i.e. Quay is not involved here (at least that's my understanding so far). Please reach out the podman team, perhaps they will shed light on this issue.

Comment 16 Brendan Shephard 2023-11-09 03:17:45 UTC
Marking this as a duplicate again. While there may be a podman issue opened to address this in podman. TripleO has been updated to interact with these images in a way that won't hit this error any more. To avoid additional confusion, let's close this BZ as a duplicate and redirect any future conversation onto the original BZ.

*** This bug has been marked as a duplicate of bug 2240163 ***