smartos hostname assignment fails due to whitespace

Bug #1236445 reported by Ben Howard on 2013-10-07
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init (Ubuntu)

Bug Description

SmartOS uses whitespace when reporting the hostname via the meta-data source. As a result, the hostname assignment fails.

Simple fix:

=== modified file 'cloudinit/sources/'
--- cloudinit/sources/ 2013-10-05 01:05:21 +0000
+++ cloudinit/sources/ 2013-10-07 16:12:19 +0000
@@ -145,6 +145,7 @@

         if not md['local-hostname']:
             md['local-hostname'] = system_uuid
+ md['local-hostname'] = md['local-hostname'].strip()

         ud = None
         if md['user-data']:

Related branches

affects: ubuntu → cloud-init (Ubuntu)
description: updated
description: updated
Launchpad Janitor (janitor) wrote :

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

cloud-init (0.7.3-0ubuntu2) saucy; urgency=low

  * fix bug where a mount entry of 'ephemeral0' would only consider
    the unpartitioned device, not also the first partition (LP: #1236594)
 -- Scott Moser <email address hidden> Mon, 07 Oct 2013 20:16:02 -0400

Changed in cloud-init (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers