Ubuntu
eucalyptus package

  1. Bug #475354
  2. Comment #11

Comment 11 for bug 475354

Revision history for this message
Boris Devouge (bdevouge) wrote : Re: Hostname not set correctly on UEC cloud due to IP address in local-hostname manifest data

Thanks for all comment and explanations for the DNS services of eucalyptus, however it is not accepted/possible in all cases, and not the whole issue.

There is still an issue where we do not get an full IP attributed as a hostname (which would help already assuming the uniqueness of hostnames and make things work), but only the first 3 digit, so '172' in the case as only the private IP space is visible from the instance.

The main issue is that '172' seems to break many things, Jboss running RMI on http://172:8083 but also other basic networking tools... and seems to not comply with what is an allowed hostname by convention. Could we not generate an unique hostname with random bits everytime, and let people the option then to edit / have them in DNS if desired?

Courtesy of Andrew Glen-Young, the following snippet of code, work around for current issue, not sure if it would help:

https://pastebin.canonical.com/27281/