yahoo-eng-team team mailing list archive

[Jorge <1749717@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

I'm using Openstack on Mitaka version. My projects use prefix delegation
to get IPv6 configuration and a common IPv4 DHCP. IPv4 addresses and
configurations are working well. But for IPv6 my instances just get the
address, probably via RA of neutron. I'm looking for a way to get other
informations like that on dhcpv6 (name servers, for example).

My subnet configuration is --ipv6_ra_mode dhcpv6-stateless
--ipv6_address_mode dhcpv6-stateless. I'm using Ubuntu Cloud Image 16.04
LTS.

Addresses are well generated and VMs have connectivity. But, dhcpv6
requests are not sent. We need that VMs request other information (like
nameservers) from dhcpv6 on boot. I've tested manually after boot and it
works.

I've seen that the file /etc/network/interfaces.d/50-cloud-init.cfg is
generated at boot time. Its content is:

---
# This file is generated from information provided by
# the datasource.  Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
auto lo
iface lo inet loopback

auto ens3
iface ens3 inet dhcp
---

To do what I'm thinking I just need to put these other lines in this
configuration file:

---
iface ens3 inet6 auto
  pre-up sleep 5
  dhcp 1
---

This was tested, running dhcpv6 manually. Sleep 5 is due a Ubuntu bug
and 'dhcp 1' indicates that information should be obtained from dhcpv6
server.

Is there some way to do cloud-init read that the subnet is configured as
dhcpv6 and then generate a configuration file as that? It's just
necessary that cloud-init launch the dhcpv6 client.

Thank you!

** Affects: cloud-init
     Importance: Undecided
         Status: New


** Tags: client dhcpv6 ipv6

** Attachment added: "cloud-init.tar"
   https://bugs.launchpad.net/bugs/1749717/+attachment/5055788/+files/cloud-init.tar

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1749717

Title:
  A way to configure dhcpv6 client

Status in cloud-init:
  New

Bug description:
  I'm using Openstack on Mitaka version. My projects use prefix
  delegation to get IPv6 configuration and a common IPv4 DHCP. IPv4
  addresses and configurations are working well. But for IPv6 my
  instances just get the address, probably via RA of neutron. I'm
  looking for a way to get other informations like that on dhcpv6 (name
  servers, for example).

  My subnet configuration is --ipv6_ra_mode dhcpv6-stateless
  --ipv6_address_mode dhcpv6-stateless. I'm using Ubuntu Cloud Image
  16.04 LTS.

  Addresses are well generated and VMs have connectivity. But, dhcpv6
  requests are not sent. We need that VMs request other information
  (like nameservers) from dhcpv6 on boot. I've tested manually after
  boot and it works.

  I've seen that the file /etc/network/interfaces.d/50-cloud-init.cfg is
  generated at boot time. Its content is:

  ---
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback

  auto ens3
  iface ens3 inet dhcp
  ---

  To do what I'm thinking I just need to put these other lines in this
  configuration file:

  ---
  iface ens3 inet6 auto
    pre-up sleep 5
    dhcp 1
  ---

  This was tested, running dhcpv6 manually. Sleep 5 is due a Ubuntu bug
  and 'dhcp 1' indicates that information should be obtained from dhcpv6
  server.

  Is there some way to do cloud-init read that the subnet is configured
  as dhcpv6 and then generate a configuration file as that? It's just
  necessary that cloud-init launch the dhcpv6 client.

  Thank you!

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1749717/+subscriptions