Hypervisor Stuck in N/A Scheduling State After Host Onboarding

Problem

• Host remains in N/A and scheduling state in the UI.

• The command openstack compute service list shows the host as “down”.

Environment

• Private Cloud Director Virtualization

• Self-Hosted Private Cloud Director Virtualization

Cause:

• Reach out to the Platform9 Support Team for assistance to figure out the cause as during the report of this issue, the cause was unknown.

Workaround

• Identify the host using the below command and confirm that it is marked as 'Down'.

$ openstack compute service list

• Delete the problematic compute service

$ openstack compute service delete <COMPUTE_SERVICE_ID>

• Reset the compute_id on the affected host through below steps (To be performed on the affected host):

$ cat /opt/pf9/data/state/compute_id  <--note this ID
$ cp /opt/pf9/data/state/compute_id /tmp/compute_id_bkp
$ rm /opt/pf9/data/state/compute_id

• Deauthorize the node using UI or CLI.

$ pcdctl deauthorize-node

• Re-authorize the hypervisor role and wait for successful onboarding.

$ pcdctl authorize-node