> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pcd/generic/hypervisor-stuck-in-n-a-scheduling-state-after-host-onboarding.md).

# 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
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.