nova-client never return when removing floating ip
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
When I run "nova remove-floating-ip <id> <ip>" the command never returns, but it still succeed in actually removing the IP. When the command is interrupted by ctrl+c it prints a traceback
nova remove-floating-ip 142 192.168.10.132
^CTraceback (most recent call last):
File "/usr/bin/nova", line 9, in <module>
load_
File "/usr/lib/
OpenStackCo
File "/usr/lib/
args.
File "/usr/lib/
server.
File "/usr/lib/
self.
File "/usr/lib/
self.
File "/usr/lib/
return self.api.
File "/usr/lib/
return self._cs_
File "/usr/lib/
**kwargs)
File "/usr/lib/
resp, body = super(HTTPClient, self).request(
File "/usr/lib/
(response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey)
File "/usr/lib/
(response, content) = self._conn_
File "/usr/lib/
response = conn.getresponse()
File "/usr/lib/
response.
File "/usr/lib/
version, status, reason = self._read_status()
File "/usr/lib/
line = self.fp.readline()
File "/usr/lib/
data = recv(1)
KeyboardInterrupt
Running Diablo 2011.3.1, with one controller, and three compute nodes. Multi_host and Vlan networking.
It sounds like the nova-network service got stuck? Does e.g. 'nova floating-ip-list' work after you hit Ctrl-C? Is this reproducible?
If you can reproduce, try removing the iptables lock file from your lock_path dir and restart the nova-network service? Does that fix things? If so, we need to figure out why the lock is being leaked
Could you also set verbose=True and attach the network service log file?