cloud-init

service order is incorrect for SUSE distros

Bug #1799709 reported by Robert Schweikert on 2018-10-24

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. This requires that cloud-init.service starts before wicked, but at present the service is started after wicked.

See original description

Related branches

~rjschwei/cloud-init:serviceOrder

Merged into cloud-init:master

Ryan Harper: Approve on 2018-10-24

Server Team CI bot: Approve (continuous-integration) on 2018-10-24

Robert Schweikert (rjschwei) on 2018-10-24

Changed in cloud-init:
assignee:	nobody → Robert Schweikert (rjschwei)

Ryan Harper (raharper) on 2018-10-24

description:	updated
Changed in cloud-init:
status:	New → Confirmed

Revision history for this message

Server Team CI bot (server-team-bot) wrote on 2018-10-24:

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

Changed in cloud-init:
status:	Confirmed → Fix Committed

Revision history for this message

Ryan Harper (raharper) wrote on 2018-12-13: Fixed in cloud-init version 18.5.

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

Thank you.