Unused Disk 0 after creating proxmox vm:s unable to boot

I'm having a problem with deploying the docker swarm using the ansible playbooks in the premix, the playbooks creates the template and the vm:s correctly but when the vm-s startup they have no boot drive to boot from... anyone have any ideas? i had to change the required provider for terraform, since the later versions of proxmox are not compatible with the provider defined in the premix, maybe this is a issue...
11 Replies
funkypenguin | ElfHosted
mmm, maybe... what do your VMs look like (in the hardware tab)..?
3nm1
3nm1OP11mo ago
No description
funkypenguin | ElfHosted
Mmm, yeah something went wrong there, it didn’t attach the disk…
3nm1
3nm1OP11mo ago
I tried it with this provider instead: https://github.com/bpg/terraform-provider-proxmox
GitHub
GitHub - bpg/terraform-provider-proxmox: Terraform Provider for Pro...
Terraform Provider for Proxmox. Contribute to bpg/terraform-provider-proxmox development by creating an account on GitHub.
3nm1
3nm1OP11mo ago
Had to lower the disksizes, to put it on an ssd-drive instead of my NAS, will buy bigger ssd-drives today, and try again...
No description
3nm1
3nm1OP11mo ago
If i alter any settings in the premix, and run the playbook again will it edit the existing virtual machines? or create new ones?
funkypenguin | ElfHosted
that depends on the provider, and whether terraform "thinks" it can modify a VM or whether it has to recreate it. So IIRC, it depends on what settings you change.. terraform plan in the terraform directory (~/.terraform/funky-penguins-are-funky) should tell you whether a recreate or a change will be applied...
3nm1
3nm1OP11mo ago
Seems to be a lot of problems with the latest version of proxmox, many different forks of the terraform provider, none of them fully working with my setup, but they make different changes in the hardware setups... Might have to reverse the proxmox setup to version 7 or something to get this to work... 🙂
Shinobi Cat
Shinobi Cat8mo ago
hi there, i'm currently running into the same issues, did you manage to find out what's causing this?
3nm1
3nm1OP8mo ago
It's a matter of compability, the terraform providers either are not compatible with the latest version of proxmox, or the terraform code in the premix, is not compatible with other terraform providers that are compatible with the latest proxmox. I downgraded my proxmox to the latest version 7 and then it worked. But i actually ended up going with TechnoTims k3s solution with ansible instead: https://www.youtube.com/watch?v=CbkEWcUZ7zM
Techno Tim
YouTube
The FASTEST Way to run Kubernetes at Home - k3s Ansible Automation ...
Setting up kubernetes is hard. That's why we made it easy. Today we'll set up a High Availability K3s cluster using etcd, MetalLB, kube-vip, and Ansible. We'll automate the entire process giving you an easy, repeatable way to create a k3s cluster that you can run at home in a few minutes. This is a great way to set up Kubernetes in your Hom...
Want results from more Discord servers?
Add your server