SUSE sysconfig renderer enablement incomplete

Bug #1799301 reported by Robert Schweikert on 2018-10-22

This bug report will be marked for expiration in 57 days if no further activity occurs. (find out why)

This bug affects 5 people
Affects Status Importance Assigned to Milestone

Bug Description

With db50bc0d9 the sysconfig renderer was enabled for openSUSE and SUSE Linux Enterprise. This implementation is incomplete and network rendering for openSUSE and SLES is now completely broken.

Message in cloud-init.log:[ERROR]: Unable to render networking. Network config is likely broken: No available network renderers found. Searched through list: ['eni', 'sysconfig', 'netplan']

The issue is that the available() method in looks for

    expected_paths = [

in addition to ifup and ifdown. While ifup and ifdown are found the above scripts do not exists on openSUSE and SLES.

The equivalent to 'etc/sysconfig/network-scripts/network-functions' would be 'etc/sysconfig/network/functions.netconfig', there is no default ifdown-eth, any ifdown scripts would exist in
'etc/sysconfig/network/if-down.d' but this is empty by default.

One option is of course to not look for such specific location and "trust" that the necessary script for the given distro are installed. We would only check for ifup and ifdown commands as those are necessary. The underying distro implementation for script handling may not be as important here.

Alejandro (alebeta) wrote :

Fedora 29 is presenting the same problem today with last release.

Error message:

2018-11-01 11:19:30,680 -[ERROR]: Unable to render networking. Network config is likely broken: No available network renderers found. Searched through list: ['eni', 'sysconfig', 'netplan']

Also cloud-init is not running at new boot.

Ryan Harper (raharper) wrote :

Thanks for filing the issue.

Changed in cloud-init:
importance: Undecided → Medium
status: New → Confirmed
yct (juraj-vitko) wrote :

I would like to stress that this is still blocking the latest Fedora Rawhide (Fedora-Cloud-Rawhide-x86_64-20190812.n.0) as well as other cloud-init distros like Fedora-Cloud-30-1.2 or openSUSE-MicroOS.x86_64-16.0.0-Kubic.

Basically in all these distros this makes it impossible to initialize an instance using cloud-init (which is the main point of "cloud" distros).

Cloud CentOS 7 19.07 is still fine but I guess this is only because they update really slow.

Also, paradoxically, cloud Ubuntu Bionic/Disco are not affected by this.

I think the severity of this should be bumped up.

Ryan Harper (raharper) wrote :


Do you know what network configuration system is present in Fedora if it isn't sysconfig?

Do you have a URL to those cloud distro images?

Changed in cloud-init:
status: Confirmed → Incomplete
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers