yahoo-eng-team team mailing list archive

[Dazhao Yu <dzyu@xxxxxxxxxx>]

Public bug reported:

I use vmware vcenter driver to nova boot instance.

After I create one ipv4 address network,  and nova boot instance, in
vsphere client, we can see the instance have been deployed, and also the
instance have been assigned the targeted IPv4 address.

But after create one IPv6 address network, and use this network to boot instance, the instance have been deployed successfully, but it can not be assigned the targeted IPv6 address. 
I use dnsmasq as dhcpv6 server, use 'tcpdump -i tapXXXX' to monitor the network data,  and in deployed instance, and run "dhclient -6",  the result of tcpdump as below:

22:02:54.354287 IP6 fe80::f816:3eff:fe34:a80e.dhcpv6-client > ff02::1:2.dhcpv6-server: dhcp6 solicit
22:02:54.354689 IP6 fe80::184d:82ff:fec4:d268.dhcpv6-server > fe80::f816:3eff:fe34:a80e.dhcpv6-client: dhcp6 advertise
22:02:55.434954 IP6 fe80::f816:3eff:fe34:a80e.dhcpv6-client > ff02::1:2.dhcpv6-server: dhcp6 solicit
22:02:55.435283 IP6 fe80::184d:82ff:fec4:d268.dhcpv6-server > fe80::f816:3eff:fe34:a80e.dhcpv6-client: dhcp6 advertise
22:02:57.587164 IP6 fe80::f816:3eff:fe34:a80e.dhcpv6-client > ff02::1:2.dhcpv6-server: dhcp6 solicit
22:02:57.587456 IP6 fe80::184d:82ff:fec4:d268.dhcpv6-server > fe80::f816:3eff:fe34:a80e.dhcpv6-client: dhcp6 advertise
22:02:59.354082 IP6 fe80::184d:82ff:fec4:d268 > fe80::f816:3eff:fe34:a80e: ICMP6, neighbor solicitation, who has fe80::f816:3eff:fe34:a80e, length 32
22:02:59.354922 IP6 fe80::f816:3eff:fe34:a80e > fe80::184d:82ff:fec4:d268: ICMP6, neighbor advertisement, tgt is fe80::f816:3eff:fe34:a80e, length 24

It seems like dnsmasq can get client request from deployed instance, and
can give response to client, but vsphere block these message.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1281916

Title:
  OpenStack cannot assign IPv6 address to booted instance due to vsphere
  settings

Status in OpenStack Compute (Nova):
  New

Bug description:
  I use vmware vcenter driver to nova boot instance.

  After I create one ipv4 address network,  and nova boot instance, in
  vsphere client, we can see the instance have been deployed, and also
  the instance have been assigned the targeted IPv4 address.

  But after create one IPv6 address network, and use this network to boot instance, the instance have been deployed successfully, but it can not be assigned the targeted IPv6 address. 
  I use dnsmasq as dhcpv6 server, use 'tcpdump -i tapXXXX' to monitor the network data,  and in deployed instance, and run "dhclient -6",  the result of tcpdump as below:

  22:02:54.354287 IP6 fe80::f816:3eff:fe34:a80e.dhcpv6-client > ff02::1:2.dhcpv6-server: dhcp6 solicit
  22:02:54.354689 IP6 fe80::184d:82ff:fec4:d268.dhcpv6-server > fe80::f816:3eff:fe34:a80e.dhcpv6-client: dhcp6 advertise
  22:02:55.434954 IP6 fe80::f816:3eff:fe34:a80e.dhcpv6-client > ff02::1:2.dhcpv6-server: dhcp6 solicit
  22:02:55.435283 IP6 fe80::184d:82ff:fec4:d268.dhcpv6-server > fe80::f816:3eff:fe34:a80e.dhcpv6-client: dhcp6 advertise
  22:02:57.587164 IP6 fe80::f816:3eff:fe34:a80e.dhcpv6-client > ff02::1:2.dhcpv6-server: dhcp6 solicit
  22:02:57.587456 IP6 fe80::184d:82ff:fec4:d268.dhcpv6-server > fe80::f816:3eff:fe34:a80e.dhcpv6-client: dhcp6 advertise
  22:02:59.354082 IP6 fe80::184d:82ff:fec4:d268 > fe80::f816:3eff:fe34:a80e: ICMP6, neighbor solicitation, who has fe80::f816:3eff:fe34:a80e, length 32
  22:02:59.354922 IP6 fe80::f816:3eff:fe34:a80e > fe80::184d:82ff:fec4:d268: ICMP6, neighbor advertisement, tgt is fe80::f816:3eff:fe34:a80e, length 24

  It seems like dnsmasq can get client request from deployed instance,
  and can give response to client, but vsphere block these message.

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