Description of problem: The installer complains and will not add a /boot/efi mount point with file system Linux HFS+ ESP because it's an "Unacceptable label format for filesystem". Version-Release number of selected component (if applicable): Fedora-Live-Workstation-x86_64-21_Alpha-TC7.iso anaconda-21.48.6-1.fc21 python-blivet-0.61.1-1.fc21 How reproducible: Always Steps to Reproduce: 1. Click on an existing, wiped 100MiB partition 2. Check Reformat, and change File System pop-up to Linux HFS+ ESP 3. Click on Mount Point field and set it to /boot/efi 4. Click Update Settings button Actual results: Message banner reads Unacceptable label format for filesystem. Expected results: Not this, but I'm not familiar with the term "label format" makes me think it has a problem with the encoding for the mkfs.hfsplus -n flag for setting the volume name/label? This was working for a prior TC though, maybe TC5, because prior to this installation attempt this partition was labeled something like "Linux HFS+ ESP" as it appeared in OS X, in contrast to past builds where this has shown up as "Untitled". Additional info:
Created attachment 937735 [details] anaconda.log
Created attachment 937736 [details] program.log
Created attachment 937737 [details] storage.log
This doesn't happen when installing to free space, and clicking the blue link option within Manual Partitioning to automatically create partitions.
Is this still happening with the final F21 release?
Yes. 17:45:44,866 INFO anaconda: /sbin/anaconda 21.48.21-1 [...] 17:46:31,992 DEBUG anaconda: new selector: existing 200 MiB partition sda4 (27) 17:46:32,014 DEBUG anaconda: populate_right_side: existing 200 MiB partition sda4 (27) 17:46:32,033 DEBUG anaconda: updated device_disks to ['sda'] 17:46:32,033 DEBUG anaconda: updated device_container_name to None 17:46:32,033 DEBUG anaconda: updated device_container_raid_level to None 17:46:32,033 DEBUG anaconda: updated device_container_encrypted to False 17:46:32,034 DEBUG anaconda: updated device_container_size to 0 17:46:32,041 DEBUG anaconda: fs type changed: Unknown 17:46:32,043 DEBUG anaconda: populate_raid: 2, None 17:46:35,878 DEBUG anaconda: fs type changed: Linux HFS+ ESP 17:46:43,780 INFO anaconda: ui: saving changes to device sda4 17:46:43,781 DEBUG anaconda: reformat: True 17:46:43,788 DEBUG anaconda: populate_right_side: existing 200 MiB partition sda4 (27) 17:46:43,809 DEBUG anaconda: updated device_disks to ['sda'] 17:46:43,809 DEBUG anaconda: updated device_container_name to None 17:46:43,809 DEBUG anaconda: updated device_container_raid_level to None 17:46:43,810 DEBUG anaconda: updated device_container_encrypted to False 17:46:43,810 DEBUG anaconda: updated device_container_size to 0 17:46:43,820 DEBUG anaconda: fs type changed: Unknown That last line is bogus, I didn't change it back to Unknown. I changed it from Unknown to Linux hFS+ ESP, then clicked Update Settings. It's like it's snapping back to Unknown and the error message is that fs type Unknown isn't acceptable. So strictly speaking the error message is correct, the problem is the UI is somehow now changing the fs type from Unknown to Linux hFS+ ESP and leaving it there (it reverts to Unknown upon clicking Update Settings). Also, if the fs type is HFS+ to start with, the bug doesn't happen. Only if the selected partition's fs type is Unknown (i.e. use wipefs -a on the partition in advance) does this bug get triggered.
"is somehow now changing" should be "is somehow not changing"
https://github.com/rhinstaller/anaconda/pull/33