Original Message-
> From: jordan j
> Sent: Tuesday, August 13, 2024 6:26 PM
> To: [email protected]
> Cc: [email protected]
> Subject: Re: Cloud-Init not working as per Cloudstack documentation
>
> Hello Granwille,
>
> Disable the network from system_in
6:26 PM
To: [email protected]
Cc: [email protected]
Subject: Re: Cloud-Init not working as per Cloudstack documentation
Hello Granwille,
Disable the network from system_info and try again.
I have found that cloud-init has issues with handling networking on some os-es
and because of th
Hi Jordan,
Thank you, I did try that with my latest template, I had this in place:
root@host cloud]# cat cloud.cfg
network:
config: disabled
users:
- default
system_info:
default_user:
name: root
disable_root: false
ssh_deletekeys: false
cloud_init_modules:
- seed_random
- boot
Hello Granwille,
Disable the network from system_info and try again.
I have found that cloud-init has issues with handling networking on some
os-es and because of that it does not start properly.
Unfortunately I have not spent time on research of "Why".
echo "system_info:
default_user:
name
Hi Ruben
Thank you very much, I have watched this and all other related online
videos to best assist with this. I can 100% confirm when I curl the
virtual router from the VM that I see the userdata perfectly fine, but
something keeps overwriting my custom changes when I boot the VM.
Something
Hi Granwille,
Wido has done a great talk about cloudinit. Check it out here:
https://www.youtube.com/watch?v=seknX44Ktfc. You can check the details of
your supplied userdata in the virtual router to see whether what you stored
in the UI/API is what is supplied to the VM.
On Fri, Aug 9, 2024 at 11
Hi Guys
Any help on this? Surely I am using *userdata* right via the UI? Or
should I log this on GitHub instead?
On 8/8/24 10:32, Granwille Strauss wrote:
Hi
I push *userdata* manually when I deploy a VM and still it does not
want to work:
I have this in place now:
#cloud-config
hostna
Hi
I push *userdata* manually when I deploy a VM and still it does not want
to work:
I have this in place now:
#cloud-config
hostname: hostname.example.com
fqdn: hostname.example.com
prefer_fqdn_over_hostname: true
create_hostname_file: true
preserve_hostname: true
Screenshot:
https://www
Hi
Thank you, you were right. After creating a new template and having the
root last, the growfs worked 100%. Thank you for this.
This now brings me to *userdata* in cloudstack that's not working. I
registered a new userdata in the UI:
#cloud-config hostname: {{ ds.meta_data.custom_hostname
Hello,
Can’t say about everything you mentioned, but regarding the disk resizinng I
can share my experience, I also had some issues before I managed to get it
working. So, from what I’ve searched, growpart does not seem to work with lvm
(could be wrong here though), so basic partitioning it is.
10 matches
Mail list logo
