Network Management
Adding a Proxmox Cluster Hangs on step 2 if a Cluster Member Is Offline in SolarWinds Platform
Proxmox Cluster enrollment can hang at step 2 if any cluster member is offline during discovery.
First published date
Last published date
Overview
When adding a Proxmox environment from Add a Virtual Object for Monitoring, the authentication step may complete successfully, but the next step that polls the environment may not finish.
In this scenario, the wizard appears to hang and the Proxmox environment is not added successfully.
SolarWinds supports monitoring Proxmox clusters, and adding a single Proxmox node causes the rest of the nodes in that Proxmox VE environment to be discovered and added automatically.
Product section
Cause
The issue occurs because the Proxmox add workflow depends on discovering the full cluster during the environment polling stage.
Proxmox API works in a way that when you poll data from, e.g:
HTTPS://HOST1:8006/API/NODE/HOST3/QEMU/ -> so list of VMs for HOST3 (offline), but using the IP of the cluster or host1, it still polls data from HOST3.
If one of the hosts (e.g HOST3) that belongs to the Proxmox cluster is offline at that time, the wizard can remain stuck during discovery and does not complete successfully.
This behavior is consistent with the cluster-based Proxmox enrollment flow in SolarWinds.
Resolution
It is not possible to add a Proxmox Cluster if a Host is offline. Verify that the target Proxmox environment is configured and reachable as a cluster.
Confirm that all hosts in the cluster are online before starting the add process.
Retry adding the Proxmox environment from the SolarWinds Web Console.
If the add previously failed and left stale virtualization data behind, verify whether the failed cluster entry still exists and clean up the orphaned entry before re-adding, if required.
After the offline cluster member is brought back online, retrying the add operation should allow the Proxmox cluster discovery to complete successfully.