Proxmox3 Upgrades

[adamb]

We have some clusters that we are finally getting a change to get upgraded from prox3 -> prox5.

However, when attempting to update any of them to the latest proxmox3, it seems the debian wheezy links are gone?

Err http://ftp.us.debian.org wheezy/main amd64 Packages
404 Not Found [IP: 64.50.236.52 80]
Err http://ftp.us.debian.org wheezy/contrib amd64 Packages
404 Not Found [IP: 64.50.236.52 80]
Fetched 198 B in 5s (33 B/s)
W: Failed to fetch http://ftp.us.debian.org/debian/dists/wheezy/main/binary-amd64/Packages 404 Not Found [IP: 64.50.236.52 80]
W: Failed to fetch http://ftp.us.debian.org/debian/dists/wheezy/contrib/binary-amd64/Packages 404 Not Found [IP: 64.50.236.52 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.

Sure enough, I am not seeing a wheezy directory anymore. Any ideas on how to get around this?

http://ftp.us.debian.org/debian/dists/

 

[mira]

It would probably be best if you were to backup everything, install PVE 5 somewhere and restore all your VMs.
If you have OpenVZ containers see here for information on how to convert them to LXC: https://pve.proxmox.com/wiki/Convert_OpenVZ_to_LXC

 

[adamb]

It would probably be best if you were to backup everything, install PVE 5 somewhere and restore all your VMs.
If you have OpenVZ containers see here for information on how to convert them to LXC: https://pve.proxmox.com/wiki/Convert_OpenVZ_to_LXC

In a perfect world that would be the plan, but these are remote clusters that would require complete forklift upgrades to do that. I have a real solid process of upgrading these cluster from prox3 -> prox5 and have been doing so with no issues. However, if I don't have access to the latest wheezy packages, that is going to be an issue.

 

[rhonda]

Debian archives outdated releases to http://archive.debian.org/debian/ - so you can pull it from there.

One sidenote though: Debian doesn't support skipping releases. So you would have to upgrade from wheezy to jessie first (and pve 4) instead of going directly to stretch and pve 5. Doing the latter you will very likely stumble into different issues, and supporting skipping releases is nothing you will very likely receive a helping hand with. There are library transitions in between and other stuff that drop intermediate workarounds, so you are mostly on your own with that approach.

 

[adamb]

Debian archives outdated releases to http://archive.debian.org/debian/ - so you can pull it from there.

One sidenote though: Debian doesn't support skipping releases. So you would have to upgrade from wheezy to jessie first (and pve 4) instead of going directly to stretch and pve 5. Doing the latter you will very likely stumble into different issues, and supporting skipping releases is nothing you will very likely receive a helping hand with. There are library transitions in between and other stuff that drop intermediate workarounds, so you are mostly on your own with that approach.

I have done a number of clusters in this fashion with no issues. I go from prox3 -> prox4 -> prox5. So far I have done roughly 6 clusters without a single hitch and they have been running rock solid for 6+ months. They were even drbd clusters and I kept all the data intact as well.

I did try going from prox3 -> prox5 but ran into all kinds of issues as you described.

 

[oguz]

I go from prox3 -> prox4 -> prox5

Keep in mind that the update instructions from Proxmox 4.x to 5.0 have been edited recently, to avoid a problem with zfs and systemd:
https://pve.proxmox.com/wiki/Upgrade_from_4.x_to_5.0

 

[adamb]

Keep in mind that the update instructions from Proxmox 4.x to 5.0 have been edited recently, to avoid a problem with zfs and systemd:
https://pve.proxmox.com/wiki/Upgrade_from_4.x_to_5.0

Appreciate the heads up. I will add this to my documentation as well.