-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
rhel-9.6
-
No
-
Low
-
1
-
image-builder-1
-
1
-
False
-
False
-
-
None
-
Image Builder 11
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
-
x86_64
-
None
What were you trying to do that didn't work?
The osbuild-composer service fails to start. Seeing below messages in the logs
osbuild-composer[8251]: cannot read state: error reading db file state: JSON unmarshal: minsize must be float64 number or string, got <nil> of type <nil>
strace shows this:
5551 15:11:37.543770 close(5</var/lib/osbuild-composer/state.json>) = 0 <0.000036>
5551 15:11:37.543893 write(1<socket:[68865]>, "cannot read state: error reading db file state: JSON unmarshal: minsize must be float64 number or string, got <nil> of type <nil>\n", 130) = 130 <0.000036>
As a procedural workaround, moved /var/lib/osbuild-composer/ to a backup location and now this is working.
Not an exact match, but looks rather similar to https://github.com/osbuild/osbuild-composer/issues/3779
What is the impact of this issue to you?
Have to reload blueprints and configurations with the workaround.
Please provide the package NVR for which the bug is seen:
osbuild package versions for this case:
osbuild-141.2-1.el9_6.noarch Sun Jul 20 15:54:14 2025 osbuild-composer-132.2-2.el9_6.x86_64 Sun Jul 20 15:54:16 2025 osbuild-composer-core-132.2-2.el9_6.x86_64 Sun Jul 20 15:54:15 2025 osbuild-composer-worker-132.2-2.el9_6.x86_64 Sun Jul 20 15:54:16 2025 osbuild-depsolve-dnf-141.2-1.el9_6.noarch Sun Jul 20 15:54:14 2025 osbuild-luks2-141.2-1.el9_6.noarch Sun Jul 20 15:54:15 2025 osbuild-lvm2-141.2-1.el9_6.noarch Sun Jul 20 15:54:15 2025 osbuild-ostree-141.2-1.el9_6.noarch Sun Jul 20 15:54:15 2025 osbuild-selinux-141.2-1.el9_6.noarch Sun Jul 20 15:54:05 2025 python3-osbuild-141.2-1.el9_6.noarch Sun Jul 20 15:52:03 2025
How reproducible is this bug?
Not able to reproduce yet. If we get a copy of /var/lib/osbuild-composer/ it may be possible (a copy of this is pending)
Tar file with /var/lib/osbuild-composer/
