Created attachment 1675199 [details] anaconda-ks.cfg + blkid.txt + fedora32-double-encrypt-2020-03-31_01.29.28.mkv + lsblk.txt Description of problem: When I do an custom storage configuration and I enable encrypt flag into VG, if I change some FS options, like fstype or volume lable and press Update Settting or change filesystem, anaconda add "luke-" before the LV device and create the filesystem on a LV device encrypted. Version-Release number of selected component (if applicable): Fedora-Workstation-Live-x86_64-32-20200328.n.0.iso How reproducible: Use a Custom layout partition, enable encryption into VG and change some filesystem option. Steps to Reproduce: 1. Seuto a Custom layout partition, 2. Enable encryption into VG 3. change some filesystem option and seehow the LV label under FS mount point Actual results: Anaconda encrypt VG and LV Expected results: Encrypt only VG Additional info: See video attach
Can you post the install logs from /var/log/anaconda? Separately attached: anaconda.log, program.log, and storage.log. These show the installer's logical decision making process and actions and is usually needed to figure out where the problem is happening. It's obvious not correct or intended to double encrypt like this. Thanks.
Created attachment 1675412 [details] Anaconda logs
(In reply to Chris Murphy from comment #1) > Can you post the install logs from /var/log/anaconda? Separately attached: > anaconda.log, program.log, and storage.log. These show the installer's > logical decision making process and actions and is usually needed to figure > out where the problem is happening. It's obvious not correct or intended to > double encrypt like this. Thanks. IMHO: Anaconda take a wrong decision because try to respect the external FS encrypt flag. This flag into fedora 32 become blue, which means it's activated/deactivated ... but it cannot be deactivated In previous version >32 this flag is enable but is grey (do not touch). The colour blue/grey is the visible difference. Hope this help
Fixed in a pull request: https://github.com/rhinstaller/anaconda/pull/2423
FEDORA-2020-176362208a has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-176362208a
FEDORA-2020-176362208a has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-176362208a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-176362208a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
I have test new version of anaconda sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-176362208a --refresh and I confirm it work. Good the '-' in the encryption FS flag. Many thank to all
Thanks for testing this Dario!
FEDORA-2020-176362208a has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
*** Bug 1823471 has been marked as a duplicate of this bug. ***