zonca / jupyterhub-deploy-kubernetes-jetstream

Configuration files for my tutorials on deploying JupyterHub on top of Kubernetes on XSEDE Jetstream (Openstack)
https://zonca.dev/categories/#jetstream
23 stars 14 forks source link

Cannot delete subnet, ports #62

Closed zonca closed 1 year ago

zonca commented 1 year ago

I have been experimenting with terraform, I got into a configuration where there is no way to delete a subnet.

The subnet id is:

3d7e56ed-6e7b-4efc-9948-1e285fbbfe9c

@zacharygraber

zonca commented 1 year ago
o port list | grep 3d7
| 4c86c134-29bd-4d07-92d1-08200794f06d |      | fa:16:3e:e6:34:64 | ip_address='10.1.28.227', subnet_id='3d7e56ed-6e7b-4efc-9948-1e285fbbfe9c' | ACTIVE |
| 89e9f501-ab43-4062-a77c-bb14c89ae66b |      | fa:16:3e:ac:8d:55 | ip_address='10.1.28.2', subnet_id='3d7e56ed-6e7b-4efc-9948-1e285fbbfe9c'   | ACTIVE |
zonca commented 1 year ago

I can delete 1 of the ports, but it is automatically re-created, not sure by what.

zacharygraber commented 1 year ago

I can delete 1 of the ports, but it is automatically re-created, not sure by what.

Which one?

zonca commented 1 year ago

I deleted 89e9f501-ab43-4062-a77c-bb14c89ae66b

zonca commented 1 year ago

and now there is another one:

o port list | grep 3d7
| 4c86c134-29bd-4d07-92d1-08200794f06d |      | fa:16:3e:e6:34:64 | ip_address='10.1.28.227', subnet_id='3d7e56ed-6e7b-4efc-9948-1e285fbbfe9c' | ACTIVE |
| c6147875-6b77-47f5-9e7d-cf2612ac9b0d |      | fa:16:3e:b2:d7:82 | ip_address='10.1.28.2', subnet_id='3d7e56ed-6e7b-4efc-9948-1e285fbbfe9c'   | ACTIVE |
zonca commented 1 year ago

I would like just everything deleted, subnet and all ports

zacharygraber commented 1 year ago

Openstack won't let us delete the subnet because of this port existing:

image

4c86... is on the subnet, by it's owned by router_centralized_snat, and ports owned by that disallow any edits. I'm going to check with some folks about this.

zonca commented 1 year ago

I noticed that there was also a load balancer resource created not sure by what process. I deleted that manually in Horizon. I'm wondering if it could be related.

zacharygraber commented 1 year ago

The solution ended up being openstack router unset --external-gateway 15cc195f-02d4-4d9b-ae24-5b2e9e52a13a which got rid of the offending port(s) and let us delete the subnet.

zonca commented 1 year ago

great, thanks! I'll do it myself if it happens again!