Troubleshooting

Troubleshooting

Health updates return 200 but do not affect hosts

This is the most common issue. The module accepts the update, but vCenter does not apply it.

Diagnosis

1. Verify Proactive HA is enabled on the cluster:

Get-PHAConfig -Cluster "DR Cluster"

2. Confirm your provider appears in HealthProviders
3. Check current health updates:

icingacli proactiveha healthupdates list --id <vcenter-id>

Cause

The cluster's Proactive HA configuration does not include your provider for that host. The module intentionally does not enable Proactive HA automatically because it requires Host.Inventory.EditCluster permission.

Fix

Enable in the GUI or run Set-PHAConfig from Williams Lam's PowerCLI library as a vCenter administrator. See Configuration.

Gray status with empty id

A gray status with empty id means vCenter has no provider update for that host. This is expected when:

• Proactive HA is not enabled for the cluster or host
• The provider is not in the cluster's provider list
• No update has been sent yet

SOAP errors

Check the module logs at Proactive HA → Logs. Common causes:

• Incorrect vCenter URL
• SSL certificate verification failure
• Missing permissions
• Provider not registered

Business Process node not found

Ensure the BP config name and node name match exactly, including case.

Pending states never push

1. Check that the worker timer is active:

systemctl status proactiveha-worker.timer
systemctl status proactiveha-worker.service

2. Check proactiveha_log for errors
3. Run the worker manually:

icingacli proactiveha worker run --once

Password in logs

SOAP request logs are sanitized to remove passwords. If you see a password in logs, report it as a security issue.