# 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](https://support.platform9.com/) 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'.

```bash
$ openstack compute service list
```

* Delete the problematic compute service

```bash
$ 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):

```bash
$ 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.

```bash
$ pcdctl deauthorize-node
```

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

```bash
$ pcdctl authorize-node
```


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://platform9.com/kb/pcd/generic/hypervisor-stuck-in-n-a-scheduling-state-after-host-onboarding.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.