maverick to natty upgrade fails on missing iptables

[Martijn Koster]

I tried to upgrade a new maverick server to natty, per https://help.ubuntu.com/community/NattyUpgrades
Running do-release-upgrade failed fairly quickly with the following error:

root@thunder:/etc# do-release-upgrade
Checking for a new ubuntu release
Get:1 Upgrade tool signature [198B]
Get:2 Upgrade tool [1304kB]
Fetched 1304kB in 0s (0B/s)
extracting 'natty.tar.gz'
authenticate 'natty.tar.gz' against 'natty.tar.gz.gpg'

File "/tmp/update-manager-7Dx7PT/DistUpgradeController.py", line 374,
in prepare
self._sshMagic()

File "/tmp/update-manager-7Dx7PT/DistUpgradeController.py", line 259,
in _sshMagic
if iptables_active():

File "/tmp/update-manager-7Dx7PT/utils.py", line 411, in
iptables_active
stdout=subprocess.PIPE).communicate()[0]

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

File "/usr/lib/python2.6/subprocess.py", line 1141, in _execute_child
raise child_exception

OSError: [Errno 2] No such file or directory
=== Command detached from window (Wed Jun 8 14:54:35 2011) ===
=== Command terminated with exit status 1 (Wed Jun 8 14:54:35 2011) ===

--------------

This machine did not have iptables installed.
After I installed iptables and re-ran do-release-upgrade, it worked.

[Tully (tully.foote)]

When upgrading from maverick to natty over ssh it crashed and then continued when restarted after an apt-get update. The same thing happened upgrading from natty to oneiric. I'm not sure if the update fixed anything but the 2nd time updating before hand didn't fix it. Just rerunning it worked the 2nd time.

Below is the console output and the log files asked for in the error.

root@jenkins-test:~# sudo do-release-upgrade -d
Checking for a new ubuntu release
Get:1 Upgrade tool signature [198 B]
Get:2 Upgrade tool [1164 kB]
Fetched 1164 kB in 0s (0 B/s)
authenticate 'oneiric.tar.gz' against 'oneiric.tar.gz.gpg'
extracting 'oneiric.tar.gz'

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, an additional ssh daemon will be started at port
'1022'.
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 has aborted.
Your original sources.list was saved in
/etc/apt/sources.list.distUpgrade.

Traceback (most recent call last):

File "/tmp/update-manager-_H3X0f/oneiric", line 7, in <module>
sys.exit(main())

File "/tmp/update-manager-_H3X0f/DistUpgradeMain.py", line 199, in
main
if app.run():

File "/tmp/update-manager-_H3X0f/DistUpgradeController.py", line
1670, in run
return self.fullUpgrade()

File "/tmp/update-manager-_H3X0f/DistUpgradeController.py", line
1526, in fullUpgrade
if not self.prepare():

File "/tmp/update-manager-_H3X0f/DistUpgradeController.py", line 390,
in prepare
self._sshMagic()

File "/tmp/update-manager-_H3X0f/DistUpgradeController.py", line 275,
in _sshMagic
if iptables_active():

File "/tmp/update-manager-_H3X0f/utils.py", line 446, in
iptables_active
stdout=subprocess.PIPE).communicate()[0]

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

File "/usr/lib/python2.7/subprocess.py", line 1213, in _execute_child
raise child_exception

OSError: [Errno 2] No such file or directory

root@jenkins-test:~# cat /var/log/dist-upgrade/main.log
2011-12-12 20:38:13,968 INFO Using config files '['./DistUpgrade.cfg']'
2011-12-12 20:38:13,968 INFO uname information: 'Linux jenkins-test.willowgarage.com 2.6.36-rc8101910 #1 SMP Tue Oct 19 19:18:34 UTC 2010 x86_64'
2011-12-12 20:38:13,968 INFO release-upgrader version '0.152.25' started
2011-12-12 20:38:13,968 INFO screen could not be run
2011-12-12 20:38:13,968 DEBUG Using 'DistUpgradeViewText' view
2011-12-12 20:38:13,998 DEBUG aufsOptionsAndEnvironmentSetup()
2011-12-12 20:38:13,998 DEBUG usi...

[Dev El Cuy (develcuy)]

Pretty old bug but this might help on comment #1, install openssh-server.

In general, the script is not looking for dependencies before running, so it fails on basic installations, like chroots.