Network unreachable error - quantum

Asked by jsb

Hi Somik,
Here is my nova.conf:

--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--logdir=/var/log/nova
--state_path=/var/lib/nova
--lock_path=/var/lock/nova
--flagfile=/etc/nova/nova-compute.conf
--use_deprecated_auth
--verbose

--sql_connection=mysql://novadbadmin:novasecret@192.168.198.59/nova

--daemonize
--s3_host=192.168.198.59
--rabbit_host=192.168.198.59
--cc_host=192.168.198.59
--ospi_host=192.168.198.59
--ec2_host=192.168.198.59
--ec2_url=http://192.168.198.59:8773/services/Cloud
--nova_url=http://192.168.198.59:8774/v1.1/

--FAKE_subdomain=ec2
--routing_source_ip=192.168.198.59
--glance_api_servers=192.168.198.59:9292
--image_service=nova.image.glance.GlanceImageService
--iscsi_ip_prefix=192.168.

# Quantum configuration
--network_manager=nova.network.quantum.manager.QuantumManager
--quantum_connection_host=192.168.198.55
--quantum_connection_port=9696
--libvirt_ovs_integration_bridge=br-int
--libvirt_vif_type=ethernet
--libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtOpenVswitchDriver
--linuxnet_interface_driver=nova.network.linux_net.LinuxOVSInterfaceDriver
--libvirt_type=qemu
--public_interface=eth0
--flat_interface=eth1
--flat_network_bridge=br-int
--quantum_default_tenant_id=tenant2

I am using minimal linux image:

ttylinux-uec-amd64-12.1_2.6.35 obtained from http://smoser.brickies.net/ubuntu/ttylinux-uec/

Is there a test VM image that is not configured with DHCP client for me test?

Tap device that got created with the launching of my VM is

tap432d5cbd-ad Link encap:Ethernet HWaddr d6:8f:3a:80:c9:ba
          inet6 addr: fe80::d48f:3aff:fe80:c9ba/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:473 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500
          RX bytes:150842 (150.8 KB) TX bytes:468 (468.0 B)

$sudo ovs-vsctl list-ifaces br-int
eth1
tap432d5cbd-ad

ovs agent that is running on the controller node does not show any logging. Only time it shows is when terminating the instances.
INFO:root:Port Disappeared: 6c2b0c4e-2185-426c-8c3b-f9014d08c5b0

Thanks,
-Jay

Hi Jay,

I would recommend for such issues, you are welcome to open up a question on
launchpad answers - https://answers.launchpad.net/quantum
That way it will easier for folks to track the history of the issue.

Rest of the comments inline.

On Tue, Mar 6, 2012 at 3:12 PM, jay_s_b <jay_s_b@xxxxxxxxx> wrote:

> Hello,
> Using quantum with openvswitch.
> I am able to launch VM . NOT using dhcp (not setting --quantum_use_dhcp).
> Still, cannot ping the VM. The console output is
> udhcpc (v1.17.2) started
> Sending discover...
> Sending discover...
> Sending discover...
>

This is DHCP Client on the Guest VM, '--quantum_use_dhcp' just allows for
existing nova-network DHCP service to plugged into the virtual Quantum
network.
If you are using a VM image where IP injection isn't working and the VM has
a DHCP Client configured, you will see the DHCP Client send out DHCP
discovers

No lease, forking to background
> starting DHCP forEthernet interface eth0 [ OK ]
> cloud-setup: checking
> http://169.254.169.254/2009-04-04/meta-data/instance-id
>

I believe you are using meta-data service, a copy of your nova.conf on
OpenStack Controller, nova-network node and nova-compute node would be
helpful.

>
> wget: can't connect to remote host (169.254.169.254): Network is
> unreachable
> cloud-setup: failed 1/30: up 16.75. request failed
> wget: can't connect to remote host (169.254.169.254): Network is
> unreachable
> cloud-setup: failed 2/30: up 17.91. request failed
> Why is VM boot using dhcp when quantum dhcp is not used?
>

I referenced the reason for this above.

>
> TAP device is correctly created. I do not any errors in the logs of
> quantum/nova-network/openvswitch.
>

I believe, if you statically configure IP on the instance which didn't
receive IP, you should be able to test pings, but thats
a guess based on what I can make out from your email.

>
> Thanks,
> -Jay
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>
>

--
Somik Behera | Nicira Networks, Inc. | somik

Question information

Language:
English Edit question
Status:
Answered
For:
neutron Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Somik Behera (somikbehera) said :
#1

Hi Jay,

Looking at the current information, I cant tell where the issue lies. If its an issue with the image containing DHCP, you can always log into the console using VNS access that is provided by virsh commands and assign statically assign the VM IPs.

Here is a guide that provides instructions around how to create your own OpenStack image as well: http://cssoss.files.wordpress.com/2011/11/openstackbookv2-0_csscorp.pdf

I would also recommend first trying devstack.sh script available at devstack.org - The devstack script provides an automated way to install all OpenStack services from source.

Thanks,
Somik

Can you help with this problem?

Provide an answer of your own, or ask jsb for more information if necessary.

To post a message you must log in.