** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/720440
Title:
/etc/hosts is updated based on /etc/cloud/templates/hosts.tmpl
To
** Branch linked: lp:ubuntu/cloud-init
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/720440
Title:
/etc/hosts is updated based on /etc/cloud/templates/hosts.tmpl
--
ubuntu-bugs mailing list
ubuntu
This bug was fixed in the package cloud-init - 0.6.1-0ubuntu1
---
cloud-init (0.6.1-0ubuntu1) natty; urgency=low
* New upstream release.
* fix for puppet configuration options (LP: #709946) [Ryan Lane]
* fix pickling of DataSource, which broke seeding.
* turn resize_rootfs def
On Thu, 17 Feb 2011, Eric Hammond wrote:
> If the user has not modified the file since it was created from a
> template, then the system should feel free to continue maintaining that
> file by regenerating it from the template on reboot, instance
> stop/start, booting of a new instance of an AMI b
I would like to see a solution like the following for this and other
files generated at startup (e.g., apt sources):
If the user has not modified the file since it was created from a
template, then the system should feel free to continue maintaining that
file by regenerating it from the template o
fix was applied.
I actually like this for Eucalyptus when there is no dns being managed. Then
you wont get warnings from 'sudo' saying it doesn't know your hostname.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Importance: Undecided => Low
** Branch linked: lp:cloud-init
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/720440
Title:
/etc/hosts is updated based on /etc/cloud/templates/hosts.tmpl
--
ubuntu-bugs mailing list
ubuntu-bugs@l
Although there is something to be said for a more general solution that
lets arbitrary files be updated automatically, according to the user's
preferences.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
Hi Scott,
Your proposal works fine for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/720440
Title:
/etc/hosts is updated based on /etc/cloud/templates/hosts.tmpl
--
ubuntu-bugs mailing list
u
> If you decide that /etc/hosts should never be overwritten, then please
> at least remove /etc/cloud/templates/hosts.tmpl. But I'd prefer a
> compromise: perhaps if hosts.tmpl exists, then it is used to overwrite
> /etc/hosts, otherwise the original stands. That way a user who wants to
> disable t
I understand that overwriting /etc/hosts, just like overwriting
/etc/hostname and other important files, can cause problems, depending
on how names get assigned by the cloud and how the user wants to
configure the system. Similarly, _not_ overwriting them can cause
problems; in my case, I discovere
Thank you for opening this bug.
bug 407861 has more information on why this change was made.
We decided not to overwrite /etc/hosts, and let that stay user-managed.
It would be easy for you to add a upstart job or startup script to
handle this if you wanted.
I'm not 100% sold on the solution tha
12 matches
Mail list logo
