DataSourceSmartOS ignores sdc:hostname

[ubuntu-server-builder]

This bug was originally filed in Launchpad as LP: #1765085

Launchpad details

affected_projects = ['cloud-init (Ubuntu)']
assignee = mgerdts
assignee_name = Mike Gerdts
date_closed = 2018-06-20T18:06:41.640920+00:00
date_created = 2018-04-18T14:39:45.391663+00:00
date_fix_committed = 2018-04-21T00:59:57.666649+00:00
date_fix_released = 2018-06-20T18:06:41.640920+00:00
id = 1765085
importance = medium
is_complete = True
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1765085
milestone = None
owner = mgerdts
owner_name = Mike Gerdts
private = False
status = fix_released
submitter = mgerdts
submitter_name = Mike Gerdts
tags = []
duplicates = []

Launchpad user Mike Gerdts(mgerdts) wrote on 2018-04-18T14:39:45.391663+00:00

In SmartOS, vmadm(1M) documents the hostname property as the way to set the VM's hostname. This property is available in the guest via the sdc:hostname metadata property. DataSourceSmartOS does not use this value. It currently sets the hostname from the following properties, the first one wins.

1. hostname
2. sdc:uuid

The order should be:

1. hostname
2. sdc:hostname
3. sdc:uuid

This allows a value that is set with 'mdata-put hostname newname' to take precedence over the hostname defined at deployment time.

[ubuntu-server-builder]

Launchpad user Scott Moser(smoser) wrote on 2018-04-21T00:59:56.447066+00:00

An upstream commit landed for this bug.

To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=23479881

[ubuntu-server-builder]

Launchpad user Chad Smith(chad.smith) wrote on 2018-05-25T20:11:49.646398+00:00

This bug is believed to be fixed in cloud-init in version 18.2-27-g6ef92c98-0ubuntu1~18.04.1. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

[ubuntu-server-builder]

Launchpad user Scott Moser(smoser) wrote on 2018-06-20T18:06:42.895439+00:00

This bug is believed to be fixed in cloud-init in version 18.3. If this is still a problem for you, please make a comment and set the state back to New

Thank you.