[Bug 475354] Re: Hostname not set correctly on UEC cloud due to IP address in local-hostname manifest data

[Scott Moser]

> I think this might be more of a problem with ec2-init.

Just to be clear on what is happening here:

- eucalyptus is intending to provide an ec2 compatible meta-data service
  (described at
http://docs.amazonwebservices.com/AWSEC2/2009-04-04/DeveloperGuide/ ).
  that includes a field "local-hostname".
- on ec2, the value of 'local-hostname' is a fully qualified domain name
  that can also be looked up via the provided dns
  (example:ip-10-212-65-188.ec2.internal)
- on eucalyptus, the value of 'local-hostname' is the internal IP address
  (example: 192.168.1.194 or 172.123.1.2).
- ec2-init is utilizing local-hostname to set the hostname.  It is doing
  so by taking the first token of a dot-delimited string.

The result, is that on eucalyptus, the hostname is set to the decimal
value of the first octet of the ip address (ie "172").

We could work around this in ec2-init, and be smarter about setting
hostname, but the real issue is that the field 'local-hostname' contains
an IP address, not a "hostname".

-- 
Hostname not set correctly on UEC cloud due to IP address in local-hostname manifest data
https://bugs.launchpad.net/bugs/475354
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.