Proxmox: upgrade PVE 1.9 to 2.0
Even though I haven’ t tried any beta version I decided to go ahead and upgrade one of my cluster nodes to version 2.0 of Proxmox virtual environment.
The tricky part would most likely be the customized PVE installation I build; two disks running partially software RAID 1 with the system split in several partitions. That might break the upgrade script provided by Proxmox.
Actually, thing went pretty well so far. The biggest error was that I had previously left open a couple of remove assignments through aptitude which removed the pve kernel, so the script halted on that when it couldn’t find it.
Nothing a reversal to lenny in the sources.list and the install of the missing kernel couldn’t fix.
One thing that didn’t match up was not being able to start cman which complained about missing the nodename in cluster.conf. It was present in /etc/pve/cluster.conf but unfortunately the init script pointed to /etc/cluster/cluster.conf.
Adding the name to the latter conf was enough to start cman and enable me to log into the web interface. That one kept looping and timed out while the cluster deamon wasn’t running.
One thing te remember is that the web interface was listening to the default port again so I had to modify the Listen entry in pve.conf under the /etc/apache/sites directories.
Next is copying the backups from the old master node to the new and import them to see if they’ll run. When they do, the old master will be upgraded after confirming that the new master works as planned.
Just started the upgrade of the second node, so far I only had to do an apt-get install console-tools after an error mentioning that package during the apt-get upgrade round, and an apt-get install vzctl during the second attempt.