flatpak runtime build fails with 'error: No such file or directory: var' #9538

New issue

Closed

opened 2020-12-17 10:43:11 +00:00 by kalev · 5 comments

kalev commented

2020-12-17 10:43:11 +00:00

We haven't built any flatpak runtime updates in a while as the container build system was down due to the aarch64 addition. Trying to get an update out now, the build is now failing (on x86_64) with:

error: No such file or directory: var
2020-12-17 08:41:01,246 - atomic_reactor.plugin - DEBUG - Traceback (most recent call last):
  File "/usr/lib/python3.9/site-packages/atomic_reactor/plugin.py", line 268, in run
    plugin_response = plugin_instance.run()
  File "/usr/lib/python3.9/site-packages/atomic_reactor/plugins/prepub_flatpak_create_oci.py", line 116, in run
    ref_name, outfile, tarred_outfile = self.builder.build_container(tarred_filesystem)
  File "/usr/lib/python3.9/site-packages/flatpak_module_tools/flatpak_builder.py", line 880, in build_container
    ref_name = self._create_runtime_oci(tarred_filesystem, outfile)
  File "/usr/lib/python3.9/site-packages/flatpak_module_tools/flatpak_builder.py", line 699, in _create_runtime_oci
    subprocess.check_call(['ostree', 'commit'] + commit_args)
  File "/usr/lib64/python3.9/subprocess.py", line 373, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['ostree', 'commit', '--repo', '/tmp/tmp0bq0h226/repo', '--owner-uid=0', '--owner-gid=0', '--no-xattrs', '--canonical-permissions', '--branch', 'runtime/org.fedoraproject.Platform/x86_64/f33', '-s', 'build of runtime/org.fedoraproject.Platform/x86_64/f33', '--tree=tar=/tmp/tmp0bq0h226/filesystem.tar.gz', '--tree=dir=/tmp/tmp0bq0h226/build', '--add-metadata-string', 'xa.metadata=[Runtime]\nname=org.fedoraproject.Platform\nruntime=org.fedoraproject.Platform/x86_64/f33\nsdk=org.fedoraproject.Sdk/x86_64/f33\n\n[Environment]\nGI_TYPELIB_PATH=/app/lib64/girepository-1.0\nGST_PLUGIN_SYSTEM_PATH=/app/lib64/gstreamer-1.0:/usr/lib64/gstreamer-1.0\nLD_LIBRARY_PATH=/app/lib64\nXDG_DATA_DIRS=/app/share:/usr/share:/usr/share/runtime/share:/run/host/share\n']' returned non-zero exit status 1.

Full log is available at https://koji.fedoraproject.org/koji/taskinfo?taskID=57630766 (x86_64.log)

This looks to be ostree commit erroring out with error: No such file or directory: var.
I am not sure what's going on here. I believe @cverna updated the flatpak base container as part of the aarch64 work so I assume ostree got updated. Maybe it's a fallout from the ostree update somehow? @otaylor @walters any ideas? :)

We haven't built any flatpak runtime updates in a while as the container build system was down due to the aarch64 addition. Trying to get an update out now, the build is now failing (on x86_64) with: ``` error: No such file or directory: var 2020-12-17 08:41:01,246 - atomic_reactor.plugin - DEBUG - Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/atomic_reactor/plugin.py", line 268, in run plugin_response = plugin_instance.run() File "/usr/lib/python3.9/site-packages/atomic_reactor/plugins/prepub_flatpak_create_oci.py", line 116, in run ref_name, outfile, tarred_outfile = self.builder.build_container(tarred_filesystem) File "/usr/lib/python3.9/site-packages/flatpak_module_tools/flatpak_builder.py", line 880, in build_container ref_name = self._create_runtime_oci(tarred_filesystem, outfile) File "/usr/lib/python3.9/site-packages/flatpak_module_tools/flatpak_builder.py", line 699, in _create_runtime_oci subprocess.check_call(['ostree', 'commit'] + commit_args) File "/usr/lib64/python3.9/subprocess.py", line 373, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '['ostree', 'commit', '--repo', '/tmp/tmp0bq0h226/repo', '--owner-uid=0', '--owner-gid=0', '--no-xattrs', '--canonical-permissions', '--branch', 'runtime/org.fedoraproject.Platform/x86_64/f33', '-s', 'build of runtime/org.fedoraproject.Platform/x86_64/f33', '--tree=tar=/tmp/tmp0bq0h226/filesystem.tar.gz', '--tree=dir=/tmp/tmp0bq0h226/build', '--add-metadata-string', 'xa.metadata=[Runtime]\nname=org.fedoraproject.Platform\nruntime=org.fedoraproject.Platform/x86_64/f33\nsdk=org.fedoraproject.Sdk/x86_64/f33\n\n[Environment]\nGI_TYPELIB_PATH=/app/lib64/girepository-1.0\nGST_PLUGIN_SYSTEM_PATH=/app/lib64/gstreamer-1.0:/usr/lib64/gstreamer-1.0\nLD_LIBRARY_PATH=/app/lib64\nXDG_DATA_DIRS=/app/share:/usr/share:/usr/share/runtime/share:/run/host/share\n']' returned non-zero exit status 1. ``` Full log is available at https://koji.fedoraproject.org/koji/taskinfo?taskID=57630766 (x86_64.log) This looks to be `ostree commit` erroring out with `error: No such file or directory: var`. I am not sure what's going on here. I believe @cverna updated the flatpak base container as part of the aarch64 work so I assume ostree got updated. Maybe it's a fallout from the ostree update somehow? @otaylor @walters any ideas? :)

otaylor commented

2020-12-17 12:39:48 +00:00

Adding @alexl here has someone else who might have ideas.

Certainly an odd error - not sure why ostree is trying to read from var. I tried a local build with Fedora 33, and the container built successfully - while a local build isn't 100% identical to a build in OSBS, I'd expect the call to 'ostree commit' to be nearly the same.

Could we get a package listing from the buildroot container? (Not the flatpak-build-base container, but the container that contains atomic-reactor)

Adding @alexl here has someone else who might have ideas. Certainly an odd error - not sure why ostree is trying to read from var. I tried a local build with Fedora 33, and the container built successfully - while a local build isn't 100% identical to a build in OSBS, I'd expect the call to 'ostree commit' to be nearly the same. Could we get a package listing from the buildroot container? (Not the flatpak-build-base container, but the container that contains atomic-reactor)

mobrien commented

2020-12-17 15:54:10 +00:00

Below is the result of rpm -qa on the buildroot image

Below is the result of rpm -qa on the buildroot image [![buildroot_package_list.txt](/fedora-infrastructure/issue/raw/files/ccdb52f6dda52372a54aa79cd86c69f432b20ccea2c33696fcc488b3980fdc53-buildroot_package_list.txt)](/fedora-infrastructure/issue/raw/files/ccdb52f6dda52372a54aa79cd86c69f432b20ccea2c33696fcc488b3980fdc53-buildroot_package_list.txt)

otaylor commented

2020-12-18 20:58:27 +00:00

I think is the same as issue 9532 - just a more obscure failure, because ostree produces a worse error message for a hardlink to a missing file than tar. Let's retest once we have the buildroot updated with the fix for issue 9532.