tmetsch
commented
10 years ago Is this still the behavior openstack shows? If so we can setup some if-else clauses to deal with it I guess
Open bhagemeier opened 10 years ago
tmetsch
commented
10 years ago Is this still the behavior openstack shows? If so we can setup some if-else clauses to deal with it I guess
bhagemeier
commented
10 years ago Hi Thijs,
we have deactivated auto-assigned floating IPs as our client can now assign them explicitly. Unassigning floating IPs is even impossible from nova, so maybe we should not be concerned about this issue. It just seemed weird that I can only delete a VM through OCCI once I've failed to delete it's floating IP. If you agree we can close this issue, as I am not particularly fond of auto-assigned floating IPs anyhow, and because of the above.
Cheers, Björn
On 09.01.2014 11:49, tmetsch wrote :
Is this still the behavior openstack shows? If so we can setup some if-else clauses to deal with it I guess
— Reply to this email directly or view it on GitHub https://github.com/tmetsch/occi-os/issues/69#issuecomment-31919760.
Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Due to interoperability issues with other OCCI implementations, we have enable automatic assignment of floating IPs to our instances. This leads to the following problem:
1) create VM 2) delete VM fails because of the auto-assigned floating IP
2013-10-10 15:20:33.248 INFO nova.occiapi.wsgi.server [req-7a2c63f6-1089-4a78-885c-6f2f04ff46fd ridGermany/OU=Forschungszentrum Juelich GmbH/CN=Bjoern Hagemeier df37f5b1ebc94604964c2854b9c0551f] 134.94.168.82,127.0.0.1 "DELETE /compute/7b1ea357-aa52-4774-a554-ecd690883daf HTTP/1.0" status: 400 len: 220 time: 0.2978840
This is what the client receives in the response body:
<- "DELETE /compute/ecd49c64-dbf1-40bd-b351-45e0c88a48b1 HTTP/1.1\r\nAccept: text/plain,text/occi\r\nUser-Agent: rOCCI HTTPClient 4.1.0\r\nX-Auth-Token: *****\r\nConnection: close\r\nHost: egi-cloud.zam.kfa-juelich.de:8787\r\n\r\n" -> "HTTP/1.1 400 Bad Request\r\n" -> "Date: Thu, 10 Oct 2013 13:26:39 GMT\r\n" -> "Server: pyssf OCCI/1.1\r\n" -> "Content-Length: 46\r\n" -> "Content-Type: text/plain\r\n" -> "Vary: Accept-Encoding\r\n" -> "Connection: close\r\n" -> "\r\n" reading 46 bytes... -> "" -> "Cannot disassociate auto assigined floating ip"
1) create VM 2) delete auto-assigned floating IP link
2013-10-10 15:22:31.138 INFO nova.occiapi.wsgi.server [req-57f1904a-e9f7-4e43-b1b4-c52a7f187740 ridGermany/OU=Forschungszentrum Juelich GmbH/CN=Bjoern Hagemeier df37f5b1ebc94604964c2854b9c0551f] 134.94.168.82,127.0.0.1 "DELETE /network/interface/bbc1b1fe-aca5-4f30-8cbb-12f36af9a163 HTTP/1.0" status: 400 len: 220 time: 0.3253710
<- "DELETE /network/interface/545f8ecb-bac0-4b11-899c-b4e78eb93ce0 HTTP/1.1\r\nAccept: text/plain,text/occi\r\nUser-Agent: rOCCI HTTPClient 4.1.0\r\nX-Auth-Token: *****\r\nConnection: close\r\nHost: egi-cloud.zam.kfa-juelich.de:8787\r\n\r\n" -> "HTTP/1.1 400 Bad Request\r\n" -> "Date: Thu, 10 Oct 2013 13:28:45 GMT\r\n" -> "Server: pyssf OCCI/1.1\r\n" -> "Content-Length: 46\r\n" -> "Content-Type: text/plain\r\n" -> "Vary: Accept-Encoding\r\n" -> "Connection: close\r\n" -> "\r\n" reading 46 bytes... -> "" -> "Cannot disassociate auto assigined floating ip"
3) delete VM SUCCESSFUL 2013-10-10 15:22:33.161 INFO nova.occiapi.wsgi.server [req-c659e1ec-ff34-40b3-9606-dcac15e9dc2c ridGermany/OU=Forschungszentrum Juelich GmbH/CN=Bjoern Hagemeier df37f5b1ebc94604964c2854b9c0551f] 134.94.168.82,127.0.0.1 "DELETE /compute/f0e37ded-e6a2-4361-bd73-c74637a66998 HTTP/1.0" status: 200 len: 146 time: 0.3598518
So, despite the deletion of the networklink being reported as failed, something changed, such that the VM can be deleted afterwards.