unable to use/assign specific fixed IP - reserved_dhcp_port.
haleyb.dev at gmail.com
Mon Dec 14 20:54:40 UTC 2020
On 12/14/20 1:02 PM, lejeczek wrote:
> Hi guys.
> I'm try to spin up and instance:
> $ openstack server create midway --flavor C1.vss.tiny --volume midway
> --nic net-id=fd8659cf-8723-4254-bf88-837b37a50a24,v4-fixed-ip=10.0.0.4
> Fixed IP address 10.0.0.4 is already in use on instance
> reserved_dhcp_port. (HTTP 400) (Request-ID:
> Having no admin access to the stack - how to troubleshoot and ideally
> resolve it before I have to admins demanding action :)
> many thanks, L.
When the device ID is set to "reserved_dhcp_port" someone has done it
manually, so you might be out of luck if you don't have admin rights to
the subnet. And if there are already instances booted on it the DHCP IP
change could cause some connectivity issues (e.g. DNS).
On a related note, if you can create your own subnet, the best way to
make sure an IP is not assigned is by specifying the allocation pool
when you create it, for example:
$ openstack subnet create --network private --subnet-range 10.0.0.0/24
--allocation-pool start=10.0.0.5,end=10.0.0.254 --gateway 10.0.0.1
That way it shouldn't allocate 10.0.0.4 to an instance. Without looking
into the code further I can't remember if the DHCP port has to follow
the allocation pool restrictions though.
More information about the openstack-discuss