> 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/networking/vm-creation-fails-with-no-avaiiable-ip.md).

# VM Creation Fails with No AvaiIable IP

### Problem <a href="#problem" id="problem"></a>

Unable to create a VM on a subnet because the UI reports **no available IPs**, even though the allocation pool still has free addresses.

### Environment <a href="#environment" id="environment"></a>

* Private Cloud Director Virtualization - till v2026.1-360
* Private Cloud Director Kubernetes – till v2026.1-360
* Self-Hosted Private Cloud Director Virtualization - till v2026.1-360
* Self-Hosted Private Cloud Director Kubernetes - till v2026.1-360
* Component: Networking Service

### Cause <a href="#cause" id="cause"></a>

The issue is caused by incorrect IP availability calculation. The system subtracts all used addresses in the subnet (including those outside the allocation pool) instead of only considering addresses within the defined allocation pool. This is a known bug tracked PCD-3647 and fix is available from **v2026.1-360 and above**

### Diagnostics <a href="#diagnostics" id="diagnostics"></a>

1. Check subnet details and allocation pool configuration. Look for **allocation\_pools** field and confirm the defined IP range.

   ```bash
   openstack subnet list --long 
   openstack subnet show <SUBNET_ID>
   ```
2. List all ports and IPs allocated in the subnet.Compare allocated IPs with allocation pool; verify how many pool IPs are actually in use.

   ```bash
   openstack port list --fixed-ip subnet=<SUBNET_ID> -c ID -c Fixed_IPs -c Device_ID
   ```
3. Verify mismatch in UI:
   1. In the **UI → Network & Security → Physical/Virtual Networks→ Subnets**, check the **Available IPs** field.
   2. Compare UI’s reported value (e.g., 0 or negative) against the manual calculation.

<figure><img src="/files/WQd9DU2l09qw4tAWvJvR" alt=""><figcaption></figcaption></figure>

### Workaround <a href="#workaround" id="workaround"></a>

Since the UI incorrectly reports available IPs, create VMs directly from the CLI using a free IP from the allocation pool.

```
openstack server create \
  --flavor <FLAVOR_ID> \
  --image <IMAGE_ID> \
  --nic net-id=<NETWORK_ID>,v4-fixed-ip=<FREE_IP> \
  --security-group <SECURITY_GROUP_ID> \
  --key-name <KEYNAME> \
   --availability-zone <CLUSTER_NAME> \
  <VM_NAME>
```


---

# 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 dynamically by asking a question.

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

```
GET https://platform9.com/kb/pcd/networking/vm-creation-fails-with-no-avaiiable-ip.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.