do-release-upgrade logs a failed usermod near the end
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
Incomplete
|
Undecided
|
Michael Vogt |
Bug Description
Binary package hint: update-manager
I logged into a dapper system using an account that gets access to the system via LDAP, and which has sudo privileges via a group other than "admin" and ran "sudo do-release-upgrade -d" to get to Hardy.
Near the end of the upgrade, I saw the following: "usermod: nick not found in /etc/passwd". mvo suggested to me in IRC that this is likely an attempt to fix retrograde installations that were created before the "admin" group became standard. We did not want my user added to this group, though.
Another question is why use "usermod" rather than "adduser"? adduser appears to be smarter about finding users via whatever path nsswitch.conf takes you through (not that we wanted it to succeed in this instance).
Changed in update-manager: | |
assignee: | nobody → mvo |
Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.