Update 5.3 to 5.4

[Curt Hall]

I have 5 Proxmox Nodes in a cluster,somehow I managed to update one to 5.4, the rest are still at 5.3
Now the 5.4 node is orphaned out of the cluster due to version difference I believe. But I have followed the documentation on updating the other nodes but I cannot get them to 5.4. All updates seem to apply but when I check their version they all still say 5.3

 

[Curt Hall]

On a side note, the ultimate goal is to have them all upgraded to 6.x so as to enable Proxmox Backup Server

 

[t.lamprecht]

Major versions are compatible to each other, so every 5.x release should be able to see the other.

How exactly did you update?

Can you please post the output of:
head -1000 /etc/apt/sources.list /etc/apt/sources.list.d/*

 

[t.lamprecht]

And pveversion -v for the nodes affected.

 

[Curt Hall]

All 4 have the same output to both commands:

==> /etc/apt/sources.list <==
deb http://ftp.us.debian.org/debian stretch main contrib

deb http://ftp.us.debian.org/debian stretch-updates main contrib

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

==> /etc/apt/sources.list.d/pve-enterprise.list <==
deb https://enterprise.proxmox.com/debian/pve stretch pve-enterprise


proxmox-ve: 5.3-1 (running kernel: 4.15.18-9-pve)
pve-manager: 5.3-5 (running version: 5.3-5/97ae681d)
pve-kernel-4.15: 5.2-12
pve-kernel-4.15.18-9-pve: 4.15.18-30
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-3
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-43
libpve-guest-common-perl: 2.0-18
libpve-http-server-perl: 2.0-11
libpve-storage-perl: 5.0-33
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-5
lxcfs: 3.0.2-2
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-22
pve-cluster: 5.0-31
pve-container: 2.0-31
pve-docs: 5.3-1
pve-edk2-firmware: 1.20181023-1
pve-firewall: 3.0-16
pve-firmware: 2.0-6
pve-ha-manager: 2.0-5
pve-i18n: 1.0-9
pve-libspice-server1: 0.14.1-1
pve-qemu-kvm: 2.12.1-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-43
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.12-pve1~bpo1

 

[t.lamprecht]

==> /etc/apt/sources.list.d/pve-enterprise.list <==
deb https://enterprise.proxmox.com/debian/pve stretch pve-enterprise

Do you have access (subscriptions) to the enterprise repository?

If not either think about getting some which supports the development of Proxmox projects, or else setup the pve-no-subscription repository for PVE 5.x (stretch):
https://pve.proxmox.com/wiki/Package_Repositories
https://pve.proxmox.com/wiki/Package_Repositories#_proxmox_ve_5_x_repositories

 

[Curt Hall]

I do not have a paid for subscription. Is there a way to make upgrades to existing servers without the paid subscription?
do I simply just add the URL's from the links you provided to the /etc/apt/sources.list.d/pve-enterprise.list file?

 

[t.lamprecht]

do not have a paid for subscription. Is there a way to make upgrades to existing servers without the paid subscription?

Yes, sure is!

do I simply just add the URL's from the links you provided to the /etc/apt/sources.list.d/pve-enterprise.list file?

Yes, that'd work. You can also add it to any other ".list" file, either in the existing /etc/apt/sources.list or a new xyz.list file in the /etc/apt/sources.list.d/ directory.
Just be sure that you use the correct line, in your case now that would be the one from "Proxmox VE 5.x No-Subscription".

 

[t.lamprecht]

On a side note, the ultimate goal is to have them all upgraded to 6.x so as to enable Proxmox Backup Server

Maybe you saw that article already, but here's our official upgrade how-to:
https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0

 

[Curt Hall]

ok, I will do that and rerun the update on the 4 nodes, will let you know.

 

[Curt Hall]

I got them all to 5.4-15

Thanks for the links, as those worked perfectly. (maybe one day we'll pay the money?)

root@NorthProxmox1:~# pveversion -v
proxmox-ve: 5.4-2 (running kernel: 4.15.18-30-pve)
pve-manager: 5.4-15 (running version: 5.4-15/d0ec33c6)

But server 5 is still orphaned in the cluster. If I log into 5 its seems fine except 1-4 is "offline".
If I log into 1, 2, 3, or 4 those are all fine, except they show 5 "offline". (Attached picts)

How do I get Node 5 back in the cluster properly?

 

[Curt Hall]

So I'm logged into Node1, it says its a stand alone node and has no join info (blue circles)
But at the same time you see it and all the other nodes in the "cluster" (red circles)
How is this possible?

 

[t.lamprecht]

How do I get Node 5 back in the cluster properly?

Please post the output of the following three command from one of the working nodes and the failed node.

pvecm status
systemctl status corosync pve-cluster
cat /etc/pve/corosync.conf

I honestly do not think that the upgrade was the cause, as when this happened you did not even had valid repositories configured..
What else was done or happened during the time this node failed?

 

[Curt Hall]

attached zip file has 5 doc's, one for each node. Node 5 failed after a startup from being powered down for a period of time (about a week or 2), the Cluster has been like this ever since. I assumed it was just Node 5 as its version was the only one on 5.4, maybe because it was powered down for an extended period of time?