[Openstack] [ovsdb-dev] DHCP agent not attached to br-int

Silvia Fichera fichera.sil at gmail.com
Thu Nov 26 17:12:14 UTC 2015


Hi guys,
yes with a new installation and Liberty I solved the problem, but only in
the controller node.
All instances spawned in a simple compute node attached to that one have no
IP address.
I tryed with
$ sudo ovs-vsctl get Open_vSwitch . _uuid
$ sudo ovs-vsctl set Open_vSwitch 8cd9e97d-46bb-418d-8616-2b21063482ad
other_config:local_ip=10.0.0.2
in the compute host, but it has no results. :(


2015-11-23 14:54 GMT+01:00 Vishal Thapar <vishal.thapar at ericsson.com>:

> Hi Sam,
>
>
>
> We debugged it in IRC. You can see errors in trying to add tap port in the
> dhcp log [search for br-int]. I am not sure if this is same log that he
> shared with me, but the problem was that br-int wasn’t created by the time
> q-dhcp tried adding it. That is why I recommended trying out with Liberty
> coz “Wait for br-int” was added post kilo.
>
>
>
> Things worked out for him in a new fresh VM. He had installed latest
> version of OVS in this failing setup. So, I’m suspecting it could be a case
> of two different instances of OVS [installed in different locations]
> running with devstack code using one while q-dhcp code using other. I
> believe q-dhcp picks it off entry-point configuration while devstack picks
> off PATH variable.
>
>
>
> Regards,
>
> Vishal.
>
>
>
> *From:* Sam Hague [mailto:shague at redhat.com]
> *Sent:* 23 November 2015 19:13
> *To:* Silvia Fichera
> *Cc:* <ovsdb-dev at lists.opendaylight.org>; openstack at lists.openstack.org;
> Vishal Thapar
> *Subject:* Re: [ovsdb-dev] DHCP agent not attached to br-int
>
>
>
> Silvia,
>
>
>
> what happens if you do ip netns? Do you see the qdhcp-xxx namespaces? And
> then can you do a ip netns exec qdhcp-xxx ip link and see any tap ports?
>
>
>
> A high-level set of actions that happens with dhcp is as follows. I don't
> think I have the ordering right, but these are the actions that happens
> eventually.
>
>
>
> - create a name space: ip netns
>
> - add a tap port to a bridge: ovs-vsctl show
>
> - move the tap port into the namespace: ip netns exec qdhcp-xxx ip link
>
> - assign ip to tap port: ip netns exec qdhcp-xxx ip addr
>
> - spin up dnsmasq: ps -ef | grep dns
>
>
>
> I also listed some debug commands you can use. The log you have assumes
> that the tap port was there. I don't see any output trying to actually add
> the port. So I would work from that log looking at the qdhcp name space and
> the port. See where it broke.
>
>
>
> It's also possible you have some left over junk somewhere. Maybe that dhcp
> name space or port do not exist and are stale. Stacking and restacking
> without cleaning the ovsdb in between runs isn't good. Also moving from one
> release to another can lead to problems. Go forward isn't as bad as going
> backwards, but still it normally leads to trouble.
>
>
>
> Thanks, Sam
>
>
>
> On Sat, Nov 21, 2015 at 6:50 AM, Silvia Fichera <fichera.sil at gmail.com>
> wrote:
>
> Hi,
>
> after a suggestion by Vishal I tryed to move to Liberty, but I faced the
> same problem.
>
> I've copied the log of q-dhcp and it seems that it is unable to create the
> tap interface. I had the same problem with kilo.
>
> http://pastebin.com/ZPKVPCSv
>
> Anyone knows how to solve it?
>
> Thaks
>
>
>
> Silvia
>
>
>
> 2015-11-20 15:22 GMT+01:00 Silvia Fichera <fichera.sil at gmail.com>:
>
> Hi all,
>
> I have a setup with odl (lithium) and Openstack (kilo) fired up by
> devstack and I'm using OVSDB feature in ODL.
>
>
>
> My problem is that when I launch a new istance in openstack this han no ip
> address assigned.
>
>
>
> here some outputs of my controller node:
>
>
>
> neutron agent-list
>
>
> +--------------------------------------+----------------+-----------+-------+----------------+------------------------+
>
> | id                                   | agent_type     | host      |
> alive | admin_state_up | binary                 |
>
>
> +--------------------------------------+----------------+-----------+-------+----------------+------------------------+
>
> | 0514a159-e823-44c2-aa9b-5fed18c1130b | DHCP agent     | devstack1 | :-)
>   | True           | neutron-dhcp-agent     |
>
> | 8546282c-ab9d-45cd-8f2d-4877d924eec9 | Metadata agent | devstack1 | :-)
>   | True           | neutron-metadata-agent |
>
>
> +--------------------------------------+----------------+-----------+-------+----------------+------------------------+
>
>
>
>
>
> neutron port-list
>
>
> +--------------------------------------+------+-------------------+-----------------------------------------------------------------------------------+
>
> | id                                   | name | mac_address       |
> fixed_ips
>       |
>
>
> +--------------------------------------+------+-------------------+-----------------------------------------------------------------------------------+
>
> | 927db2be-5106-451d-95d1-5c1459d1a271 |      | fa:16:3e:40:7f:a0 |
> {"subnet_id": "547881c1-c4aa-4144-819a-64bc211f181b", "ip_address":
> "10.10.10.2"} |
>
>
> +--------------------------------------+------+-------------------+----------------------------------------------------------------------------
>
>
>
> neutron port-show 927db2be-5106-451d-95d1-5c1459d1a271
>
>
> +-----------------------+-----------------------------------------------------------------------------------+
>
> | Field                 | Value
>                                   |
>
>
> +-----------------------+-----------------------------------------------------------------------------------+
>
> | admin_state_up        | True
>                                  |
>
> | allowed_address_pairs |
>                                   |
>
> | binding:host_id       | devstack1
>                                   |
>
> | binding:profile       | {}
>                                  |
>
> | binding:vif_details   | {"port_filter": true}
>                                   |
>
> | binding:vif_type      | ovs
>                                   |
>
> | binding:vnic_type     | normal
>                                  |
>
> | device_id             |
> dhcp6d13ba27-f5a3-57ff-8437-9fbb02a7daef-410760e0-bf34-4889-993d-526a918610bd
>     |
>
> | device_owner          | network:dhcp
>                                  |
>
> | extra_dhcp_opts       |
>                                   |
>
> | fixed_ips             | {"subnet_id":
> "547881c1-c4aa-4144-819a-64bc211f181b", "ip_address": "10.10.10.2"} |
>
> | id                    | 927db2be-5106-451d-95d1-5c1459d1a271
>                                  |
>
> | mac_address           | fa:16:3e:40:7f:a0
>                                   |
>
> | name                  |
>                                   |
>
> | network_id            | 410760e0-bf34-4889-993d-526a918610bd
>                                  |
>
> | security_groups       |
>                                   |
>
> | status                | ACTIVE
>                                  |
>
> | tenant_id             | dee5fcd4edd6471db647e0ff7eb36309
>                                  |
>
>
> +-----------------------+-----------------------------------------------------------------------------------+
>
>
>
>
>
> sudo ovs-vsctl show
>
> a450ea16-a6c0-4f1b-ac49-5167b8c105ac
>
>     Manager "tcp:10.30.3.234:6640"
>
>         is_connected: true
>
>     Bridge br-ex
>
>         Controller "tcp:10.30.3.234:6653"
>
>             is_connected: true
>
>         fail_mode: secure
>
>         Port br-ex
>
>             Interface br-ex
>
>                 type: internal
>
>         Port "eth1"
>
>             Interface "eth1"
>
>         Port patch-int
>
>             Interface patch-int
>
>                 type: patch
>
>                 options: {peer=patch-ext}
>
>     Bridge br-int
>
>         Controller "tcp:10.30.3.234:6653"
>
>             is_connected: true
>
>         fail_mode: secure
>
>         Port br-int
>
>             Interface br-int
>
>                 type: internal
>
>         Port patch-ext
>
>             Interface patch-ext
>
>                 type: patch
>
>                 options: {peer=patch-int}
>
>     ovs_version: "2.3.2"
>
>
>
>
>
> sudo ovs-ofctl -O Openflow13 show br-int
>
> OFPT_FEATURES_REPLY (OF1.3) (xid=0x2): dpid:0000be80fe69c946
>
> n_tables:254, n_buffers:256
>
> capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS
>
> OFPST_PORT_DESC reply (OF1.3) (xid=0x3):
>
>  3(patch-ext): addr:5a:d2:aa:c8:4b:9e
>
>      config:     0
>
>      state:      0
>
>      speed: 0 Mbps now, 0 Mbps max
>
>  LOCAL(br-int): addr:be:80:fe:69:c9:46
>
>      config:     0
>
>      state:      0
>
>      speed: 0 Mbps now, 0 Mbps max
>
> OFPT_GET_CONFIG_REPLY (OF1.3) (xid=0x5): frags=normal miss_send_len=0
>
>
>
> sudo ovs-ofctl -O Openflow13 dump-ports br-int
>
> OFPST_PORT reply (OF1.3) (xid=0x2): 2 ports
>
>   port LOCAL: rx pkts=8, bytes=648, drop=0, errs=0, frame=0, over=0, crc=0
>
>            tx pkts=0, bytes=0, drop=0, errs=0, coll=0
>
>            duration=95700.292s
>
>   port  3: rx pkts=10376, bytes=949680, drop=0, errs=0, frame=0, over=0,
> crc=0
>
>            tx pkts=8151, bytes=921063, drop=0, errs=0, coll=0
>
>            duration=90707.741s
>
>
>
> The output of
>
>
>
> ip netns
>
>
>
> is empty.
>
>
>
> There is a way to create manually the connection between br-int and the
> dhcp agent?
>
>
>
> Thanks
>
>
>
>
>
> Silvia
>
>
>
>
>
> --
>
> Silvia Fichera
>
>
> _______________________________________________
> ovsdb-dev mailing list
> ovsdb-dev at lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/ovsdb-dev
>
>
>



-- 
Silvia Fichera
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20151126/f4b228ad/attachment.html>


More information about the Openstack mailing list