Since after the 42.20250604.0 build, Fedora Atomic Desktops 42 testing builds have all been failing, for all variants. Sometimes, we get the following error:
42.20250604.0
Traceback (most recent call last): File "/usr/bin/pungi-make-ostree", line 33, in <module> sys.exit(load_entry_point('pungi==4.9.2', 'console_scripts', 'pungi-make-ostree')()) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^ File "/usr/lib/python3.13/site-packages/pungi/ostree/__init__.py", line 202, in main func() ~~~~^^ File "/usr/lib/python3.13/site-packages/pungi/ostree/tree.py", line 157, in run self._make_tree() ~~~~~~~~~~~~~~~^^ File "/usr/lib/python3.13/site-packages/pungi/ostree/tree.py", line 62, in _make_tree shortcuts.run( ~~~~~~~~~~~~~^ cmd, ^^^^ ...<4 lines>... errors="replace", ^^^^^^^^^^^^^^^^^ ) ^ File "/usr/lib/python3.13/site-packages/kobo/shortcuts.py", line 408, in run raise exc RuntimeError: ERROR running command: rpm-ostree compose tree --repo=/mnt/koji/compose/ostree/repo --write-commitid-to=/mnt/koji/compose/updates/Fedora-42-updates-testing-20250617.0/logs/x86_64/Kinoite/ostree-3/commitid.log --touch-if-changed=/mnt/koji/compose/updates/Fedora-42-updates-testing-20250617.0/logs/x86_64/Kinoite/ostree-3/commitid.log.stamp --unified-core --add-metadata-string=version=42.20250617.0 /mnt/koji/compose/updates/Fedora-42-updates-testing-20250617.0/work/ostree-3/config_repo/kinoite-ostree.json For more details see /mnt/koji/compose/updates/Fedora-42-updates-testing-20250617.0/logs/x86_64/Kinoite/ostree-3/create-ostree-repo.log
See: https://kojipkgs.fedoraproject.org//work/tasks/1100/134061100/runroot.log
When possible. It makes it harder for users to test upcoming package updates for Atomic Desktops but it does not block stable builds so it's not "drop everything" critical.
N/A
No updates-testing builds for Atomic Desktops. Stable builds are not impacted (which is weird).
Is this a pungi bug perhaps? @lsedlar ?
Metadata Update from @james: - Issue tagged with: medium-gain, medium-trouble
We have new builds now, so closing for now. Thanks
Metadata Update from @siosm: - Issue close_status updated to: It's all good - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.