Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2227273

Summary: dasbus.error.DBusError: No such interface “org.freedesktop.DBus.Properties” on object at path /org/fedoraproject/Anaconda/Modules/Storage/Task/1
Product: Red Hat Enterprise Linux 9 Reporter: Jose Fernandez <jose>
Component: libblockdevAssignee: Vojtech Trefny <vtrefny>
Status: CLOSED MIGRATED QA Contact: Storage QE <storage-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.2CC: jkonecny, tbzatek, vtrefny
Target Milestone: rcKeywords: MigratedToJIRA
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:8fc192e43f940d234d74f7615d71ceefa950eca61df3d8c57c901670ac2b4d63;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-23 12:39:01 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: dbus.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 Jose Fernandez 2023-07-28 15:16:46 UTC
Description of problem:
I am installing RHEL 9.2 on a Dell T7920.

I did an UEFI boot from a USB with a RHEL 9.2 install iso. Anaconda fails inmediatelly upload loading the keabyboard map selection.

I have used the same USB to install RHEL 9.2 in my laptop.

I did try the  install using VNC with the same problem.

Version-Release number of selected component:
anaconda-34.25.2.10

The following was filed automatically by anaconda:
anaconda 34.25.2.10 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/lib/python3.9/site-packages/dasbus/client/handler.py", line 376, in _get_property_value
    variant = self._call_method(
  File "/usr/lib/python3.9/site-packages/dasbus/client/property.py", line 54, in __get__
    return self._getter()
  File "/usr/lib/python3.9/site-packages/dasbus/client/property.py", line 43, in get
    return self.__get__(None, None)
  File "/usr/lib/python3.9/site-packages/dasbus/client/proxy.py", line 164, in __getattr__
    return member.get()
  File "/usr/lib64/python3.9/site-packages/pyanaconda/modules/common/task/__init__.py", line 39, in sync_run_task
    while task_proxy.IsRunning:
  File "/usr/lib64/python3.9/site-packages/pyanaconda/ui/lib/storage.py", line 97, in reset_storage
    sync_run_task(task_proxy)
  File "/usr/lib64/python3.9/threading.py", line 917, 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: No such interface “org.freedesktop.DBus.Properties” on object at path /org/fedoraproject/Anaconda/Modules/Storage/Task/1

Additional info:
addons:         org_fedora_oscap, com_redhat_kdump
cmdline:        /usr/bin/python3  /sbin/anaconda
cmdline_file:   BOOT_IMAGE=/images/pxeboot/vmlinuz inst.stage2=hd:LABEL=RHEL-9-2-0-BaseOS-x86_64 quiet
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         5.14.0-284.11.1.el9_2.x86_64
product:        Red Hat Enterprise Linux 9
release:        Red Hat Enterprise Linux release 9.2 (Plow)
type:           anaconda
version:        9.2

Comment 1 Jose Fernandez 2023-07-28 15:16:50 UTC
Created attachment 1980468 [details]
File: anaconda-tb

Comment 2 Jose Fernandez 2023-07-28 15:16:51 UTC
Created attachment 1980469 [details]
File: anaconda.log

Comment 3 Jose Fernandez 2023-07-28 15:16:53 UTC
Created attachment 1980470 [details]
File: dbus.log

Comment 4 Jose Fernandez 2023-07-28 15:16:54 UTC
Created attachment 1980471 [details]
File: dnf.librepo.log

Comment 5 Jose Fernandez 2023-07-28 15:16:55 UTC
Created attachment 1980472 [details]
File: environ

Comment 6 Jose Fernandez 2023-07-28 15:16:56 UTC
Created attachment 1980473 [details]
File: lorax-packages.log

Comment 7 Jose Fernandez 2023-07-28 15:16:57 UTC
Created attachment 1980474 [details]
File: lsblk_output

Comment 8 Jose Fernandez 2023-07-28 15:16:58 UTC
Created attachment 1980475 [details]
File: lvm.log

Comment 9 Jose Fernandez 2023-07-28 15:16:59 UTC
Created attachment 1980476 [details]
File: nmcli_dev_list

Comment 10 Jose Fernandez 2023-07-28 15:17:00 UTC
Created attachment 1980477 [details]
File: os_info

Comment 11 Jose Fernandez 2023-07-28 15:17:02 UTC
Created attachment 1980478 [details]
File: program.log

Comment 12 Jose Fernandez 2023-07-28 15:17:03 UTC
Created attachment 1980479 [details]
File: storage.log

Comment 13 Jose Fernandez 2023-07-28 15:17:05 UTC
Created attachment 1980480 [details]
File: syslog

Comment 14 Jose Fernandez 2023-07-28 15:17:06 UTC
Created attachment 1980481 [details]
File: packaging.log

Comment 15 Jose Fernandez 2023-07-28 20:37:32 UTC

It seems to be a regression. I burned the RHEL 9.0 BaseOS iso image in the same USB, and I was able to install it without no issues.

Comment 16 Jiri Konecny 2023-08-10 12:01:25 UTC
Seems that there is a Segmentation fault from Blivet, our storage library.


```
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:Fatal Python error: Segmentation fault
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:Current thread 0x00007f273d2ca640 (most recent call first):
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:  File "/usr/lib/python3.9/site-packages/blivet/populator/helpers/disk.py", line 280 in _get_kwargs
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:  File "/usr/lib/python3.9/site-packages/blivet/populator/helpers/disk.py", line 73 in run
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:  File "/usr/lib/python3.9/site-packages/blivet/populator/populator.py", line 297 in handle_device
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:  File "/usr/lib/python3.9/site-packages/blivet/threads.py", line 53 in run_with_lock
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:  File "/usr/lib/python3.9/site-packages/blivet/populator/populator.py", line 490 in _populate
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:  File "/usr/lib/python3.9/site-packages/blivet/threads.py", line 53 in run_with_lock
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:  File "/usr/lib/python3.9/site-packages/blivet/populator/populator.py", line 446 in populate
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:  File "/usr/lib/python3.9/site-packages/blivet/threads.py", line 53 in run_with_lock
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:  File "/usr/lib/python3.9/site-packages/blivet/blivet.py", line 141 in reset
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:  File "/usr/lib/python3.9/site-packages/blivet/threads.py", line 53 in run_with_lock
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:  File "/usr/lib64/python3.9/site-packages/pyanaconda/modules/storage/devicetree/model.py", line 261 in reset
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:  File "/usr/lib/python3.9/site-packages/blivet/threads.py", line 53 in run_with_lock
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:  File "/usr/lib64/python3.9/site-packages/pyanaconda/modules/storage/reset.py", line 82 in _reset_storage
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:  File "/usr/lib64/python3.9/site-packages/pyanaconda/modules/storage/reset.py", line 63 in run
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:  File "/usr/lib64/python3.9/site-packages/pyanaconda/modules/common/task/task.py", line 109 in _task_run_callback
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:  File "/usr/lib64/python3.9/site-packages/pyanaconda/modules/common/task/task.py", line 96 in _thread_run_callback
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:  File "/usr/lib64/python3.9/threading.py", line 917 in run
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:  File "/usr/lib64/python3.9/site-packages/pyanaconda/threading.py", line 275 in run
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:  File "/usr/lib64/python3.9/threading.py", line 980 in _bootstrap_inner
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:  File "/usr/lib64/python3.9/threading.py", line 937 in _bootstrap
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:Thread 0x00007f274f789740 (most recent call first):
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:  File "/usr/lib/python3.9/site-packages/gi/overrides/GLib.py", line 497 in run
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:  File "/usr/lib64/python3.9/site-packages/pyanaconda/modules/common/base/base.py", line 92 in run
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:  File "/usr/lib64/python3.9/site-packages/pyanaconda/modules/storage/__main__.py", line 30 in <module>
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:  File "/usr/lib64/python3.9/runpy.py", line 87 in _run_code
15:01:41,765 WARNING org.fedoraproject.Anaconda.Modules.Storage:  File "/usr/lib64/python3.9/runpy.py", line 197 in _run_module_as_main
15:01:41,811 INFO systemd:Created slice Slice /system/systemd-coredump.
15:01:41,813 INFO systemd:Started Process Core Dump (PID 2749/UID 0).
15:01:41,860 INFO systemd-coredump:Resource limits disable core dumping for process 2521 (python3).
15:01:41,861 CRIT systemd-coredump:Process 2521 (python3) of user 0 dumped core.
15:01:41,865 INFO systemd:systemd-coredump: Deactivated successfully.
15:01:41,865 WARNING org.fedoraproject.Anaconda.Modules.Storage:/usr/libexec/anaconda/start-module: line 41:  2521 Segmentation fault      (core dumped) python3 -m $1
```

Switching the component. Vojto could you please take a look on this to find what is the source of this segfault?

Comment 17 Vojtech Trefny 2023-08-10 13:30:39 UTC
Moving this one more time to libblockdev, our low level storage library. The segfault happens when we try to gather information about the NVMe namespace nvme0n1 so it's either libblockdev or libnvme causing it. Unfortunately we don't have the full coredump in the journal so I can't see where it actually failed.

> It seems to be a regression. I burned the RHEL 9.0 BaseOS iso image in the same USB, and I was able to install it without no issues.

We added NVMe support in 9.2.

Comment 19 Tomáš Bžatek 2023-08-10 14:11:35 UTC
Would be handy to get a coredump to see where exactly the segfault happened.

For the start, could you please provide output of the following commands?
  nvme id-ctrl -H /dev/nvme0
  nvme id-ctrl -H /dev/nvme1
  nvme id-ns -H /dev/nvme0n1
  nvme id-ns -H /dev/nvme1n1
  nvme ns-descs /dev/nvme0n1
  nvme ns-descs /dev/nvme1n1
  nvme cmdset-ind-id-ns /dev/nvme0n1
  nvme cmdset-ind-id-ns /dev/nvme1n1

These are the calls we do from libblockdev and may give us a hint. Alternatively, try to boot up Fedora rawhide ISO (or any Fedora 39 nightly build), even a LiveCD might give us more info as the libblockdev code is mostly similar and the new udisks makes use of it (in Fedora 39).

Comment 20 RHEL Program Management 2023-09-23 12:36:14 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 21 RHEL Program Management 2023-09-23 12:39:01 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.