← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1728151] [NEW] IPv4 and IPv6 Dual Stack Does Not work when instance is not assigned public IPv4 address

 

Public bug reported:

With the following cloud-init configuration:
system_info:
  network:
    renderers: ['netplan', 'eni', 'sysconfig']
    

network:
  version: 2
  ethernets:
    id0:
        match:
            name: e*
        dhcp4: true
        dhcp6: true

with version  17.1-18-gd4f70470-0ubuntu1 on ami-36a8754c, it writes out the following network configuration:
# 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}
network:
    version: 2
    ethernets:
        ens3:
            dhcp6: true
            match:
                macaddress: 02:14:13:66:8a:66
            set-name: ens3


----

This instance is in a (default) VPC with a private IPv4 address and no
public IPv4 addresses.

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

-- 
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/1728151

Title:
  IPv4 and IPv6 Dual Stack Does Not work when instance is not assigned
  public IPv4 address

Status in cloud-init:
  New

Bug description:
  With the following cloud-init configuration:
  system_info:
    network:
      renderers: ['netplan', 'eni', 'sysconfig']
      

  network:
    version: 2
    ethernets:
      id0:
          match:
              name: e*
          dhcp4: true
          dhcp6: true

  with version  17.1-18-gd4f70470-0ubuntu1 on ami-36a8754c, it writes out the following network configuration:
  # 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}
  network:
      version: 2
      ethernets:
          ens3:
              dhcp6: true
              match:
                  macaddress: 02:14:13:66:8a:66
              set-name: ens3

  
  ----

  This instance is in a (default) VPC with a private IPv4 address and no
  public IPv4 addresses.

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