ONBOOT not supported in SUSE distros

Bug #1799540 reported by Robert Schweikert
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
Fix Released
Undecided
Robert Schweikert

Bug Description

With db50bc0d9 the sysconfig renderer was enabled for openSUSE and SUSE Linux Enterprise. The current implementation renders ONBOOT=yes into ifcfg-* but this setting is not recognized and the device is not started by wicked. This should be rendered as STARTMODE=auto or for ONBOOT=no as STARTMODE=manual.

Related branches

Changed in cloud-init:
assignee: nobody → Robert Schweikert (rjschwei)
Revision history for this message
Server Team CI bot (server-team-bot) wrote :

This bug is fixed with commit 3f12012e to cloud-init on branch master.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=3f12012e

Changed in cloud-init:
status: New → Fix Committed
Revision history for this message
Chad Smith (chad.smith) wrote : Fixed in cloud-init version 19.1.

This bug is believed to be fixed in cloud-init in version 19.1. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in cloud-init:
status: Fix Committed → Fix Released
Revision history for this message
James Falcon (falcojr) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.