Comments (7)
Thanks for the report @Neels-v-Wyk! Definitely, there is something interesting going on, I haven't seen such behaviour before. Would you mind provide some extra details?
If you deploy just one VM, does it work?
Is it always failing on server-01
? Could you try reverse order of the servers?
Is there any errors in tasks lists on the cluster?
from terraform-provider-proxmox.
If you deploy just one VM, does it work?
Yup! Setting the count
to 1
results in one working vm on server-01. Setting it to 2 results in one broken one on server-01 and a working one on server-02. Interestingly enough, setting the servers to be created by trying to reverse the count 3 - count.index
yields the same result, I think probably because terraform doesn't creating things in order but in parrallel, so this would make no difference
Is there any errors in tasks lists on the cluster?
No task errors, no errors in the logs either. It seems that the creation process is working, I'm assuming this is something to do with how the machine starts
Explicitly excluding server-01 form being selected for creating VMs and only creating them on 02 and 03, both still get created correctly :(
...
Alright, I tried a few more things and ended up reinstalling proxmox on server-01 and re joining it to the cluster. Everything is working now, consistently. I wish I had more info on why this worked when creating 1 VM but not multiple. I'll close this issue for now and reopen it if it happens again but it seems like I must have messed something up myself
from terraform-provider-proxmox.
Heck, the issue is back. I can't terraform apply -destroy
and then terraform apply
again without making it happen. Something that does seem to help though is rebooting the first server, then it works for one instance of terraform apply
and a subsequent destroy
from terraform-provider-proxmox.
That is no longer the case ^, I am consistently getting the same issue again :(
from terraform-provider-proxmox.
This seems to be a ZFS related issue. I deleted my ZFS pool and recreated another one, and then nothing started coming up. I deleted my ZFS pool again and extended local-lvm to make use of the freed up space, and now everything works.
I also attempted to use a different proxmox node as the entrypoint but that still resulted on the vm on server-01 not having a boot disk
from terraform-provider-proxmox.
Hi @Neels-v-Wyk!
Was you able to sort things out? Do you need any support from the provider's side?
From what I'm reading here, there seems to be an obscure issue with the Proxmox ZFS storage that prevents VM from a normal boot.
Realistically, I don't think provider / terraform can do anything about it, except maybe set parallelism to 1, so only one VM is provisioned at a time?
from terraform-provider-proxmox.
Interesting! I don't know if that will solve the problem but I think it's a step in the right direction. I'll have to try this later, I'll get back to you if there's any new results
from terraform-provider-proxmox.
Related Issues (20)
- Cannot use cloudinit with initialization HOT 1
- Disk resize for VM not updated in terraform state HOT 15
- CD-ROM is not attached when creating a VM from scratch HOT 1
- Not sure why I have these issue HOT 2
- Cannot Set Disk Passthrough Serial
- Terraform unable to set CIUPGRADE config, regardless of running as root or not, using API token HOT 3
- proxmox_virtual_environment_user_token is not idempotent if no expiration_date is set HOT 1
- Idempotence issues in "proxmox_virtual_environment_vm" after cloning from another VM HOT 3
- Support provider_override HOT 4
- Document which is the latest compatible version for Proxmox 7.4 HOT 1
- Align Defaults with Proxmox Defaults HOT 1
- Error: unknown time zone HOT 3
- HTTP 596 response Connection timed out in proxmox_virtual_environment_file HOT 1
- disk resize fails: error waiting for VM disk resize: All attempts fail: HOT 2
- Allow VM clone to pass with warnings HOT 3
- Missing "none" and "VirGL" to VGA type in proxmox_vm proxmox_virtual_environment_vm HOT 1
- Container volume mount backup flag defaults to true in provider but false in Proxmox, so volume mounts are created with the flag missing. HOT 1
- 0.58.0 VM resource: `expected clipboard to be one of ["vnc"], got .` HOT 1
- Selection of the components you want to be hotpluggable HOT 1
- error creating clonr vm linked clone HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from terraform-provider-proxmox.