Search results

Another update to my quest for GLORY! Turns out the Prod node 1, which was a install from scratch 5.0 in our last episode, had a few packages to update. I updated them, and now have the bond0 LACP working. I don't think I did anything special. Apt update, apt upgrade, install presented packages...

Another bit of info. Prod node 2, upgraded from 4.4 to 5.0, keeps the old eth0/eth1 interface naming, and it has the /etc/udev/rules.d/70-persistent-net.rules file Prod node 1, reinstalled from scratch 5.0 release, has the "new" renaming of interfaces to enp4s0 or whatever, and I manually...

Okay so the node I upgraded from 4.4 to 5.0 has ifconfig but the node I rebuilt from scratch 5.0 does not have ifconfig... what.. the hell... :( EDIT: fresh installs do not get the package "net-tools", but upgraded ones retain it. This is how I got my precious ifconfig back.

BTW I'm loving the little nuanced GUI improvements, like: Shift click to select multiple VMs during migration. This is really convenient! (should be documented so others know) Right click on nodes in the left list to issue node-centric commands, like mass migrate. Colourising of the logs and...

I was upgrading the whole cluster, which consisted of two nodes that operate 24/7, two nodes that are turned on for labbing purposes, then turned off when not needed (due to their power inefficiencies and loudness). All nodes were previously 4.4 with the latest updates. I upgraded the lab nodes...

I googled the snot out of the error, and likely found a bunch of results you did too. Unfortunately what I found did not help at all. I tried doing very drastic stuff including rebooting the switch, reconfiguring the ports, switching which ports are used on the switch in the LACP bond...

You're not bad at all! I think you sufficiently explained your situation :) Nice! :D Perhaps reconsider ZFS in the future, but I understand your hesitation.

Did you have any LACP going on? Live migration between nodes during upgrade did not work for me at all :( (but might have been due to... other... issues as my notes above outline).

This issue is current for proxmox 5.0, as I'm using a monitor that has a max res of 1280x1024, and what I assume to be the grub menu for the USB stick is out of range or something like that. Hitting enter boots into the installer. Thanks for this!

I just upgraded the cluster, and the last node, I was able to live migrate a bunch of VMs on it, but now I can't migrate them off it. No matter what node it tries to migrate to I get: ERROR: migration aborted (duration 00:00:01): Can't connect to destination address using public key EXCEPT it...

I'm in the process of upgrading an environment I work with from 4.4 to 5.0, and I just tried migrating a test VM from a 4.4 box to 5.0, as in live migration, and it seems to fail every time. :/ It looks like this version upgrade might be one of those ones where you will experience downtime, but...

THIS is definitely something that NEEDS TO BE DOCUMENTED.

Oh, and I'm ever so glad that we can import VMs from other hypervisors now! That came faster than I thought :D Hopefully we can also get export too at some point, so that I can do all kinds of tasty stuff with that. But that's another day ;)

Upgrade instructions don't talk about 4.x -> 5.0 :( only 5.x -> 5.0 and 5.0beta -> 5.0 What do I need to do to upgrade from 4.4 to 5.0? I'm talking about this page : https://pve.proxmox.com/wiki/Downloads edit: seems there's a page for this (...