Truncating host name for Netbios compatibility

[shaun]

Some of our users have been having issues with their machines randomly renaming themselves.

https://ask.cloudbase.it/question/2986/random-truncating-host-name-for-netbios-compatibility/
https://ask.cloudbase.it/question/2987/truncating-host-name-for-netbios-compatibility/

[shaun (shauncitrix)]

More logs

[shaun (shauncitrix)]

More logs

[Adrian Vladu (avladu)]

Hello,

When you create the image, you have to set in the cloudbase-init.conf and cloudbase-init-unattend.conf:

netbios_host_name_compatibility=false

Otherwise, the hostname received from the metadata will be truncated to 15 characters.

Thanks.

[shaun (shauncitrix)]

Hi Adrian,

Correct but it should only do this once when the computer first comes online, correct?

This is happening way later after a machine has been running a while and then all of a sudden and randomly it renames a machine.

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Adrian Vladu
Sent: Thursday, June 20, 2019 11:27 AM
To: Shaun Rothermel <email address hidden>
Subject: [Bug 1833569] Re: Truncating host name for Netbios compatibility

Hello,

When you create the image, you have to set in the cloudbase-init.conf and cloudbase-init-unattend.conf:

netbios_host_name_compatibility=false

Otherwise, the hostname received from the metadata will be truncated to
15 characters.

Thanks.

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1833569

Title:
  Truncating host name for Netbios compatibility

Status in cloudbase-init:
  New

Bug description:
  Some of our users have been having issues with their machines randomly renaming themselves.

  https://ask.cloudbase.it/question/2986/random-truncating-host-name-for-netbios-compatibility/
  https://ask.cloudbase.it/question/2987/truncating-host-name-for-netbios-compatibility/

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloudbase-init/+bug/1833569/+subscriptions

[Adrian Vladu (avladu)]

Got it, I verified the logs and it happens twice, as you said.

The reason is that it cannot find the OpenStack metadata and it fails back to the EC2 based metadata format which is provided by OpenStack too. The EC2 metadata provides another instance ID and it considers that the VM is new and unprovisioned.

The problem might be related to a slow connectivity at boot time. There are multiple ways you can make sure this situation does not happen.

You can set the in cloudbase-init configuration files to use only the OpenStack metadata and to increase the retry interval/counts to check for metadata:

metadata_services = cloudbaseinit.metadata.services.httpservice.HttpService
retry_count = 10 # default is 5
retry_count_interval = 10 # default is 4 (seconds)

Let me know if you need more information or if it solves the issue in your scenario.

[shaun (shauncitrix)]

Hi Adrian,

Can you please confirm the location of the cloud-init config file on windows?

(cloudbaseinit.metadata.services.httpservice.HttpService) is this the actual value or am I supposed to use or am I to replace this value with my own setting?

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Adrian Vladu
Sent: Thursday, June 20, 2019 1:34 PM
To: Shaun Rothermel <email address hidden>
Subject: [Bug 1833569] Re: Truncating host name for Netbios compatibility

Got it, I verified the logs and it happens twice, as you said.

The reason is that it cannot find the OpenStack metadata and it fails back to the EC2 based metadata format which is provided by OpenStack too. The EC2 metadata provides another instance ID and it considers that the VM is new and unprovisioned.

The problem might be related to a slow connectivity at boot time. There are multiple ways you can make sure this situation does not happen.

You can set the in cloudbase-init configuration files to use only the OpenStack metadata and to increase the retry interval/counts to check for metadata:

metadata_services = cloudbaseinit.metadata.services.httpservice.HttpService
retry_count = 10 # default is 5
retry_count_interval = 10 # default is 4 (seconds)

Let me know if you need more information or if it solves the issue in your scenario.

--
You received this bug notification because you are subscribed to the bug report.
https://bugs.launchpad.net/bugs/1833569

Title:
  Truncating host name for Netbios compatibility

Status in cloudbase-init:
  New

Bug description:
  Some of our users have been having issues with their machines randomly renaming themselves.

  https://ask.cloudbase.it/question/2986/random-truncating-host-name-for-netbios-compatibility/
  https://ask.cloudbase.it/question/2987/truncating-host-name-for-netbios-compatibility/

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloudbase-init/+bug/1833569/+subscriptions

[Adrian Vladu (avladu)]

Hello @shaun,

The cloudbase-init config usually stays in C:\Program Files\Cloudbase Solutions\Cloudbase-Init\conf\cloudbase-init.conf

You need to set in the group DEFAULT, the key metadata_services = cloudbaseinit.metadata.services.httpservice.HttpService

[DEFAULT]
metadata_services = cloudbaseinit.metadata.services.httpservice.HttpService

Thank you,
Adrian Vladu