Bug 1385172

Summary:	Writes NM_CONTROLLED=no into autogenerated network configuration
Product:	[Fedora] Fedora	Reporter:	Colin Walters <walters>
Component:	cloud-init	Assignee:	Garrett Holmstrom <gholms>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	25	CC:	adimania, apevec, gholms, Jan.van.Eldik, mattdm, shardy, s
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	cloud-init-0.7.8-2.fc25	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1413060 (view as bug list)		Environment:
Last Closed:	2016-10-18 11:29:43 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1413060

Description Colin Walters 2016-10-14 20:56:29 UTC

This breaks the current Atomic Host qcow2.

The likely  quick fix is to omit NM_CONTROLLED=no (hence enable it).

The better fix would be to change cloud-init back to not writing a network config unless one was provided.

Comment 1 Fedora Update System 2016-10-16 01:55:51 UTC

cloud-init-0.7.8-2.fc25 has been pushed to the Fedora 25 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-e96b704c39

Comment 2 Fedora Update System 2016-10-18 11:29:43 UTC

cloud-init-0.7.8-2.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.