Hello,
Indeed, scw-generate-network-config does create a circular dependancy
hence systemd ends up shooting the cloud-init unit which breaks the
cloud-init.process.
We are in the process of implementing cloud-init on our platform. Please
keep yourself up to date, there should be some
Yeah, there is a significant overlap between scw-generate-network-config and
cloud-init here.
I think it makes sense to align both approaches ;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Marking as not a bug as it feels like the resolution really needs to be
on the Scaleway platform with this script. Please feel free to re-open
this bug if you disagree. I may have misunderstood the intent.
Also, if scw-generate-network-config is in use on artful, bionic or
cosmic, it'll need to
This unit is generating network config which I thought would be owned
solely by cloud-init. Cloudinit should be generating a fallback network
configuration, which sets up dhcp on the primary nic (eth0/enp0s2 etc).
First you'll need to resolve the ordering cycle conflict with cloud-
init.service
I created another instance and did 'systemctl --no-pager disable scw-
generate-net-config' before installing cloud-init.
2 reboots later and things are still fine.
I think that counts as a workaround but I don't know systemd enough to
decide if someone is wrong here :-/
** Attachment added: "list-dependencies.txt"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1775086/+attachment/5148786/+files/list-dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
systemctl status cloud-init.service
● cloud-init.service - Initial cloud-init job (metadata service crawler)
Loaded: loaded (/lib/systemd/system/cloud-init.service; enabled; vendor
prese Active: inactive (dead)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
root@image-builder-scw-amd64:~# systemctl --no-pager status cloud-init.service
● cloud-init.service - Initial cloud-init job (metadata service crawler)
Loaded: loaded (/lib/systemd/system/cloud-init.service; enabled; vendor
preset: enabled)
Active: inactive (dead)
--
You received this bug
Thanks vincent for making cloud-init better please also attach the
output of the following:
systemctl list-dependencies output
and systemctl status cloud-init.service
from journal.txt I see
Jun 04 21:31:30.292811 image-builder-scw-amd64 systemd[1]: sysinit.target:
Breaking ordering cycle by
> user_data.txt: Error: [Errno 2] No such file or directory:
'/var/lib/cloud/instance/user-data.txt'
Fallout from /var/lib/cloud/instance being a dir rather than a symlink.
I empirically understood that this is caused by
cloudinit.util.write_file calling ensure_dir()
--
You received this bug
10 matches
Mail list logo
