New Question

Truncating host name for Netbios compatibility

asked 2019-04-10 19:57:17 +0300

anonymous user


Randomly, we see working VMs running for 20+ days and then the name of the host is changed which causing issues in the AD domain. What is setting off the name change? We can't have cloudbase-init randomly renaming machines.

2019-03-04 12:21:59.755 1144 INFO cloudbaseinit.init [-] Executing plugins for stage 'MAIN': 2019-03-04 12:21:59.755 1144 INFO cloudbaseinit.init [-] Executing plugin 'SetHostNamePlugin' 2019-03-04 12:21:59.770 1144 DEBUG cloudbaseinit.utils.classloader [-] Loading class '' loadclass c:\program files\cloudbase solutions\cloudbase-init\python\lib\site-packages\cloudbaseinit\utils\ 2019-03-04 12:21:59.770 1144 DEBUG [-] Using cached copy of metadata: '2009-04-04/meta-data/local-hostname' _getcache_data c:\program files\cloudbase solutions\cloudbase-init\python\lib\site-packages\cloudbaseinit\metadata\services\ 2019-03-04 12:21:59.770 1144 WARNING cloudbaseinit.utils.hostname [-] Truncating host name for Netbios compatibility. Old name: frank-frank-2019-dir-ltsr---windows2016dc-scalr-1, new name: frank-frank-201 2019-03-04 12:21:59.786 1144 INFO cloudbaseinit.utils.hostname [-] Setting hostname: frank-frank-201

edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted

answered 2019-04-18 02:47:09 +0300

avladu gravatar image


You need to change cloudbase-init configuration accordingly. By default, netbioshostname_compatibility=True in the config file.

In the cloudbase-init config file you have to set:


Thank you,
Adrian Vladu

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


Asked: 2019-04-10 19:57:17 +0300

Seen: 931 times

Last updated: Apr 18 '19