[
https://issues.apache.org/jira/browse/CAMEL-26492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18137886#comment-18137886
]
Guillaume Nodet commented on CAMEL-26492:
-----------------------------------------
This issue is being investigated by a coding agent (on behalf of gnodet).
Gap confirmed: the check-container-versions.py script in
.github/actions/check-container-upgrade/ only checks whether newer image *tags*
are available, with no multi-architecture validation. It does not query the
Docker Registry v2 manifest list API to verify that a new tag includes
linux/s390x and linux/ppc64le manifests before proposing the upgrade. This
means PRs can be auto-generated for image versions that are only available for
amd64, breaking builds on alternative architectures.
Fix: add manifest list inspection to the registry API classes in
check-container-versions.py. Use the Docker Registry v2 API (GET
/v2/<repo>/manifests/<tag> with Accept:
application/vnd.docker.distribution.manifest.list.v2+json) to verify platform
availability for required architectures before recommending a version bump.
Single-PR scope.
_Note: This comment was generated by an AI coding agent and requires manual
verification._
> On PR upgrading image container, check image is available for all
> architectures used
> ------------------------------------------------------------------------------------
>
> Key: CAMEL-26492
> URL: https://issues.apache.org/jira/browse/CAMEL-26492
> Project: Camel
> Issue Type: Task
> Components: build system
> Affects Versions: 4.24.0
> Reporter: Aurélien Pupier
> Assignee: Guillaume Nodet
> Priority: Major
>
> currently, as soon as a amd6' architecture container image is available, a
> new PR is provided. We should check for the availability for s390x and
> ppc64le (when i tis used) either before creating the PR or as a PR check.
> it will avoid to break main branch for these architectures. And due to anoher
> bug to clean the Jenkins nodes cache as they download the amd64 version
> instead of just mentioning the version is not available. And when a version
> is available, even if the architecture is incorrect, it is still using the
> bad architecture one. see [CAMEL-26387]
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
