yahoo-eng-team team mailing list archive

[Chad Smith <1765085@xxxxxxxxxxxxxxxxxx>]

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.

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: cloud-init (Ubuntu)
     Assignee: (unassigned) => Chad Smith (chad.smith)

** Changed in: cloud-init
       Status: Fix Committed => Fix Released

** Changed in: cloud-init (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1765085

Title:
  DataSourceSmartOS ignores sdc:hostname

Status in cloud-init:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released

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.

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