Description of problem: It crashed during 'Creating lvmpv on /dev/md/Volume0_0p3' step. There is FW RAID (mirror) which was empty and I tried to do the default installation. Version-Release number of selected component: anaconda-26.21.3-1 The following was filed automatically by anaconda: anaconda 26.21.3-1 exception report Traceback (most recent call first): File "/usr/lib64/python3.6/site-packages/gi/overrides/BlockDev.py", line 762, in wrapped raise transform[1](msg) File "/usr/lib/python3.6/site-packages/blivet/formats/lvmpv.py", line 125, in _create blockdev.lvm.pvcreate(self.device, data_alignment=self.data_alignment) File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.6/site-packages/blivet/formats/__init__.py", line 509, in create self._create(**kwargs) File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.6/site-packages/blivet/deviceaction.py", line 607, in execute options=self.device.format_args) File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.6/site-packages/blivet/actionlist.py", line 325, in process action.execute(callbacks) File "/usr/lib/python3.6/site-packages/blivet/actionlist.py", line 48, in wrapped_func return func(obj, *args, **kwargs) File "/usr/lib/python3.6/site-packages/blivet/blivet.py", line 163, in do_it self.devicetree.actions.process(callbacks=callbacks, devices=self.devices) File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.6/site-packages/blivet/osinstall.py", line 1112, in turn_on_filesystems storage.do_it(callbacks) File "/usr/lib64/python3.6/site-packages/pyanaconda/install_tasks.py", line 437, in run_task self._task(*self._task_args, **self._task_kwargs) File "/usr/lib64/python3.6/site-packages/pyanaconda/install_tasks.py", line 471, in start self.run_task() File "/usr/lib64/python3.6/site-packages/pyanaconda/install_tasks.py", line 303, in start item.start() File "/usr/lib64/python3.6/site-packages/pyanaconda/install_tasks.py", line 303, in start item.start() File "/usr/lib64/python3.6/site-packages/pyanaconda/install.py", line 356, in doInstall installation_queue.start() File "/usr/lib64/python3.6/threading.py", line 864, in run self._target(*self._args, **self._kwargs) File "/usr/lib64/python3.6/site-packages/pyanaconda/threads.py", line 251, in run threading.Thread.run(self, *args, **kwargs) gi.overrides.BlockDev.LVMError: Waiting for 'PvCreate' method of the '/com/redhat/lvmdbus1/Manager' object to finish failed: Failed to get Complete property of the / object: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist Additional info: addons: com_redhat_kdump, com_redhat_docker cmdline: /usr/libexec/system-python /sbin/anaconda executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.11.0-0.rc6.git0.1.fc26.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 26
Created attachment 1274122 [details] File: anaconda-tb
Created attachment 1274123 [details] File: environ
Created attachment 1274124 [details] File: lsblk_output
Created attachment 1274125 [details] File: nmcli_dev_list
Created attachment 1274126 [details] File: os_info
This is actually a problem in lvmdbusd which returns ('/', '/') from the PvCreate method if it is called with the '/dev/md/Volume0_0p3' path. But if called with the '/dev/md126p3' (which is the target of the '/dev/md/Volume0_0p3' symlink), it returns an object path of the newly created PV.
Correction committed upstream
https://sourceware.org/git/?p=lvm2.git;a=commit;h=405a3689bcc40c8782685a739310e337a7c268a9
lvm2-2.02.168-5.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-f1874caad5
lvm2-2.02.168-5.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
With lvm2-2.02.168-5 I'm unable to reproduce this problem. So this seems to be fixed.