Bug 2077582

Summary: dasbus.error.DBusError: [Errno 2] No such file or directory: '/mnt/sysroot/etc/resolv.conf'
Product: [Fedora] Fedora Reporter: kubakazika5
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 35CC: anaconda-maint-list, jonathan, kellin, vanmeeuwen+fedora, vponcova, w
Target Milestone: ---   
Target Release: ---   
Hardware: aarch64   
OS: Unspecified   
Whiteboard: abrt_hash:5906a38ccc22ed4baed60983e5212d646e5a91c70da6045b97f09f72ad15125e;VARIANT_ID=server;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-21 17:23:54 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:
Description Flags
File: anaconda-tb
none
File: anaconda.log
none
File: dnf.librepo.log
none
File: environ
none
File: lorax-packages.log
none
File: lsblk_output
none
File: lvm.log
none
File: nmcli_dev_list
none
File: os_info
none
File: program.log
none
File: storage.log
none
File: syslog
none
File: packaging.log none

Description kubakazika5 2022-04-21 16:05:02 UTC 
Description of problem:
1. Insert installation media (tried both on Server and Everything editions).
2. Configure the installation.
3. Select Minimal installation.
4. Error happens during installation process.

Despite the error the system seems to be installed, but signing-in is impossible. I tried signing-in to the root and user account. Tried reinstalling the system without setting the user's password (set to blank) and still couldn't sign-in.
To investigate a bit further I mounted the root partition to see if the user's are present in /etc/shadow and user login that was set in the installer wasn't present. I guess that's the error that prevents creating them.

Version-Release number of selected component:
anaconda-35.22.2

The following was filed automatically by anaconda:
anaconda 35.22.2 exception report
Traceback (most recent call first):
  File "/usr/lib/python3.10/site-packages/dasbus/client/handler.py", line 497, in _handle_method_error
    raise exception from None
  File "/usr/lib/python3.10/site-packages/dasbus/client/handler.py", line 477, in _get_method_reply
    return self._handle_method_error(error)
  File "/usr/lib/python3.10/site-packages/dasbus/client/handler.py", line 444, in _call_method
    return self._get_method_reply(
  File "/usr/lib64/python3.10/site-packages/pyanaconda/modules/common/task/__init__.py", line 46, in sync_run_task
    task_proxy.Finish()
  File "/usr/lib64/python3.10/site-packages/pyanaconda/network.py", line 293, in write_configuration
    sync_run_task(task_proxy)
  File "/usr/lib64/python3.10/site-packages/pyanaconda/installation_tasks.py", line 458, in run_task
    self._task(*self._task_args, **self._task_kwargs)
  File "/usr/lib64/python3.10/site-packages/pyanaconda/installation_tasks.py", line 496, in start
    self.run_task()
  File "/usr/lib64/python3.10/site-packages/pyanaconda/installation_tasks.py", line 311, in start
    item.start()
  File "/usr/lib64/python3.10/site-packages/pyanaconda/installation_tasks.py", line 311, in start
    item.start()
  File "/usr/lib64/python3.10/site-packages/pyanaconda/installation_tasks.py", line 311, in start
    item.start()
  File "/usr/lib64/python3.10/site-packages/pyanaconda/installation.py", line 415, in run_installation
    queue.start()
  File "/usr/lib64/python3.10/threading.py", line 946, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib64/python3.10/site-packages/pyanaconda/threading.py", line 275, in run
    threading.Thread.run(self)
dasbus.error.DBusError: [Errno 2] Nie ma takiego pliku ani katalogu: '/mnt/sysroot/etc/resolv.conf'

Additional info:
addons:         com_redhat_kdump
cmdline:        /usr/bin/python3  /sbin/anaconda
cmdline_file:   BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=FEDORA-S-DV rd.live.check
executable:     /sbin/anaconda
hashmarkername: anaconda
hawkey.log:     2022-04-21T11:44:11-0400 INFO === Started libdnf-0.64.0 ===
kernel:         5.14.10-300.fc35.aarch64
product:        Fedora
release:        Fedora release 35 (Thirty Five)
type:           anaconda
version:        35
Comment 1 kubakazika5 2022-04-21 16:05:09 UTC 
Created attachment 1874162 [details]
File: anaconda-tb
Comment 2 kubakazika5 2022-04-21 16:05:11 UTC 
Created attachment 1874163 [details]
File: anaconda.log
Comment 3 kubakazika5 2022-04-21 16:05:13 UTC 
Created attachment 1874164 [details]
File: dnf.librepo.log
Comment 4 kubakazika5 2022-04-21 16:05:14 UTC 
Created attachment 1874165 [details]
File: environ
Comment 5 kubakazika5 2022-04-21 16:05:15 UTC 
Created attachment 1874166 [details]
File: lorax-packages.log
Comment 6 kubakazika5 2022-04-21 16:05:16 UTC 
Created attachment 1874167 [details]
File: lsblk_output
Comment 7 kubakazika5 2022-04-21 16:05:18 UTC 
Created attachment 1874168 [details]
File: lvm.log
Comment 8 kubakazika5 2022-04-21 16:05:19 UTC 
Created attachment 1874169 [details]
File: nmcli_dev_list
Comment 9 kubakazika5 2022-04-21 16:05:21 UTC 
Created attachment 1874170 [details]
File: os_info
Comment 10 kubakazika5 2022-04-21 16:05:22 UTC 
Created attachment 1874171 [details]
File: program.log
Comment 11 kubakazika5 2022-04-21 16:05:24 UTC 
Created attachment 1874172 [details]
File: storage.log
Comment 12 kubakazika5 2022-04-21 16:05:27 UTC 
Created attachment 1874173 [details]
File: syslog
Comment 13 kubakazika5 2022-04-21 16:05:28 UTC 
Created attachment 1874174 [details]
File: packaging.log
Comment 14 kubakazika5 2022-04-21 16:10:18 UTC 
Tried also performing the Minimal install in the VirtualBox on x86_64 PC and got the same error.
Comment 15 Brian Lane 2022-04-21 17:23:54 UTC 
It's a systemd bug #2074083

You can work around it if you install without including the update repos. Then update the system after first boot.

*** This bug has been marked as a duplicate of bug 2074083 ***
Comment 16 kubakazika5 2022-04-21 17:30:28 UTC 
I managed to successfully complete installation by adding a boot flag as stated in this comment: https://bugzilla.redhat.com/show_bug.cgi?id=2019579#c24

> It can be applied either by installer boot option:
>
> inst.updates=https://rvykydal.fedorapeople.org/update-images/updates.f35-2019579-resolvconf.img