Unable to Assign Fixed IP While Creating Port
PreviousNo Valid Host From Host Aggregates Resulted in Instance Spawning FailureNextInstances Lose External Connectivity After Detaching Floating IP
Last updated
When trying to assign a fixed IP to a port using Clarity UI, an error saying "Invalid or out-of-range IP address" is observed.
Platform9 Managed OpenStack - v3.6.0 and Higher
Neutron
The allocation pool mentioned within the subnet is entered incorrectly.
Login to the Clarity UI and navigate to the "Networks" tab.
Click on the Network name in which the port is to be created.
Navigate to the "Subnets" section.
Check the allocation pool corresponding to the subnet in which the port is to be created.
If the allocation range covers 2 subnets as shown below, split the allocation pool into two. One for each subnet.
After updating the allocation pool, it should look like this.
Last updated
10.195.2.150 - 10.195.3.5010.195.2.2 - 10.195.2.25410.195.3.2 - 10.195.3.150