strange debian upgrade issue. Stuck on 5.0.3

M

msmart

New Member
Jun 24, 2010
10
0
1
Guys,
I am installing PVE on a third node in my blade enclosure (identical hardware in all blades). I have it loaded and basic configuration done and have also upgraded to the 32 branch of the kernel. Same steps as the first 2 nodes.

When I cat /etc/debian_version on nodes 1 and 2 it prints 5.0.4 but node 3 prints 5.0.3

I have rebooted and tried aptitude update, upgrade, and safe-upgrade to no avail. This third node will not upgrade to 5.0.4. Any ideas?

Here is my pveversion and I have confirmed it is identical amongst the nodes:
pve-manager: 1.5-9 (pve-manager/1.5/4728)
running kernel: 2.6.32-2-pve
proxmox-ve-2.6.32: 1.5-7
pve-kernel-2.6.32-2-pve: 2.6.32-7
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-14
pve-firmware: 1.0-5
libpve-storage-perl: 1.0-13
vncterm: 0.9-2
vzctl: 3.0.23-1pve11
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.4-1
ksm-control-daemon: 1.0-3


Thanks,
Matt
 
sources.list are identical on all three nodes

After aptitude install lsb-release (step included for posterity).

Nodes 1 and 2 lsb_release -a returns:
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 5.0.4 (lenny)
Release: 5.0.4
Codename: lenny

Node 3 lsb_release -a returns:
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 5.0.3 (lenny)
Release: 5.0.3
Codename: lenny


Just strange that I followed the exact same install process on all three servers. I am somewhat unfamiliar with Debian. I assume that aptitude upgrade (have tried safe and full) should take me from 5.0.3 to 5.0.4?

Wouldn't be a huge deal but corosync is complaining about the version difference and I am trying to finish my manual HA setup so I can start helping Dietmar with HA in V2. Once I get a 3 node cluster running HA into production on 1.5, I will be in a position to help get HA in V2.

Thanks for the quick response. God I love this product.
 
Yeah I tried that too. Just weird. Tried again today and it pulled a couple updates from the pve server (qemu-server and pve-manager). But still at 5.0.3.

Unless you can think of anything else to check and since this is a newly loaded server I am gonna just do a reinstall. That way maybe I can get some additional debug info from the initial upgrade after install. I only waited this long because it appears that whatever the issue is only occurs at most 33% of the time and the odds are the issue will not recur after reload. I hate to leave an intermittent issue that we have a test case for undiagnosed.
 
post your sources.list - any pinning used in apt config, e.g. for using lenny-backports?
 
So I start work today by trying the standard update and upgrade process once more before I reload and the server updates to 5.0.5 without any issues. All of my nodes are now on 5.0.5. I am going to load a fourth server with the iso and see if I have the same issue.

Maybe there is some temporal variable that keeps apt from checking for an upgrade for a certain period of time since the last one or something? I will let you know if the 4th node exhibits the same behavior and if so will post the info Tom requested from that server.

Thanks,
Matt
 
You must log in or register to reply here.
Top Bottom