yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #16775
[Bug 1304862] Re: The metadata network gets unreachable on again adding the network interface to router requires
Changed state from Incomplete to Invalid since exact steps are given but
it seems bug has been fixed indirectly.
** Changed in: neutron
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1304862
Title:
The metadata network gets unreachable on again adding the network
interface to router requires
Status in OpenStack Neutron (virtual network service):
Invalid
Bug description:
Problem description :
The VM instance during creation failed to connect 169.254.169.254/16
network once the network is again added to the router port.
Release -- Icehouse
Build Used
ii neutron-common 1:2014.1+git201404071258~precise-0ubuntu1 Neutron is a virtual network service for Openstack - common
ii neutron-dhcp-agent 1:2014.1+git201404071258~precise-0ubuntu1 Neutron is a virtual network service for Openstack - DHCP agent
ii neutron-l3-agent 1:2014.1+git201404071258~precise-0ubuntu1 Neutron is a virtual network service for Openstack - l3 agent
ii neutron-metadata-agent 1:2014.1+git201404071258~precise-0ubuntu1 Neutron is a virtual network service for Openstack - metadata agent
ii neutron-plugin-nicira 1:2014.1+git201404071258~precise-0ubuntu1 transitional dummy package
ii neutron-plugin-vmware 1:2014.1+git201403311932~precise-0ubuntu1 Neutron is a virtual network service for Openstack - VMware plugin
ii neutron-server 1:2014.1+git201404071258~precise-0ubuntu1 Neutron is a virtual network service for Openstack - server
Steps Performed
1. Created a router and set a gateway to it.
2. Created a network "40.40.40.0/24" and added this network as
interface to the router.
3. On adding as interface a meta network "169.254.169.252/30" also
got added to router as interface.
4. During VM creation it sends it gets connected to meta network and
receives the metadata.
5. Removed the the network "40.40.40.0/24" interface from the router.
6. Later on again added the same network "40.40.40.0/24" network as
interface to the same router.
7. On creating the instance on this network "40.40.40.0/24" observed
the instance failed to connect the metadata network.
8. After restarting the dhcp service " service neutron-dhcp-agent restart", then the instance during creation able to
connect the meta data network.
Note : This issue we haven't observed during grizzly and havana
release.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1304862/+subscriptions
References