Created attachment 1427637 [details] reproducer kickstart Description of problem: Having LVM PV used for cache on raid returning error: Cache PVs must belong to the same VG as the cached LV In the kickstart file I have only 1 VG and all the PVs are in it. It is working correctly when the PV is not raid. Version-Release number of selected component (if applicable): anaconda-29.12-1 How reproducible: Always Steps to Reproduce: 1. Start automatic installation with attached kickstart file Actual results: Error that the kickstart file not correct. Expected results: Installation should correctly finish. Additional info: This is happening also on Fedora 27 and most probably for 28 too.
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'.
This one is present in Centos 7.5 as well.
This bug still exists in Fedora 30 Beta
Since Fedora 29 installer is golden, this should probably be moved to Fedora 30 where it still has a chance of being fixed. Also, you can't (safely) have a writeback cache without raid to provide redundancy, so until this is fixed only writethrough cache creation commands are supportable in a kickstart. I also set the severity to high on this bug because there is no workaround. You can't create the lvs in a %pre because the --useexisting and --noformat options for raid devices is not working properly either (I'll file a separate bug about that).
Do you need logs for this bug, or is the reproducer sufficient? This bug and bug #1695913 are the only ones remaining that block my particular kickstart drive setup.
This message is a reminder that Fedora 30 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26. 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 '30'. 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 30 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.
Still reproducible on Rawhide.
This bug appears to have been reported against 'rawhide' during the Fedora 33 development cycle. Changing version to 33.
This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. 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 '33'. 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 33 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 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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.