[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

[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:

[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:

[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:

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

2017-11-07 Thread Chad Smith
Manual Verification performed on Xenial Zesty and artful in the following 3 scenarios: 1. ipv4 public only 2. public ipv4 & ipv6 addresses configured 3. private ipv4 only addresses All results passed and properly configured interfaces === SRU verification output === xenial xenial

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

2017-11-07 Thread Łukasz Zemczak
Hello Sargun, or anyone else affected, Accepted cloud-init into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/17.1-27-geb292c18-0ubuntu1~16.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this

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

2017-11-07 Thread Łukasz Zemczak
Accepted the artful version - please test. ** Changed in: cloud-init (Ubuntu Artful) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-artful ** Changed in: cloud-init (Ubuntu Zesty) Status: In Progress => Fix Committed ** Tags added:

[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:

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

2017-10-31 Thread Chad Smith
** Changed in: cloud-init Status: In Progress => Fix Committed ** Changed in: cloud-init (Ubuntu Xenial) Assignee: (unassigned) => Chad Smith (chad.smith) ** Changed in: cloud-init (Ubuntu Zesty) Assignee: (unassigned) => Chad Smith (chad.smith) ** Changed in: cloud-init

[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
** Merge proposal linked: https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/333050 ** Merge proposal linked: https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/333051 -- You received this bug notification because you are a member of Ubuntu

[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
** Merge proposal linked: https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/333048 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728152 Title: EC2 IPv4 and IPv6 Dual

[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
** Merge proposal linked: https://code.launchpad.net/~chad.smith/cloud-init/+git/cloud-init/+merge/333047 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728152 Title: EC2 IPv4 and IPv6 Dual

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

2017-10-30 Thread Scott Moser
** Description changed: + === 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