scripted update from 2.3 to 3.0 ended with latest 3.1 ?

m.ardito

Active Member
Feb 17, 2010
1,473
14
38
Torino, Italy
I just updated another old 2.1 node, by documented steps:
- first to latest 2.3
- then running the script as http://pve.proxmox.com/wiki/Upgrade_from_2.3_to_3.0

but, after rebooting, I had a full 3.1 !! I did this nearly a week ago on another 2.1 node, but the same procedure ended in a 3.0, like pve-manager/3.0/957f0862...
and then I am sure had to follow the procedure http://pve.proxmox.com/wiki/Downloads#Update_a_running_Proxmox_Virtual_Environment_3.x_to_latest_3.1

but on the latest updated node i still have

Code:
root@pve1:~# cat /etc/apt//sources.list
deb http://ftp.it.debian.org/debian wheezy main contrib

# PVE packages provided by proxmox.com
deb http://download.proxmox.com/debian wheezy pve

# security updates
deb http://security.debian.org/ wheezy/updates main contrib

so not the new repositories... ?!?

now I have on both nodes (double checked)
Code:
root@pve1:~# pveversion -v
proxmox-ve-2.6.32: 3.1-114 (running kernel: 2.6.32-26-pve)
pve-manager: 3.1-21 (running version: 3.1-21/93bf03d4)
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-11-pve: 2.6.32-66
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-2
pve-cluster: 3.0-8
qemu-server: 3.1-8
pve-firmware: 1.0-23
libpve-common-perl: 3.0-8
libpve-access-control: 3.0-7
libpve-storage-perl: 3.0-17
pve-libspice-server1: 0.12.4-2
vncterm: 1.1-4
vzctl: 4.0-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-17
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.1-1
root@pve1:~# cat /etc/apt//sources.list
deb [URL]http://ftp.it.debian.org/debian[/URL] wheezy main contrib

is this expected, should the wiki be updated (I can contribute if needed) or what?!?

Marco
 

BenHippynet

New Member
Jan 24, 2013
5
0
1
If upgrading from v2.3 to the newest version is it best to use this method then upgrade again to the latest?
 

m.ardito

Active Member
Feb 17, 2010
1,473
14
38
Torino, Italy
If upgrading from v2.3 to the newest version is it best to use this method then upgrade again to the latest?

Hi,
it could even work, but since now latest is 5.x (!) there could well be the chance that something can go wrong, or be painful in the full path 2.x > 3.x > 4.x > 5.x : too many things have changed, and you 2.x hardware could be quite old, and may lack support for something in the newest versions (kernels, drivers).

If you wish to reach 5.x, and if you have 2.x cluster with a few nodes, maybe try the easiest (and faster, safer) path, if you can, eg:, migrate VMs from one node, and keep 2.x working, on other nodes.

Then, on that node, test a new install of 5.x on your hardware: backup and restore VMs from 2.x and test each different VM. If all test are good, you can save time, avoid 2.x > 3.x > 4.x > 5.x upgrade, and after a full, working backup go for a fresh 5.x cluster install, and restore all. I would try this, if possible.

Anyway, iven if going for the 2.x > 3.x > 4.x > 5.x upgrade, I would test that before on reference (old) hardware.

Don't do anything this directly on production!
 

BenHippynet

New Member
Jan 24, 2013
5
0
1
Thanks for the advice, I think it's best to take the safe route! Unfortunately the machine isn't in a cluster so I can't migrate....I'll have to factor in a longer downtime window. To be safe I'll swap in a fresh hard disk and install 5.x, then if there are problems I can just swap back in the old drives.

Will a back up of an OpenVZ VM from v2.3 resotre okay in Proxmox v5.x?
 

m.ardito

Active Member
Feb 17, 2010
1,473
14
38
Torino, Italy
Will a back up of an OpenVZ VM from v2.3 resotre okay in Proxmox v5.x?

The "current" .vma format was introduced in 2.3 so I guess you just need to have them in that format.
see https://pve.proxmox.com/wiki/VMA

You could also create a VM on your 2.3 running the 5.x, and check if they are still compatible and all (just restore them and maybe run them off network or on a test network)

If you have openvz containers, though, you'll need to convert them to the new container format used since 4.x, LXC
see https://pve.proxmox.com/wiki/Convert_OpenVZ_to_LXC
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!