do-release-upgrade assumes /usr/sbin/sshd exists if you are upgrading over ssh

Bug #1123343 reported by James Troup on 2013-02-12
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Medium
Unassigned
update-manager (Ubuntu)
Medium
Unassigned

Bug Description

do-release-upgrade assumes that /usr/sbin/sshd exists if you are
upgrading over ssh. While that may seem intuitively true, it's not
always the case, e.g. I was upgrading a chroot on a machine via ssh.
The host/base OS had openssh-server installed; the chroot did not.

Requiring /usr/sbin/sshd is not unreasonable, but the code should give
a more useful error message (i.e. not a python traceback), if it
doesn't.

James Troup (elmo) wrote :

This was trying to upgrade a lucid chroot to precise, FWIW. The base OS was also lucid, if it matters.

Changed in update-manager (Ubuntu):
importance: Undecided → Medium
Brian Murray (brian-murray) wrote :

This code appears to be unchanged since Precise and so this is likely still an issue.

Changed in update-manager (Ubuntu):
status: New → Triaged
Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers