pve-upgrade-2.3-to-3.0 fails with a dist-upgrade failed

[keyjey]

Hi, I'm trying to upgrade a proxmox 2.3 to 3.0 and there's something wrong in my system it fails and now I'm stuck without any version working, I mean the only VM is working but apache doesn't work now and pveversion is not existing anymore...

This is the last lines of the upgrade:

Setting up libpam-runtime (1.1.3-9) ...(Reading database ... 43542 files and directories currently installed.)
Preparing to replace cron 3.0pl1-116 (using .../cron_3.0pl1-124_amd64.deb) ...
/etc/environment has been deprecated for locale information; use /etc/default/locale for LANG=en_GB.UTF-8 instead ... (warning).
Stopping periodic command scheduler: cron.
Moving obsolete conffile /etc/cron.daily/standard out of the way...
Unpacking replacement cron ...
Preparing to replace install-info 4.13a.dfsg.1-6 (using .../install-info_5.1.dfsg.1-3_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/install-info_5.1.dfsg.1-3_amd64.deb (--unpack):
 triggers ci file contains unknown directive `interest-noawait'
configured to not write apport reports
Processing triggers for man-db ...
Errors were encountered while processing:
 /var/cache/apt/archives/install-info_5.1.dfsg.1-3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
dist-upgrade failed

Any tip ?

Thanks

 

[keyjey]

Also:

root@srv:~/files# pveversion -v
-bash: pveversion: command not found

 

[jleg]

Hi, I'm trying to upgrade a proxmox 2.3 to 3.0 and there's something wrong in my system it fails and now I'm stuck without any version working, I mean the only VM is working but apache doesn't work now and pveversion is not existing anymore...

This is the last lines of the upgrade:

Setting up libpam-runtime (1.1.3-9) ...(Reading database ... 43542 files and directories currently installed.)
Preparing to replace cron 3.0pl1-116 (using .../cron_3.0pl1-124_amd64.deb) ...
/etc/environment has been deprecated for locale information; use /etc/default/locale for LANG=en_GB.UTF-8 instead ... (warning).
Stopping periodic command scheduler: cron.
Moving obsolete conffile /etc/cron.daily/standard out of the way...
Unpacking replacement cron ...
Preparing to replace install-info 4.13a.dfsg.1-6 (using .../install-info_5.1.dfsg.1-3_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/install-info_5.1.dfsg.1-3_amd64.deb (--unpack):
 triggers ci file contains unknown directive `interest-noawait'
configured to not write apport reports
Processing triggers for man-db ...
Errors were encountered while processing:
 /var/cache/apt/archives/install-info_5.1.dfsg.1-3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
dist-upgrade failed

Any tip ?

Thanks

i'd try an "aptitude clean" - and just restart the upgrade script. I also upgraded a few installations this way - not a single one went through without errors, but all were successful at the end, after some fix/restart iterations.

 

[keyjey]

Done, but same error ....

 

[jleg]

Done, but same error ....

does an "aptitude install dpkg" work? looks like as if that's still the old version...
with dpkg version 1.16.x, that "unknown directive" should disappear.

 

[keyjey]

Now worked better, but stuck in here:

The following information may help to resolve the situation:


The following packages have unmet dependencies:
 proxmox-ve-2.6.32 : Depends: pve-manager but it is not going to be installed
                     Depends: qemu-server but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
install failed at ./pve-upgrade-2.3-to-3.0 line 263, <TMP> line 1361.

Argh ....

 

[tom]

post your /etc/hosts

 

[keyjey]

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
18.217.66.183 la03.domain.com la03
18.217.201.85 la0.domain.com la0
# The following lines are desirable for IPv6 capable hosts
#(added automatically by netbase upgrade)
::1 ip6-localhost ip6-loopback
feo0::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

 

[keyjey]

Hi .... any tip please ?

Thanks in advance.

 

[qstraza]

I had similar problems yesterday while upgrading from 2.3 to 3.1.

First node went great, I did not run
./pve-upgrade-2.3-to-3.0 --purge

at the end.

On the second node also everything went smooth, then I ran

./pve-upgrade-2.3-to-3.0 --purge

And it delete all of my CTs (on this node), it also removed a lot of binaries, such as vzlist, pveversion... All of them gone.

So I downloaded 3.1 iso and installed from scratch and restored from backup.

No more purging for me.