yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #06228
[Bug 1257446] [NEW] Creating a dual-stacked network causes dhcp for both stacks to fail
Public bug reported:
Currently, we are running Havana in a lab with l2 provider networks.
Upstream is done via 802.1Q tags, and we are using dnsmasq 2.59 (Compile
time options IPv6 GNU-getopt DBus i18n DHCP TFTP conntrack IDN).
Creating a working IPv4-only network works fine, by creating a shared
(provider) network and an IPv4 subnet. Instances are brought up as
expected. However, upon adding a second subnet to this network with an
IPv6 scope, all new instances fail to receive dhcp for IPv4. The
following lines are found in the devstack q-dhcp output:
http://paste.openstack.org/show/54386/
** Affects: neutron
Importance: Undecided
Assignee: Openstack@Comcast (comcast-openstack)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Openstack@Comcast (comcast-openstack)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1257446
Title:
Creating a dual-stacked network causes dhcp for both stacks to fail
Status in OpenStack Neutron (virtual network service):
New
Bug description:
Currently, we are running Havana in a lab with l2 provider networks.
Upstream is done via 802.1Q tags, and we are using dnsmasq 2.59
(Compile time options IPv6 GNU-getopt DBus i18n DHCP TFTP conntrack
IDN). Creating a working IPv4-only network works fine, by creating a
shared (provider) network and an IPv4 subnet. Instances are brought
up as expected. However, upon adding a second subnet to this network
with an IPv6 scope, all new instances fail to receive dhcp for IPv4.
The following lines are found in the devstack q-dhcp output:
http://paste.openstack.org/show/54386/
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1257446/+subscriptions
Follow ups
References