Builder role - Anaconda gets stuck on no root info

[zjpeterson]

When kickstarting from an image built by the infra.osbuild.builder role (using the role defaults - builder_pub_key set, builder_password not set), anaconda (RHEL 9.1) stops to complain that it doesn't have all the information it needs. You can make the install proceed by filling out a root password interactively. However, this stop in the process makes it unsuitable for zero-touch provisioning.

This is not an issue if you supply builder_password (that ends up being the root password) but that means that the documentation stating "builder_password or builder_pub_key needs to be defined when using the kickstart file" is not accurate, and you can't have a system with no root password/key-only. The documentation isn't clear on where exactly the key/password data applies, as it's asked for as role-level variables but there are examples of that same information being passed as compose customizations as well.