Hide Forgot
Description of problem: Choosing an installation disk throws an errror. Version-Release number of selected component: anaconda-core-25.20.4-1.fc25.x86_64 The following was filed automatically by anaconda: anaconda 25.20.4-1 exception report Traceback (most recent call first): File "/usr/lib64/python3.5/site-packages/gi/overrides/BlockDev.py", line 441, in wrapped raise transform[1](msg) File "/usr/lib/python3.5/site-packages/blivet/formats/lvmpv.py", line 167, in free pv_info = blockdev.lvm.pvinfo(self.device) File "/usr/lib/python3.5/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib/python3.5/site-packages/blivet/blivet.py", line 754, in get_free_space elif hasattr(partition.format, "free"): File "/usr/lib/python3.5/site-packages/blivet/threads.py", line 45, in run_with_lock return m(*args, **kwargs) File "/usr/lib64/python3.5/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 661, in _add_disk_overview free = self.storage.get_free_space(disks=[disk])[disk.name][0] File "/usr/lib64/python3.5/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 574, in refresh self._add_disk_overview(disk, self.local_disks_box) File "/usr/lib64/python3.5/site-packages/pyanaconda/ui/gui/hubs/__init__.py", line 387, in _on_spoke_clicked spoke.refresh() gi.overrides.BlockDev.LVMError: Process reported exit code 1280: WARNING: Not using lvmetad because duplicate PVs were found. WARNING: Use multipath or vgimportclone to resolve duplicate PVs? WARNING: After duplicates are resolved, run "pvscan --cache" to enable lvmetad. Failed to find device for physical volume "/dev/md/ARRAY0_0p2". Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img root=live:CDLABEL=Fedora-WS-Live-25_B-1-1 rd.live.image quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.8.0-0.rc7.git0.1.fc25.x86_64 other involved packages: python3-blivet-2.1.6-1.fc25.noarch, anaconda-gui-25.20.4-1.fc25.x86_64, python3-blockdev-1.9-4.fc25.x86_64 product: Fedora release: Fedora release 25 (Twenty Five) type: anaconda version: 25
Created attachment 1219966 [details] File: anaconda-tb
Created attachment 1219967 [details] File: anaconda.log
Created attachment 1219968 [details] File: environ
Created attachment 1219969 [details] File: journalctl
Created attachment 1219970 [details] File: lsblk_output
Created attachment 1219971 [details] File: lvm.log
Created attachment 1219972 [details] File: nmcli_dev_list
Created attachment 1219973 [details] File: os_info
Created attachment 1219974 [details] File: program.log
Created attachment 1219975 [details] File: storage.log
Created attachment 1219976 [details] File: ifcfg.log
Similar problem has been detected: - Inserted Fedora 25 Workstation - Chose to Install the software - Chose English Lang, English (US) Keyboard - Had to click on [Installation Destination] because it was flagged for addressing - Crashed. My system was previously running Fedora 22 (2 SSD Raided) on /dev/md126 and /dev/127 I noticed that vgs did not output anything, so i added: filter = [ "a|^/dev/md12[67]$|" ] to /etc/lvm/lvm.conf and ran vgscan. Now lvs lists my old fedora partition (logical volume). Ideally i'd like to at least keep the home partition from it. Re-ran setup (no reboot) from the menu and it crashed at the same spot. Have a Laptop: Acer Aspire S7 Fedora 22 still works awesome, but i'd really like to upgrade. Is this a bug, or a configuration issue i have? Perhaps my (Software) Raid is interfering some how? addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-WS-Live-25-1-3 rd.live.image quiet hashmarkername: anaconda kernel: 4.8.6-300.fc25.x86_64 other involved packages: python3-blockdev-1.9-8.fc25.x86_64, python3-blivet-2.1.6-4.fc25.noarch, anaconda-gui-25.20.8-1.fc25.x86_64 package: anaconda-core-25.20.8-1.fc25.x86_64 packaging.log: product: Fedora reason: gi.overrides.BlockDev.LVMError: Process reported exit code 1280: WARNING: Device for PV idt9cj-pj0b-PwHS-gy7N-qtfj-v7gl-AJzvjQ not found or rejected by a filter. release: Fedora release 25 (Twenty Five) version: 25
As an update, i found this RH Solution 1532583 which tells me to use the global_filter= entry in the lvm.conf and not the filter= # I tried this (just now) followed by running vgscan with same error global_filter = [ "a|^/dev/md/HDD0_0p[1-3]$|", "r|.*|" ] # Both of these gave the same error too (tried these originally) filter = [ "a|^/dev/md12[67]$|" ] filter = [ "a|^/dev/md/HDD0_0p[1-3]$|" ]
Similar problem has been detected: Just started installation process and clicked on "INSTALLATION DESTINATION". May the cause be that I have raid configuration? addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/images/pxeboot/vmlinuz root=live:CDLABEL=Fedora-WS-Live-25-1-3 rd.live.image quiet hashmarkername: anaconda kernel: 4.8.6-300.fc25.x86_64 other involved packages: anaconda-gui-25.20.8-1.fc25.x86_64, python3-blivet-2.1.6-4.fc25.noarch, python3-blockdev-1.9-8.fc25.x86_64 package: anaconda-core-25.20.8-1.fc25.x86_64 packaging.log: product: Fedora reason: gi.overrides.BlockDev.LVMError: Process reported exit code 1280: WARNING: Device for PV 0nufTs-z8uM-lLMq-AgPF-7ZHZ-4wwY-IMBWwr not found or rejected by a filter. release: Fedora release 25 (Twenty Five) version: 25
Could somebody bump the severity of this bug to "urgent", since there is no way I know of (but I am eager for suggestions) to install Fedora 25 without fixing it, please? And, yes, it really seems that this is due to Raid.
I too have run into this problem trying to install Fedora-25. Occurs with both Workstation and MATE spins. Trying Server next as a last resort to install. Unless that works, I'm dead in the water trying to install Fedora-25. (Note I had earlier done an upgrade install from F24 but that left me with some components not working so I need to do a clean install). Initially auto reported as https://bugzilla.redhat.com/show_bug.cgi?id=1403980 based on the MATE Spin error reason (the "duplicate PVs" error message was supplanted by the "failed to mount the install tree" message).
Wow - Installing the Fedora-25 "Server Edition" succeeded while the "Workstation" and "MATE Spin" fail. So I have a path forward. Further that should be a big clue (diffing the relevant anaconda (or whatever) scripts between Server and Workstation. Please note - I have provided a full set of diagnostic files for the "failure case" under https://bugzilla.redhat.com/show_bug.cgi?id=1403980 . I will attach there here as well. Lastly - Echoing comment 15, could somebody that has access assign a severity and/or priority to this ticket.
Created attachment 1278722 [details] Diagnostic files from failed MATE spin install
Created attachment 1278723 [details] Diagnostic files from failed Workstation spin install
Repeat the SERVER Edition WORKED FOR ME !!! I did not make that as obvious as I should have.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.