Description of problem: When doing a kickstart install on armhfp for modular fedora we get the following Installation 1) [x] Language settings 2) [x] Time settings (English (United States)) (Etc/UTC timezone) 3) [x] Installation source 4) [x] Software selection (https://kojipkgs.fedoraproject (Custom software selected) .org/compose/Fedora-Modular-27- 6) [x] Network configuration 20171020.n.1/compose/Server/arm (Wired (eth0) connected) hfp/os) 5) [!] Installation Destination (Kickstart insufficient) 7) [ ] User creation (No user will be created) Please make a selection from the above ['b' to begin installation, 'h' to help, 'q' to quit, 'r' to refresh]: systemd-logind.service: Got notification message from PID 1226 (WATCHDOG=1) ============== When trying to configure the storage I get the following 1 disk selected; 4 GiB capacity; 4 GiB free ... autopart failed: /boot file system cannot be of type lvmlv /boot file system cannot be of type xfs. It may be a bug in anaconda, but 32 bit arm can not use lvm of XFS for /boot so autopartitioning correctly fails. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Proposed as a Blocker and Freeze Exception for 27-server-beta by Fedora user ausil using the blocker tracking app because: Container image creation on arm is failing. we also think it is the cause of the failures seen on ppc64le
Discussed during the 2017-10-23 blocker review meeting: [1] The decision to classify this bug as an AcceptedBlocker was made, as it causes some images on armhfp to not build. [1] https://meetbot.fedoraproject.org/fedora-blocker-review/2017-10-23/f27-blocker-review.2017-10-23-16.00.txt
This should be fixed with the recent composes. The cause of the issue was missing the e2fsprogs package in the lorax templates used to generate the images. This was fixed in https://github.com/fedora-modularity/lorax/commit/6adda1da3d003be6190e96279730b183ce084ad1