Description of problem: Error appeared during installation. It says "creating swap on /dev/sdb3" in the progress display. Version-Release number of selected component: anaconda-core-38.23.4-2.fc38.x86_64 The following was filed automatically by anaconda: anaconda 38.23.4 exception report Traceback (most recent call first): File "/usr/lib/python3.11/site-packages/dasbus/client/handler.py", line 509, in _handle_method_error raise exception from None File "/usr/lib/python3.11/site-packages/dasbus/client/handler.py", line 483, in _get_method_reply return self._handle_method_error(error) File "/usr/lib/python3.11/site-packages/dasbus/client/handler.py", line 450, in _call_method return self._get_method_reply( File "/usr/lib64/python3.11/site-packages/pyanaconda/modules/common/task/__init__.py", line 46, in sync_run_task task_proxy.Finish() File "/usr/lib64/python3.11/site-packages/pyanaconda/installation_tasks.py", line 280, in _run sync_run_task(self._task_proxy) File "/usr/lib64/python3.11/site-packages/pyanaconda/installation_tasks.py", line 75, in start self._run() File "/usr/lib64/python3.11/site-packages/pyanaconda/installation_tasks.py", line 188, in _run item.start() File "/usr/lib64/python3.11/site-packages/pyanaconda/installation_tasks.py", line 75, in start self._run() File "/usr/lib64/python3.11/site-packages/pyanaconda/installation_tasks.py", line 188, in _run item.start() File "/usr/lib64/python3.11/site-packages/pyanaconda/installation_tasks.py", line 75, in start self._run() File "/usr/lib64/python3.11/site-packages/pyanaconda/installation_tasks.py", line 188, in _run item.start() File "/usr/lib64/python3.11/site-packages/pyanaconda/installation_tasks.py", line 75, in start self._run() File "/usr/lib64/python3.11/site-packages/pyanaconda/installation.py", line 515, in _run_installation queue.start() File "/usr/lib64/python3.11/site-packages/pyanaconda/installation.py", line 80, in run self._run_installation( File "/usr/lib64/python3.11/site-packages/pyanaconda/modules/common/task/task.py", line 109, in _task_run_callback self._set_result(self.run()) File "/usr/lib64/python3.11/site-packages/pyanaconda/modules/common/task/task.py", line 96, in _thread_run_callback self._task_run_callback() File "/usr/lib64/python3.11/threading.py", line 975, in run self._target(*self._args, **self._kwargs) File "/usr/lib64/python3.11/site-packages/pyanaconda/threading.py", line 275, in run threading.Thread.run(self) File "/usr/lib64/python3.11/site-packages/pyanaconda/threading.py", line 166, in raise_if_error raise exc_info[1] File "/usr/lib64/python3.11/site-packages/pyanaconda/modules/common/task/task.py", line 175, in finish threadMgr.raise_if_error(self._thread_name) File "/usr/lib64/python3.11/site-packages/pyanaconda/ui/gui/spokes/installation_progress.py", line 75, in _on_installation_done self._task.finish() File "/usr/lib64/python3.11/site-packages/pyanaconda/core/signal.py", line 41, in emit func(obj, *args, **kargs) File "/usr/lib64/python3.11/site-packages/pyanaconda/modules/common/task/runnable.py", line 115, in _task_stopped_callback self._stopped_signal.emit() File "/usr/lib64/python3.11/site-packages/pyanaconda/core/async_utils.py", line 68, in _idle_method func(*args, **kwargs) pyanaconda.modules.common.errors.general.AnacondaError: Process reported exit code 1: ERROR: cannot access '/tmp/btrfs-tmp.26065cq1end9/@var': No such file or directory Additional info: comment: Error appeared during installation. It says "creating swap on /dev/sdb3" in the progress display. cmdline: /usr/bin/python3 /sbin/anaconda --liveinst --graphical executable: /sbin/anaconda hashmarkername: anaconda product: Fedora package: anaconda-core-38.23.4-2.fc38.x86_64 reason: pyanaconda.modules.common.errors.general.AnacondaError: Process reported exit code 1: ERROR: cannot access '/tmp/btrfs-tmp.26065cq1end9/@var': No such file or directory kernel: 6.2.9-300.fc38.x86_64 type: anaconda release: Fedora release 38 (Thirty Eight) cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-KDE-Live-38-1-6 rd.live.image rd.live.check quiet addons: com_redhat_kdump version: 38 other involved packages: python3-libs-3.11.2-1.fc38.x86_64, python3-dasbus-1.7-2.fc38.noarch, anaconda-gui-38.23.4-2.fc38.x86_64
Created attachment 1971250 [details] File: backtrace
Created attachment 1971251 [details] File: os_info
Created attachment 1971252 [details] File: environ
Created attachment 1971253 [details] File: journalctl
Created attachment 1971254 [details] File: description
Created attachment 1971255 [details] File: storage.log
Created attachment 1971256 [details] File: program.log
Created attachment 1971257 [details] File: nmcli_dev_list
Created attachment 1971258 [details] File: anaconda.log
Created attachment 1971259 [details] File: lsblk_output
Created attachment 1971260 [details] File: dbus.log
Error appeared during installation. It says "creating swap on /dev/sdb3" in the progress display. comment: Error appeared during installation. It says "creating swap on /dev/sdb3" in the progress display. cmdline: /usr/bin/python3 /sbin/anaconda --liveinst --graphical hashmarkername: anaconda product: Fedora package: anaconda-core-38.23.4-2.fc38.x86_64 reason: pyanaconda.modules.common.errors.general.AnacondaError: Process reported exit code 1: ERROR: cannot access '/tmp/btrfs-tmp.26065cq1end9/@var': No such file or directory kernel: 6.2.9-300.fc38.x86_64 release: Fedora release 38 (Thirty Eight) cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-KDE-Live-38-1-6 rd.live.image rd.live.check quiet addons: com_redhat_kdump version: 38 other involved packages: python3-libs-3.11.2-1.fc38.x86_64, python3-dasbus-1.7-2.fc38.noarch, anaconda-gui-38.23.4-2.fc38.x86_64
> ERROR: cannot access '/tmp/btrfs-tmp.26065cq1end9/@var' Vojto, is this based on the made up syntax for subvolumes we use somewhere? I think this bug is just that we use it somewhere that a path should be used, right?
Moving this issue to blivet. The problem seems to be the creation of `@var/log` subvolume without creating `@var` subvolume first. I am not sure whether this is something supported by btrfs or not. But either way, this needs to be fixed in blivet. Either by fixing how we create the subvolume (if it's supported) or by returning an error earlier.