Config drive ensure local-hostname

Bug #1061964 reported by Joshua Harlow
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
Joshua Harlow
cloud-init (Ubuntu)
Fix Released

Bug Description

Openstack writes out a metadata file with 'hostname' but most of cloud-init does not use this as the primary 'hostname' but instead uses 'local-hostname' (main effect being that the instance doesn't get named right when the set/update hostname modules are ran). So perform a similar action like the OVF datasource where we ensure that 'hostname' is copied over to 'local-hostname' if that key exists (and 'local-hostname' doesn't).

Example of this missing data:

Related branches

Joshua Harlow (harlowja)
description: updated
Changed in cloud-init:
assignee: nobody → Joshua Harlow (harlowja)
Scott Moser (smoser)
affects: ubuntu → cloud-init (Ubuntu)
Changed in cloud-init:
status: New → Fix Committed
importance: Undecided → Medium
Changed in cloud-init (Ubuntu):
status: New → In Progress
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package cloud-init - 0.7.0-0ubuntu2

cloud-init (0.7.0-0ubuntu2) quantal; urgency=low

  * config-drive: copy metadata entry 'hostname' to 'local-hostname' to fix
    config modules (set_hostname) will function as expected (LP: #1061964)
 -- Scott Moser <email address hidden> Fri, 05 Oct 2012 11:45:15 -0400

Changed in cloud-init (Ubuntu):
status: In Progress → Fix Released
Scott Moser (smoser)
Changed in cloud-init:
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.