Randomly, we see where a VM is running for 20+ days and then we see this in the logs below. What is setting off this name change? This name change causes major outage. 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 'cloudbaseinit.osutils.windows.WindowsUtils' loadclass c:\program files\cloudbase solutions\cloudbase-init\python\lib\site-packages\cloudbaseinit\utils\classloader.py:27 2019-03-04 12:21:59.770 1144 DEBUG cloudbaseinit.metadata.services.base [-] 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\base.py:73 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
