DataSourceSmartOS ignores sdc:hostname

Bug #1765085 reported by Mike Gerdts
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init
Fix Released
Medium
Mike Gerdts
cloud-init (Ubuntu)
Fix Released
Undecided
Chad Smith
Nominated for Bionic by Chad Smith
Nominated for Cosmic by Chad Smith

Bug Description

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.

Related branches

Mike Gerdts (mgerdts)
Changed in cloud-init:
assignee: nobody → Mike Gerdts (mgerdts)
Mike Gerdts (mgerdts)
description: updated
Scott Moser (smoser)
Changed in cloud-init:
importance: Undecided → Medium
Scott Moser (smoser)
Changed in cloud-init:
status: New → Confirmed
Revision history for this message
Scott Moser (smoser) wrote :

An upstream commit landed for this bug.

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

Changed in cloud-init:
status: Confirmed → Fix Committed
Revision history for this message
Chad Smith (chad.smith) wrote : Fixed in cloud-init version 18.2-27-g6ef92c98-0ubuntu1~18.04.1.

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.

Changed in cloud-init (Ubuntu):
assignee: nobody → Chad Smith (chad.smith)
Changed in cloud-init:
status: Fix Committed → Fix Released
Changed in cloud-init (Ubuntu):
status: New → Fix Released
Revision history for this message
Scott Moser (smoser) wrote : Fixed in cloud-init version 18.3.

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.

Changed in cloud-init:
status: Fix Released → Fix Committed
status: Fix Committed → Fix Released
Revision history for this message
James Falcon (falcojr) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.