A workaround for the dummy template issue could be editing it in the DB
and enabling password for it.
On 2024-10-23 19:46, tdtmusic2 wrote:
GitHub user tdtmusic2 created a discussion: Importing a vm from another
source - cloud-init issues
Hi everyone. Did any of you manage to switch to ACS from another
similar solution via the import feature? In my case I ended up with a
few issues, hopefully someone will point me in the right direction. The
current app has a number of vms on kvm hypervisors. The instances are
not in qcow2 format, they're img but ACS can import those too. My first
issue was with the template being applied to the imported vm, that
default or dummy import template - it's not password enabled. I
couldn't find a way to apply a different template on the vm other than
editing the template id directly in the database, so it would use one
that is password enabled (yes, I need that). The second issue is that
no matter how I try cloud-init does not work on the imported vm (I
apply user-data on them) but it does work on any instance created
directly in ACS. The imported vm also uses cloud-init and somehow it
seems there's a conflict somewhere, since user-data does not apply. If
I look at the output log of cloud-
init from that vm it does not seem to do anything, the only line that
I see related to cloud-init is about datasource: nocloud and seed:
/dev/sda, I have no idea what this is. If I do a cloud-init clean on
that vm then user-data from ACS works perfectly but I would really like
it to work right after importing the vm, if that's possible.
Anyone else having these issues so far?
Thank you!
GitHub link: https://github.com/apache/cloudstack/discussions/9846
----
This is an automatically sent email for users@cloudstack.apache.org.
To unsubscribe, please send an email to:
users-unsubscr...@cloudstack.apache.org
