On Mon, 2021-12-20 at 10:43 -0500, Stephen John Smoogen wrote:
On Mon, 20 Dec 2021 at 10:31, Ondrej Mosnacek
<omosnace(a)redhat.com> wrote:
>
> Hi,
>
> When I set up a rawhide cloud image
> (Fedora-Cloud-Base-Rawhide-20211217.n.1.x86_64.qcow2 from
>
download.fedoraproject.org) with a root password using virt-sysprep:
>
> virt-sysprep -a <image> --root-password password:123456
> --selinux-relabel [...]
>
I believe this is intentional. Please see emails with subjects:
F36 Change: Make Rescue Mode Work With Locked Root (System-Wide Change proposal)
F36 Change: Users are administrators by default in the installer GUI.
(Self-Contained Change proposal)
there may be some others. Basically root login is no longer allowed
via PAM and possibly other tools. My understanding is that you need to
login as a user, and then become root.
No, I don't think that's it. None of those changes is meant to preclude
explicitly setting a root password.
I think this is actually a bug in Rawhide since 20211215.n.0 . I did
not investigate it in detail since I'm on PTO, my colleague Frantisek
Zatloukal (CC'ed) is looking into it. We see the same problem with any
login attempt on console after a minimal install; it works OK after a
Server install. The Workstation live images also fail to boot, they
just get stuck at the splash screen. We're not sure yet if it's two
different problems.
The most likely suspect seems to be:
Package: authselect-1.3.0-3.fc36
Old package: authselect-1.2.4-2.fc36
So CCing pbrezina. It's notable that the bug doesn't happen on upgraded
systems - there's a test that starts from a minimal install of F35 and
upgrades to F36, and that test works OK. So I suspect the problem
occurs when the installer tries to do initial authselect configuration
of the installed system. That's about as far as we got up to the
weekend. Frantisek has logs he could forward to pbrezina.
--
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net