The instance created on compute node of multi node cannot get IP address from DHCP

asked 2015-09-07 20:06:42 -0500

5010stack gravatar image

Hello, I'm a beginner of Openstack.

I have used Openstack Juno on 2 hosts, 1 controll + network and 1 compute node, installed by packstack.

When I create a instance on controller+network node, it can get IP address assigned by DHCP Server of controller +network node.

However, It is impossible for the instance created on a compute node to get IP address by DHCP. There is excerpt of console log when ubuntu 14.04 cloud image. http://uec-images.ubuntu.com/trusty/current/trusty-server-cloudimg-amd64-disk1.img (http://uec-images.ubuntu.com/trusty/c...)

2015-09-06 01:42:59,353 - url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [2/120s]: request error [HTTPConnectionPool(host='169.254.169.254', port=80): Max retries exceeded with url: /2009-04-04/meta-data/instance-id (Caused by <class 'socket.error'="">: [Errno 101] Network is unreachable)]^M^M

I try to find the solution, but I cannot find the clue to solve this problem because there are a lot of elements or components related to DHCP(private network,NIC,libvirt,VLAN, openvswitch etc).

Here's the Configuration files and logs. (If information is insufficient, tell me what information is necessary.) Please help.

Version Of Openstack

It is Juno series.

[root@node1 ~(keystone_admin)]# nova-manage version
2014.2.2-1.fc22

https://wiki.openstack.org/wiki/Releases

Nodes

node1:Controller & Network Node

OS:Fedora release 20 (Heisenbug)

Kernel:3.11.10-301.fc20.x86_64

node2:Compute node

OS:Fedora release 20 (Heisenbug)

Kernel:3.19.8-100.fc20.x86_64

Network Configration

node1

[root@node1 ~(keystone_admin)]# ovs-vsctl show && ifconfig
9f3bad00-a34f-4009-886c-41bbabb48f99
    Bridge br-ex
        Port "p2p1"
            Interface "p2p1"
        Port br-ex
            Interface br-ex
                type: internal
        Port "qg-507e9b86-de"
            Interface "qg-507e9b86-de"
                type: internal
    Bridge br-int
        fail_mode: secure
        Port br-int
            Interface br-int
                type: internal
        Port "qvoab4d255b-06"
            tag: 1
            Interface "qvoab4d255b-06"
        Port "qvoeea2dc18-e7"
            tag: 1
            Interface "qvoeea2dc18-e7"
        Port "qvobb6b311e-9c"
            tag: 1
            Interface "qvobb6b311e-9c"
        Port "qvo632daf67-c3"
            tag: 1
            Interface "qvo632daf67-c3"
        Port "qvo14d3d40d-3f"
            tag: 1
            Interface "qvo14d3d40d-3f"
        Port "qvo80c3ceaf-27"
            tag: 1
            Interface "qvo80c3ceaf-27"
        Port "qr-61d740c6-4c"
            tag: 1
            Interface "qr-61d740c6-4c"
                type: internal
        Port "qvo70866fd3-f0"
            tag: 1
            Interface "qvo70866fd3-f0"
        Port "qvoaa61c482-0f"
            tag: 1
            Interface "qvoaa61c482-0f"
        Port "qvo855bb809-fe"
            tag: 1
            Interface "qvo855bb809-fe"
        Port "qvo20718396-de"
            tag: 1
            Interface "qvo20718396-de"
        Port "qvo011a85ba-21"
            tag: 1
            Interface "qvo011a85ba-21"
        Port "tap0e20d2c6-88"
            tag: 1
            Interface "tap0e20d2c6-88"
                type: internal
        Port "qvo78c3e797-70"
            tag: 1
            Interface "qvo78c3e797-70"
        Port "qvod8bc9377-71"
            tag: 1
            Interface "qvod8bc9377-71"
        Port "qvo08e9afdc-2b"
            tag: 1
            Interface "qvo08e9afdc-2b"
        Port "qvo40473d60-1a"
            tag: 1
            Interface "qvo40473d60-1a"
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
    Bridge br-tun
        Port "vxlan-0a17214f"
            Interface "vxlan-0a17214f"
                type: vxlan
                options: {df_default="true", in_key=flow, local_ip="10.23.33.80", out_key=flow, remote_ip="10.23.33.79"}
        Port br-tun
            Interface br-tun
                type: internal
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
    ovs_version: "2.3.1-git4750c96"
br-ex: flags=4163<up,broadcast,running,multicast>  mtu 1500
        inet 10.23.33.80  netmask 255.255.0.0  broadcast 10.23.255.255
        inet6 fe80::1ca8:ebff:fe6e:7445  prefixlen 64  scopeid 0x20<link>
        ether 00:13:3b:12:3c:df  txqueuelen 0  (Ethernet)
        RX packets 65355932  bytes 9606059254 (8.9 GiB)
        RX errors 0 ...
(more)
edit retag flag offensive close merge delete

Comments

I am too facing the same issue here.. on SUSE Linux..

Moorthy gravatar imageMoorthy ( 2015-09-08 23:54:33 -0500 )edit

just trace the dhcp request and offer messages using tcpdump on the interfaces. This will give you the clue.

ritesh.singh.aricent@gmail.com gravatar imageritesh.singh.aricent@gmail.com ( 2015-10-01 06:09:18 -0500 )edit

Moothy,retesh, thanks for your reply. Finally I solved this problem for updating node1's kernel from 3.11* to 3.19. Maybe VXLAN isn't adopted to kernel 3.11..

5010stack gravatar image5010stack ( 2015-11-10 20:34:33 -0500 )edit