canonical / cloud-init

Official upstream for the cloud-init: cloud instance initialization
https://cloud-init.io/
Other
2.87k stars 855 forks source link

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

Closed ubuntu-server-builder closed 1 year ago

ubuntu-server-builder commented 1 year ago

This bug was originally filed in Launchpad as LP: #1728152

Launchpad details
affected_projects = ['cloud-init (Ubuntu)', 'cloud-init (Ubuntu Xenial)', 'cloud-init (Ubuntu Zesty)', 'cloud-init (Ubuntu Artful)', 'cloud-init (Ubuntu Bionic)']
assignee = chad.smith
assignee_name = Chad Smith
date_closed = 2017-12-14T21:02:50.819976+00:00
date_created = 2017-10-27T21:11:28.470806+00:00
date_fix_committed = 2017-10-31T19:37:49.074646+00:00
date_fix_released = 2017-12-14T21:02:50.819976+00:00
id = 1728152
importance = high
is_complete = True
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1728152
milestone = None
owner = sargun
owner_name = Sargun
private = False
status = fix_released
submitter = sargun
submitter_name = Sargun
tags = ['verification-done', 'verification-done-artful', 'verification-done-xenial', 'verification-done-zesty']
duplicates = [1728151]

Launchpad user Sargun(sargun) wrote on 2017-10-27T21:11:28.470806+00:00

=== 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=XXXXXXXXXX

=== 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.

ubuntu-server-builder commented 1 year ago

Launchpad user Launchpad Janitor(janitor) wrote on 2017-10-31T21:48:59.133942+00:00

This bug was fixed in the package cloud-init - 17.1-27-geb292c18-0ubuntu1


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

ubuntu-server-builder commented 1 year ago

Launchpad user Łukasz Zemczak(sil2100) wrote on 2017-11-07T17:04:42.337842+00:00

Accepted the artful version - please test.

ubuntu-server-builder commented 1 year ago

Launchpad user Łukasz Zemczak(sil2100) wrote on 2017-11-07T17:08:32.940901+00:00

Hello Sargun, or anyone else affected,

Accepted cloud-init into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/17.1-27-geb292c18-0ubuntu1~17.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

ubuntu-server-builder commented 1 year ago

Launchpad user Łukasz Zemczak(sil2100) wrote on 2017-11-07T17:18:57.138251+00:00

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 new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

ubuntu-server-builder commented 1 year ago

Launchpad user Chad Smith(chad.smith) wrote on 2017-11-08T04:29:16.458851+00:00

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 public-ipv4-only

Get launch-ec2 script

Setup ec2 credentials obtained from aws ui

cat ~/.aws/credentials [default] aws_access_key_id = aws_secret_access_key =

$ git clone git@github.com:cloud-init/qa-scripts.git $ git clone https://github.com/smoser/talk-simplestreams.git $ export PATH=$PATH:./qa-scripts/scripts:./talk-simplestreams/bin $ launch-ec2 --pubkey-file ~/.ssh/id_rsa.pub --series xenial --proposed --keep-alive --clean

default xenial instance with public ipv4 configuration

$ ssh -i ~/.ssh/id_rsa.pub ubuntu@ec2-18-221-189-101.us-east-2.compute.amazonaws.com -- dpkg-query --show cloud-init cloud-init 17.1-27-geb292c18-0ubuntu1~16.04.1

$ ssh -i ~/.ssh/id_rsa.pub ubuntu@ec2-18-221-189-101.us-east-2.compute.amazonaws.com -- cat /etc/network/interfaces.d/50-cloud-init.cfg

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 eth0 iface eth0 inet dhcp

---- xenial public-ipv4-and-ipv6 instance manually created through ec2 UI

Test before cloud-init upgrade to 17.1.27

$ cat /etc/network/interfaces.d/50-cloud-init.cfg

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 eth0 iface eth0 inet dhcp

$ sudo sed -i 's/ xenial / xenial-proposed /' /etc/apt/sources.list; $ sudo apt-get update; $ sudo apt-get install cloud-init; $ sudo rm -rf /var/lib/cloud /var/log/cloud-init*; sudo reboot;

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 eth0 iface eth0 inet dhcp

control-alias eth0

iface eth0 inet6 dhcp

$ dpkg-query --show cloud-init cloud-init 17.1-27-geb292c18-0ubuntu1~16.04.1 $ grep Trace /var/log/cloud-init.log $

$ ip address

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9001 qdisc pfifo_fast state UP group default qlen 1000 link/ether 06:e5:24:b6:f6:08 brd ff:ff:ff:ff:ff:ff inet 172.31.18.159/20 brd 172.31.31.255 scope global eth0 valid_lft forever preferred_lft forever inet6 2600:1f16:9cb:7102:6935:42f4:88f3:2dab/128 scope global valid_lft forever preferred_lft forever inet6 fe80::4e5:24ff:feb6:f608/64 scope link valid_lft forever preferred_lft forever

---- xenial private-ipv4 instance manipv6ually created through ec2 UI ubuntu@ip-172-31-30-150:~$ dpkg-query --show cloud-init cloud-init 17.1-27-geb292c18-0ubuntu1~16.04.1 ubuntu@ip-172-31-30-150:~$ cat /run/cloud-init/result.json { "v1": { "datasource": "DataSourceEc2Local", "errors": [] } } ubuntu@ip-172-31-30-150:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg

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 eth0 iface eth0 inet dhcp ubuntu@ip-172-31-30-150:~$ ip address show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9001 qdisc pfifo_fast state UP group default qlen 1000 link/ether 06:5a:ac:36:55:ea brd ff:ff:ff:ff:ff:ff inet 172.31.30.150/20 brd 172.31.31.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::45a:acff:fe36:55ea/64 scope link valid_lft forever preferred_lft forever ubuntu@ip-172-31-30-150:~$ grep Trace /var/log/cloud-init.log ubuntu@ip-172-31-30-150:~$

---- zesty public ipv4 only ubuntu@ip-172-31-43-227:~$ dpkg-query --show cloud-init cloud-init 17.1-27-geb292c18-0ubuntu1~17.04.1 ubuntu@ip-172-31-43-227:~$ cat /run/cloud-init/result.json { "v1": { "datasource": "DataSourceEc2Local", "errors": [] } } ubuntu@ip-172-31-43-227:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg

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 eth0 iface eth0 inet dhcp

$ ip address show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9001 qdisc pfifo_fast state UP group default qlen 1000 link/ether 0a:cf:5a:06:cf:7e brd ff:ff:ff:ff:ff:ff inet 172.31.43.227/20 brd 172.31.47.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::8cf:5aff:fe06:cf7e/64 scope link valid_lft forever preferred_lft forever

---- zesty public ipv4&ipv6 $ cat /etc/network/interfaces.d/50-cloud-init.cfg

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 eth0 iface eth0 inet dhcp

ubuntu@ip-172-31-16-217:~$ sudo sed -i 's/ zesty / zesty-proposed /' /etc/apt/sources.list ubuntu@ip-172-31-16-217:~$ sudo apt updat ubuntu@ip-172-31-16-217:~$ sudo apt install cloud-init

$ sudo rm -rf /var/lib/cloud /var/log/cloud-init*; sudo reboot

ubuntu@ip-172-31-16-217:~$ dpkg-query --show cloud-init cloud-init 17.1-27-geb292c18-0ubuntu1~17.04.1 ubuntu@ip-172-31-16-217:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg

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 eth0 iface eth0 inet dhcp

control-alias eth0

iface eth0 inet6 dhcp ubuntu@ip-172-31-16-217:~$ cat /run/cloud-init/result.json { "v1": { "datasource": "DataSourceEc2Local", "errors": [] } } ubuntu@ip-172-31-16-217:~$ grep Trace /var/log/cloud-init.log ubuntu@ip-172-31-16-217:~$

ubuntu@ip-172-31-16-217:~$ ip address show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9001 qdisc pfifo_fast state UP group default qlen 1000 link/ether 06:2f:d0:12:7c:a0 brd ff:ff:ff:ff:ff:ff inet 172.31.16.217/20 brd 172.31.31.255 scope global eth0 valid_lft forever preferred_lft forever inet6 2600:1f16:9cb:7102:61e7:e24e:9c70:2b81/128 scope global valid_lft forever preferred_lft forever inet6 fe80::42f:d0ff:fe12:7ca0/64 scope link valid_lft forever preferred_lft forever

---- zesty public ipv4 private only

ubuntu@ip-172-31-20-72:~$ dpkg-query --show cloud-init cloud-init 17.1-27-geb292c18-0ubuntu1~17.04.1 ubuntu@ip-172-31-20-72:~$ cat /run/cloud-init/result.json { "v1": { "datasource": "DataSourceEc2Local", "errors": [] } } ubuntu@ip-172-31-20-72:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg

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 eth0 iface eth0 inet dhcp ubuntu@ip-172-31-20-72:~$ ip address show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9001 qdisc pfifo_fast state UP group default qlen 1000 link/ether 06:8a:8d:6a:b0:a8 brd ff:ff:ff:ff:ff:ff inet 172.31.20.72/20 brd 172.31.31.255 scope global eth0 valid_lft forever preferred_lft forever inet6 fe80::48a:8dff:fe6a:b0a8/64 scope link valid_lft forever preferred_lft forever ubuntu@ip-172-31-20-72:~$ grep Trace /var/log/cloud-init.log ubuntu@ip-172-31-20-72:~$

---- artful public ipv4 only ubuntu@ip-172-31-31-224:~$ dpkg-query --show cloud-init cloud-init 17.1-27-geb292c18-0ubuntu1~17.10.1 ubuntu@ip-172-31-31-224:~$ cat /run/cloud-init/result.json { "v1": { "datasource": "DataSourceEc2Local", "errors": [] } } ubuntu@ip-172-31-31-224:~$ cat /etc/net netplan/ network/ networks
ubuntu@ip-172-31-31-224:~$ cat /etc/net netplan/ network/ networks
ubuntu@ip-172-31-31-224:~$ cat /etc/netplan/50-cloud-init.yaml

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: eth0: dhcp4: true match: macaddress: 06:a6:c2:4f:9a:04 set-name: eth0 ubuntu@ip-172-31-31-224:~$ ip address show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9001 qdisc pfifo_fast state UP group default qlen 1000 link/ether 06:a6:c2:4f:9a:04 brd ff:ff:ff:ff:ff:ff inet 172.31.31.224/20 brd 172.31.31.255 scope global dynamic eth0 valid_lft 3502sec preferred_lft 3502sec inet6 fe80::4a6:c2ff:fe4f:9a04/64 scope link valid_lft forever preferred_lft forever ubuntu@ip-172-31-31-224:~$ grep Trace /var/log/cloud-init.log ubuntu@ip-172-31-31-224:~$

---- artful public ipv4&ipv6 ubuntu@ip-172-31-22-23:~$ dpkg-query --show cloud-init cloud-init 17.1-18-gd4f70470-0ubuntu1 ubuntu@ip-172-31-22-23:~$ cat /run/cloud-init/result.json { "v1": { "datasource": "DataSourceEc2Local", "errors": [] } } ubuntu@ip-172-31-22-23:~$ cat /etc/netplan/50-cloud-init.yaml

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: eth0: dhcp4: true dhcp6: true match: macaddress: 06:50:c6:8f:e1:54 set-name: eth0 ubuntu@ip-172-31-22-23:~$ ip address show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9001 qdisc pfifo_fast state UP group default qlen 1000 link/ether 06:50:c6:8f:e1:54 brd ff:ff:ff:ff:ff:ff inet 172.31.22.23/20 brd 172.31.31.255 scope global dynamic eth0 valid_lft 3428sec preferred_lft 3428sec inet6 2600:1f16:9cb:7102:f57b:c54:5d83:2b10/128 scope global noprefixroute dynamic valid_lft 447sec preferred_lft 147sec inet6 fe80::450:c6ff:fe8f:e154/64 scope link valid_lft forever preferred_lft forever ubuntu@ip-172-31-22-23:~$ grep Trace /var/log/cloud-init.log ubuntu@ip-172-31-22-23:~$

---- artful private ipv4 only ubuntu@ip-172-31-18-234:~$ dpkg-query --show cloud-init cloud-init 17.1-27-geb292c18-0ubuntu1~17.10.1 ubuntu@ip-172-31-18-234:~$ cat /run/cloud-init/result.json { "v1": { "datasource": "DataSourceEc2Local", "errors": [] } } ubuntu@ip-172-31-18-234:~$ cat /etc/netplan/50-cloud-init.yaml

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: eth0: dhcp4: true match: macaddress: 06:a4:43:d2:52:34 set-name: eth0 ubuntu@ip-172-31-18-234:~$ ip address show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9001 qdisc pfifo_fast state UP group default qlen 1000 link/ether 06:a4:43:d2:52:34 brd ff:ff:ff:ff:ff:ff inet 172.31.18.234/20 brd 172.31.31.255 scope global dynamic eth0 valid_lft 3477sec preferred_lft 3477sec inet6 fe80::4a4:43ff:fed2:5234/64 scope link valid_lft forever preferred_lft forever ubuntu@ip-172-31-18-234:~$ grep Trace /var/log/cloud-init.log ubuntu@ip-172-31-18-234:~$

=== End SRU verification output ===

ubuntu-server-builder commented 1 year ago

Launchpad user Launchpad Janitor(janitor) wrote on 2017-11-14T22:17:37.585066+00:00

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

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

ubuntu-server-builder commented 1 year ago

Launchpad user Brian Murray(brian-murray) wrote on 2017-11-14T22:17:47.663764+00:00

The verification of the Stable Release Update for cloud-init has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

ubuntu-server-builder commented 1 year ago

Launchpad user Launchpad Janitor(janitor) wrote on 2017-11-14T22:23:59.287002+00:00

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

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

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

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

ubuntu-server-builder commented 1 year ago

Launchpad user Launchpad Janitor(janitor) wrote on 2017-11-15T01:07:42.077466+00:00

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

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

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

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

ubuntu-server-builder commented 1 year ago

Launchpad user Scott Moser(smoser) wrote on 2017-12-14T21:02:53.222904+00:00

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.