Description of problem: I was trying to create a new logical volume on an SD card but the logical volume tab wasn't showing (using blivet), so I pressed "OK" twice so I could go to the main menu and when I clicked installation destination again I got the error Version-Release number of selected component: anaconda-28.22.10 The following was filed automatically by anaconda: anaconda 28.22.10 exception report Traceback (most recent call first): File "/usr/lib/python3.6/site-packages/blivet/formats/lvmpv.py", line 166, in free raise PhysicalVolumeError("Unknown free space information for the PV '%s'" % self.device) File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 53, in run_with_lock return m(*args, **kwargs) File "/usr/lib64/python3.6/site-packages/pyanaconda/storage/osinstall.py", line 1488, in get_free_space elif hasattr(partition.format, "free"): File "/usr/lib/python3.6/site-packages/blivet/threads.py", line 53, in run_with_lock return m(*args, **kwargs) File "/usr/lib64/python3.6/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 737, in _add_disk_overview free = self.storage.get_free_space(disks=[disk])[disk.name][0] File "/usr/lib64/python3.6/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 651, in refresh self._add_disk_overview(disk, self.local_disks_box) File "/usr/lib64/python3.6/site-packages/pyanaconda/ui/gui/hubs/__init__.py", line 419, in _on_spoke_clicked spoke.refresh() blivet.errors.PhysicalVolumeError: Unknown free space information for the PV '/dev/req20' Additional info: addons: com_redhat_kdump, com_redhat_docker cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-28 rd.live.check quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.16.3-301.fc28.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 28
Created attachment 1480615 [details] File: anaconda-tb
Created attachment 1480616 [details] File: anaconda.log
Created attachment 1480617 [details] File: blivet-gui-utils.log
Created attachment 1480618 [details] File: dbus.log
Created attachment 1480619 [details] File: dnf.librepo.log
Created attachment 1480620 [details] File: environ
Created attachment 1480621 [details] File: hawkey.log
Created attachment 1480622 [details] File: lorax-packages.log
Created attachment 1480623 [details] File: lsblk_output
Created attachment 1480624 [details] File: nmcli_dev_list
Created attachment 1480625 [details] File: os_info
Created attachment 1480626 [details] File: program.log
Created attachment 1480627 [details] File: storage.log
Created attachment 1480628 [details] File: syslog
Created attachment 1480629 [details] File: ifcfg.log
Created attachment 1480630 [details] File: packaging.log
It seems to be an issue in the storage configuration library. Reassigning to blivet.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.