Bug 1963778
| Summary: | dasbus.error.DBusError: [Errno 2] No such file or directory: 'systemd-machine-id-setup' | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John Schmitt <marmalodak> | ||||||||||||||||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||||||||||||
| Status: | NEW --- | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||
| Version: | 39 | CC: | anaconda-maint-list, bugs.michael, fedorarpmcreator, georkei10, jkonecny, jonathan, kellin, lnie, lukaskandler, vanmeeuwen+fedora, vponcova, vslavik, w | ||||||||||||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||
| Whiteboard: | abrt_hash:6011da28014ba6581fae2d62a6fb5f4612bb078c3db9ef2bea7709d993f8126e;VARIANT_ID=workstation; | ||||||||||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||
| Last Closed: | 2022-06-07 20:05:15 UTC | Type: | --- | ||||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||
| Embargoed: | |||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||
Created attachment 1786222 [details]
File: anaconda-tb
Created attachment 1786223 [details]
File: anaconda.log
Created attachment 1786224 [details]
File: dbus.log
Created attachment 1786225 [details]
File: environ
Created attachment 1786226 [details]
File: journalctl
Created attachment 1786227 [details]
File: lsblk_output
Created attachment 1786228 [details]
File: lvm.log
Created attachment 1786229 [details]
File: nmcli_dev_list
Similar problem has been detected: This installation is from a live installation on a USB drive to another USB drive. On this machine, the internally install disk is /dev/sda. The live image is on /dev/sdb. The destination disk is /dev/sdc. addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda --liveinst --graphical cmdline_file: BOOT_IMAGE=/syslinux/vmlinuz root=live:UUID=D32A-D3F1 rd.live.image rw quiet dnf.librepo.log: hashmarkername: anaconda kernel: 5.11.12-300.fc34.x86_64 other involved packages: python3-dasbus-1.4-3.fc34.noarch, python3-libs-3.9.2-1.fc34.x86_64 package: anaconda-core-34.24.9-1.fc34.x86_64 packaging.log: 18:34:14,149 INF packaging: rsync exited with code 0 product: Fedora reason: dasbus.error.DBusError: [Errno 2] No such file or directory: 'systemd-machine-id-setup' release: Fedora release 34 (Thirty Four) version: 34 Hello, I don't see any issues in the installation logs. Could you please try to download the ISO again and verify its checksum? It might be corrupted. That sounds so unlikely since the image mounted and ran cleanly. If the image was corrupt I would have seen many other symptoms. I was able to work around this problem by running systemd-machine-id-setup --commit *** Bug 1978583 has been marked as a duplicate of this bug. *** *** Bug 2006942 has been marked as a duplicate of this bug. *** *** Bug 1904149 has been marked as a duplicate of this bug. *** The bugs linked above as duplicates all appear to be the same problem. It seems (not 100%) that systemd-machine-id-setup is the first thing we try running from a chroot to the installed system (it's a prerequisite for bootloader setup). So it could be that for some reason the resulting system is corrupted, and this is finding out the hard way. One common theme is that we have all 3 independent reports from Live (one KDE). The code moved a bit around over the versions but it is still the same, so Fedora 33 or 35 does not really matter here. This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed. Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed. Still happens on Fedora 38. Closing new bug as duplicate of this one too keep track of it. *** Bug 2192134 has been marked as a duplicate of this bug. *** > So it could be that for some reason the resulting system is corrupted, In case of bug 2192134, no corruption or anything. Just going back within the installer at least once, like leaving the custom partitioning screen and returning to the main screen. Subsequently entering the partitioning screen again ended up with a broken installer. And yes, I've used exactly the same USB Live stick (GNOME Workstation) to install F38 successfully afterwards. *** Bug 2212602 has been marked as a duplicate of this bug. *** Bumping seen-in-version to rawhide according to last reports. This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle. Changing version to 39. |
Description of problem: This installation is from a live installation on a USB drive to another USB drive. On this machine, the internally install disk is /dev/sda. The live image is on /dev/sdb. The destination disk is /dev/sdc. Version-Release number of selected component: anaconda-core-34.24.9-1.fc34.x86_64 The following was filed automatically by anaconda: anaconda 34.24.9 exception report Traceback (most recent call first): File "/usr/lib/python3.9/site-packages/dasbus/client/handler.py", line 497, in _handle_method_error raise exception from None File "/usr/lib/python3.9/site-packages/dasbus/client/handler.py", line 477, in _get_method_reply return self._handle_method_error(error) File "/usr/lib/python3.9/site-packages/dasbus/client/handler.py", line 444, in _call_method return self._get_method_reply( File "/usr/lib64/python3.9/site-packages/pyanaconda/modules/common/task/__init__.py", line 46, in sync_run_task task_proxy.Finish() File "/usr/lib64/python3.9/site-packages/pyanaconda/installation.py", line 322, in run_install_bootloader sync_run_task(STORAGE.get_proxy(task)) File "/usr/lib64/python3.9/site-packages/pyanaconda/installation_tasks.py", line 458, in run_task self._task(*self._task_args, **self._task_kwargs) File "/usr/lib64/python3.9/site-packages/pyanaconda/installation_tasks.py", line 496, in start self.run_task() File "/usr/lib64/python3.9/site-packages/pyanaconda/installation_tasks.py", line 311, in start item.start() File "/usr/lib64/python3.9/site-packages/pyanaconda/installation_tasks.py", line 311, in start item.start() File "/usr/lib64/python3.9/site-packages/pyanaconda/installation_tasks.py", line 311, in start item.start() File "/usr/lib64/python3.9/site-packages/pyanaconda/installation.py", line 372, in run_installation queue.start() File "/usr/lib64/python3.9/threading.py", line 892, in run self._target(*self._args, **self._kwargs) File "/usr/lib64/python3.9/site-packages/pyanaconda/threading.py", line 275, in run threading.Thread.run(self) dasbus.error.DBusError: [Errno 2] No such file or directory: 'systemd-machine-id-setup' Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda --liveinst --graphical cmdline_file: BOOT_IMAGE=/syslinux/vmlinuz root=live:UUID=D32A-D3F1 rd.live.image rw quiet dnf.librepo.log: executable: /sbin/anaconda hashmarkername: anaconda kernel: 5.11.12-300.fc34.x86_64 other involved packages: python3-dasbus-1.4-3.fc34.noarch, python3-libs-3.9.2-1.fc34.x86_64 product: Fedora release: Fedora release 34 (Thirty Four) type: anaconda version: 34