Ask Your Question
2

Instance unable to get ip from dhcp. (Havana with neutron gre)

asked 2014-04-25 17:16:17 -0500

anonymous user

Anonymous

updated 2014-09-08 14:11:28 -0500

rbowen gravatar image

Hello, I have used RDO packstack to deploy Openstack Havana with neutron gre configuraton on 3 hosts (CentOS 6.5) , 1 control node and 2 compute nodes, everything seems fine, except the instance can't get dhcp ip.

Starting network...
udhcpc (v1.20.1) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing
WARN: /etc/rc3.d/S40-network failed
cirros-ds 'net' up at 181.54
checking http://169.254.169.254/2009-04-04/instance-id
failed 1/20: up 181.57. request failed
failed 2/20: up 183.74. request failed

# nova-manage service list
Binary           Host                                 Zone             Status     State Updated_At
nova-consoleauth control-node                         internal         enabled    :-)   2014-04-25 22:05:03
nova-scheduler   control-node                         internal         enabled    :-)   2014-04-25 22:05:03
nova-conductor   control-node                         internal         enabled    :-)   2014-04-25 22:05:06
nova-cert        control-node                         internal         enabled    :-)   2014-04-25 22:05:03
nova-compute     compute-node1                        nova             enabled    :-)   2014-04-25 22:05:05
nova-compute     compute-node1                        nova             enabled    :-)   2014-04-25 22:05:05

# neutron agent-list
+--------------------------------------+--------------------+-----------------------------+-------+----------------+
| id                                   | agent_type         | host                        | alive | admin_state_up |
+--------------------------------------+--------------------+-----------------------------+-------+----------------+
| 7d5bf9e0-aa05-4783-b7d8-ee0df7359021 | Open vSwitch agent | compute-node2               | :-)   | True           |
| 148caf87-d303-424d-b117-1bbe9b6f3727 | Open vSwitch agent | compute-node1               | :-)   | True           |
| cf29a952-cede-4e13-9e5d-0610689cd8da | Open vSwitch agent | control-node                | :-)   | True           |
| df83bba5-8039-4766-8b70-3ce7ff5544f7 | L3 agent           | control-node                | :-)   | True           |
| f8732e04-707a-4ae1-8331-b520c7c8b65f | DHCP agent         | control-node                | :-)   | True           |
+--------------------------------------+--------------------+-----------------------------+-------+----------------+

# ip netns
qdhcp-18a57ea1-0023-4102-a39b-9b8e86feb1d8

# ip netns exec qdhcp-18a57ea1-0023-4102-a39b-9b8e86feb1d8 ip a
14: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
15: ns-cd9933c9-4a: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether fa:16:3e:e2:5d:f7 brd ff:ff:ff:ff:ff:ff
    inet 192.168.8.3/24 brd 192.168.8.255 scope global ns-cd9933c9-4a
    inet 169.254.169.254/16 brd 169.254.255.255 scope global ns-cd9933c9-4a
# ovs-vsctl show | grep cd9933c9-4a
        Port "tapcd9933c9-4a"
            Interface "tapcd9933c9-4a"

# ovs-vsctl show 
245fb0d2-daae-4794-9f97-c7ba84cc68bd
    Bridge br-int
        Port int-br-ex
            Interface int-br-ex
        Port "tapcd9933c9-4a"
            tag: 2
            Interface "tapcd9933c9-4a"
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port br-int
            Interface br-int
                type: internal
    Bridge br-ex
        Port br-ex
            Interface br-ex
                type: internal
        Port "eth0"
            Interface "eth0"
        Port phy-br-ex
            Interface phy-br-ex
    Bridge br-tun
        Port "gre-2"
            Interface "gre-2"
                type: gre
                options: {in_key=flow, local_ip="192.168.0.121", out_key=flow, remote_ip="192.168.0.126"}
        Port br-tun
            Interface br-tun
                type: internal
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port "gre-1"
            Interface "gre-1"
                type: gre
                options: {in_key=flow, local_ip="192.168.0.121", out_key=flow, remote_ip="192.168.0.125"}
    ovs_version: "1.11.0"
edit retag flag offensive close merge delete

Comments

1

Your ip netns output doesn't show any qrouter-router-id namespace. That is a symptom of broken system. What is your neutron router-list output ?

DanIzack gravatar imageDanIzack ( 2014-04-25 20:45:51 -0500 )edit
1

Please format your text. What reports:-
$ps -ef | grep dhcp
Similar report for your qdhcp-xxxxxxx namespace :-
Link to sample
Please, also provide /var/log/neutron/dnsmasq.log

dbaxps gravatar imagedbaxps ( 2014-04-26 02:52:03 -0500 )edit

I haven't added a router yet, as I want to fix the vm dhcp ip issue first. Thanks Danlzack.

aamw gravatar imageaamw ( 2014-04-28 10:24:24 -0500 )edit

ps -ef | grep dhcp

neutron   2066     1  0 09:20 ?        00:00:02 /usr/bin/python /usr/bin/neutron-dhcp-agent --log-file /var/log/neutron/dhcp-agent.log --config-file /usr/share/neutron/neutron-dist.conf --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/dhcp_agent.ini
nobody    4289     1  0 09:27 ?        00:00:00 dnsmasq --no-hosts --no-resolv --strict-order --bind-interfaces --interface=ns-00753cc5-6c --except-interface=lo --pid-file=/var/lib/neutron/dhcp/b62f8e90-83cc-4386-8b9e-b86665cfb2ab/pid --dhcp-hostsfile=/var/lib/neutron/dhcp/b62f8e90-83cc-4386-8b9e-b86665cfb2ab/host --dhcp-optsfile=/var/lib/neutron/dhcp/b62f8e90-83cc-4386-8b9e-b86665cfb2ab/opts --leasefile-ro --dhcp-range=tag0,192.168.8.0,static,120s --dhcp-lease-max=256 --conf-file= --domain=openstacklocal
root      4944  3609  0 09:28 pts/0    00:00:00 grep dhcp

The instance network is 192.168.8.0/24.

# ip netns
qdhcp-b62f8e90-83cc-4386-8b9e-b86665cfb2ab

# ip netns exec qdhcp-b62f8e90-83cc-4386-8b9e-b86665cfb2ab ip a
11: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00 ...
(more)
aamw gravatar imageaamw ( 2014-04-28 10:39:52 -0500 )edit

Just find error in openvswitch-agent.log

2014-04-28 14:44:59.261 8890 ERROR neutron.agent.linux.ovs_lib [-] Unable to execute ['ovs-ofctl', 'add-flow', 'br-tun', 'hard_timeout=0,idle_timeout=0,priority=1,in_port=-1,actions=resubmit(,2)']. Exception: 
Command: ['sudo', 'neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ovs-ofctl', 'add-flow', 'br-tun', 'hard_timeout=0,idle_timeout=0,priority=1,in_port=-1,actions=resubmit(,2)']
Exit code: 1
Stdout: ''
Stderr: 'ovs-ofctl: -1: negative values not supported for in_port\n'

uname -r
2.6.32-431.11.2.el6.x86_64

Seems like GRE tunnel is NOT working, does this Centos kernel version support ovs GRE?

aamw gravatar imageaamw ( 2014-04-28 15:55:29 -0500 )edit
see more comments

2 answers

Sort by ยป oldest newest most voted
0

answered 2014-09-29 23:13:43 -0500

tuna gravatar image

Hi, I got the same issue. I'm using Centos 6.4 64bit & Openstack Havana.

"Stderr: 'ovs-ofctl: -1: negative values not supported for in_port\n'"

Can anyone solve this problem?

edit flag offensive delete link more

Comments

Some people said to install openvswitch-datapath-dkms, but I'm using CentOS. Openvswitch version 1.11 is not really old, because I see some people deployed successfully with OVS 1.10.

I don't know how to fix this issue. Any help?

tuna gravatar imagetuna ( 2014-09-30 00:10:11 -0500 )edit
add a comment
0

answered 2014-10-27 00:27:25 -0500

Hari gravatar image

Try making up and down the bridge and interface associated to it. It worked for me.

ifdown br-ex ; ifup br-ex'
ifdown eth2 ; ifup eth2
edit flag offensive delete link more
add a comment

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

subscribe to rss feed

Stats

Asked: 2014-04-25 17:16:17 -0500

Seen: 6,536 times

Last updated: Oct 27 '14

Related questions

external Net reachable but not the internet!

How does passthrough of a networking device work with Neutron?

neutron agent-list error

vlans with nova-network in havana

Gre vs Vlan

Confused about physnet1

Mystery subnet

Failed to notify nova on events

why is the cinder-volume service down ?

Multiple Subnets Per Network