Bootstrap issue after interruption of the process

Bootstrap issue after interruption of the process

Hi,

In this blog I want to show you how you can fix a bootstrap crash. Can a bootstrap process crash? Yes it can! How?

  • Rebooting the VM during the process
  • Forgot to open all firewall ports
  • Unintendedly killing the process in windows
  • Reinstalling the daas agent

Problem:

In the DaaS agent log, which can be found here: “C:\Program Files (x86)\VMware\VMware DaaS Agent\service\logs\DaaS Agent”
You will see issues like.

2018-12-21 12:48:52 [INFO ] DaaS Agent – using dtcollector service @ 10.25.77.8
2018-12-21 12:48:52 [ERROR] DaaS Agent – Code: SOAP-ENV:Server; Actor: ; String: Cannot write part return. RPC/Literal parts cannot be null. (WS-I BP R2211)
2018-12-21 12:48:52 [INFO ] DaaS Agent – using dtcollector service @ 10.25.77.7
2018-12-21 12:48:52 [ERROR] DaaS Agent – Code: SOAP-ENV:Server; Actor: ; String: Cannot write part return. RPC/Literal parts cannot be null. (WS-I BP R2211)


2018-12-21 15:16:15 [INFO ] DaaS Agent – Successfully sent a request to fetch bootstrap credentials
2018-12-21 15:16:15 [INFO ] DaaS Agent – Bootstrap not done yet, waiting
2018-12-21 15:16:16 [INFO ] DaaS Agent – Bootstrap not done yet, waiting
2018-12-21 15:16:17 [INFO ] DaaS Agent – Bootstrap not done yet, waiting
2018-12-21 15:16:18 [INFO ] DaaS Agent – Bootstrap not done yet, waiting
2018-12-21 15:16:19 [INFO ] DaaS Agent – Bootstrap not done yet, waiting
2018-12-21 15:16:21 [INFO ] DaaS Agent – Timed out waiting for bootstrap, sending out a new request
2018-12-21 15:16:21 [INFO ] DaaS Agent – Successfully sent a request to fetch bootstrap credentials
2018-12-21 15:16:21 [INFO ] DaaS Agent – Bootstrap not done yet, waiting
2018-12-21 15:16:22 [INFO ] DaaS Agent – Bootstrap not done yet, waiting
2018-12-21 15:16:23 [INFO ] DaaS Agent – Bootstrap not done yet, waiting
2018-12-21 15:16:24 [INFO ] DaaS Agent – Bootstrap not done yet, waiting
2018-12-21 15:16:25 [INFO ] DaaS Agent – Bootstrap not done yet, waiting

And in the tenant portal the VM status of the DaaS agent under Imported VMs stays in the Unknown state.

Your hosting provider will probably see something like this in the desktone log: (guid is the guid of my problem VM)
2018-12-21 13:52:18,732 WARN  [com.desktone.collector.swiftmq.ChangeKeyWorker]-[pool-26-thread-30] CHANGEKEY message from fd3a4f40-1904-49cb-9739-02b89c1a1db8 discarded: signature validation failed

Cause:

The cause is that the bootstrap process is interrupted somehow. And the most common causes could be:

  • Rebooting the VM during the process
  • Forgot to open all firewall ports
  • Unintendedly killing the process in windows
  • Reinstalling the daas agent

Solution:

  1. Uninstall the DaaS agent
  2. Delete the DaaS agent folder
    • 64-bit “C:\Program Files (x86)\VMware\VMware DaaS Agent”
    • 32-bit “C:\Program Files\VMware\VMware DaaS Agent”
  3. Remove ” VMware DaaS Agent ” key from the registry
    • 64-bit “HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432NODE\VMware, Inc.”
    • 32-bit “HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.”
  4. Turn off the image
  5. Delete image from the t_general_machine tabel in the EDB database inside the tenant appliance.
  6. Turn on the VM
  7. Reinstall DaaS agent
  8. Try to convert to image again.

These steps fixed it for me 🙂

837 total views, 36 views today

Leave a Reply

Your email address will not be published. Required fields are marked *