Fedora Account System
Red Hat Associate
Red Hat Customer
Created attachment 1172453 [details] details of my LVM setup collected under F23 Description of problem: My existing (and working fine under F23) VG can not be used in F24 anaconda. I get This LVM Volume Group is missing 1 of 2 physical volumes. You can remove it or select a different device. Version-Release number of selected component (if applicable): F24 x86_64 GA netboot of Everything How reproducible: always Steps to Reproduce: 1. have an existing LVM setup as can be seen in LVM-karhu-F23.txt 2. netboot F24 Everything 3. go to storage screen, select all my drives plus "I will configure partitioning" Actual results: This LVM Volume Group is missing 1 of 2 physical volumes. You can remove it or select a different device. Expected results: My existing VG is available as an installation target Additional info:
entry used for booting off my install server; label F24-Everything-x86_64 MENU LABEL Fedora 24 Everything x86_64 Live TEXT HELP initrd and kernel from Everything images/pxelinux/ repo points at Everything ENDTEXT IPAPPEND 2 kernel images/F24-Everything-x86_64/vmlinuz append initrd=images/F24-Everything-x86_64/initrd.img inst.stage2=ftp://haswell.internal.pcfe.net/pub/redhat/Fedora/linux/releases/24/Everything/x86_64/os/ inst.repo=ftp://haswell.internal.pcfe.net/pub/redhat/Fedora/linux/releases/24/Everything/x86_64/os/ ip=dhcp
Created attachment 1172455 [details] anaconda.log from the F24 install attempt
Created attachment 1172456 [details] dnf.librepo.log from the F24 install attempt
Created attachment 1172457 [details] dnf.log from the F24 install attempt
Created attachment 1172458 [details] dnf.rpm.log from the F24 install attempt
Created attachment 1172459 [details] hawkey.log from the F24 install attempt
Created attachment 1172460 [details] ifcfg.log from the F24 install attempt
Created attachment 1172461 [details] packaging.log from the F24 install attempt
Created attachment 1172462 [details] program.log from the F24 install attempt
Created attachment 1172463 [details] storage.log from the F24 install attempt
Created attachment 1172464 [details] syslog from the F24 install attempt
Created attachment 1172465 [details] X.log from the F24 install attempt
A work-around of sorts is dnf-plugin-system-upgrade https://fedoraproject.org/wiki/DNF_system_upgrade This allowed me to pull the affected machine up to F24, even though I would have preferred to install into a new LV Coul;d it be that my use of lvmcache for the /home LV confused anaconda?
This is a bit like 1348688, in which we don't get any info from lvm-dbus about a luks pv. The md pv would have been activated quite a bit earlier, though, so I don't know if this could be the same underlying problem or not.
Patrick, could you please try using the updates.img for the bug #1348688? https://fedoraproject.org/wiki/Common_F24_bugs#lvm-on-luks-reuse-broken
Vratislav, anaconda still reports 1 out of 2 PV missing when I use the umdates.img
(In reply to Patrick C. F. Ernzer from comment #16) > Vratislav, > > anaconda still reports 1 out of 2 PV missing > when I use the umdates.img Not so good news, but thanks!
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.