** Changed in: cloud-init
Status: Fix Committed = Fix Released
--
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/890501
Title:
EC2 cloud-init overwrites 127.0.1.1 in
This bug was fixed in the package cloud-init - 0.6.3~bzr497-0ubuntu1
---
cloud-init (0.6.3~bzr497-0ubuntu1) precise; urgency=low
* New upstream snapshot.
- cloud-config support for configuring apt-proxy
- selection of local mirror based on presense of 'ubuntu-mirror' dns
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = Medium
** Changed in: cloud-init
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
** Branch linked: lp:cloud-init
--
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/890501
Title:
EC2 cloud-init overwrites 127.0.1.1 in /etc/hosts on every reboot
To manage
This is fix-commited in cloud-init in revision 491
(http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/revision/491).
See the commit message there for more information.
** Changed in: cloud-init
Status: New = Fix Committed
** Changed in: cloud-init
Assignee: (unassigned)
On Tue, 15 Nov 2011, Eric Hammond wrote:
Scott: Your suggested approach works for me even though I can't find any
documentation on how this is supposed to work. Everything I read says
that 127.0.1.1 should be the canonical hostname of the instance. Do you
happen to have any pointers to the
** Description changed:
When running an EC2 instance of Ubuntu 11.10 Oneiric, cloud-init sets up
/etc/hosts with a default value for 127.0.1.1 looking something like:
127.0.1.1 ip-10-202-61-233.ec2.internal ip-10-202-61-233
I edit /etc/hosts to change this value to
** Description changed:
cloud-init sets up /etc/hosts with a default value for 127.0.1.1 looking
something like:
- 127.0.1.1 ip-10-202-61-233.ec2.internal ip-10-202-61-233
+ 127.0.1.1 ip-10-202-61-233.ec2.internal ip-10-202-61-233
I edit /etc/hosts to change this
--
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/890501
Title:
EC2 cloud-init overwrites 127.0.1.1 in /etc/hosts on every reboot
To manage notifications about this bug go to:
Thanks for the bug report.
I believe that you should be able to simply add an entry above the one labeled
'cloud-init'
$ grep -v :: /etc/hosts
127.0.0.1 localhost
127.0.1.2 superman.brickies.net superman
# The following lines are desirable for IPv6 capable hosts
# Added by cloud-init
Scott: Learn something new every day. I will give this a try.
** Changed in: cloud-init (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
** Changed in: cloud-init (Ubuntu)
Status: Incomplete = Invalid
--
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/890501
Title:
EC2 cloud-init overwrites 127.0.1.1 in
Scott: Your suggested approach works for me even though I can't find any
documentation on how this is supposed to work. Everything I read says
that 127.0.1.1 should be the canonical hostname of the instance. Do you
happen to have any pointers to the information you are alluding to with
IPv6 and
13 matches
Mail list logo
