Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1517087

Summary: wait for anaconda to finish
Product: Red Hat Enterprise Linux 7 Reporter: Dan Kenigsberg <danken>
Component: cloud-initAssignee: Ryan McCabe <rmccabe>
Status: ASSIGNED --- QA Contact: Vratislav Hutsky <vhutsky>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3CC: jbadiapa, jgreguske, lars, mavital, mmagr, mrunge
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Dan Kenigsberg 2017-11-24 07:35:13 UTC
Sorry about this logless, versionless bug. However, I believe that I've seen a race between anaconda and cloud-init inside a guest.

cloud init was running, created proper ifcfg files, only to be written by stock content provided by anaconda. I think that cloud-init should modify the guest only after anaconda has finished.