New Question

Revision history [back]

click to hide/show revision 1
initial version

cloudbase-init errors intermittently after image is created

Hello, I have a Instance I created from a windows 2016 image (which already has installed). I added secure join domain to the unattend.xml file in the cloudbase folder. I then sysprep Instance pointing to the unattend.xml file, create a snapshot of image, from snapshot I create a volume and uploaded the volume to Image and allow users to build instances using that image. Here is the problem I can create 10 instances and out of the 10 - 2 would fail, or I could create 6 and 1 would fail ect... The good instances created I am able to join the domain with no problems.

I looked at the logs and it looks like cloudbase-init.log is trying to add the hostname - whereas the ones created properly cloudbase-init-unattend.log is where the hostname gets created. I would rather not have hostname created by openstack name and would like it to be the default windows name win-xxxxxx. We would rather not have our users (students) create server names in AD.

Any help would be great. I believe I am getting confused over the conf files. I am assuming cloudbase-init-unattend.conf file gets ran first as the logs show in cloudbase-init.logs show it skips because it was already done. Its almost like the cloudbase-init.conf gets ahead of the cloudbase-init-unattend.conf.

Thanks Kb269