After updating the osbuild/images to a version with V2 depsolver API used by default and the latest osbuild version, the image-builder manifest job test case started to fail.
The bottom line is that is unexpected due to:
osbuild-depsolve-dnf still provides the V1 depsolver API that is unchanged. Thus image-builder would end up using the V1 API and depsolving should keep working. So the new version of osbuild should not have any effect on the test case.image-builder is built against its own version of osbuild/images library, so updating it in the osbuild-composer should not affect the job in ideal case.
Potential issues:
osbuild-composer and image-builder may still expect different versions of data structures, such as RepoConfig or the Blueprint (due to being built with different version of osbuild/blueprint).- Changes in
image-builder CLI arguments and how the job calls the tool.
The latest failure is: https://gitlab.com/redhat/services/products/image-builder/ci/osbuild-composer/-/jobs/13017392997
...
[2026-02-06T12:51:44+00:00] Sending compose: Fail test
127.0.0.1 - - [06/Feb/2026 12:52:02] "GET /repodata/repomd.xml HTTP/1.1" 200 -
127.0.0.1 - - [06/Feb/2026 12:52:02] "GET /repodata/f5fd11b0770a53104d897016fb772de497c0798e0995a52fb51fc16ee0db14b1-primary.xml.zst HTTP/1.1" 200 -
[2026-02-06T12:52:14+00:00] Sending compose: Retry test
127.0.0.1 - - [06/Feb/2026 12:52:19] "GET /repodata/repomd.xml HTTP/1.1" 200 -
127.0.0.1 - - [06/Feb/2026 12:54:47] "GET /repodata/repomd.xml HTTP/1.1" 200 -
127.0.0.1 - - [06/Feb/2026 12:57:18] "GET /repodata/repomd.xml HTTP/1.1" 200 -
Image compose failed
API output: {"href":"/api/image-builder-composer/v2/composes/5103851e-e82a-445d-a3d0-0405cf80fad8","id":"5103851e-e82a-445d-a3d0-0405cf80fad8","image_status":{"error":{"details":[{"id":27,"reason":"Workers running this job stopped responding more than 2 times."}],"id":9,"reason":"Manifest dependency failed"},"status":"failure"},"kind":"ComposeStatus","status":"failure"}
[2026-02-06T12:59:44+00:00] Cleaning up
...
After talking to @achilleas-k , we agreed to temporarily disable the test in CI, since it is not yet used anywhere in practice.
The goal of this issue is to find the root cause of the problem and re-enable the test case.
After updating the
osbuild/imagesto a version with V2 depsolver API used by default and the latestosbuildversion, the image-builder manifest job test case started to fail.The bottom line is that is unexpected due to:
osbuild-depsolve-dnfstill provides the V1 depsolver API that is unchanged. Thusimage-builderwould end up using the V1 API and depsolving should keep working. So the new version of osbuild should not have any effect on the test case.image-builderis built against its own version ofosbuild/imageslibrary, so updating it in the osbuild-composer should not affect the job in ideal case.Potential issues:
osbuild-composerandimage-buildermay still expect different versions of data structures, such asRepoConfigor the Blueprint (due to being built with different version ofosbuild/blueprint).image-builderCLI arguments and how the job calls the tool.The latest failure is: https://gitlab.com/redhat/services/products/image-builder/ci/osbuild-composer/-/jobs/13017392997
After talking to @achilleas-k , we agreed to temporarily disable the test in CI, since it is not yet used anywhere in practice.
The goal of this issue is to find the root cause of the problem and re-enable the test case.