Description of problem: I was trying to install Fedora, I'd gone through setting the partitions, packages, partitioning, and then I hit the ok button to start the installation. I entered the password for root and my general user's information. I hit OK, it kept going, then a few seconds later, this error. Version-Release number of selected component: anaconda-27.19-1 The following was filed automatically by anaconda: anaconda 27.19-1 exception report Traceback (most recent call first): File "/usr/lib64/python3.6/site-packages/gi/overrides/BlockDev.py", line 824, in wrapped raise transform[1](msg) File "/usr/lib/python3.6/site-packages/blivet/devices/lvm.py", line 1966, in _setup blockdev.lvm.lvactivate(self.vg.name, self._name) File "/usr/lib/python3.6/site-packages/blivet/devices/lvm.py", line 1839, in decorated return meth(self, *args, **kwargs) # pylint: disable=not-callable 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/devices/storage.py", line 377, in setup self._setup(orig=orig) 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/devices/lvm.py", line 1936, in setup return DMDevice.setup(self, orig) File "/usr/lib/python3.6/site-packages/blivet/devices/lvm.py", line 1839, in decorated return meth(self, *args, **kwargs) # pylint: disable=not-callable 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 695, in execute self.device.setup(orig=True) 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/installation_tasks.py", line 438, in run_task self._task(*self._task_args, **self._task_kwargs) File "/usr/lib64/python3.6/site-packages/pyanaconda/installation_tasks.py", line 472, in start self.run_task() File "/usr/lib64/python3.6/site-packages/pyanaconda/installation_tasks.py", line 304, in start item.start() File "/usr/lib64/python3.6/site-packages/pyanaconda/installation_tasks.py", line 304, in start item.start() File "/usr/lib64/python3.6/site-packages/pyanaconda/installation.py", line 365, 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/threading.py", line 252, in run threading.Thread.run(self) gi.overrides.BlockDev.LVMError: Failed to call the 'Activate' method on the '/com/redhat/lvmdbus1/Lv/0' object: GDBus.Error:org.freedesktop.DBus.Python.dbus.exceptions.DBusException: ('com.redhat.lvmdbus1.Lv', 'Exit code 5, stderr = Volume group "mainvg" not found\n Cannot process volume group mainvg\n') Additional info: addons: com_redhat_kdump, com_redhat_docker cmdline: /usr/libexec/system-python /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-rawh quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.13.0-0.rc2.git3.1.fc27.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: rawhide
Created attachment 1307793 [details] File: anaconda-tb
Created attachment 1307794 [details] File: anaconda.log
Created attachment 1307795 [details] File: dnf.librepo.log
Created attachment 1307796 [details] File: environ
Created attachment 1307797 [details] File: hawkey.log
Created attachment 1307798 [details] File: lsblk_output
Created attachment 1307799 [details] File: lvm.log
Created attachment 1307800 [details] File: nmcli_dev_list
Created attachment 1307801 [details] File: os_info
Created attachment 1307802 [details] File: storage.log
Created attachment 1307803 [details] File: syslog
Created attachment 1307804 [details] File: ifcfg.log
Created attachment 1307805 [details] File: packaging.log
Created attachment 1307806 [details] File: program.log
This looks like the volume group is not activated/created properly. I'm changing component to blivet our storage library.
This installation is a re-install of my previously fine working rawhide setup. I'd had a bit of trouble getting the new vpn packages working, so I'd been updating, downgrading all of them, but still I wasn't able to connect, even though I was able to before trying to update hte vpn packages. I did a full dnf clean all && dnf update -y (or as best I could without dnf complaining), then the system hung up. I let it go for a while, but still it was unresponsive. I held the power button to restart, and then got I/O errors on booting up. I tried a few other kernels, but no better. After that, I tried this re-install. Just now, I booted up off my usb drive that I'm using for the install iso. I didn't enter my luks password and I was then able to control + alt + f2, get to a terminal, and then manually mount the luks drive. I did # cryptsetup luksOpen /dev/sda2 mydrive # pvdisplay # vgdisplay # lvdisplay and my partitions were all there. I was then able to mount them # mkdir /mnt/mydrive # mount /dev/mainvg/data /mnt/mydrive # ls /mnt/mydrive # umount /mnt/mydrive # mount /dev/mainvg/root /mnt/mydrive # ls /mnt/mydrive and I could see the data from my system still there. Even though I'd always told the installer to reformat /, I guess the installer hadn't gotten that far before blowing up. I was able to rsync -av my old /home/ to /mnt/data. All that said, I wasn't able to mount the old partition until I'd rebooted but not entered my luks password. I'd get some error about it being unlocked already. Rather than figure that out, I just rebooted and manually unlocked it rather than entering my password into the installer program.
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'.
Peter, are you able to reproduce this? It looks like opening the LUKS device failed/was skipped for some weird reason. That doesn't seem to be happening usually -- I just tried reinstallation of a rawhide system and it worked fine.
Wait long enough and things work themselves out. This isn't a problem anymore using the latest rawhide.