Upgrade to ProxmoxVE v8 Issue

[mnyawo]

Please advise I am new to Proxmox.

We have an environment with three cluster nodes(a,b,c) running on:
- Proxmox VE v7 (no-subscription repository)
- Debian 11
- Ceph Pacific v16.2.15

With a lack of full understanding of how Proxmox and the Ceph world operate, I tried upgrading cluster node-c (Test Environment) to Proxmox VE v8, Ceph Quincy and Debian 12 using the generic guide provided https://pve.proxmox.com/wiki/Upgrade_from_7_to_8.

However, I experienced an issue, the node failed to come up after rebooting into the updated packages and it entered into a quorum state where it is currently offline and inaccessible in the pve-manager. Node-c current state (Proxmox Version: 8.2, Ceph: 16.2.11 and Debian 12 )

I am seeking guidance on how to bring the node back online in a safe method without breaking the cluster and other nodes, as well as the best practice/s to upgrade.

I have attached the cluster Ceph status.

 

[mira]

However, I experienced an issue, the node failed to come up after rebooting into the updated packages and it entered into a quorum state where it is currently offline and inaccessible in the pve-manager. Node-c current state (Proxmox Version: 8.2, Ceph: 16.2.11 and Debian 12 )

Is it not booting at all, or is it just the lack of quorum?

Could you provide the journal of Node-c since the last boot?
journalctl -b > journal.txt
Please attach the resulting file `journal.txt` here.

Did you see https://pve.proxmox.com/wiki/Upgrade_from_7_to_8#Network_Interface_Name_Change ?
Could it be that some interfaces were renamed?