| 2017-11-23 17:37:56 |
Michael Lyle |
bug |
|
|
added bug |
| 2017-11-24 17:13:41 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu) |
|
| 2017-11-24 17:13:53 |
Scott Moser |
bug task added |
|
systemd (Ubuntu) |
|
| 2017-11-24 17:20:59 |
Scott Moser |
cloud-init: status |
New |
Confirmed |
|
| 2017-11-24 17:21:01 |
Scott Moser |
cloud-init: importance |
Undecided |
High |
|
| 2017-11-24 17:21:06 |
Scott Moser |
cloud-init (Ubuntu): status |
New |
Confirmed |
|
| 2017-11-24 17:21:09 |
Scott Moser |
cloud-init (Ubuntu): importance |
Undecided |
High |
|
| 2017-11-24 17:21:12 |
Scott Moser |
systemd (Ubuntu): status |
New |
Confirmed |
|
| 2017-11-24 17:21:16 |
Scott Moser |
systemd (Ubuntu): importance |
Undecided |
High |
|
| 2017-11-24 17:46:45 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Artful |
|
| 2017-11-24 17:46:45 |
Dimitri John Ledkov |
bug task added |
|
cloud-init (Ubuntu Artful) |
|
| 2017-11-24 17:46:45 |
Dimitri John Ledkov |
bug task added |
|
systemd (Ubuntu Artful) |
|
| 2017-11-24 17:46:45 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Bionic |
|
| 2017-11-24 17:46:45 |
Dimitri John Ledkov |
bug task added |
|
cloud-init (Ubuntu Bionic) |
|
| 2017-11-24 17:46:45 |
Dimitri John Ledkov |
bug task added |
|
systemd (Ubuntu Bionic) |
|
| 2017-11-24 17:46:45 |
Dimitri John Ledkov |
nominated for series |
|
Ubuntu Zesty |
|
| 2017-11-24 17:46:45 |
Dimitri John Ledkov |
bug task added |
|
cloud-init (Ubuntu Zesty) |
|
| 2017-11-24 17:46:45 |
Dimitri John Ledkov |
bug task added |
|
systemd (Ubuntu Zesty) |
|
| 2017-11-24 17:56:38 |
Scott Moser |
cloud-init (Ubuntu Artful): status |
New |
Confirmed |
|
| 2017-11-24 17:56:41 |
Scott Moser |
cloud-init (Ubuntu Artful): importance |
Undecided |
Medium |
|
| 2017-11-24 17:56:46 |
Scott Moser |
cloud-init (Ubuntu Artful): importance |
Medium |
High |
|
| 2017-11-24 17:56:51 |
Scott Moser |
systemd (Ubuntu Artful): status |
New |
Confirmed |
|
| 2017-11-24 17:56:55 |
Scott Moser |
systemd (Ubuntu Artful): importance |
Undecided |
High |
|
| 2017-11-24 17:56:58 |
Scott Moser |
systemd (Ubuntu Zesty): status |
New |
Confirmed |
|
| 2017-11-24 17:58:28 |
Scott Moser |
systemd (Ubuntu Zesty): status |
Confirmed |
Fix Released |
|
| 2017-11-24 17:58:39 |
Scott Moser |
cloud-init (Ubuntu Zesty): status |
New |
Fix Released |
|
| 2017-11-27 20:40:54 |
Scott Moser |
systemd (Ubuntu Bionic): assignee |
|
Canonical Foundations Team (canonical-foundations) |
|
| 2017-11-27 22:06:21 |
Ryan Harper |
bug |
|
|
added subscriber Ryan Harper |
| 2017-11-28 16:56:23 |
Scott Moser |
cloud-init (Ubuntu Bionic): importance |
High |
Critical |
|
| 2017-11-28 16:56:28 |
Scott Moser |
cloud-init (Ubuntu Artful): importance |
High |
Critical |
|
| 2017-11-28 16:56:35 |
Scott Moser |
systemd (Ubuntu Bionic): importance |
High |
Critical |
|
| 2017-11-29 16:09:17 |
Scott Moser |
description |
I use no-cloud to test the kernel in CI (I am maintainer of the bcache subsystem), and have been running it successfully under 16.04 cloud images from qemu, using a qemu command that includes:
-smbios "type=1,serial=ds=nocloud-net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud-metadata/linuxtst/"
As documented here:
http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html
Under the new 17.10 cloud images, this doesn't work: the network comes up, but name resolution doesn't work-- /etc/resolv.conf is a symlink to a nonexistent file at this point of the boot and systemd-resolved is not running. When I manually hack /etc/resolv.conf in the cloud image to point to 4.2.2.1 it works fine.
I don't know if nameservice not working is by design, but it seems like it should work. The documentation states:
"With ds=nocloud-net, the seedfrom value must start with http://, https:// or ftp://"
And https is not going to work for a raw IP address. |
I use no-cloud to test the kernel in CI (I am maintainer of the bcache subsystem), and have been running it successfully under 16.04 cloud images from qemu, using a qemu command that includes:
-smbios "type=1,serial=ds=nocloud-net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud-metadata/linuxtst/"
As documented here:
http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html
Under the new 17.10 cloud images, this doesn't work: the network comes up, but name resolution doesn't work-- /etc/resolv.conf is a symlink to a nonexistent file at this point of the boot and systemd-resolved is not running. When I manually hack /etc/resolv.conf in the cloud image to point to 4.2.2.1 it works fine.
I don't know if nameservice not working is by design, but it seems like it should work. The documentation states:
"With ds=nocloud-net, the seedfrom value must start with http://, https:// or ftp://"
And https is not going to work for a raw IP address.
Related bugs:
* bug 1734939: #include fails silently. |
|
| 2017-12-11 18:35:23 |
Dimitri John Ledkov |
systemd (Ubuntu Bionic): status |
Confirmed |
Fix Committed |
|
| 2017-12-14 13:53:53 |
Dimitri John Ledkov |
systemd (Ubuntu Artful): status |
Confirmed |
In Progress |
|
| 2018-01-03 19:24:22 |
Launchpad Janitor |
systemd (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2018-01-14 16:09:44 |
NauxLiu |
bug |
|
|
added subscriber NauxLiu |
| 2018-01-17 21:35:40 |
Scott Moser |
bug task deleted |
cloud-init (Ubuntu Bionic) |
|
|
| 2018-01-17 21:35:55 |
Scott Moser |
cloud-init (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2018-02-15 19:50:40 |
Francis Ginther |
tags |
|
id-5a1c7e7be1c6883c5a843d1f |
|
| 2018-02-22 18:12:33 |
Dimitri John Ledkov |
description |
I use no-cloud to test the kernel in CI (I am maintainer of the bcache subsystem), and have been running it successfully under 16.04 cloud images from qemu, using a qemu command that includes:
-smbios "type=1,serial=ds=nocloud-net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud-metadata/linuxtst/"
As documented here:
http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html
Under the new 17.10 cloud images, this doesn't work: the network comes up, but name resolution doesn't work-- /etc/resolv.conf is a symlink to a nonexistent file at this point of the boot and systemd-resolved is not running. When I manually hack /etc/resolv.conf in the cloud image to point to 4.2.2.1 it works fine.
I don't know if nameservice not working is by design, but it seems like it should work. The documentation states:
"With ds=nocloud-net, the seedfrom value must start with http://, https:// or ftp://"
And https is not going to work for a raw IP address.
Related bugs:
* bug 1734939: #include fails silently. |
[Impact]
* resolved does not start early enough in the boot-process preventing DNS resolution to be operational during early boot, for example as required by special early stages of cloud-init, resulting in failure to boot / provision the instance fully.
[Test Case]
* Boot container or a VM with a nocloud-net data source, and a URL pointing to the datasource as explained below
* Observe that boot completes and provisioning is successful
* Check that there are no dns-resolution errors in the cloud-init log / boot log
[Regression Potential]
* starting resolved earlier may prevent it from connecting to dbus, and may require a restart later on when re-triggered over dbus. This is on artful only, as in bionic resolved has gained ability to reconnected to dbus post-start. Backporting that, however, is too large for an SRU as it requires sd-bus changes.
[Other Info]
* Original bug report.
I use no-cloud to test the kernel in CI (I am maintainer of the bcache subsystem), and have been running it successfully under 16.04 cloud images from qemu, using a qemu command that includes:
-smbios "type=1,serial=ds=nocloud-net;s=https://raw.githubusercontent.com/mlyle/mlyle/master/cloud-metadata/linuxtst/"
As documented here:
http://cloudinit.readthedocs.io/en/latest/topics/datasources/nocloud.html
Under the new 17.10 cloud images, this doesn't work: the network comes up, but name resolution doesn't work-- /etc/resolv.conf is a symlink to a nonexistent file at this point of the boot and systemd-resolved is not running. When I manually hack /etc/resolv.conf in the cloud image to point to 4.2.2.1 it works fine.
I don't know if nameservice not working is by design, but it seems like it should work. The documentation states:
"With ds=nocloud-net, the seedfrom value must start with http://, https:// or ftp://"
And https is not going to work for a raw IP address.
Related bugs:
* bug 1734939: #include fails silently. |
|
| 2018-02-22 18:36:44 |
Brian Murray |
systemd (Ubuntu Artful): status |
In Progress |
Fix Committed |
|
| 2018-02-22 18:36:46 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2018-02-22 18:36:49 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2018-02-22 18:36:54 |
Brian Murray |
tags |
id-5a1c7e7be1c6883c5a843d1f |
id-5a1c7e7be1c6883c5a843d1f verification-needed verification-needed-artful |
|
| 2018-03-16 14:54:16 |
Scott Moser |
attachment added |
|
verification log on artful https://bugs.launchpad.net/cloud-init/+bug/1734167/+attachment/5081507/+files/lp-1734167-verify-artful.txt |
|
| 2018-03-16 14:54:43 |
Scott Moser |
tags |
id-5a1c7e7be1c6883c5a843d1f verification-needed verification-needed-artful |
id-5a1c7e7be1c6883c5a843d1f verification-done verification-done-artful |
|
| 2018-03-21 11:42:35 |
Launchpad Janitor |
systemd (Ubuntu Artful): status |
Fix Committed |
Fix Released |
|
| 2018-03-21 11:42:35 |
Launchpad Janitor |
cve linked |
|
2017-15908 |
|
| 2018-03-21 11:43:03 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2019-10-25 23:19:12 |
Joshua Powers |
cloud-init: status |
Confirmed |
Fix Released |
|
| 2019-10-25 23:19:16 |
Joshua Powers |
cloud-init (Ubuntu Artful): status |
Confirmed |
Won't Fix |
|
| 2019-10-25 23:19:31 |
Joshua Powers |
bug |
|
|
added subscriber Joshua Powers |
| 2023-05-11 08:00:13 |
James Falcon |
bug watch added |
|
https://github.com/canonical/cloud-init/issues/3065 |
|
