users.createUser() has an argument named 'name', the kwargs passed cannot contain name without raising a TypeError.
Can you elaborate on the impact of this bug a little more? I don't understand what the user would hit for this.
Anyone doing a kickstart install which sets up users will hit this.
Is there an estimated timeline for when a fix might be ready and how invasive it would be? This isn't covered explicitly by any of the alpha release criteria but that doesn't mean that it can't be an alpha blocker since the result is rather nasty. [1] http://fedoraproject.org/wiki/Fedora_16_Alpha_Release_Criteria
Discussed at the weekly QA meeting of 2011-08-15 (with anaconda team and releng in attendance). Rejected as blocker and NTH: we felt this doesn't hit any Alpha criteria, and though it's a bad bug, it's too late to take as NTH for Alpha, we want minimal changes for RC4. Re-proposing as Beta blocker.
Discussed in the 2011-08-26 blocker review meeting. No decision was made regarding blocker status because details about the kickstart release criteria have not yet been finalized. Accepted as NTH for Fedora 16 beta because this isn't an uncommon use case.
bcl says the fix made 16.16, so we should now be able to re-test this.
I think this probably depends on 734861.
actually, since you can do a GUI kickstart install, it really doesn't... so, I tested this, with this line in my .ks: user --name=test --password=test --plaintext the install was successful and the user 'test' shows up in /etc/passwd , but trying to login with username test, password test gives 'Login incorrect'. Did I do something wrong with the parameters, or is that another bug? This bug does seem fixed, though.
there's no /home/test either...
this was discussed at the 2011-09-02 blocker meeting and agreed to be RejectedBlocker, but we didn't update the bug - doing so now.
16.18 is in stable now. This bug is fixed, the symptoms I saw in comment #8 relate to another bug.