New Question
0

Why does Config Drive metadata retrieval takes long?

asked 2022-09-18 11:27:04 +0300

matth7 gravatar image

updated 2022-09-18 11:29:33 +0300

The current version of Cloudbase is installed on Windows Server 2022. The configuration is done via Config Drive. It takes several minutes for these to be applied. The log shows that there are timeouts when checking an HTTP metaservice before the Config Drive metaservice is used. This process takes far too long. Is this normal behavior? Can the HTTP metaservice be disabled so that Config Drive is used directly?

Log:

2022-09-17 17:26:32.881 3764 DEBUG cloudbaseinit.utils.classloader [-] Loading class 'cloudbaseinit.osutils.windows.WindowsUtils' loadclass C:\Program Files\Cloudbase Solutions\Cloudbase-Init\Python\lib\site-packages\cloudbaseinit\utils\classloader.py:27 2022-09-17 17:26:33.959 3764 DEBUG cloudbaseinit.osutils.windows [-] Checking if service exists: cloudbase-init checkserviceexists C:\Program Files\Cloudbase Solutions\Cloudbase-Init\Python\lib\site-packages\cloudbaseinit\osutils\windows.py:1092 2022-09-17 17:26:33.959 3764 DEBUG cloudbaseinit.osutils.windows [-] Getting service username: cloudbase-init getserviceusername C:\Program Files\Cloudbase Solutions\Cloudbase-Init\Python\lib\site-packages\cloudbaseinit\osutils\windows.py:1225 2022-09-17 17:26:33.975 3764 DEBUG cloudbaseinit.osutils.windows [-] Resetting password for service user: .\cloudbase-init resetservicepassword C:\Program Files\Cloudbase Solutions\Cloudbase-Init\Python\lib\site-packages\cloudbaseinit\osutils\windows.py:1248 2022-09-17 17:26:34.022 3764 DEBUG cloudbaseinit.osutils.windows [-] Setting service credentials: cloudbase-init setservicecredentials C:\Program Files\Cloudbase Solutions\Cloudbase-Init\Python\lib\site-packages\cloudbaseinit\osutils\windows.py:1208 2022-09-17 17:26:34.022 3764 INFO cloudbaseinit.init [-] Respawning current process with updated credentials. 2022-09-17 17:26:34.022 3764 DEBUG cloudbaseinit.osutils.windows [-] Creating logon session for user: .\cloudbase-init createuserlogonsession C:\Program Files\Cloudbase Solutions\Cloudbase-Init\Python\lib\site-packages\cloudbaseinit\osutils\windows.py:649 2022-09-17 17:26:34.069 3764 DEBUG cloudbaseinit.osutils.windows [-] Executing process as user, command line: ['C:\Program Files\Cloudbase Solutions\Cloudbase-Init\Python\Scripts\cloudbase-init', '--config-file', 'C:\Program Files\Cloudbase Solutions\Cloudbase-Init\conf\cloudbase-init.conf', '--noresetservicepassword'] executeprocessasuser C:\Program Files\Cloudbase Solutions\Cloudbase-Init\Python\lib\site-packages\cloudbaseinit\osutils\windows.py:703 2022-09-17 17:26:35.319 844 DEBUG cloudbaseinit.utils.classloader [-] Loading class 'cloudbaseinit.osutils.windows.WindowsUtils' loadclass C:\Program Files\Cloudbase Solutions\Cloudbase-Init\Python\lib\site-packages\cloudbaseinit\utils\classloader.py:27 2022-09-17 17:26:35.631 844 INFO cloudbaseinit.init [-] Cloudbase-Init version: 1.1.2 2022-09-17 17:26:35.631 844 DEBUG cloudbaseinit.utils.classloader [-] Loading class 'cloudbaseinit.plugins.common.mtu.MTUPlugin' loadclass C:\Program Files\Cloudbase Solutions\Cloudbase-Init\Python\lib\site-packages\cloudbaseinit\utils\classloader.py:27 2022-09-17 17:26:35.678 844 DEBUG cloudbaseinit.utils.classloader [-] Loading class 'cloudbaseinit.plugins.windows.ntpclient.NTPClientPlugin' loadclass C:\Program Files\Cloudbase Solutions\Cloudbase-Init\Python\lib\site-packages\cloudbaseinit\utils\classloader.py:27 2022-09-17 17:26:35.694 844 DEBUG cloudbaseinit.utils.classloader [-] Loading class 'cloudbaseinit.plugins.common.sethostname.SetHostNamePlugin' loadclass C:\Program Files\Cloudbase Solutions\Cloudbase-Init\Python\lib\site-packages\cloudbaseinit\utils\classloader.py:27 2022-09-17 17:26:35.709 844 DEBUG cloudbaseinit.utils.classloader [-] Loading class 'cloudbaseinit.plugins.windows.createuser.CreateUserPlugin' loadclass C:\Program ...

(more)
edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted
0

answered 2022-09-19 18:17:00 +0300

avladu gravatar image

Hello,

Cloudbase-Init has two stages, one running during the sysprep stage (running once at first boot) with config-file cloudbase-init-unattend.conf and the Windows service stage (running at every boot) with config-file cloudbase-init.conf.

By default, the unattend stage is configured to use config drive first, while the normal stage is configured to use http metadata first, and only after it timeouts, it falls back to config-drive (and other metadata types).

If your setup has only config drive metadata, please set in both configuration files to use only the config drive:

[DEFAULT] metadata_services=cloudbaseinit.metadata.services.configdrive.ConfigDriveService,

More information can be found here:

https://cloudbase-init.readthedocs.io...

Thank you,
Adrian

edit flag offensive delete link more

Your Answer

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

Add Answer

Question Tools

1 follower

Stats

Asked: 2022-09-18 11:27:04 +0300

Seen: 32 times

Last updated: Sep 19