← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1202758] Re: hostname not resolvable on azure

 

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

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

  * debian/control: fix bad dependency on python-jsonpatch
    by build-depending on python-json-patch, so dh_python2
    can find the right package (LP: #1205358).
 -- Scott Moser <smoser@xxxxxxxxxx>   Fri, 26 Jul 2013 10:47:59 -0400

** Changed in: cloud-init (Ubuntu)
       Status: Confirmed => 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/1202758

Title:
  hostname not resolvable on azure

Status in Init scripts for use on cloud images:
  Fix Committed
Status in “cloud-init” package in Ubuntu:
  Fix Released

Bug description:
  
  $ sudo hostname
  sudo: unable to resolve host smfoo3
  smfoo3

  I think that this is because we've disabled MonitorHostName in
  walinuxagent.

  that code would actually:
   * get the hostname of the system
   * monitor every X seconds for changs in the output of 'hostname'
   * if achange was found, it would bounce the eth0 interface (ifdown eth0; ifup eth0) in order to have dhclient convey the hostname to the server.

  the odd part of that is that the platform what *gave* us the hostname
  (inside the ovf-env.xml).

  it woudl seem like cloud-init should do something like that also.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: cloud-init 0.7.3~bzr829-0ubuntu1
  ProcVersionSignature: User Name 3.10.0-3.12-generic 3.10.1
  Uname: Linux 3.10.0-3-generic x86_64
  ApportVersion: 2.11-0ubuntu1
  Architecture: amd64
  Date: Thu Jul 18 17:13:29 2013
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cloud-init
  UpgradeStatus: No upgrade log present (probably fresh install)

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