Activity log for bug #1549793

Date Who What changed Old value New value Message
2016-02-25 12:49:47 Alex Stafeyev bug added bug
2016-02-25 12:51:09 Alex Stafeyev 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 ~]# 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
2016-02-25 12:51:21 Alex Stafeyev bug added subscriber John Schwarz
2016-02-25 12:51:38 Alex Stafeyev bug added subscriber Toni Freger
2016-02-25 12:51:44 Alex Stafeyev bug added subscriber Assaf Muller
2016-02-26 05:04:18 Eugene Nikanorov neutron: status New Incomplete
2016-02-26 05:06:10 Eugene Nikanorov neutron: status Incomplete New
2016-02-27 10:11:01 Li Xipeng neutron: status New Confirmed
2016-02-27 10:12:54 Li Xipeng neutron: assignee Li Xipeng (lixipeng)
2016-03-01 01:16:04 OpenStack Infra neutron: status Confirmed In Progress
2016-03-03 16:04:03 Dariusz Smigiel neutron: status In Progress Incomplete
2016-03-03 17:16:43 John Schwarz neutron: status Incomplete In Progress
2016-03-25 02:06:32 OpenStack Infra neutron: assignee Li Xipeng (lixipeng) Brian Haley (brian-haley)
2016-03-28 05:01:15 OpenStack Infra neutron: assignee Brian Haley (brian-haley) Li Xipeng (lixipeng)
2016-04-12 10:49:48 OpenStack Infra neutron: status In Progress Fix Released
2016-04-13 00:46:52 Armando Migliaccio neutron: status Fix Released Confirmed
2016-04-13 00:47:38 Armando Migliaccio neutron: milestone newton-1
2016-04-13 00:48:04 Armando Migliaccio neutron: importance Undecided High
2016-04-14 05:44:24 OpenStack Infra neutron: status Confirmed In Progress
2016-06-03 19:31:31 Armando Migliaccio neutron: milestone newton-1 newton-2
2016-06-29 23:23:42 OpenStack Infra neutron: status In Progress Fix Released
2016-06-30 13:37:09 Ihar Hrachyshka tags metadata metadata neutron-proactive-backport-potential
2016-10-07 15:41:54 Ihar Hrachyshka tags metadata neutron-proactive-backport-potential metadata mitaka-backport-potential
2016-10-07 15:50:39 Ihar Hrachyshka tags metadata mitaka-backport-potential mitaka-backport-potential
2016-10-07 15:50:47 Ihar Hrachyshka tags mitaka-backport-potential l3-ipam-dhcp mitaka-backport-potential
2016-11-03 20:05:06 OpenStack Infra tags l3-ipam-dhcp mitaka-backport-potential in-stable-mitaka l3-ipam-dhcp mitaka-backport-potential