Bug 854962

I'm not sure about correct release blocking criteria for this, neither milestone but seems to be very confusing. Proposing as Alpha blocker, let's talk about it.

anaconda uses something like 'rsync -a / $NEW_ROOT' to copy the system

If I understand that, anaconda is copying the live system image *after* the livecd init script has run, instead of dd'ing the underlying live image device that doesn't have the at-boot changes done?

If so, that's a behavior change from prior releases, and would cause the symptoms seen here.

Well, I believe we always kept anaconda in the installed system.  It was in the on-media environment, so it got copied to the system.  There's likely an old old bug around about that somewhere.  I wouldn't be too optimistic about us dealing with that particular portion any time soon.

Right, but IIRC, all the basic live customization (enabling the 'install to hard disk' option, adding the live user, setting up autologin) was done in the ram-based overlay to the system, and therefore didn't make it to the installed system when copying the underlying image.

If we're just copying over the running image, then we get extra stuff we didn't before.

Yeah, Brian is already looking into this.

+1 NTH

anaconda-18.6.6-1.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/anaconda-18.6.6-1.fc18

Tested an install with 18.6.6-1. There's no liveuser after install, so this has been improved. However, I noticed at least one thing still wrong, that's possibly a part of this. I did not complete the 'root password' spoke in liveinst. I'd expect that to result in a locked root account, but it doesn't - the installed system has a root user with empty password, just like the live environment.

bcl says the thing I noted in comment #10 is a separate bug, so filed as https://bugzilla.redhat.com/show_bug.cgi?id=855481 .

we're not great on 'negative criteria', really ('thing X definitely shouldn't happen'), so this isn't terribly well covered. You could argue that auto-logging in as 'liveuser' is a violation of "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. This includes correctly accessing any encrypted partitions when the correct passphrase is supplied", though it's a bit of a stretch. I guess I'll vote +1 blocker on that basis. Definitely NTH. We have enough votes to accept this as at least NTH at this point (me, Johann, Jaroslav), so accepting as NTH at least.

As comment #10 is a separate bug, marking VERIFIED, I've confirmed the update fixes this.

Package anaconda-18.6.6-1.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing anaconda-18.6.6-1.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-13611/anaconda-18.6.6-1.fc18
then log in and leave karma (feedback).

Confirmed. Live user stuff is not installed anymore. Root password problem has a separate bug.

Discussed at 2012-09-10 QA meeting acting as a blocker review meeting. Accepted as a blocker per criterion cited in comment #12.

Setting to verified per comment 10 and comment 15.

18.6.7 went stable, so closing this.

anaconda-18.6.6-1.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.