yahoo-eng-team team mailing list archive

[OpenStack Infra <1549793@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/305615
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=dfacba0f2d7586df51962c2b927e5272358ea3c1
Submitter: Jenkins
Branch:    master

commit dfacba0f2d7586df51962c2b927e5272358ea3c1
Author: Li Xipeng <lixipeng@xxxxxxxxxxx>
Date:   Tue Feb 23 13:54:34 2016 -0800

    Add 169.254.169.254 when enable force_metadata
    
    When enable force_metadata in dhcp.ini, and create a network
    and a subnet, none 169.254.169.254/24 ip info set in related
    namespace(qdhcp-XXX) with `ip a` command. In this case, vms could
    not get metadata any more.
    
    Change-Id: Ibd73824658c9759d32fa53ffcf41f2b719c1028b
    Closes-Bug: #1549793


** Changed in: neutron
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1549793

Title:
  force_metadata = True : qdhcp namespace has no interface with ip
  169.254.169.254

Status in neutron:
  Fix Released

Bug description:
  [root@overcloud-controller-0 ~]#  cat /etc/neutron/dhcp_agent.ini | grep metadata | grep -v "#"
  force_metadata = True
  enable_isolated_metadata = False
  enable_metadata_network = False

  [stack@undercloud ~]$ neutron net-list
  +--------------------------------------+----------------------------------------------------+-------------------------------------------------------+
  | id                                   | name                                               | subnets                                               |

  | d7ebddcd-9989-4068-a8d9-66381e83d1f5 | int_net                                            | 739b813d-4863-44e3-acd5-0bf6c3aaec76 192.168.3.0/24   |
  +--------------------------------------+----------------------------------------------------+-------------------------------------------------------+

  [root@overcloud-controller-0 ~]# ip netns exec  qdhcp-d7ebddcd-9989-4068-a8d9-66381e83d1f5 ip a
  1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 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
         valid_lft forever preferred_lft forever
      inet6 ::1/128 scope host
         valid_lft forever preferred_lft forever
  36: tap7002581e-a4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
      link/ether fa:16:3e:3b:e9:ae brd ff:ff:ff:ff:ff:ff
      inet 192.168.3.3/24 brd 192.168.3.255 scope global tap7002581e-a4
         valid_lft forever preferred_lft forever
      inet6 fe80::f816:3eff:fe3b:e9ae/64 scope link
         valid_lft forever preferred_lft forever

  We should have interface on qdhcp namespace  with 169.254.169.254 ip
  for metadata when "force_metadata = True" in /etc/neutron/dhcp-
  agent.ini.

  VMs are not receiving metadata in this scenario


  [root@overcloud-controller-0 ~]# rpm -qa | grep neutron
  openstack-neutron-bigswitch-lldp-2015.1.38-1.el7ost.noarch
  openstack-neutron-ml2-2015.1.2-9.el7ost.noarch
  python-neutronclient-2.4.0-2.el7ost.noarch
  python-neutron-2015.1.2-9.el7ost.noarch
  openstack-neutron-2015.1.2-9.el7ost.noarch
  openstack-neutron-lbaas-2015.1.2-1.el7ost.noarch
  python-neutron-lbaas-2015.1.2-1.el7ost.noarch
  openstack-neutron-common-2015.1.2-9.el7ost.noarch
  openstack-neutron-openvswitch-2015.1.2-9.el7ost.noarch
  openstack-neutron-metering-agent-2015.1.2-9.el7ost.noarch


  [root@overcloud-controller-0 ~]# rpm -qa | grep meta
  yum-metadata-parser-1.1.4-10.el7.x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1549793/+subscriptions