lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as Won't Fix.
** Changed in: cloud-init (Ubuntu Lucid)
Status: Confirmed = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cloud-init (Ubuntu Lucid)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
Will these changes be backported to lucid?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/596993
Title:
hostname handling needs improvement for elastic-ip and ebs start-stop
To
Scott,
I just tested a recent Maverick AMI and it does indeed correctly set the
hostname to the newly assigned internal domain name after a stop/start
sequence. So no need to open any other bugs on that score.
+ uname -n
ip-10-117-39-235
+ hostname -s
ip-10-117-39-235
+ hostname -d
cloud-init does a lot of things. I guess what I'm looking for is
whether cloud-init could be made to emit events as it works such that
other upstart jobs can listen for those events and then use them to
trigger their startup as opposed to waiting for the entire cloud-init
process to complete.
This fix is needed for Lucid as well.
I have a clustered filesystem that fails because of this bug. It relies
upon the hostname value always being set correctly.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in ubuntu.
** Also affects: cloud-init (Ubuntu Lucid)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in ubuntu.
https://bugs.launchpad.net/bugs/596993
Title:
hostname handling needs
As the ec2 meta-data, local-hostname, returns the long form of hostname,
I would also propose that an enhancement that a new ec2 meta-data attribute be
added:
local-shortname
that would return the short version of hostname such as is returned from
'hostname -s' on a properly configured
When hostname is properly working on a system all of the following
commands should work as expected:
#uname -n
#hostname -a
#hostname -s
#hostname -d
#hostname -f
#hostname
Source: http://www.debianadmin.com/change-hostname-or-server-name-of-a
-linux-machine.html
--
You received this bug
Running the following commands appears to correctly set all the forms of
hostname on my Lucid ec2 instance:
echo $(curl -s http://169.254.169.254/latest/meta-data/local-hostname)
| sed 's:\..*$::' /etc/hostname
/sbin/sysctl -w kernel.hostname=$(curl -s http://169.254.169.254/latest
Now since my cluster filesystem starts real early in the bootup (S20) I
need the hostname to be set correctly even earlier.
So that would probably require some upstart job to run at S10.
So now I need to see how cloud-init is doing this and if it is early in
the bootup.
--
You received this
On Thu, 20 Jan 2011, Gerry Reno wrote:
Running the following commands appears to correctly set all the forms of
hostname on my Lucid ec2 instance:
echo $(curl -s http://169.254.169.254/latest/meta-data/local-hostname)
| sed 's:\..*$::' /etc/hostname
/sbin/sysctl -w kernel.hostname=$(curl
12 matches
Mail list logo
