[Group.of.nepali.translators] [Bug 1728152] Re: EC2 IPv4 and IPv6 Dual Stack Does Not work when instance is not assigned public IPv4 address

2017-12-14 Thread Scott Moser 
This bug is believed to be fixed in cloud-init in 1705804. If this is
still a problem for you, please make a comment and set the state back to
New

Thank you.

** Changed in: cloud-init
   Status: Fix Committed => Fix Released

-- 
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:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Zesty:
  Fix Released
Status in cloud-init source package in Artful:
  Fix Released
Status in cloud-init source package in Bionic:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  Support for configuration of IPV6 addresses on the primary network
  interface in EC2 changed behavior of the automatic network configuration.
  This changed behavior in 2 ways:
  a.) Instances with only a private ipv4 address would not get *any* ipv4
  address.

  b.) Instances with multiple NICs attached at boot would get all NICs
  configured. Previously only the primary network interface would be
  configured by cloud-init.

  'b' is not necessarily a bug for Artful.  A new release can bring new
  behavior.  However, the change of behavior was not intended and not desired
  for an SRU.  In an effort to keep this behavior consistent across 16.04+
  we will be changing the behavior of Artful to only configure the primary
  network interface.

  [Test Case]
  To verify this code is fixed for all cases involved:

  1. Verify that instances without public ipv4 get an ipv4 address.
   * Launch an instance on EC2 without a public IPV4 address.
   * Verify the instance has its Ipv4 address configured via ssh and
 checking 'ip' output.

  2. Verify no regression is done to public systems.
   * Launch an instance on EC2 with a public IPV4 address.
   * Verify the instance has its ipv4 address configured.

  3. Verify only the primary NIC is configured (17.10 only)
   * Launch an instance on EC2 with multiple  nics configured.
   * Verify that only the primary nic has configuration by default.

  For each of the above, verification entails inspection of
  network config (/etc/network/interfaces.d/* or /etc/netplan/)
  and also network state ('ip a' output).

  [Regression Potential]
  Regression in this area of code is certainly limited to EC2,
  and most likely limited to network configuration.

  Complete failure would show itself as no networking at all and
  a WARNING or stack trace on the console logs.

  [Other Info]
  Upstream commit at
https://git.launchpad.net/cloud-init/commit/?id=XX

  === End SRU Template ===

  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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

[Group.of.nepali.translators] [Bug 1728152] Re: EC2 IPv4 and IPv6 Dual Stack Does Not work when instance is not assigned public IPv4 address

2017-11-14 Thread Launchpad Bug Tracker 
This bug was fixed in the package cloud-init -
17.1-27-geb292c18-0ubuntu1~16.04.1

---
cloud-init (17.1-27-geb292c18-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * New upstream snapshot.
- EC2: Limit network config to fallback nic, fix local-ipv4 only
  instances. (LP: #1728152)
- Gentoo: Use "rc-service" rather than "service". [Carlos Konstanski]

cloud-init (17.1-25-g17a15f9e-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * New upstream snapshot.
- resizefs: Fix regression when system booted with root=PARTUUID=
  (LP: #1725067)
- tools: make yum package installation more reliable
- citest: fix remaining warnings raised by integration tests.
- citest: show the class actual class name in results.
- ntp: fix config module schema to allow empty ntp config
  (LP: #1724951)
- tools: disable fastestmirror if using proxy [Joshua Powers]

cloud-init (17.1-18-gd4f70470-0ubuntu1~16.04.2) xenial-proposed;
urgency=medium

  * cherry-pick 41152f1: schema: Log debug instead of warning when
jsonschema is absent (LP: #1724354)

cloud-init (17.1-18-gd4f70470-0ubuntu1~16.04.1) xenial-proposed;
urgency=medium

  * drop the following cherry picks, now incorporated in snapshot.
+ debian/patches/cpick-a2f8ce9c-Do-not-provide-systemd-fsck-drop...
  * debian/copyright: dep5 updates, reorganize, add Apache 2.0 license.
(LP: #1718681)
  * debian/control: drop dependency on python3-prettytable
  * debian/rules: install rsyslog file with 0644 mode instead of 0755.
  * debian/rules, debian/apport-launcher.py: add an apport hook. (LP: #1607345)
  * New upstream snapshot. (LP: #1721847)
- simpletable: Fix get_string method to return table-formatted string
- net: Handle bridge stp values of 0 and convert to boolean type
  [Chad Smith]
- tools: Give specific --abbrev=8 to "git describe"
- network: bridge_stp value not always correct [Ryan Harper]
- tests: re-enable tox with nocloud-kvm support [Joshua Powers]
- systemd: remove limit on tasks created by cloud-init-final.service.
  [Robert Schweikert]
- suse: Support addition of zypper repos via cloud-config.
  [Robert Schweikert]
- tests: Combine integration configs and testcases [Joshua Powers]
- Azure, CloudStack: Support reading dhcp options from systemd-networkd.
  [Dimitri John Ledkov]
- packages/debian/copyright: remove mention of boto and MIT license
- systemd: only mention Before=apt-daily.service on debian based distros.
  [Robert Schweikert]
- Add missing simpletable and simpletable tests for failed merge
  [Chad Smith]
- Remove prettytable dependency, introduce simpletable [Andrew Jorgensen]
- debian/copyright: dep5 updates, reorganize, add Apache 2.0 license.
  [Joshua Powers]
- tests: remove dependency on shlex [Joshua Powers]
- AltCloud: Trust PATH for udevadm and modprobe.
- DataSourceOVF: use util.find_devs_with(TYPE=iso9660)
  [Ryan Harper]
- tests: remove a temp file used in bootcmd tests.
- release 17.1
- doc: document GCE datasource. [Arnd Hannemann]
- suse: updates to templates to support openSUSE and SLES.
  [Robert Schweikert]
- suse: Copy sysvinit files from redhat with slight changes.
  [Robert Schweikert]
- docs: fix sphinx module schema documentation [Chad Smith]
- tests: Add cloudinit package to all test targets [Chad Smith]
- Makefile: No longer look for yaml files in obsolete ./bin/.
- tests: fix ds-identify unit tests to set EC2_STRICT_ID_DEFAULT.
- ec2: Fix maybe_perform_dhcp_discovery to use /var/tmp as a tmpdir
  [Chad Smith]
- Azure: wait longer for SSH pub keys to arrive.
  [Paul Meyer]
- GCE: Fix usage of user-data.
- cmdline: add collect-logs subcommand. [Chad Smith]
- CloudStack: consider dhclient lease files named with a hyphen.
- resizefs: Drop check for read-only device file, do not warn on
  overlayroot. [Chad Smith]
- tests: Enable the NoCloud KVM platform [Joshua Powers]
- resizefs: pass mount point to xfs_growfs [Dusty Mabe]
- vmware: Enable nics before sending the SUCCESS event. [Sankar Tanguturi]
- cloud-config modules: honor distros definitions in each module
  [Chad Smith]
- chef: Add option to pin chef omnibus install version
  [Ethan Apodaca]
- tests: execute: support command as string [Joshua Powers]
- schema and docs: Add jsonschema to resizefs and bootcmd modules
  [Chad Smith]
- tools: Add xkvm script, wrapper around qemu-system [Joshua Powers]
- vmware customization: return network config format
  [Sankar Tanguturi]
- Ec2: only attempt to operate at local mode on known platforms.
- Use /run/cloud-init for tempfile operations.
- ds-identify: Make OpenStack return maybe on arch other than intel.
- tests: mock missed openstack metadata uri network_data.json
  [Chad Smith]
- relocate

[Group.of.nepali.translators] [Bug 1728152] Re: EC2 IPv4 and IPv6 Dual Stack Does Not work when instance is not assigned public IPv4 address

2017-11-14 Thread Launchpad Bug Tracker 
This bug was fixed in the package cloud-init -
17.1-27-geb292c18-0ubuntu1~17.04.1

---
cloud-init (17.1-27-geb292c18-0ubuntu1~17.04.1) zesty-proposed; urgency=medium

  * New upstream snapshot.
- EC2: Limit network config to fallback nic, fix local-ipv4 only
  instances. (LP: #1728152)
- Gentoo: Use "rc-service" rather than "service". [Carlos Konstanski]

cloud-init (17.1-25-g17a15f9e-0ubuntu1~17.04.1) zesty-proposed;
urgency=medium

  * New upstream snapshot.
- resizefs: Fix regression when system booted with root=PARTUUID=
  (LP: #1725067)
- tools: make yum package installation more reliable
- citest: fix remaining warnings raised by integration tests.
- citest: show the class actual class name in results.
- ntp: fix config module schema to allow empty ntp config
  (LP: #1724951)
- tools: disable fastestmirror if using proxy [Joshua Powers]

cloud-init (17.1-18-gd4f70470-0ubuntu1~17.04.2) zesty-proposed;
urgency=medium

  * cherry-pick 41152f1: schema: Log debug instead of warning when
jsonschema is absent (LP: #1724354)

cloud-init (17.1-18-gd4f70470-0ubuntu1~17.04.1) zesty-proposed;
urgency=medium

  * drop the following cherry picks, now incorporated in snapshot.
+ debian/patches/cpick-a2f8ce9c-Do-not-provide-systemd-fsck-drop...
  * debian/copyright: dep5 updates, reorganize, add Apache 2.0 license.
(LP: #1718681)
  * debian/control: drop dependency on python3-prettytable
  * debian/rules: install rsyslog file with 0644 mode instead of 0755.
  * debian/rules, debian/apport-launcher.py: add an apport hook. (LP: #1607345)
  * New upstream snapshot (LP: #1721847)
- simpletable: Fix get_string method to return table-formatted string
- net: Handle bridge stp values of 0 and convert to boolean type
  [Chad Smith]
- tools: Give specific --abbrev=8 to "git describe"
- network: bridge_stp value not always correct [Ryan Harper]
- tests: re-enable tox with nocloud-kvm support [Joshua Powers]
- systemd: remove limit on tasks created by cloud-init-final.service.
  [Robert Schweikert]
- suse: Support addition of zypper repos via cloud-config.
  [Robert Schweikert]
- tests: Combine integration configs and testcases [Joshua Powers]
- Azure, CloudStack: Support reading dhcp options from systemd-networkd.
  [Dimitri John Ledkov]
- packages/debian/copyright: remove mention of boto and MIT license
- systemd: only mention Before=apt-daily.service on debian based distros.
  [Robert Schweikert]
- Add missing simpletable and simpletable tests for failed merge
  [Chad Smith]
- Remove prettytable dependency, introduce simpletable [Andrew Jorgensen]
- debian/copyright: dep5 updates, reorganize, add Apache 2.0 license.
  [Joshua Powers]
- tests: remove dependency on shlex [Joshua Powers]
- AltCloud: Trust PATH for udevadm and modprobe.
- DataSourceOVF: use util.find_devs_with(TYPE=iso9660)
  [Ryan Harper]
- tests: remove a temp file used in bootcmd tests.
- release 17.1
- doc: document GCE datasource. [Arnd Hannemann]
- suse: updates to templates to support openSUSE and SLES.
  [Robert Schweikert]
- suse: Copy sysvinit files from redhat with slight changes.
  [Robert Schweikert]
- docs: fix sphinx module schema documentation [Chad Smith]
- tests: Add cloudinit package to all test targets [Chad Smith]
- Makefile: No longer look for yaml files in obsolete ./bin/.
- tests: fix ds-identify unit tests to set EC2_STRICT_ID_DEFAULT.
- ec2: Fix maybe_perform_dhcp_discovery to use /var/tmp as a tmpdir
  [Chad Smith]
- Azure: wait longer for SSH pub keys to arrive.
  [Paul Meyer]
- GCE: Fix usage of user-data.
- cmdline: add collect-logs subcommand. [Chad Smith]
- CloudStack: consider dhclient lease files named with a hyphen.
- resizefs: Drop check for read-only device file, do not warn on
  overlayroot. [Chad Smith]
- tests: Enable the NoCloud KVM platform [Joshua Powers]
- resizefs: pass mount point to xfs_growfs [Dusty Mabe]
- vmware: Enable nics before sending the SUCCESS event. [Sankar Tanguturi]
- cloud-config modules: honor distros definitions in each module
  [Chad Smith]
- chef: Add option to pin chef omnibus install version
  [Ethan Apodaca]
- tests: execute: support command as string [Joshua Powers]
- schema and docs: Add jsonschema to resizefs and bootcmd modules
  [Chad Smith]
- tools: Add xkvm script, wrapper around qemu-system [Joshua Powers]
- vmware customization: return network config format
  [Sankar Tanguturi]
- Ec2: only attempt to operate at local mode on known platforms.
- Use /run/cloud-init for tempfile operations.
- ds-identify: Make OpenStack return maybe on arch other than intel.
- tests: mock missed openstack metadata uri network_data.json
  [Chad Smith]
- relocate

[Group.of.nepali.translators] [Bug 1728152] Re: EC2 IPv4 and IPv6 Dual Stack Does Not work when instance is not assigned public IPv4 address

2017-11-14 Thread Launchpad Bug Tracker 
This bug was fixed in the package cloud-init -
17.1-27-geb292c18-0ubuntu1~17.10.1

---
cloud-init (17.1-27-geb292c18-0ubuntu1~17.10.1) artful-proposed; urgency=medium

  * New upstream snapshot.
- EC2: Limit network config to fallback nic, fix local-ipv4 only
  instances. (LP: #1728152)
- Gentoo: Use "rc-service" rather than "service". [Carlos Konstanski]

cloud-init (17.1-25-g17a15f9e-0ubuntu1~17.10.1) artful-proposed;
urgency=medium

  * New upstream snapshot.
- resizefs: Fix regression when system booted with root=PARTUUID=
  (LP: #1725067)
- tools: make yum package installation more reliable
- citest: fix remaining warnings raised by integration tests.
- citest: show the class actual class name in results.
- ntp: fix config module schema to allow empty ntp config
  (LP: #1724951)
- tools: disable fastestmirror if using proxy [Joshua Powers]
- schema: Log debug instead of warning when jsonschema is not available.
  (LP: #1724354)

 -- Chad Smith   Tue, 31 Oct 2017 12:56:34
-0600

** Changed in: cloud-init (Ubuntu Artful)
   Status: Fix Committed => Fix Released

-- 
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:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Committed
Status in cloud-init source package in Zesty:
  Fix Released
Status in cloud-init source package in Artful:
  Fix Released
Status in cloud-init source package in Bionic:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  Support for configuration of IPV6 addresses on the primary network
  interface in EC2 changed behavior of the automatic network configuration.
  This changed behavior in 2 ways:
  a.) Instances with only a private ipv4 address would not get *any* ipv4
  address.

  b.) Instances with multiple NICs attached at boot would get all NICs
  configured. Previously only the primary network interface would be
  configured by cloud-init.

  'b' is not necessarily a bug for Artful.  A new release can bring new
  behavior.  However, the change of behavior was not intended and not desired
  for an SRU.  In an effort to keep this behavior consistent across 16.04+
  we will be changing the behavior of Artful to only configure the primary
  network interface.

  [Test Case]
  To verify this code is fixed for all cases involved:

  1. Verify that instances without public ipv4 get an ipv4 address.
   * Launch an instance on EC2 without a public IPV4 address.
   * Verify the instance has its Ipv4 address configured via ssh and
 checking 'ip' output.

  2. Verify no regression is done to public systems.
   * Launch an instance on EC2 with a public IPV4 address.
   * Verify the instance has its ipv4 address configured.

  3. Verify only the primary NIC is configured (17.10 only)
   * Launch an instance on EC2 with multiple  nics configured.
   * Verify that only the primary nic has configuration by default.

  For each of the above, verification entails inspection of
  network config (/etc/network/interfaces.d/* or /etc/netplan/)
  and also network state ('ip a' output).

  [Regression Potential]
  Regression in this area of code is certainly limited to EC2,
  and most likely limited to network configuration.

  Complete failure would show itself as no networking at all and
  a WARNING or stack trace on the console logs.

  [Other Info]
  Upstream commit at
https://git.launchpad.net/cloud-init/commit/?id=XX

  === End SRU Template ===

  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

[Group.of.nepali.translators] [Bug 1728152] Re: EC2 IPv4 and IPv6 Dual Stack Does Not work when instance is not assigned public IPv4 address

2017-10-31 Thread Launchpad Bug Tracker 
This bug was fixed in the package cloud-init -
17.1-27-geb292c18-0ubuntu1

---
cloud-init (17.1-27-geb292c18-0ubuntu1) bionic; urgency=medium

  * New upstream snapshot.
- EC2: Limit network config to fallback nic, fix local-ipv4 only
  instances. (LP: #1728152)
- Gentoo: Use "rc-service" rather than "service".
  [ckonstanski] (LP: #1727121)

 -- Chad Smith   Tue, 31 Oct 2017 12:51:10
-0600

** Changed in: cloud-init (Ubuntu Bionic)
   Status: In Progress => Fix Released

-- 
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:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  In Progress
Status in cloud-init source package in Zesty:
  In Progress
Status in cloud-init source package in Artful:
  In Progress
Status in cloud-init source package in Bionic:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  Support for configuration of IPV6 addresses on the primary network
  interface in EC2 changed behavior of the automatic network configuration.
  This changed behavior in 2 ways:
  a.) Instances with only a private ipv4 address would not get *any* ipv4
  address.

  b.) Instances with multiple NICs attached at boot would get all NICs
  configured. Previously only the primary network interface would be
  configured by cloud-init.

  'b' is not necessarily a bug for Artful.  A new release can bring new
  behavior.  However, the change of behavior was not intended and not desired
  for an SRU.  In an effort to keep this behavior consistent across 16.04+
  we will be changing the behavior of Artful to only configure the primary
  network interface.

  [Test Case]
  To verify this code is fixed for all cases involved:

  1. Verify that instances without public ipv4 get an ipv4 address.
   * Launch an instance on EC2 without a public IPV4 address.
   * Verify the instance has its Ipv4 address configured via ssh and
 checking 'ip' output.

  2. Verify no regression is done to public systems.
   * Launch an instance on EC2 with a public IPV4 address.
   * Verify the instance has its ipv4 address configured.

  3. Verify only the primary NIC is configured (17.10 only)
   * Launch an instance on EC2 with multiple  nics configured.
   * Verify that only the primary nic has configuration by default.

  For each of the above, verification entails inspection of
  network config (/etc/network/interfaces.d/* or /etc/netplan/)
  and also network state ('ip a' output).

  [Regression Potential]
  Regression in this area of code is certainly limited to EC2,
  and most likely limited to network configuration.

  Complete failure would show itself as no networking at all and
  a WARNING or stack trace on the console logs.

  [Other Info]
  Upstream commit at
https://git.launchpad.net/cloud-init/commit/?id=XX

  === End SRU Template ===

  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

___
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp