Hey there,
I'm setting up our WHMCS environment to use the Proxmox VPS module from modulesgarden (https://www.modulesgarden.com/products/whmcs/proxmox-vps). I'm having an issue with the cloud init for KVM when provisioning, it picks up the custom disk size and applies it to the qemu disk when it's cloned but the partition and LVM for '/' do not get extended when it is cloned.
All the other settings such as IP addresses, usernames, passwords, ssh keys, RAM etc get pass along and applied correctly.
The template is a pretty basic install of CentOS 8.
Has anyone ran into this issue before with extending LVMs after creating a VM from a template and using cloud-init?
Thanks!
I'm setting up our WHMCS environment to use the Proxmox VPS module from modulesgarden (https://www.modulesgarden.com/products/whmcs/proxmox-vps). I'm having an issue with the cloud init for KVM when provisioning, it picks up the custom disk size and applies it to the qemu disk when it's cloned but the partition and LVM for '/' do not get extended when it is cloned.
All the other settings such as IP addresses, usernames, passwords, ssh keys, RAM etc get pass along and applied correctly.
The template is a pretty basic install of CentOS 8.
Has anyone ran into this issue before with extending LVMs after creating a VM from a template and using cloud-init?
Thanks!
