Comment 6 for bug 1810859

@Scott,

You are correct I was not very specific in the original description. I was more concerned about describing the general problem and the "race condition" to allow others that may experience similar problems to associate the issue with whatever they are seeing.

In our particular case, yes it is NoCloud, and in addition to just setting "ds=NoCloud" on the command line as a work around I added Ryan's suggestions to the SUSE bug.

The basic problem remains. When ds-identify runs and the source is not there, for whatever reason, then cloud-init by default gets disabled. In our specific case it just takes longer to attach the device that holds the config.