[Bug 296070] Re: do-release-upgrade via ssh requires sshd in the same system

[Launchpad Bug Tracker]

[Expired for update-manager (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: update-manager (Ubuntu)
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/296070

Title:
  do-release-upgrade via ssh requires sshd in the same system

Status in “update-manager” package in Ubuntu:
  Expired

Bug description:
  Binary package hint: update-manager-core

  Problems upgrading Ubuntu Server 8.04.1 to 8.10:

  The release upgrade helper "do-release-upgrade" shipped with upgrade-
  manager-core on an Ubuntu 8.04.1 Server tries to start an additional
  ssh daemon if run in server mode and if it can find SSH_CONNECTION or
  SSH_TTY in the environment. There's no option to skip launching the
  additional sshd, one can either continue or abort the whole upgrade.

  If there is no openssh-server installed in this system (thus no
  /usr/bin/sshd), do-release-upgrade will receive a child_exception from
  module subprocess and die.

  This scenario is possible while upgrading a guest system within a
  Linux-VServer setup. We connect to the host system's sshd and enter
  the guest systems using util-vserver's "vserver <guest> enter". This
  can also happen if you're using several other setups involving
  chrooted Ubuntu Server systems.

  The quick fix is to get rid of SSH_CONNECTION and SSH_TTY in the
  chrooted environment prior to launching do-release-upgrade.

  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu.
  $ lsb_release -rd
  Description:    Ubuntu 8.04.1
  Release:        8.04

  2) The version of the package you are using, via 'apt-cache policy packagename' or by checking in Synaptic.
  $ apt-cache policy update-manager-core
  update-manager-core:
    Installed: 1:0.87.30
    Candidate: 1:0.87.30
    Version table:
   *** 1:0.87.30 0
          500 http://de.archive.ubuntu.com hardy-updates/main Packages
          100 /var/lib/dpkg/status
       1:0.87.24 0
          500 http://de.archive.ubuntu.com hardy/main Packages

  3) What you expected to happen
  Catch the exception and ask me to continue without an additional ssh daemon.

  4) What happened instead
  $ do-release-upgrade
  Checking for a new ubuntu release
  Done Upgrade tool signature
  Done Upgrade tool
  Done downloading
  extracting 'intrepid.tar.gz'
  authenticate 'intrepid.tar.gz' against 'intrepid.tar.gz.gpg'

  Reading cache

  Checking package manager

  Continue running under SSH?

  This session appears to be running under ssh. It is not recommended
  to perform a upgrade over ssh currently because in case of failure it
  is harder to recover.

  If you continue, a additional ssh daemon will be started at port
  '9004'.
  Do you want to continue?

  Continue [yN] y

  
  A fatal error occurred

  Please report this as a bug and include the files
  /var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in
  your report. The upgrade aborts now.
  Your original sources.list was saved in
  /etc/apt/sources.list.distUpgrade.

  Traceback (most recent call last):

  File "/tmp/tmp3Pqofq/intrepid", line 76, in <module>
  app.run()

  File "/tmp/tmp3Pqofq/DistUpgradeController.py", line 1458, in run
  self.fullUpgrade()

  File "/tmp/tmp3Pqofq/DistUpgradeController.py", line 1332, in
  fullUpgrade
  if not self.prepare():

  File "/tmp/tmp3Pqofq/DistUpgradeController.py", line 297, in prepare
  self._sshMagic()

  File "/tmp/tmp3Pqofq/DistUpgradeController.py", line 206, in
  _sshMagic
  "-p",str(port)])

  File "/usr/lib/python2.5/subprocess.py", line 444, in call
  return Popen(*popenargs, **kwargs).wait()

  File "/usr/lib/python2.5/subprocess.py", line 594, in __init__
  errread, errwrite)

  File "/usr/lib/python2.5/subprocess.py", line 1147, in _execute_child
  raise child_exception

  OSError: [Errno 2] No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/296070/+subscriptions