vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/bms/image-creation-guide/en-us_topic_0100601386.html
guoyanyan fe8c0cf45c BMS Image Creation Guide 1109 
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-authored-by: guoyanyan <guoyanyan3@huawei.com>
Co-committed-by: guoyanyan <guoyanyan3@huawei.com>
2022-11-16 08:53:42 +00:00

3.9 KiB
Raw Permalink Blame History

What Do I Do If Cloudbase-Init Is Stopped on a Provisioned Windows BMS?

Symptom

If Cloudbase-Init is stopped after a Windows BMS is provisioned, and information "Failed to find trace ID description from Cloudbase-Init because the component triggering the trace is not installed or has been damaged. You can install or recover the component." is displayed, you need to reinstall Cloudbase-Init.

Solution

  1. Log in to the BMS using BMC and back up the .conf files in the C:\Program Files\Cloudbase Solutions\Cloudbase-Init\ directory and all the files in the LocalScripts directory.
  2. Download Cloudbase-Init from the official website.

    https://cloudbase.it/cloudbase-init/#download

  3. Click Remote Control on the BMC host management page.

    The remote control window is displayed.

  4. Click in the upper toolbar. Select Directory and click Browse.

    A dialog box is displayed.

  5. Select the Cloudbase-Init package and click Connect to upload it to the BMS. The CD-ROM drive read and install the Cloudbase-Init.
  6. Copy the files you backed up in step 1 to the new Cloudbase-Init directory.
  7. Restart the BMS and check whether Cloudbase-Init runs properly.
Parent topic: FAQ