When you deploy Fedora from the ARM minimal disk image, the first thing you should see on boot is the console version of initial-setup. However, since the kmscon Change landed recently, it does not appear; you boot straight to a (kmscon) login prompt, where you can't log in, because there are no user accounts and no root password. This probably affects any other case where console initial-setup should appear as well, but the ARM minimal disk image case is probably the most important. ARM minimal disk image is release-blocking per https://docs.fedoraproject.org/en-US/releases/f44/blocking/ , so proposing as a Beta blocker as a violation of https://fedoraproject.org/wiki/Basic_Release_Criteria#Expected_installed_system_boot_behavior , "A working mechanism to create a user account must be clearly presented during installation and/or first boot of the installed system." The bug is likely not in kmscon itself, but filing against kmscon initially to ensure the right folks see it.
It should be possible to start kmscon with the initial-setup script as a login program. Something like this may work: systemctl stop kmsconvt@tty1 kmscon --vt=tty1 --no-switchvt --login -- initial-setup
I've added a --oneshot argument to kmscon, to help solve this issue: https://github.com/kmscon/kmscon/pull/427
I've proposed the following PR to initial setup, that solve the issue. https://github.com/rhinstaller/initial-setup/pull/161 This also require the --oneshot support in kmscon, and some selinux rules, as by default selinux will prevent kmscon to start initial-setup.