Bug 16387 - AB-INT: libgit2: attempting to fetch <commit>, which is in the commit graph file but not in the object database
Summary: AB-INT: libgit2: attempting to fetch <commit>, which is in the commit graph f...
Status: RESOLVED WORKSFORME
Alias: None
Product: AutoBuilder
Classification: Infrastructure
Component: autobuilder (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 6.1 M3
Assignee: Michael Halstead
QA Contact:
URL:
Whiteboard: AB-INT
Depends on:
Blocks:
 
Reported: 2026-08-06 08:54 UTC by Mathieu Dubois-Briand
Modified: 2026-08-13 14:55 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mathieu Dubois-Briand 2026-08-06 08:54:18 UTC
We are seeing this error, since libgit2 upgrade:

ERROR: libgit2-native-1.9.6-r0 do_fetch: Fetcher failure: Fetch command ['git', '-c', 'gc.autoDetach=false', '-c', 'core.pager=cat', '-c', 'safe.bareRepository=all', '-c', 'clone.defaultRemoteName=origin', 'fetch', '-f', '--update-head-ok', '--progress', 'mirror'] failed with exit code 128, output:
fatal: You are attempting to fetch 921e3a68e26ad23d9c5b389fdc61c9591bdc4cff, which is in the commit graph file but not in the object database.
This is probably due to repo corruption.
If you are attempting to repair this repo corruption by refetching the missing object, use 'git fetch --refetch' with the missing object.
ERROR: libgit2-native-1.9.6-r0 do_fetch: Bitbake Fetcher Error: FetchError('Unable to fetch URL from any source.', 'git://github.com/libgit2/libgit2.git;branch=maint/v1.9;protocol=https;tag=v1.9.6')

Is there really something wrong with this recipe or the remote? Or is it some infrastructure issue on our side?
Comment 1 Mathieu Dubois-Briand 2026-08-06 08:55:26 UTC
qemuarm64-musl-ptest alma10-vk-arm1 master completed at 2026-08-06 02:13:19+00:00
https://valkyrie.yocto.io/pub/non-release/20260806-8/testresults/qemuarm64-musl-ptest/
https://autobuilder.yoctoproject.org/valkyrie/#/builders/109/builds/897/steps/14/logs/stdio

qemuarm64-ltp alma10-vk-arm1 mathieu/master-next completed at 2026-08-05 13:42:43+00:00
https://autobuilder.yoctoproject.org/valkyrie/#/builders/98/builds/4156/steps/14/logs/stdio

qemuarm64-armhost alma10-vk-arm1 mathieu/master-next-tests&mathieu/master-next completed at 2026-08-05 19:21:11+00:00
https://autobuilder.yoctoproject.org/valkyrie/#/builders/8/builds/4349/steps/15/logs/stdio
Comment 2 Richard Purdie 2026-08-06 12:00:03 UTC
It is looking like the libgit2 sources mounted on this host are corrupted somehow over NFS.
Comment 3 Randy MacLeod 2026-08-06 14:46:31 UTC
Paused the alma10 worker in question.
Comment 4 Mathieu Dubois-Briand 2026-08-07 11:30:11 UTC
qemuarm64-armhost alma10-vk-arm1 master-next&master completed at 2026-08-06 10:37:59+00:00
https://autobuilder.yoctoproject.org/valkyrie/#/builders/8/builds/4353/steps/15/logs/stdio

qemuarm64-musl-ptest alma10-vk-arm1 mathieu/master-next completed at 2026-08-06 12:56:47+00:00
https://valkyrie.yocto.io/pub/non-release/20260806-79/testresults/qemuarm64-musl-ptest/
https://autobuilder.yoctoproject.org/valkyrie/#/builders/109/builds/901/steps/14/logs/stdio

Probably related: dbus-wait:do_unpack errors
qa-extras2 stream9-vk-1 master-next&master completed at 2026-08-06 17:03:55+00:00
https://autobuilder.yoctoproject.org/valkyrie/#/builders/26/builds/4287/steps/15/logs/stdio

genericarm64-alt debian12-vk-7 master-next&master completed at 2026-08-06 14:29:23+00:00
https://autobuilder.yoctoproject.org/valkyrie/#/builders/22/builds/4332/steps/14/logs/stdio

qemuarm64-armhost ubuntu2404-vk-arm2 master-next&master completed at 2026-08-06 18:47:09+00:00
https://autobuilder.yoctoproject.org/valkyrie/#/builders/8/builds/4356/steps/18/logs/stdio
Comment 5 Randy MacLeod 2026-08-13 14:55:43 UTC
Michael Halstead change the NFS mount options.
Let's see if that fixes this.