Yeah I did stumble upon that bug when I was researching this issue last
week.
Thanks for all your help Scott.
--
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/1086646
Title:
On Fri, 7 Dec 2012, DaveQB wrote:
Yes actually I did fix that in a later boothook, but this is after I
went with the all-in-one boothook (that injects into rc.local to run a
shell script once network was up)
I see. So messing with the cloud.cfg broke the system. My bad.
Thanks for the time
Thanks for the info Scott.
To to clarify, I under you can user hostname in a cloud-config, the
problem I am solving is for autoscaling launch configuration and needing
a common base hostname (for config management purposes and only for
humans to identify) but unique amongst them.
So the host
Ok. There must be something up with my scripts then. Launching with your
user-data file Scott,
root@ip-10-199-0-143:~# cat userscript.log
=== Fri Dec 7 12:01:16 EST 2012: running
/var/lib/cloud/instance/scripts/my-userscript ===
root@ip-10-199-0-143:~# cat boothook.log
=== Fri Dec 7
#cloud-boothook
#!/bin/bash
if [ ! -f /etc/id ]
then
sed -i 's/preserve_hostname/preserve_hostname: True/g' /etc/cloud/cloud.cfg
sed -i 's/apt_preserve_sources_list/apt_preserve_sources_list: True/g'
/etc/cloud/cloud.cfg
It seems to me that the sed editing here might be creating invalid
Yes actually I did fix that in a later boothook, but this is after I
went with the all-in-one boothook (that injects into rc.local to run a
shell script once network was up)
I see. So messing with the cloud.cfg broke the system. My bad.
Thanks for the time Scott and sorry for sending you on a
Error in syntax. No bug here.
** 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/1086646
Title:
Hi,
Thanks for taking the time to open a bug and help in making Ubuntu better.
I'm not able to recreate the issue you're seeing. Working off the doc at
https://help.ubuntu.com/community/CloudInit . I've attached the user-data that
was created by write-mime-multipart, but here is what I did
Could you give me an example that fails?
Also, just fyi,
a.) you dont have to change /etc/cloud/cloud.cfg's value of preserve_hostname.
cloud-config input setting that will do the same thing as you were attempting.
b.) you can set the hostname by cloud-config input with 'hostname'.