But it is visible AFAICS.
But it's not possible to delete it with regular user rights:
Failed to delete port with name or ID '3258ebd9-2be4-4cf9-a110-c619906708ec': ConflictException: 409: Client Error for url: http://51.89.5.207:9696/v2.0/ports/3258ebd9-2be4-4cf9-a110-c619906708ec, Port 3258ebd9-2be4-4cf9-a110-c619906708ec cannot be deleted directly via the port API: has device owner network:router_centralized_snat.
1 of 1 ports failed to delete.
For me this is quite the same as a network:router_interface_distributed port, which is also not possible to delete.
I also dont think we should hide it from user, as the port is using an IP from the subnet pool, just like DHCP agent is doing. If we hide it, then is a chance the user think the IP is 'free'.
But it is visible AFAICS.
But it's not possible to delete it with regular user rights:
Failed to delete port with name or ID '3258ebd9- 2be4-4cf9- a110-c619906708 ec': ConflictException: 409: Client Error for url: http:// 51.89.5. 207:9696/ v2.0/ports/ 3258ebd9- 2be4-4cf9- a110-c619906708 ec, Port 3258ebd9- 2be4-4cf9- a110-c619906708 ec cannot be deleted directly via the port API: has device owner network: router_ centralized_ snat.
1 of 1 ports failed to delete.
For me this is quite the same as a network: router_ interface_ distributed port, which is also not possible to delete.
I also dont think we should hide it from user, as the port is using an IP from the subnet pool, just like DHCP agent is doing. If we hide it, then is a chance the user think the IP is 'free'.