force_metadata = True : qdhcp namespace has no interface with ip 169.254.169.254
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Li Xipeng |
Bug Description
[root@overcloud
force_metadata = True
enable_
enable_
[stack@undercloud ~]$ neutron net-list
+------
| id | name | subnets |
| d7ebddcd-
+------
[root@overcloud
1: lo: <LOOPBACK,
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,
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:
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/
VMs are not receiving metadata in this scenario
[root@overcloud
openstack-
openstack-
python-
python-
openstack-
openstack-
python-
openstack-
openstack-
openstack-
[root@overcloud
yum-metadata-
description: | updated |
Changed in neutron: | |
status: | New → Confirmed |
assignee: | nobody → Li Xipeng (lixipeng) |
Changed in neutron: | |
assignee: | Li Xipeng (lixipeng) → Brian Haley (brian-haley) |
Changed in neutron: | |
assignee: | Brian Haley (brian-haley) → Li Xipeng (lixipeng) |
Changed in neutron: | |
milestone: | newton-1 → newton-2 |
tags: | added: neutron-proactive-backport-potential |
tags: |
added: mitaka-backport-potential removed: neutron-proactive-backport-potential |
tags: | removed: metadata |
tags: | added: l3-ipam-dhcp |
since 169.254 is alias, it will not be shown in ifconfig output. Try running ip a in the namespace instead