** Changed in: eucalyptus
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/475354
Title:
Hostname not set correctly on UEC cloud due to
This bug was fixed in the package ec2-init - 0.4.999-0ubuntu7.2
---
ec2-init (0.4.999-0ubuntu7.2) karmic-proposed; urgency=low
* fix install/upgrade failure if python2.4 is installed (LP: #520734)
* set hostname to a hostname-like value (ip-W-X-Y-Z) if instance
metadata
Ok, Verified and confirmed fixing.
I effectively get the right hostname without even a reboot.
Thanks !!
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
https://bugs.launchpad.net/bugs/475354
You received this bug notification because you are
Accepted ec2-init into karmic-proposed, the package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: ec2-init (Ubuntu
** Branch linked: lp:ubuntu/karmic-proposed/ec2-init
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
https://bugs.launchpad.net/bugs/475354
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
I've tested this on karmic released uec image (20100121):
$ hostname
172
$ echo deb http://archive.ubuntu.com/ubuntu/ karmic-proposed restricted main
multiverse universe | sudo tee /etc/apt/sources.list.d/proposed.list
$ sudo apt-get update
$ apt-cache policy ec2-init
ec2-init:
Installed:
** Changed in: ec2-init (Ubuntu Karmic)
Status: Fix Committed = In Progress
** Changed in: ec2-init (Ubuntu Karmic)
Assignee: Scott Moser (smoser) = Thierry Carrez (ttx)
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
Uploaded to -proposed
** Changed in: ec2-init (Ubuntu Karmic)
Status: In Progress = Triaged
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
https://bugs.launchpad.net/bugs/475354
You received this bug notification because you are a
** Branch linked: lp:~smoser/ec2-init/karmic-updates
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
https://bugs.launchpad.net/bugs/475354
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Also affects: ec2-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ec2-init (Ubuntu Lucid)
Status: New = Fix Released
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
https://bugs.launchpad.net/bugs/475354
You
** Also affects: cloud-init (Ubuntu Karmic)
Importance: Undecided
Status: New
** Also affects: ec2-init (Ubuntu Karmic)
Importance: Undecided
Status: New
** Also affects: eucalyptus (Ubuntu Karmic)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu
** Description changed:
UEC images use the local-hostname setting of the manifest data to set
the hostname. On Eucalyptus that appears to be set to the local ip
address - which doesn't work properly as the hostname obviously stops at
the first period it sees.
Hence you have a lot of
** Changed in: cloud-init (Ubuntu Karmic)
Status: Won't Fix = Invalid
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
https://bugs.launchpad.net/bugs/475354
You received this bug notification because you are a member of Ubuntu
Server
** Description changed:
UEC images use the local-hostname setting of the manifest data to set
the hostname. On Eucalyptus that appears to be set to the local ip
address - which doesn't work properly as the hostname obviously stops at
the first period it sees.
Hence you have a lot of
I'm in need of a sponsor for lp:~smoser/ubuntu/karmic/ec2-init/karmic-
updates . That branch contains fixes for bug 520734 and bug 475354 .
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
https://bugs.launchpad.net/bugs/475354
You received
** Changed in: ec2-init (Ubuntu Karmic)
Importance: Undecided = Medium
** Changed in: ec2-init (Ubuntu Karmic)
Status: New = Fix Committed
** Changed in: ec2-init (Ubuntu Karmic)
Milestone: None = karmic-updates
** Changed in: ec2-init (Ubuntu Karmic)
Assignee: (unassigned) =
fixed in cloud-init 0.5.3-0ubuntu1
** Changed in: cloud-init (Ubuntu Lucid)
Status: Triaged = Fix Released
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
https://bugs.launchpad.net/bugs/475354
You received this bug notification because
revno: 1172
committer: decker dec...@hawaii
branch nick: 1.6.2
timestamp: Fri 2010-02-05 04:04:49 -0800
message:
fix updating of vm state w/ dns info
** Changed in:
This bug was fixed in the package eucalyptus - 1.6.2~bzr1166-0ubuntu6
---
eucalyptus (1.6.2~bzr1166-0ubuntu6) lucid; urgency=low
* Merge from upstream bzr revision, should fix:
- LP: #475354 - send correct hostname in metadata service
- LP: #461464 - fix ec2 tools
** Branch linked: lp:ubuntu/eucalyptus
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
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
Any time you say the images should work around.., that means that
UEC's EC2 compatibility is -broken-. UEC should return a text hostname
(ip-a-b-c-d? instancename? no-dns-you-loser.euca-a-b-c-d? whatever.) in
the hostname field. Regardless of configuration. The spec you are
claiming compatibility
Dustin,
Which version of UEC are you using? Not managed to get internal DNS
working here (up2date 9.10 UEC). Cheers.
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
https://bugs.launchpad.net/bugs/475354
You received this bug notification
We're developing/testing 10.04 Lucid right now. 9.10 is closed to
development, for all but the most critical data-loss or security bugs.
:-Dustin
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
https://bugs.launchpad.net/bugs/475354
You
** Branch linked: lp:ubuntu/cloud-init
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
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
** Changed in: eucalyptus
Status: Invalid = In Progress
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
https://bugs.launchpad.net/bugs/475354
You received this bug notification because you are a member of Ubuntu
Server Team, which is
this is fixed with the 'ip-uuu.xxx.yyy.zzz' solution that Boris
suggested. (ec2-init was renamed to cloud-init)
** Package changed: ec2-init (Ubuntu Lucid) = cloud-init (Ubuntu Lucid)
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
A fix (note status change to In Progress) is in QA. Merge later
tonight.
On Thu, Feb 4, 2010 at 4:33 PM, Scott Moser smo...@canonical.com wrote:
this is fixed with the 'ip-uuu.xxx.yyy.zzz' solution that Boris
suggested. (ec2-init was renamed to cloud-init)
** Package changed: ec2-init
Dan, would enabling the Eucalyptus DNS feature actually fix this
problem? If so, then is there a good reason to disable it in the first
place?
--
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
Reopening eucalyptus and closing ec2-init task: looks like enabling DNS
on CLC is the right way to fix this.
** Changed in: eucalyptus (Ubuntu)
Status: Invalid = Triaged
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
** Changed in: ec2-init
** Changed in: eucalyptus (Ubuntu Lucid)
Importance: Medium = High
--
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
** Summary changed:
- Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data
+ Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
** Changed in: ec2-init (Ubuntu Lucid)
Status: Invalid = Triaged
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
https://bugs.launchpad.net/bugs/475354
You received this bug notification because you are a member of Ubuntu
Server Team,
** Changed in: eucalyptus (Ubuntu Lucid)
Importance: High = Wishlist
** Changed in: eucalyptus (Ubuntu Lucid)
Milestone: lucid-alpha-3 = ubuntu-10.04
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
https://bugs.launchpad.net/bugs/475354
Okay, worked on this a bit here today at the Distro Sprint.
We enabled Eucalyptus' DNS with: DISABLE_DNS=N in
/etc/eucalyptus/eucalyptus.conf.
This seems to work well enough to provide dynamically generated host
names to vm's. See:
RESERVATION r-43AC08FE admin default
INSTANCE
Unassigning myself. Anyone could theoretically document this. Hint
hint ;-)
** Changed in: eucalyptus (Ubuntu Lucid)
Assignee: Dustin Kirkland (kirkland) = (unassigned)
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
The cloud images should workaround this by using a ip-x-y-z-w hostname
whenever local-hostname returns an IP address.
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data (DNS)
https://bugs.launchpad.net/bugs/475354
You received this bug notification
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
To be clear, i understand Eucalytus has a mapping as described in the
url Dan Nurmi provided, but i am trying to understand if it is the job
of UEC to assign a proper hostname to its instances (even when DNS is
missing), or if it sole responsibility is to launch the instances, even
if they all end
Talking to Dan, it sounds like this should be solved in ec2-init, rather
than Eucalyptus.
** Also affects: ec2-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ec2-init (Ubuntu)
Status: New = Triaged
** Changed in: ec2-init (Ubuntu)
Importance: Undecided =
For those of us who aren't Dan, why would you solve an ec2
incompatibility with a distribution-specific workaround? Seems like
either a dns lookup (at startup and cached?) or a simple iterator
mapping (Hostname format: cloud-$1-$2-$3-$4.foo.com for example) would
be a proper fix.
--
Hostname not
This also badly breaks JBoss. I am not sure this is specific to Jboss,
as other java app servers will also most likely grab the wrong 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
This is not a bug in Eucalyptus: to get the hostname information there
DNS needs to be enabled. It is disabled by default for the UEC.
** Changed in: eucalyptus
Assignee: (unassigned) = chris grzegorczyk (chris-grze)
** Changed in: eucalyptus
Status: New = Invalid
--
Hostname not
Some more context: if the eucalyptus DNS feature is disabled (as it is
in the UEC, by default), then we cannot guarantee that the IP addresses
that are specified by the administrator resolve to an actual hostname
(as, often, users are choosing private/unroutable IP addresses for VMs).
Inventing a
As suggested, tried editing /etc/ec2-init/templates/hosts.tmpl and
replacing the $hostname var with a fixed value (ubuntu), rebundling and
restarted the instance still landed me in a shell: ubu...@172
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest data
ubu...@172:~$ cat /etc/ec2-init/templates/hosts.tmpl
127.0.0.1 localhost
127.0.1.1 ubuntu
# The following lines are desirable for IPv6 capable hosts
::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
** Also affects: eucalyptus
Importance: Undecided
Status: New
--
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
I think this might be more of a problem with ec2-init.
Regards
chuck
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = Medium
** Changed in: eucalyptus (Ubuntu)
Status: New = Incomplete
--
Hostname not set correctly on UEC cloud due to IP address in local-hostname
manifest
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
** Changed in: eucalyptus (Ubuntu)
Status: Incomplete = Triaged
--
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
49 matches
Mail list logo
