← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1728152] Re: IPv4 and IPv6 Dual Stack Does Not work when instance is not assigned public IPv4 address

 

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
       Status: New

** Summary changed:

- IPv4 and IPv6 Dual Stack Does Not work when instance is not assigned public IPv4 address
+ EC2 IPv4 and IPv6 Dual Stack Does Not work when instance is not assigned public IPv4 address

** Also affects: cloud-init (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Also affects: cloud-init (Ubuntu Artful)
   Importance: Undecided
       Status: New

** Also affects: cloud-init (Ubuntu Bionic)
   Importance: Undecided
       Status: New

** Also affects: cloud-init (Ubuntu Zesty)
   Importance: Undecided
       Status: New

** Changed in: cloud-init (Ubuntu Xenial)
       Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Zesty)
       Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Artful)
       Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Bionic)
       Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: cloud-init (Ubuntu Zesty)
   Importance: Undecided => High

** Changed in: cloud-init (Ubuntu Artful)
   Importance: Undecided => High

** Changed in: cloud-init (Ubuntu Bionic)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1728152

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

Status in cloud-init:
  In Progress
Status in cloud-init package in Ubuntu:
  Confirmed
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Zesty:
  Confirmed
Status in cloud-init source package in Artful:
  Confirmed
Status in cloud-init source package in Bionic:
  Confirmed

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/1728152/+subscriptions