Public bug reported:
As per documentation:
- late-commands
-- Shell commands to run after the install has completed successfully and any
updates and packages installed, just before the system reboots.
Doesn’t seem to be the case. At least during late-commands I would
expect the system to be finished as per description, but i.e. the
defined user in identity isn’t even in `/target/etc/passwd` nor in
`/etc/passwd`. Caused my late-command script to fail.
The specified user(s) in the `identity` or `user-data` section is/are
not applied until the final reboot happens. Therefore, late-command is
not being run in a complete state of the install!
How to check? Watch both passwd or group until the installer finishes.
Nothing happens there. On reboot everything is suddenly there.
This prevents my late-command scripts to fail, `in-target
target=/target`, i.e. `su: user USER does not exist`.
Manually adding users in late-command using `useradd` causes this user
to be id 1000 and every other following counted up. Furthermore those
users added by the installer are not being able to login then because
their home directory belongs to `root:root`.
** Affects: subiquity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1954719
Title:
Ubuntu Server 20.04.3 autoinstall - User not available until reboot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/1954719/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
