Hello o/ This reminds me of an "edge case” I stumbled on recently. In Nova it raises a PortInUse exception in the neutron network driver if the device_id on a port that you try to use for an instance is still set [1]. I proposed —device and —device-id to the `openstack port unset` command [2]. You could try removing/unsetting the device ID on the port. Not sure about the permission issue, one issue we’ve seen when trying to move our service users to not have the admin role is that the service role did not have permissions to create/update the device_id field on ports, that was fixed with [3]. /Tobias [1] https://github.com/openstack/nova/blob/a1c47fc242b6002d2be60fc41176ce29d19d9... [2] https://review.opendev.org/c/openstack/python-openstackclient/+/944130 [3] https://review.opendev.org/c/openstack/neutron/+/947003 On 3 Jun 2025, at 14:10, Eugen Block <eblock@nde.ag> wrote: Hello again, this is version Caracal, recently upgraded from Antelope. We're currently facing an issue with pre-created ports. This used to work just fine for years, now we have to delete the port, recreate it and try again. For example, we launch an instance with a pre-created port, notice that something is wrong and delete the instance. Previously, we could just launch a new instance and use the same port-id, but now we get this error: # openstack server create --image <image> --flavor 1 --port d10298ea-6dd9-40af-af7e-507f4d83a8cf test-port4 Port d10298ea-6dd9-40af-af7e-507f4d83a8cf is still in use. (HTTP 409) (Request-ID: req-e6cef8b4-d8af-4312-852b-d44ec92cf27a) I noticed that the device_id was still pointing to the previous instance, so I tried a couple of things to clear the port state, but to no avail. I tried: - openstack port set --device None d10298ea-6dd9-40af-af7e-507f4d83a8cf - openstack port set --device "" d10298ea-6dd9-40af-af7e-507f4d83a8cf and a couple of more set commands. I also don't see any option for port creation to allow reusing a pre-created port. Am I missing something? Thanks! Eugen