In recent F28 and Rawhide composes, Workstation live installs suppress the root password and user creation needles.
I've been trying to hack around this tonight, but ran into a bit of a big problem at the end.
So far I've put stuff in place to not try and create a user account and root password during install, and something that should hopefully set a root password at the end of install. Longer term we may want to look at using sudo instead of su to become root on Workstation installs, but that's kind of a more complex change.
However, I found something more difficult to deal with, something that's a slightly unexpected behaviour change: the installer now auto-quits on completion in the Workstation live. It doesn't get to the end screen and wait till you click the 'Quit' button to actually quit, it just automatically quits when the install completes.
This is kinda 'intended' on the anaconda side - basically, it seems like they believe the 'wait for you to click on the button' behaviour is only needed if there are any spokes on the hub, i.e. anything you might still want to go and interact with. If there isn't anything, they figure there's no need to wait for an explicit quit action.
This is a bit tricky for openQA, though; it's not obvious what would be the best way to detect 'oh hey, anaconda just finished what it was doing and went away'. We can't just assert on the desktop background cos it changes all the damn time. I'll have to have a think about this one.
@catanzaro
This is silly. I would just make Anaconda not quit automatically. How else is the user going to know whether the install completed successfully or not?
the install completed successfully when you boot into it ?
OK, I wasn't sure what you'd think of the behaviour. Let me run it by the anaconda folks and see if my understanding is correct.
@m4rtink what's your take on this? (is my understanding of anaconda's behaviour correct?)
@mclasen I think so. openQA doesn't try, that's why this issue exists - it believes the install failed as it never sees the 'install complete' screen. I did do a manual install yesterday for other reasons and the installed system booted, though. I didn't specifically notice this behaviour in that manual install attempt, but I was doing five things at once at the time and probably just didn't notice anaconda had gone away without me clicking Quit.
Yeah, users will figure it out in the end, when they try to reboot. But they won't even see the message telling them that they need to reboot. My first guess would be that the installer crashed....
As for the accounts - do I understand it correctly there will be no account at all, just GIS scheduled to start and enable user creation ? I guess that's going to work as long as you are sure GIS will start & users can't easily quit it by mistake before a user is created. Otherwise (if I understand things correctly) they would likely have to reinstall.
Also debugging of issues preventing GIS & co from starting could be a bit more complicated, but likely doable (mounting the rootfs externally, setting systemd to boot to bash, etc.).
As for the issue with quitting immediately - that's definitely incorrect in this usecase and we should do something about it. Likely add a property to the Hub that tells Anaconda to stay on the hub even if there are no spokes & the property would be set to True for live installations. Can you fill a RFE bug for this so we can track it ? Thanks in advance! :)
Will do.
The broader consequences of the change are a bit out of scope for this ticket, but to give a very general answer, they've mostly thought about it and it does work, yes. :) We could go into it in more detail via IRC or in the Change bug or something if you like.
https://bugzilla.redhat.com/show_bug.cgi?id=1553935
So the series of changes I threw at this (check the commit log...) should finally be more or less working now, I think. Gonna close this. Will clean up any remaining messes as I go along.
For now I'm handling the 'anaconda just goes away' behaviour by checking every 60 seconds if the anaconda icon is still in the top bar, and assuming the install finished if it isn't. whee, fun.
Metadata Update from @adamwill: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.