Skip to content

checkpatch: Update image digest#41360

Merged
aanm merged 1 commit intomainfrom
pr/HadrienPatte/checkpatch-digest
Aug 25, 2025
Merged

checkpatch: Update image digest#41360
aanm merged 1 commit intomainfrom
pr/HadrienPatte/checkpatch-digest

Conversation

@HadrienPatte
Copy link
Copy Markdown
Member

@HadrienPatte HadrienPatte commented Aug 24, 2025

More details in cilium/image-tools#385


The image-tools CI is supposed to only build an image if there isn't already a tag for the last commit that changed that image directory on quay.io.

There seems to have been an issue with this check in this job for the checkpatch image causing the job to fail to check for the existing tag, assume it didn't exist and proceed to rebuild it:

/usr/local/bin/crane
2025/08/23 18:59:33 HEAD request failed, falling back on GET: error getting credentials - err: exit status 1, out: ANY_REGISTRY_USERNAME is not set
Error: error getting credentials - err: exit status 1, out: ANY_REGISTRY_USERNAME is not set
error: crane returned 1
quay.io/cilium/cilium-checkpatch:1755701578-b97bd7a doesn't exist

With the 1755701578-b97bd7a tag rebuilt and repushed, quay.io must have garbage collected the previous image digest with the same tag, causing pulls of the previous digest for that tag to start failing (example):

docker: Error response from daemon: manifest for quay.io/cilium/cilium-checkpatch@sha256:edc094e3c306bbf9b9481f5a99aa6e8e00539cd1f4f7f7f4ffefeeabb0ff88b5 not found: manifest unknown: manifest unknown

@maintainer-s-little-helper maintainer-s-little-helper bot added the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Aug 24, 2025
@HadrienPatte HadrienPatte added the release-note/misc This PR makes changes that have no direct user impact. label Aug 24, 2025
@maintainer-s-little-helper maintainer-s-little-helper bot removed the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Aug 24, 2025
@HadrienPatte
Copy link
Copy Markdown
Member Author

/test

@HadrienPatte HadrienPatte marked this pull request as ready for review August 24, 2025 12:43
@HadrienPatte HadrienPatte requested a review from a team as a code owner August 24, 2025 12:43
@HadrienPatte HadrienPatte force-pushed the pr/HadrienPatte/checkpatch-digest branch from 3c030c3 to 3d9f352 Compare August 24, 2025 21:20
@aanm aanm enabled auto-merge August 25, 2025 07:59
@aanm
Copy link
Copy Markdown
Member

aanm commented Aug 25, 2025

/test

The `image-tools` CI is supposed to only build an image if there isn't
already a tag for the last commit that changed that image
directory on quay.io.

There seem to have been an issue with this check in [this job](https://github.com/cilium/image-tools/actions/runs/17178799757/job/48738420427) for the
`checkpatch` image causing the job to fail to check for the existing
tag, assume it didn't exist and proceed to rebuild it:

> /usr/local/bin/crane
> 2025/08/23 18:59:33 HEAD request failed, falling back on GET: error getting credentials - err: exit status 1, out: `ANY_REGISTRY_USERNAME is not set`
> Error: error getting credentials - err: exit status 1, out: `ANY_REGISTRY_USERNAME is not set`
> error: crane returned 1
> quay.io/cilium/cilium-checkpatch:1755701578-b97bd7a doesn't exist

With the `1755701578-b97bd7a` tag rebuilt and repushed, quay.io must have
garbage collected the previous image digest with the same tag, causing pulls of
the previous digest for that tag to start failing ([example](https://github.com/cilium/cilium/actions/runs/17182063773/job/48745850927?pr=41345#step:3:16)):

> docker: Error response from daemon: manifest for quay.io/cilium/cilium-checkpatch@sha256:edc094e3c306bbf9b9481f5a99aa6e8e00539cd1f4f7f7f4ffefeeabb0ff88b5 not found: manifest unknown: manifest unknown

Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
@HadrienPatte HadrienPatte force-pushed the pr/HadrienPatte/checkpatch-digest branch from 3d9f352 to 6640a0d Compare August 25, 2025 11:44
@HadrienPatte
Copy link
Copy Markdown
Member Author

/test

@HadrienPatte
Copy link
Copy Markdown
Member Author

Not sure why @cilium/loader was tagged as codeowner but no individual got assigned by the round-robin logic

@HadrienPatte HadrienPatte added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Aug 25, 2025
@aanm aanm added this pull request to the merge queue Aug 25, 2025
Merged via the queue into main with commit c232aaf Aug 25, 2025
436 of 445 checks passed
@aanm aanm deleted the pr/HadrienPatte/checkpatch-digest branch August 25, 2025 14:28
@julianwiedmann
Copy link
Copy Markdown
Member

@HadrienPatte 👋 given that #41290 is being backported to the various stable branches, do we need to backport this fix as well? I'm seeing the same error in a v1.16 PR.

(fyi @giorio94 )

@HadrienPatte
Copy link
Copy Markdown
Member Author

@julianwiedmann ah yes indeed, this PR will need to be backported to all branches where #41290 has been backported since the image sha in that PR no longer exists

@julianwiedmann julianwiedmann added needs-backport/1.16 needs-backport/1.17 This PR / issue needs backporting to the v1.17 branch needs-backport/1.18 This PR / issue needs backporting to the v1.18 branch labels Sep 2, 2025
@viktor-kurchenko viktor-kurchenko mentioned this pull request Sep 2, 2025
3 tasks
@viktor-kurchenko viktor-kurchenko mentioned this pull request Sep 2, 2025
18 tasks
@viktor-kurchenko viktor-kurchenko added backport-pending/1.18 The backport for Cilium 1.18.x for this PR is in progress. and removed needs-backport/1.18 This PR / issue needs backporting to the v1.18 branch labels Sep 2, 2025
@github-actions github-actions bot added backport-done/1.17 The backport for Cilium 1.17.x for this PR is done. backport-done/1.16 The backport for Cilium 1.16.x for this PR is done. backport-done/1.18 The backport for Cilium 1.18.x for this PR is done. and removed backport-pending/1.17 The backport for Cilium 1.17.x for this PR is in progress. backport-pending/1.16 backport-pending/1.18 The backport for Cilium 1.18.x for this PR is in progress. labels Sep 3, 2025
HadrienPatte added a commit that referenced this pull request Sep 16, 2025
This PR does the same thing as #41360. The initial issue has been
resolved with cilium/image-tools#386 but other
PRs (cilium/image-tools#387 and cilium/image-tools#383) have been merged before the fix PR, causing the issue to happen again.

Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
HadrienPatte added a commit that referenced this pull request Sep 16, 2025
This PR does the same thing as #41360. The initial issue has been
resolved with cilium/image-tools#386 but other
PRs (cilium/image-tools#387 and cilium/image-tools#383) have been merged before the fix PR, causing the issue to happen again.

Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
HadrienPatte added a commit that referenced this pull request Sep 16, 2025
This PR does the same thing as #41360. The initial issue has been
resolved with cilium/image-tools#386 but other
PRs (cilium/image-tools#387 and cilium/image-tools#383) have been merged before the fix PR, causing the issue to happen again.

Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
HadrienPatte added a commit that referenced this pull request Sep 16, 2025
This PR does the same thing as #41360. The initial issue has been
resolved with cilium/image-tools#386 but other
PRs (cilium/image-tools#387 and cilium/image-tools#383) have been merged before the fix PR, causing the issue to happen again.

Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
joestringer pushed a commit that referenced this pull request Sep 16, 2025
This PR does the same thing as #41360. The initial issue has been
resolved with cilium/image-tools#386 but other
PRs (cilium/image-tools#387 and cilium/image-tools#383) have been merged before the fix PR, causing the issue to happen again.

Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
pippolo84 pushed a commit that referenced this pull request Sep 22, 2025
[ upstream commit 3642fc4 ]

This PR does the same thing as #41360. The initial issue has been
resolved with cilium/image-tools#386 but other
PRs (cilium/image-tools#387 and cilium/image-tools#383) have been merged before the fix PR, causing the issue to happen again.

Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
Signed-off-by: Fabio Falzoi <fabio.falzoi@isovalent.com>
pippolo84 pushed a commit that referenced this pull request Sep 22, 2025
[ upstream commit 3642fc4 ]

This PR does the same thing as #41360. The initial issue has been
resolved with cilium/image-tools#386 but other
PRs (cilium/image-tools#387 and cilium/image-tools#383) have been merged before the fix PR, causing the issue to happen again.

Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
Signed-off-by: Fabio Falzoi <fabio.falzoi@isovalent.com>
pippolo84 pushed a commit that referenced this pull request Sep 22, 2025
[ upstream commit 3642fc4 ]

This PR does the same thing as #41360. The initial issue has been
resolved with cilium/image-tools#386 but other
PRs (cilium/image-tools#387 and cilium/image-tools#383) have been merged before the fix PR, causing the issue to happen again.

Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
Signed-off-by: Fabio Falzoi <fabio.falzoi@isovalent.com>
pippolo84 pushed a commit that referenced this pull request Sep 22, 2025
[ upstream commit 3642fc4 ]

This PR does the same thing as #41360. The initial issue has been
resolved with cilium/image-tools#386 but other
PRs (cilium/image-tools#387 and cilium/image-tools#383) have been merged before the fix PR, causing the issue to happen again.

Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
Signed-off-by: Fabio Falzoi <fabio.falzoi@isovalent.com>
pippolo84 pushed a commit that referenced this pull request Sep 22, 2025
[ upstream commit 3642fc4 ]

This PR does the same thing as #41360. The initial issue has been
resolved with cilium/image-tools#386 but other
PRs (cilium/image-tools#387 and cilium/image-tools#383) have been merged before the fix PR, causing the issue to happen again.

Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
Signed-off-by: Fabio Falzoi <fabio.falzoi@isovalent.com>
pippolo84 pushed a commit that referenced this pull request Sep 26, 2025
[ upstream commit 3642fc4 ]

This PR does the same thing as #41360. The initial issue has been
resolved with cilium/image-tools#386 but other
PRs (cilium/image-tools#387 and cilium/image-tools#383) have been merged before the fix PR, causing the issue to happen again.

Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
Signed-off-by: Fabio Falzoi <fabio.falzoi@isovalent.com>
pippolo84 pushed a commit that referenced this pull request Sep 26, 2025
[ upstream commit 3642fc4 ]

This PR does the same thing as #41360. The initial issue has been
resolved with cilium/image-tools#386 but other
PRs (cilium/image-tools#387 and cilium/image-tools#383) have been merged before the fix PR, causing the issue to happen again.

Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
Signed-off-by: Fabio Falzoi <fabio.falzoi@isovalent.com>
pippolo84 pushed a commit that referenced this pull request Sep 26, 2025
[ upstream commit 3642fc4 ]

This PR does the same thing as #41360. The initial issue has been
resolved with cilium/image-tools#386 but other
PRs (cilium/image-tools#387 and cilium/image-tools#383) have been merged before the fix PR, causing the issue to happen again.

Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
Signed-off-by: Fabio Falzoi <fabio.falzoi@isovalent.com>
github-merge-queue bot pushed a commit that referenced this pull request Sep 26, 2025
[ upstream commit 3642fc4 ]

This PR does the same thing as #41360. The initial issue has been
resolved with cilium/image-tools#386 but other
PRs (cilium/image-tools#387 and cilium/image-tools#383) have been merged before the fix PR, causing the issue to happen again.

Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
Signed-off-by: Fabio Falzoi <fabio.falzoi@isovalent.com>
github-merge-queue bot pushed a commit that referenced this pull request Sep 29, 2025
[ upstream commit 3642fc4 ]

This PR does the same thing as #41360. The initial issue has been
resolved with cilium/image-tools#386 but other
PRs (cilium/image-tools#387 and cilium/image-tools#383) have been merged before the fix PR, causing the issue to happen again.

Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
Signed-off-by: Fabio Falzoi <fabio.falzoi@isovalent.com>
pippolo84 pushed a commit that referenced this pull request Oct 6, 2025
[ upstream commit 3642fc4 ]

This PR does the same thing as #41360. The initial issue has been
resolved with cilium/image-tools#386 but other
PRs (cilium/image-tools#387 and cilium/image-tools#383) have been merged before the fix PR, causing the issue to happen again.

Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
Signed-off-by: Fabio Falzoi <fabio.falzoi@isovalent.com>
github-merge-queue bot pushed a commit that referenced this pull request Oct 6, 2025
[ upstream commit 3642fc4 ]

This PR does the same thing as #41360. The initial issue has been
resolved with cilium/image-tools#386 but other
PRs (cilium/image-tools#387 and cilium/image-tools#383) have been merged before the fix PR, causing the issue to happen again.

Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
Signed-off-by: Fabio Falzoi <fabio.falzoi@isovalent.com>
@cilium-release-bot cilium-release-bot bot moved this to Released in cilium v1.19.0 Feb 3, 2026
nddq pushed a commit to nddq/cilium that referenced this pull request Feb 17, 2026
[ upstream commit 3642fc4 ]

This PR does the same thing as cilium#41360. The initial issue has been
resolved with cilium/image-tools#386 but other
PRs (cilium/image-tools#387 and cilium/image-tools#383) have been merged before the fix PR, causing the issue to happen again.

Signed-off-by: Hadrien Patte <hadrien.patte@datadoghq.com>
Signed-off-by: Fabio Falzoi <fabio.falzoi@isovalent.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-done/1.16 The backport for Cilium 1.16.x for this PR is done. backport-done/1.17 The backport for Cilium 1.17.x for this PR is done. backport-done/1.18 The backport for Cilium 1.18.x for this PR is done. ready-to-merge This PR has passed all tests and received consensus from code owners to merge. release-note/misc This PR makes changes that have no direct user impact.

Projects

No open projects
Status: Released

Development

Successfully merging this pull request may close these issues.

5 participants