yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1383794@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package cloud-init - 0.7.7~bzr1055-0ubuntu1

---------------
cloud-init (0.7.7~bzr1055-0ubuntu1) vivid; urgency=medium

  * New upstream snapshot.
    * move to python3 (LP: #1247132)
    * systemd: run cloud-init before systemd-user-sessions.service
    * Use the GCE short hostname. (LP: #1383794)
    * Enable user-data encoding support for GCE. (LP: #1404311)
    * Update to use a newer and better OMNIBUS_URL
    * Be more tolerant of 'ssh_authorized_keys' types
    * Fix parse_ssh_config failing in ssh_util.py
    * Increase the robustness/configurability of the chef module.
    * retain trailing newline from template files when using
      jinja2 (LP: #1355343)
    * fix broken output handling (LP: #1387340)
    * digital ocean datasource
    * update url in config drive documentation
    * freebsd: enable correct behavior on Ec2.
    * freebsd: Use the proper virtio FreeBSD network interface name.
 -- Scott Moser <smoser@xxxxxxxxxx>   Wed, 11 Feb 2015 15:55:58 -0500

** 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/1383794

Title:
  [SRU] GCE datasource should use the short hostname

Status in Init scripts for use on cloud images:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Precise:
  New
Status in cloud-init source package in Trusty:
  New
Status in cloud-init source package in Utopic:
  New

Bug description:
  [IMPACT] Since GCE FQDN are usually longer than 64-characters, several
  hi-profile tools like Java and Hadoop may break.

  [FIX] Per GCE's recommendation, Linux instances should use the short
  hostname over the FQDN. This change sets the system hostname to the
  short name.

  [VERIFICATION]
  1. Install new cloud-init from proposed
  2. Re-run cloud-config:
     * 14.04/14.10: cloud-init single -n set_hostname --frequency=always
     * 12.04: cloud-init-cfg set_hostname always
  3. Check to make sure that the short name is used for /etc/hostname

  [RISK] This is a very low risk change. The actual change is a single
  line, and has test cases for 14.04 and 14.10. Further, since this
  change is only in the GCE datasource, it only affects GCE instances.

  [ORIGINAL REPORT]
  The GCE datasource uses the long hostname. Hostnames longer than 64 characters can break several tools.

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