oem user gets deleted even before "Prepare for shipping to end user"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ubiquity (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
A regression was introduced in fixing this bug:
https:/
As it stands now, the oem user gets deleted every time the oem-config upstart job gets run (not just when running the end user config, after clicking "Prepare for shipping to end user"). So you can never log into the OEM account... on the first boot after the install, the OEM account will already be gone, only the temporary session is available.
I know it's getting down the wire and the proper fix might not make the ISO, but my vote is to at least back this change out because it actually makes it worse from an OEM perspective.
At least in terms of the processes that System76 uses, it's not a deal-breaker if the ISO doesn't contain a Ubiquity version that we can ship to customers, because we regularly update our golden image, can easily add a patched Ubiquity if needed. But it's a huge pain if the ISO contains an oem-config so broken that we can't easily master our golden images in the first place.
Currently to work around this you must do an OEM mode install, then remount the target device after the install finishes (before you reboot) and edit /etc/init/
post-start script
# Remove the temporary OEM configuration user, again, if possible.
# If and when oem-config-wrapper fails http://
[ -f /var/lib/
rm -f /var/lib/
if getent passwd oem >/dev/null; then
userdel --force --remove oem || true
fi
end script
Note that it would of course be nice to have a proper fix SRU in the near future. I'm just thinking strategically about what we'll be stuck with on the 13.10 ISO.
Related branches
- Colin Watson (community): Approve
-
Diff: 104 lines (+26/-16)5 files modifiedbin/oem-config-firstboot (+12/-0)
bin/oem-config-wrapper (+0/-5)
debian/changelog (+13/-0)
debian/control (+1/-1)
debian/oem-config.oem-config.upstart (+0/-10)
Note I have a hacky (but usable) fix here that System76 will use if need be:
https:/ /code.launchpad .net/~jderose/ ubiquity/ fix-1239471
The problem with my fix is it assumes the customer config finishes successfully. But I think it's workable anyway.