Description of problem: I followed test case: https://fedoraproject.org/wiki/QA:Testcase_Server_role_deploy I installed F22 Server Beta RC3 with all defaults set. After installation I followed steps from https://fedorahosted.org/rolekit/wiki/DomainController In booted system I set hostname to ipa.example.com. Run /usr/sbin/rngd -r /dev/urandom, created settings.json file with suggested minimum. Then I run 'rolectl deploy --settings-file=./settings.json domaincontroller' After a while the process failed with message: "Error: COMMAND_FAILED: 256" In journal I found ERROR messages (see attached journal nearly at the end there is whole output) which says: ERROR: ipa : DEBUG The ipa-server-install command failed, exception: SystemExit: Invalid hostname 'ipa', must be f ully-qualified. ERROR: ERROR: Invalid hostname 'ipa', must be fully-qualified. Which is strange because hostname is set to ipa.example.com Version-Release number of selected component (if applicable): rolekit-0.3.2-1.fc22.noarch How reproducible: I tried it three time and it happened all the time. Yesterday it worked with RC2 Additional info: I propose this as a beta blocker because it violates beta criterion: "The core functional requirements for all Featured Server Roles must be met, without any workarounds being necessary."
Created attachment 1015267 [details] output of journalctl -a
How precisely did you set the hostname? Did you use 'hostnamectl set-hostname ipa.example.com'?
I just booted a VM, installed Server Beta RC3 taking all of the defaults (including the default hostname). When it booted up, I ran 'hostnamectl set-hostname domaincontroller.brc3.ipa' and then 'rolectl deploy --settings-file=dc.json domaincontroller' (with a settings file containing only admin_password. The domain controller installed successfully. I cannot reproduce this issue. My best guess is that whatever mechanism you used to set the hostname did not set it correctly. The appropriate way to do so is with hostnamectl or via cockpit.