<div dir="ltr">I did some dhcpdump and I could see that the requests were coming<div>to the DHCP server and replies were sent. </div><div><br></div><div>I am not able to ping the VMs from anywhere, DHCP namespace or </div>
<div>Router namespace. I guess the problem is with interface being </div><div>configured with the supplied IP address.</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jul 4, 2014 at 4:49 PM, Anant Patil <span dir="ltr"><<a href="mailto:anant.techie@gmail.com" target="_blank">anant.techie@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I am using Ubuntu 14.04 and running devstack from top of the tree. <div>Everything goes fine, but I am not able to ping the instance IP </div>
<div>addresses. I am not able to log into the VM using novnc, but I</div>
<div>am sure the VM is not getting the IP Address.</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jul 4, 2014 at 4:47 PM, Anant Patil <span dir="ltr"><<a href="mailto:anant.techie@gmail.com" target="_blank">anant.techie@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Paul, you need run the command as admin. If you are sourcing<div>openrc as demo tenant or something it will not list.<div>
<br></div><div>However, I also face this issue of IP address not getting assigned. </div>
</div></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jul 4, 2014 at 2:35 AM, Kyle Mestery <span dir="ltr"><<a href="mailto:mestery@noironetworks.com" target="_blank">mestery@noironetworks.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On Thu, Jul 3, 2014 at 10:14 AM, Paul Czarkowski<br>
<<a href="mailto:paul.czarkowski@rackspace.com" target="_blank">paul.czarkowski@rackspace.com</a>> wrote:<br>
> I¹m seeing similar. Instances launch, they show as having Ips in<br>
> `neutron list` but I cannot access them via IP.<br>
><br>
> Other thing I¹ve notices is that doing a `neutron agent-list` gives me an<br>
> empty list, I would assume it should at least show the dhcp agent ?<br>
><br>
</div>Which plugin are you using? For ML2 with OVS or LB, you should have L2<br>
agents on each compute host in addition to the DHCP and L3 agents. I<br>
think perhaps your problem is different than Rob's.<br>
<div><div><br>
> On 7/1/14, 12:00 PM, "Kyle Mestery" <<a href="mailto:mestery@noironetworks.com" target="_blank">mestery@noironetworks.com</a>> wrote:<br>
><br>
>>Hi Rob:<br>
>><br>
>>Can you try adding the following config to your local.conf? I'd like<br>
>>to see if this gets you going or not. It will force it to use gre<br>
>>tunnels for tenant networks. By default it will not.<br>
>><br>
>>ENABLE_TENANT_TUNNELS=True<br>
>><br>
>>On Tue, Jul 1, 2014 at 10:53 AM, Rob Crittenden <<a href="mailto:rcritten@redhat.com" target="_blank">rcritten@redhat.com</a>><br>
>>wrote:<br>
>>> Rob Crittenden wrote:<br>
>>>> Mark Kirkwood wrote:<br>
>>>>> On 25/06/14 10:59, Rob Crittenden wrote:<br>
>>>>>> Before I get punted onto the operators list, I post this here because<br>
>>>>>> this is the default config and I'd expect the defaults to just work.<br>
>>>>>><br>
>>>>>> Running devstack inside a VM with a single NIC configured and this in<br>
>>>>>> localrc:<br>
>>>>>><br>
>>>>>> disable_service n-net<br>
>>>>>> enable_service q-svc<br>
>>>>>> enable_service q-agt<br>
>>>>>> enable_service q-dhcp<br>
>>>>>> enable_service q-l3<br>
>>>>>> enable_service q-meta<br>
>>>>>> enable_service neutron<br>
>>>>>> Q_USE_DEBUG_COMMAND=True<br>
>>>>>><br>
>>>>>> Results in a successful install but no DHCP address assigned to<br>
>>>>>>hosts I<br>
>>>>>> launch and other oddities like no CIDR in nova net-list output.<br>
>>>>>><br>
>>>>>> Is this still the default way to set things up for single node? It is<br>
>>>>>> according to <a href="https://wiki.openstack.org/wiki/NeutronDevstack" target="_blank">https://wiki.openstack.org/wiki/NeutronDevstack</a><br>
>>>>>><br>
>>>>>><br>
>>>>><br>
>>>>> That does look ok: I have an essentially equivalent local.conf:<br>
>>>>><br>
>>>>> ...<br>
>>>>> ENABLED_SERVICES+=,-n-net<br>
>>>>> ENABLED_SERVICES+=,q-svc,q-agt,q-dhcp,q-l3,q-meta,q-metering,tempest<br>
>>>>><br>
>>>>> I don't have 'neutron' specifically enabled... not sure if/why that<br>
>>>>> might make any difference tho. However instance launching and ip<br>
>>>>>address<br>
>>>>> assignment seem to work ok.<br>
>>>>><br>
>>>>> However I *have* seen the issue of instances not getting ip addresses<br>
>>>>>in<br>
>>>>> single host setups, and it is often due to use of virt io with bridges<br>
>>>>> (with is the default I think). Try:<br>
>>>>><br>
>>>>> nova.conf:<br>
>>>>> ...<br>
>>>>> libvirt_use_virtio_for_bridges=False<br>
>>>><br>
>>>> Thanks for the suggestion. At least in master this was replaced by a<br>
>>>>new<br>
>>>> section, libvirt, but even setting it to False didn't do the trick for<br>
>>>> me. I see the same behavior.<br>
>>><br>
>>> OK, I've tested the havana and icehouse branches in F-20 and they don't<br>
>>> seem to have a working neutron either. I see the same thing. I can<br>
>>> launch a VM but it isn't getting a DHCP address.<br>
>>><br>
>>> Maybe I'll try in some Ubuntu release to see if this is Fedora-specific.<br>
>>><br>
>>> rob<br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> OpenStack-dev mailing list<br>
>>> <a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
>>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
>><br>
>>_______________________________________________<br>
>>OpenStack-dev mailing list<br>
>><a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
>><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>