| 2016-04-11 00:05:41 |
Scott Moser |
bug |
|
|
added bug |
| 2016-04-11 00:05:56 |
Scott Moser |
bug task added |
|
cloud-init |
|
| 2016-04-11 00:06:10 |
Scott Moser |
bug task added |
|
maas-images |
|
| 2016-04-12 13:13:51 |
Scott Moser |
cloud-init (Ubuntu): status |
New |
Confirmed |
|
| 2016-04-12 13:13:53 |
Scott Moser |
cloud-init (Ubuntu): importance |
Undecided |
High |
|
| 2016-04-12 13:13:56 |
Scott Moser |
cloud-init: status |
New |
Confirmed |
|
| 2016-04-12 13:13:58 |
Scott Moser |
cloud-init: importance |
Undecided |
High |
|
| 2016-04-12 13:14:00 |
Scott Moser |
maas-images: status |
New |
Confirmed |
|
| 2016-04-12 13:14:03 |
Scott Moser |
maas-images: importance |
Undecided |
Medium |
|
| 2016-04-15 19:10:16 |
Scott Moser |
description |
when i removed the symlink in the maas ephemeral image from /etc/network/interfaces
the iscsi root boot fails, and maas deployment would also fail. |
when i removed the symlink in the maas ephemeral image from /etc/network/interfaces the iscsi root boot fails, and maas deployment would also fail.
The real reason for the difference was that cloud-init was rendering 'auto' for the device that was brought up in the initramfs.
Instead it needs to leave it to be manually controled (no 'auto' or 'allow-hotplug'). |
|
| 2016-04-15 19:11:40 |
Scott Moser |
summary |
iscsi root boot fails without /etc/network/interfaces aid of cloud-initramfs-dyn-netconf |
network config of initramfs devices writes 'auto', breaking iscsi root boot |
|
| 2016-04-15 19:12:19 |
Scott Moser |
description |
when i removed the symlink in the maas ephemeral image from /etc/network/interfaces the iscsi root boot fails, and maas deployment would also fail.
The real reason for the difference was that cloud-init was rendering 'auto' for the device that was brought up in the initramfs.
Instead it needs to leave it to be manually controled (no 'auto' or 'allow-hotplug'). |
when i removed the symlink in the maas ephemeral image from /etc/network/interfaces the iscsi root boot fails, and maas deployment would also fail.
The real reason for the difference was that cloud-init was rendering 'auto' for the device that was brought up in the initramfs.
Instead it needs to leave it to be manually controled (no 'auto' or 'allow-hotplug').
Related bugs:
* bug 1570142: [open-isci] net-interface-handler needs updating for newer ifupdown |
|
| 2016-04-15 20:25:30 |
Launchpad Janitor |
branch linked |
|
lp:cloud-init |
|
| 2016-04-15 20:30:36 |
Launchpad Janitor |
branch linked |
|
lp:~smoser/ubuntu/xenial/cloud-init/pkg |
|
| 2016-04-15 21:18:55 |
Launchpad Janitor |
cloud-init (Ubuntu): status |
Confirmed |
Fix Released |
|
| 2021-11-01 19:32:37 |
James Falcon |
cloud-init: status |
Confirmed |
Fix Released |
|
| 2023-05-10 12:17:33 |
James Falcon |
bug watch added |
|
https://github.com/canonical/cloud-init/issues/2644 |
|
| 2024-02-13 14:13:43 |
Nick De Villiers |
maas-images: status |
Confirmed |
Fix Released |
|
