Comment 8 for bug 1407842

Alessandro,

I believe I see where our processes differ. I am not using the automatic sysprep option within the cloudbase-init installer so I do not get the benefit of the SetupComplete.cmd script setting the cloudbase-init service to start= demand. I am performing a manual sysprep after the cloudbase-init completes using my own unattend.xml as I need to perform a few additional customizations. In my case, it appears that cloudbase-init is set to start= auto during the cloudbase-init installation. Without the extra commands in SetupComplete.cmd to delay the service start upon first boot, I get the race condition between the standalone and service instances of cloudbase-init during sysprep.

I think the current approach is reasonable where we assume that if a user does not choose to initiate a sysprep during the installation process, that they would want cloudbase-init set to start= auto upon next boot. We may want to somehow document what is happening in the background with the enable/delay options for the cloudbase-init service in these cases so others do not encounter the same error. Once you explained what is happening with the cloudbase-init service startup options in the two scenarios, the behavior made complete sense. :-)

Thanks!
-Curt