Default Gateway is set in the wrong file in openSUSE
Bug #1805644 reported by
Zurdo
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Expired
|
Medium
|
Unassigned |
Bug Description
openSUSE's network renderer sets the gateway in `/etc/sysconfig
I'm using openSUSE Leap 15.0, OpenStack build downloaded from [here](https:/
Data source is `nocloud`, using the image generated by Proxmox. Attached.
To post a comment you must log in.
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.