Cloud-init network config not apply to system

Tumbleweed Cloud image does not includes wicked.(

As a result cloud-init network config will not apply to system.

1 Like

@bin456789 Hi and welcome to the Forum :smile:
Correct, wicked is deprecated in Tumbleweed, you will need to adapt for using NetworkManager.

But Tumbleweed Cloud image not includes NetworkManager as well.

@bin456789 Unfortunately I’m not using cloud-init :frowning_face:
Perhaps you need to change your source;

Else you could report as a bug… openSUSE:Submitting bug reports - openSUSE Wiki

+1 The Tumbleweed Cloud (Minimal VM) images are totally busted since this change.

cloud-init is pre-installed and enabled on the image (good) but its cloud-init network module cannot apply any type of network configuration because the pre-installed network module still expects systemd-network.

In case anyone isn’t familiar: the “network” YAML file provided to cloud-init is implementation-agnostic and not specific to wicked, NetworkManager, or any other management system. The guest image is responsible for adopting the configuration using its preferred management system. There’s nothing that users can do to mitigate this.

cloud-init fails with:

KeyError: "getpwnam(): name not found: 'systemd-network'"

The intent of this image flavor is to use cloud-init autoconfiguration, so it’s clear that there are no regression tests for Minimal VM.

Finally NetworkManager has beed add to tumbleweed cloud images after Snapshot 20231220.

But due to a bug on cloud-init.

cloud-init still fails with

KeyError: "getpwnam(): name not found: 'systemd-network'"

This bug has beed fixed.
But we still need to wait for next release of cloud-init, and next tumbleweed snapshot with it.