cloudbaseinit.osutils.windows [-] Waiting for sysprep completion

asked 2016-01-06 11:21:56 +0300

maestropandy
16 ●1 ●2 ●2

Hi All,

I have spawn windows server 2012 instance in my openstack and using cloudbase it for VM and while going to access seen error as "Console is currently unavailable. please try again later"

Found Cloudbase init logs

2016-01-05 18:20:41.282 1948 INFO cloudbaseinit.osutils.windows [-] Waiting for sysprep completion. GeneralizationState: 3 2016-01-05 18:20:42.298 1948 INFO cloudbaseinit.osutils.windows [-] Waiting for sysprep completion. GeneralizationState: 3 2016-01-05 18:20:43.313 1948 INFO cloudbaseinit.osutils.windows [-] Waiting for sysprep completion. GeneralizationState: 3 2016-01-05 18:20:44.313 1948 INFO cloudbaseinit.osutils.windows [-] Waiting for sysprep completion. GeneralizationState: 3 2016-01-05 18:20:45.328 1948 INFO cloudbaseinit.osutils.windows [-] Waiting for sysprep completion. GeneralizationState: 3 2016-01-05 18:20:46.328 1948 INFO cloudbaseinit.osutils.windows [-] Waiting for sysprep completion. GeneralizationState: 3 2016-01-05 18:20:47.345 1948 INFO cloudbaseinit.osutils.windows [-] Waiting for sysprep completion. GeneralizationState: 3 2016-01-05 18:20:48.359 1948 INFO cloudbaseinit.osutils.windows [-] Waiting for sysprep completion. GeneralizationState: 3 2016-01-05 18:20:49.359 1948 INFO cloudbaseinit.osutils.windows [-] Waiting for sysprep completion. GeneralizationState: 3 2016-01-05 18:20:50.375 1948 INFO cloudbaseinit.osutils.windows [-] Waiting for sysprep completion. GeneralizationState: 3 2016-01-05 18:20:51.375 1948 INFO cloudbaseinit.osutils.windows [-] Waiting for sysprep completion. GeneralizationState: 3 2016-01-05 18:20:52.375 1948 INFO cloudbaseinit.osutils.windows [-] Waiting for sysprep completion. GeneralizationState: 3 2016-01-05 18:20:53.391 1948 INFO cloudbaseinit.osutils.windows [-] Waiting for sysprep completion. GeneralizationState: 3 2016-01-05 18:20:54.391 1948 INFO cloudbaseinit.osutils.windows [-] Waiting for sysprep completion. GeneralizationState: 3 2016-01-05 18:20:55.391 1948 INFO cloudbaseinit.osutils.windows [-] Waiting for sysprep completion. GeneralizationState: 3 2016-01-05 18:20:56.391 1948 INFO cloudbaseinit.osutils.windows [-] Waiting for sysprep completion. GeneralizationState: 3 2016-01-05 18:20:57.407 1948 INFO cloudbaseinit.osutils.windows [-] Waiting for sysprep completion. GeneralizationState: 3 2016-01-05 18:20:58.407 1948 INFO cloudbaseinit.osutils.windows [-] Waiting for sysprep completion. GeneralizationState: 3 2016-01-05 18:20:59.423 1948 INFO cloudbaseinit.osutils.windows [-] Waiting for sysprep completion. GeneralizationState: 3 2016-01-05 18:21:00.423 1948 INFO cloudbaseinit.osutils.windows [-] Waiting for sysprep completion. GeneralizationState: 3 2016-01-05 18:21:01.423 1948 INFO cloudbaseinit.osutils.windows [-] Waiting for sysprep completion. GeneralizationState: 3 2016-01-05 18:21:02.438 1948 INFO cloudbaseinit.osutils.windows [-] Waiting for sysprep completion. GeneralizationState: 3 2016-01-05 18:21:02.907 1948 CRITICAL cloudbaseinit [-] IOError: [Errno 4] Interrupted function call 2016-01-05 18:21:02.907 1948 TRACE cloudbaseinit Traceback (most recent call last): 2016-01-05 18:21:02.907 1948 TRACE cloudbaseinit File "C:\Program Files (x86)\Cloudbase Solutions\Cloudbase-Init\Python27\Scripts\cloudbase-init-script.py", line 9, in <module> 2016-01-05 18:21:02.907 1948 TRACE cloudbaseinit loadentrypoint('cloudbase-init==0.9.6.dev265.gc1a3f38', 'consolescripts', 'cloudbase-init')() 2016-01-05 18:21:02.907 1948 TRACE cloudbaseinit File "C:\Program Files (x86)\Cloudbase Solutions\Cloudbase-Init\Python27\lib\site-packages\cloudbaseinit\shell.py", line 31, in main 2016-01-05 18:21:02.907 1948 TRACE cloudbaseinit init.InitManager().configurehost() 2016-01-05 ... (more)

edit retag flag offensive close merge delete

add a comment

2 answers

Sort by » oldest newest most voted

answered 2019-03-22 16:42:32 +0300

jghal
26 ●1 ●1 ●4

I am seeing the same "Waiting for sysprep completion. GeneralizationState: 3" repeating over and over in my cloudbase-init.log file. The first 3 lines of my log file are

2019-03-21 23:50:06.004 2752 INFO cloudbaseinit.init [-] Respawning current process with updated credentials.
2019-03-21 23:50:06.723 2796 INFO cloudbaseinit.init [-] Cloudbase-Init version: 0.9.11
2019-03-21 23:50:07.734 2796 INFO cloudbaseinit.osutils.windows [-] Waiting for sysprep completion. GeneralizationState: 3

And that last line is repeating for over 24 hours now. There is no cloud-init-unattend.log being generated.

I'm building images with Packer vmware-iso. My OS install autounattend.xml runs a powershell script that disables some power management (like turning of the network interface after idle, etc) and enables WinRM over https. Then Packer provisioners connect via WinRM to install VMWare Tools, reboot, install Cloudbase-init

$cbinit_params = @("/i", $cbinit_msi, "/qn", "/l*v", "C:\Windows\Temp\cloudbase-init-install-log.txt", "LOGGINGSERIALPORTNAME=COM1")
$cbinit_proc = Start-Process -FilePath msiexec.exe -ArgumentList $cbinit_params -Wait -Passthru
$cbinit_proc.WaitForExit()
if (-Not ($cbinit_proc.ExitCode -In @("0", "1641", "3010"))) {
    Write-EventLog -LogName 'Windows Powershell' -Source $ScriptName -EventID "105" -EntryType "Error" -Message

"Install of CloudBase-Init failed with status $cbinit_proc.ExitCode" } Start-Sleep -s 10

and run sysprep

"inline": [
    "cd \"C:\\Program Files\\Cloudbase Solutions\\Cloudbase-Init\\conf\"",
    "C:\\Windows\\System32\\Sysprep\\Sysprep.exe /generalize /oobe /quit /unattend:Unattend.xml",
    "Start-Sleep 20"
]

I use the /quit and Start-Sleep as I was concerned it was shuting down before it had actually finished.

edit flag offensive delete link

Comments

I would try your evaluation image, but they don't list vmware as supported hypervisor

jghal ( 2019-03-22 16:45:27 +0300 )edit

I ended up moving the sysprep to a cmd script on the floppy and running it as packer's shutdown script.

jghal ( 2019-04-05 16:49:28 +0300 )edit

add a comment

answered 2016-01-27 16:40:10 +0300

avladu

613 ●1 ●3 ●5

Hello,

"Console is currently unavailable. please try again later" is an OpenStack Horizon/Nova related issue and not directly related to cloudbase-init. This can be an issue with the integration between horizon and nova.

On the cloudbase-init issue, can you provide more details on the Windows image you have used? I have noticed that the version of the cloudbase-init on the image is 0.9.6. The current master version is 0.9.10. If possible, you can try using the evaluation images from our website: https://cloudbase.it/windows-cloud-im..., which have the stable 0.9.9 cloudbase-init version.

Thank you, Adrian

edit flag offensive delete link

add a comment

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

cloudbaseinit.osutils.windows [-] Waiting for sysprep completion

2 answers

Comments

Your Answer

Question Tools

Stats

Related questions

cloudbaseinit.osutils.windows [-] Waiting for sysprep completion edit

2 answers

Comments

Your Answer

Question Tools

Stats

Related questions

cloudbaseinit.osutils.windows [-] Waiting for sysprep completion