from:"sark2012"

[Bug 1026621] Re: nova-network gets release_fixed_ip events from someplace, but the database still keeps them associated with instances

2014-03-04 Thread sark2012

** Description changed:

  We've been seeing a lot of instances simply vanish from the network.
  Usually people have been willing to work around this by simply rebooting
  or re-creating their instances, but it's troubling for long-running
  instances (especially those that have volumes associated).
  
  Here's the relevant bit of nova-network.log for one of these:
  
- 2012-07-16 14:06:32 DEBUG nova.rpc.amqp [-] received {u'_context_roles': 
[u'admin'], u'_context_request_id': 
u'req-d0905711-c4d1-4452-a3b2-46815d1983d7', u'_context_read_deleted': u'no', 
u'args': {u'address': u'10.55.60.141'}, u'_context_auth_token': 'SANITIZED', 
u'_context_is_admin': True, u'_context_project_id': None, 
u'_context_timestamp': u'2012-07-16T14:06:32.169100', u'_context_user_id': 
None, u'method': u'release_fixed_ip', u'_context_remote_address': None} from 
(pid=493) _safe_log /usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
- 2012-07-16 14:06:32 DEBUG nova.rpc.amqp 
[req-d0905711-c4d1-4452-a3b2-46815d1983d7 None None] unpacked context: 
{'user_id': None, 'roles': [u'admin'], 'timestamp': 
'2012-07-16T14:06:32.169100', 'auth_token': 'SANITIZED', 'remote_address': 
None, 'is_admin': True, 'request_id': 
u'req-d0905711-c4d1-4452-a3b2-46815d1983d7', 'project_id': None, 
'read_deleted': u'no'} from (pid=493) _safe_log 
/usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
- 2012-07-16 14:06:32 DEBUG nova.network.manager 
[req-d0905711-c4d1-4452-a3b2-46815d1983d7 None None] Released IP |10.55.60.141| 
from (pid=493) release_fixed_ip 
/usr/lib/python2.7/dist-packages/nova/network/manager.py:1260
+ 2012-07-16 14:06:32 DEBUG nova.rpc.amqp [-] received {u'_context_roles': 
[u'admin'], u'_context_request_id': 
u'req-d0905711-c4d1-4452-a3b2-46815d1983d7', u'_context_read_deleted': u'no', 
u'args': {u'address': u'10.55.60.141'}, u'_context_auth_token': 'SANITIZED', 
u'_context_is_admin': True, u'_context_project_id': None, 
u'_context_timestamp': u'2012-07-16T14:06:32.169100', u'_context_user_id': 
None, u'method': u'release_fixed_ip', u'_context_remote_address': None} from 
(pid=493) _safe_log /usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
+ 2012-07-16 14:06:32 DEBUG nova.rpc.amqp 
[req-d0905711-c4d1-4452-a3b2-46815d1983d7 None None] unpacked context: 
{'user_id': None, 'roles': [u'admin'], 'timestamp': 
'2012-07-16T14:06:32.169100', 'auth_token': 'SANITIZED', 'remote_address': 
None, 'is_admin': True, 'request_id': 
u'req-d0905711-c4d1-4452-a3b2-46815d1983d7', 'project_id': None, 
'read_deleted': u'no'} from (pid=493) _safe_log 
/usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
+ 2012-07-16 14:06:32 DEBUG nova.network.manager 
[req-d0905711-c4d1-4452-a3b2-46815d1983d7 None None] Released IP |10.55.60.141| 
from (pid=493) release_fixed_ip 
/usr/lib/python2.7/dist-packages/nova/network/manager.py:1260
  
  Then the dhcpbridge shows it being revoked:
  
- 2012-07-16 14:04:29 DEBUG nova.dhcpbridge [-] Called 'old' for mac 
'fa:16:3e:11:c5:37' with ip '10.55.60.141' from (pid=23699) main 
/usr/bin/nova-dhcpbridge:113
- 2012-07-16 14:06:32 DEBUG nova.dhcpbridge [-] Called 'del' for mac 
'fa:16:3e:11:c5:37' with ip '10.55.60.141' from (pid=24946) main 
/usr/bin/nova-dhcpbridge:113
+ 2012-07-16 14:04:29 DEBUG nova.dhcpbridge [-] Called 'old' for mac 
'fa:16:3e:11:c5:37' with ip '10.55.60.141' from (pid=23699) main 
/usr/bin/nova-dhcpbridge:113
+ 2012-07-16 14:06:32 DEBUG nova.dhcpbridge [-] Called 'del' for mac 
'fa:16:3e:11:c5:37' with ip '10.55.60.141' from (pid=24946) main 
/usr/bin/nova-dhcpbridge:113
  
  Is there any way we can find out what might have placed the
  release_fixed_ip event on the message queue?  There doesn't seeem to be
  any other mention of the IP in the nova logs on any of our systems.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1026621

Title:
  nova-network gets release_fixed_ip events from someplace, but the
  database still keeps them associated with instances

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1026621/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1026621] Re: nova-network gets release_fixed_ip events from someplace, but the database still keeps them associated with instances

2014-03-04 Thread sark2012

** Description changed:

  We've been seeing a lot of instances simply vanish from the network.
  Usually people have been willing to work around this by simply rebooting
  or re-creating their instances, but it's troubling for long-running
  instances (especially those that have volumes associated).
  
  Here's the relevant bit of nova-network.log for one of these:
  
- 2012-07-16 14:06:32 DEBUG nova.rpc.amqp [-] received {u'_context_roles': 
[u'admin'], u'_context_request_id': 
u'req-d0905711-c4d1-4452-a3b2-46815d1983d7', u'_context_read_deleted': u'no', 
u'args': {u'address': u'10.55.60.141'}, u'_context_auth_token': 'SANITIZED', 
u'_context_is_admin': True, u'_context_project_id': None, 
u'_context_timestamp': u'2012-07-16T14:06:32.169100', u'_context_user_id': 
None, u'method': u'release_fixed_ip', u'_context_remote_address': None} from 
(pid=493) _safe_log /usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
- 2012-07-16 14:06:32 DEBUG nova.rpc.amqp 
[req-d0905711-c4d1-4452-a3b2-46815d1983d7 None None] unpacked context: 
{'user_id': None, 'roles': [u'admin'], 'timestamp': 
'2012-07-16T14:06:32.169100', 'auth_token': 'SANITIZED', 'remote_address': 
None, 'is_admin': True, 'request_id': 
u'req-d0905711-c4d1-4452-a3b2-46815d1983d7', 'project_id': None, 
'read_deleted': u'no'} from (pid=493) _safe_log 
/usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
- 2012-07-16 14:06:32 DEBUG nova.network.manager 
[req-d0905711-c4d1-4452-a3b2-46815d1983d7 None None] Released IP |10.55.60.141| 
from (pid=493) release_fixed_ip 
/usr/lib/python2.7/dist-packages/nova/network/manager.py:1260
+ 2012-07-16 14:06:32 DEBUG nova.rpc.amqp [-] received {u'_context_roles': 
[u'admin'], u'_context_request_id': 
u'req-d0905711-c4d1-4452-a3b2-46815d1983d7', u'_context_read_deleted': u'no', 
u'args': {u'address': u'10.55.60.141'}, u'_context_auth_token': 'SANITIZED', 
u'_context_is_admin': True, u'_context_project_id': None, 
u'_context_timestamp': u'2012-07-16T14:06:32.169100', u'_context_user_id': 
None, u'method': u'release_fixed_ip', u'_context_remote_address': None} from 
(pid=493) _safe_log /usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
+ 2012-07-16 14:06:32 DEBUG nova.rpc.amqp 
[req-d0905711-c4d1-4452-a3b2-46815d1983d7 None None] unpacked context: 
{'user_id': None, 'roles': [u'admin'], 'timestamp': 
'2012-07-16T14:06:32.169100', 'auth_token': 'SANITIZED', 'remote_address': 
None, 'is_admin': True, 'request_id': 
u'req-d0905711-c4d1-4452-a3b2-46815d1983d7', 'project_id': None, 
'read_deleted': u'no'} from (pid=493) _safe_log 
/usr/lib/python2.7/dist-packages/nova/rpc/common.py:160
+ 2012-07-16 14:06:32 DEBUG nova.network.manager 
[req-d0905711-c4d1-4452-a3b2-46815d1983d7 None None] Released IP |10.55.60.141| 
from (pid=493) release_fixed_ip 
/usr/lib/python2.7/dist-packages/nova/network/manager.py:1260
  
  Then the dhcpbridge shows it being revoked:
  
- 2012-07-16 14:04:29 DEBUG nova.dhcpbridge [-] Called 'old' for mac 
'fa:16:3e:11:c5:37' with ip '10.55.60.141' from (pid=23699) main 
/usr/bin/nova-dhcpbridge:113
- 2012-07-16 14:06:32 DEBUG nova.dhcpbridge [-] Called 'del' for mac 
'fa:16:3e:11:c5:37' with ip '10.55.60.141' from (pid=24946) main 
/usr/bin/nova-dhcpbridge:113
+ 2012-07-16 14:04:29 DEBUG nova.dhcpbridge [-] Called 'old' for mac 
'fa:16:3e:11:c5:37' with ip '10.55.60.141' from (pid=23699) main 
/usr/bin/nova-dhcpbridge:113
+ 2012-07-16 14:06:32 DEBUG nova.dhcpbridge [-] Called 'del' for mac 
'fa:16:3e:11:c5:37' with ip '10.55.60.141' from (pid=24946) main 
/usr/bin/nova-dhcpbridge:113
  
  Is there any way we can find out what might have placed the
  release_fixed_ip event on the message queue?  There doesn't seeem to be
  any other mention of the IP in the nova logs on any of our systems.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1026621

Title:
  nova-network gets release_fixed_ip events from someplace, but the
  database still keeps them associated with instances

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1026621/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1026621] Re: nova-network gets release_fixed_ip events from someplace, but the database still keeps them associated with instances

[Bug 1026621] Re: nova-network gets release_fixed_ip events from someplace, but the database still keeps them associated with instances

2 matches

Site Navigation

Mail list logo

Footer information