RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1073170 - Timeout while waiting on RPC response - topic: "network", RPC method: "allocate_for_instance"
Summary: Timeout while waiting on RPC response - topic: "network", RPC method: "alloca...
Keywords:
Status: CLOSED DUPLICATE of bug 1049503
Alias: None
Product: RDO
Classification: Community
Component: openstack-nova
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact: Ami Jeain
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-06 00:06 UTC by Giulio Fidente
Modified: 2014-03-10 16:41 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-03-10 16:41:14 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1257626 0 None None None Never

Description Giulio Fidente 2014-03-06 00:06:11 UTC
Description of problem:
with icehouse-2 on el7 , booting an instance fails with the following in compute.log

2014-03-05 18:58:58.618 17364 ERROR nova.compute.manager [-] Instance failed network setup after 1 attempt(s)
2014-03-05 18:58:58.618 17364 TRACE nova.compute.manager Traceback (most recent call last):
2014-03-05 18:58:58.618 17364 TRACE nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1239, in _allocate_network_async
2014-03-05 18:58:58.618 17364 TRACE nova.compute.manager     dhcp_options=dhcp_options)
2014-03-05 18:58:58.618 17364 TRACE nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/network/api.py", line 96, in wrapped
2014-03-05 18:58:58.618 17364 TRACE nova.compute.manager     return func(self, context, *args, **kwargs)
2014-03-05 18:58:58.618 17364 TRACE nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/network/api.py", line 50, in wrapper
2014-03-05 18:58:58.618 17364 TRACE nova.compute.manager     res = f(self, context, *args, **kwargs)
2014-03-05 18:58:58.618 17364 TRACE nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/network/api.py", line 304, in allocate_for_instance
2014-03-05 18:58:58.618 17364 TRACE nova.compute.manager     nw_info = self.network_rpcapi.allocate_for_instance(context, **args)
2014-03-05 18:58:58.618 17364 TRACE nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/network/rpcapi.py", line 190, in allocate_for_instance
2014-03-05 18:58:58.618 17364 TRACE nova.compute.manager     macs=jsonutils.to_primitive(macs))
2014-03-05 18:58:58.618 17364 TRACE nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/rpcclient.py", line 85, in call
2014-03-05 18:58:58.618 17364 TRACE nova.compute.manager     return self._invoke(self.proxy.call, ctxt, method, **kwargs)
2014-03-05 18:58:58.618 17364 TRACE nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/rpcclient.py", line 63, in _invoke
2014-03-05 18:58:58.618 17364 TRACE nova.compute.manager     return cast_or_call(ctxt, msg, **self.kwargs)
2014-03-05 18:58:58.618 17364 TRACE nova.compute.manager   File "/usr/lib/python2.7/site-packages/nova/openstack/common/rpc/proxy.py", line 130, in call
2014-03-05 18:58:58.618 17364 TRACE nova.compute.manager     exc.info, real_topic, msg.get('method'))
2014-03-05 18:58:58.618 17364 TRACE nova.compute.manager Timeout: Timeout while waiting on RPC response - topic: "network", RPC method: "allocate_for_instance" info: "<unknown>"


Version-Release number of selected component (if applicable):
2014.1-0.11.b2.el7


Steps to Reproduce:
1. install using nova-network (using packstack allinone)
2. try to boot an instance


Additional info:
system is configured with nova-network, not with neutron

Comment 1 Giulio Fidente 2014-03-07 13:34:58 UTC
I'm changing the severity to "high" as I'm able to reproduce this 100% times.

Comment 2 Brent Eagles 2014-03-10 16:41:14 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=1049503 turns out to be the root cause here. To verify, we disabled selinux and tried again and everything worked. So the issue seems to be with our selinux packages. Closing as duplicate.

*** This bug has been marked as a duplicate of bug 1049503 ***


Note You need to log in before you can comment on or make changes to this bug.