- https://bugs.launchpad.net/cloud-init/+bug/1799301 - SUSE sysconfig renderer enablement incomplete (This bugs sees cloud-init believing it should behave the same in RHEL/CentOS as in openSUSE, assuming /etc/sysconfig/network-scripts exists, when it's just /etc/sysconfig/network in SUSE)
- https://bugs.launchpad.net/cloud-init/+bug/1733226 - cloud-init-local service fails on SUSE distros (Wicked appears to be unique to SUSE, and it apparently expects the default gateway in `routes` instead of `ifcfg-eth0`. This is another easily overlooked difference when compared to RHEL)
SLES remains untested, but given that the "sles.py" distro loads the "opensuse.py" distro, I expect the same behaviour.
Possibly related to:
- https:/ /bugs.launchpad .net/cloud- init/+bug/ 1799301 - SUSE sysconfig renderer enablement incomplete (This bugs sees cloud-init believing it should behave the same in RHEL/CentOS as in openSUSE, assuming /etc/sysconfig/ network- scripts exists, when it's just /etc/sysconfig/ network in SUSE) /bugs.launchpad .net/cloud- init/+bug/ 1733226 - cloud-init-local service fails on SUSE distros (Wicked appears to be unique to SUSE, and it apparently expects the default gateway in `routes` instead of `ifcfg-eth0`. This is another easily overlooked difference when compared to RHEL)
- https:/
SLES remains untested, but given that the "sles.py" distro loads the "opensuse.py" distro, I expect the same behaviour.