Additional nuance:
On a netplan enabled system also using cloud-init (+ curtin), the same
assertion is made regarding how to disable network functionality tied to
cloud-init is mentioned in /etc/netplan/50-cloud-init.yaml ("… disable
via stanza in
** Also affects: netplan
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640635
Title:
cloud-init creates /etc/network/interfaces.d/50-cloud-init.cfg even
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640635
Title:
We can tackle the other aspects of this on other tickets, but it does
seem like we have a good understanding of what is happening here. I want
to make sure we don't end up derailing slightly here from the "bug" as
it were (though it's not so much a bug, it appears)
Just operating from the
The way this is working in cloud-init seems to me to make some sense.
Basically, there are 3 places cloud-init can get its network configuration. In
order of increasing precedence:
1. datasource (only works for local datasources currently)
2. system configuration
3. kernel command line.
Kernel command line:
$ cat /proc/cmdline
BOOT_IMAGE=(http)/kernel initrd=initrd root=/dev/sda3 ro
netroot=iscsi:@169.254.0.2::3260::iqn.2015-02.oracle.boot:uefi crashkernel=auto
ip=dhcp iscsi_initiator=iqn.2015-10.oracle:2.1g1538-gb000393 LANG=en_US.UTF-8
console=ttyS0,9600 console=tty0
The
ok, so
Nov 10 17:17:26 ubuntu [CLOUDINIT] stages.py[INFO]: Applying network
configuration from cmdline bringup=False: {'version': 1, 'config': [{'subnets':
[{'gateway': '10.0.0.1', 'broadcast': '10.0.0.255', 'control': 'manual',
'type': 'dhcp', 'dns_nameservers': ['169.254.169.254'],
Trying another time. Again, clean instance. This time using a very
minimal cloud.cfg:
$ cat /etc/cloud/cloud.cfg
users:
- default
datasource_list: ['OpenStack']
datasource:
OpenStack:
metadata_urls: ['http://169.254.169.254']
timeout: 10
max_wait: 20
cloud_init_modules:
Clean instance, ran apt upgrade, and apt install cloud-init. I didn't
replace the cloud.cfg file with one of our format as I tried to keep
changes as minimal as possible, and the supplied one seems to work
sufficiently.
$ echo "network: {config: disabled}" | sudo tee
cloudinit/stages.py uses 'net.is_disabled_cfg()'.
I just verified on a fresh lxc container.
* boot system
* lxc exec x1
% echo "network: {config: disabled}" >
/etc/cloud/cloud.cfg.d/99-disable-network-config.cfg
% rm /etc/network/interfaces.d/50-cloud-init.cfg
% reboot
* lxc exec
10 matches
Mail list logo
