= problem = We currently don't have an explicit release criterion about user creation, but we have release criteria and test cases that require a user account.
= analysis = While filing [https://bugzilla.redhat.com/show_bug.cgi?id=863886 a bug about anaconda not installing firstboot], I realized that we currently don't have a release criterion that explicitly states that a user must be created and this user must be able to log in.
In the alpha release criteria we have something close: ''"Following on from the previous criterion, after firstboot is completed and on subsequent boots, a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to a working graphical environment without unintended user intervention."'' However this criterion only mentions firstboot, but not the user creation.
= enhancement recommendation = Another release criterion: "If a desktop environment was installed or the system was configured to boot into a graphical target, a regular user account must be created, either during install or on the subsequent boot. e.g. with firstboot. After creation, this user must be able to successfully log into the newly installed system."
The very previous criterion reads:
"In most cases (see Blocker_Bug_FAQ), a system installed according to any of the above criteria (or the appropriate Beta or Final criteria, when applying this criterion to those releases) must boot to the 'firstboot' utility on the first boot after installation, without unintended user intervention, unless the user explicitly chooses to boot in non-graphical mode. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied. ''The firstboot utility must be able to create a working user account''" (emphasis added).
Ouch, I wonder how I can have missed this.
Login to comment on this ticket.