Dear Chad. That you very much for those very detailed comment about
subiquity artifacts.
I did
root@ubuntutemplate:~# cloud-init clean --logs
root@ubuntutemplate:~# sudo rm -f /etc/netplan/00-installer-config.yaml
/etc/cloud/cloud.cfg.d/curtin-preserve-sources.cfg
/etc/cloud/cloud.cfg.d/99-inst
I certainly did not put one of those in there. But Subiquity did:
root@ubuntutemplate:~# cat
/etc/cloud/cloud.cfg.d/subiquity-disable-cloudinit-networking.cfg
network: {config: disabled}
I may not have noticed a warning of the installer regarding this, but in
case it did not warn about it, IMO i
Hmmm, Launchpad does not seem to like me to add the log files from
cloned VM "ubuntu01". Well, I confirmed that the provided log matches
what I see on the original "ubuntutemplate" VM so I bet this will do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
I can confirm the log lines you posted with exactly the same time stamp
on the affected VM.
One thing to note: There was already an initial cloud init setup
straight after the installation. I changed cloud-init.cfg and logging to
my needs afterwards. As far as I can remember also the initial
confi
I used "ubuntu-bug cloud-init" to report the bug. I do not see how the
logs it send should be incorrect. I did not disable network
configuration. I disable a lot of things I do not need, but initial
network configuration is mostly what I use cloud-init for. I made sure
the cloud init configuration
I believe the ISO to have the correct name as well:
root@ubuntutemplate:~# file -sk /dev/sr0
/dev/sr0: ISO 9660 CD-ROM filesystem data 'cidata'\012- (Lepton 3.x), scale
0-0, spot sensor temperature 0.00, unit celsius, color scheme 0,
calibration: offset 0.00, slope 0.00\012- (Lepto
Ah, and of course in order to send the additional data for this bug
report, I manually fixed up the network configuration.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958377
Title:
cloud-init doe
One more comment. I switched to
GRUB_CMDLINE_LINUX_DEFAULT="net.ifnames=0 biosdevname=0"
as well, in order to make sure cloud-init finds the network interface
after it did not work with "ens18".
However on the other Ubuntu LTS 20.04 VM I did not so this and cloud-
init generates a config with "s
Public bug reported:
I installed a new Ubuntu 20.04.3 LTS from server ISO yesterday to
prepare a new template for my Proxmox VE based training setup.
It works, but cloud-init does not apply network configuration from
NoCloud resource.
I have:
root@ubuntutemplate:~# cat /mnt/tmp/network-config
