-
Notifications
You must be signed in to change notification settings - Fork 542
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
3.0.1-rc6 creating a proxmox_cloud_init_disk returns Error 500 #1196
Comments
Can you try to do this without "for_each" and only for single host? |
Hi, yes I did that as well. Same error. Is there some other way to attach a custom ci iso to a qemu_vm resource without putting it on the shared storage beforehand? Like creating it on a local volume and attaching it as cloudinit disk? Somehow disks of type cloudinit seem to be excempt from that rbd storage rule (are they even stored as iso images?). I just want to avoid having a second shared volume just for iso images when a disk of type cloud-init seems to be usable on a storage of type rbd. |
@kagehisa as far as i understand, you would have to set up another shared storage. Ceph has block and file storage, but they are separate storages. The iso gets treated as a file, while the cloud-init disk (while technically just an iso) gets created as a virtual disk. (Not too wel versed with ceph, so i might be mixing up the block and the file storage) |
@Tinyblargon thanks for the clarifiactation. Same is true for using |
I'm trying to reproduce the example code for creating a cloud-init disk resource from the docs.
My cluster uses a cephfs storage and so far no issue.
tofu validate
states my code is valid, but when I apply my code I get the following output (loglevel debug):My code is similar to the one in the docs except that I use "for_each".
Did I forget something or is there something I have to enable for our storage pool?
The text was updated successfully, but these errors were encountered: