Skip to content
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

FedoraCoreOS qemu args #385

Closed
danielraq opened this issue Aug 13, 2021 · 7 comments
Closed

FedoraCoreOS qemu args #385

danielraq opened this issue Aug 13, 2021 · 7 comments
Labels

Comments

@danielraq
Copy link

Hi
Is it possible to add qemu args to proxmox_vm_qemu? I need them to install fedora coreos and they need to be passed at the first boot. According to: coreos/fedora-coreos-tracker#736 proxmox will handle it

https://docs.fedoraproject.org/en-US/fedora-coreos/provisioning-qemu/
https://pve.proxmox.com/pve-docs/chapter-qm.html

@hellraiserinchief
Copy link

I was looking to provision a cluster to try out OKD and I was also looking at this field to install FCOS. Looks like there is a args argument in the qemu resource, which is undocumented. It is in the code, but haven't tested it yet.

https://github.com/Telmate/terraform-provider-proxmox/blob/master/proxmox/resource_vm_qemu.go#L138

@dcode
Copy link

dcode commented Dec 8, 2021

@hellraiserinchief I tried this and it works, except that only root has permissions to modify args

Error: 500 only root can set 'args' config

According to a comment on a related issue I ran into using Ansible (ansible-collections/community.general#1641 (comment)), this is non-negotiable. Unfortunately, in my case my root account is using MFA, which is just cumbersome. I did however manually run through this as a one-off. The API did force me to auth with root + password + otp... even so, it didn't show up in the qm showcmd output, and didn't get picked up by Fedora CoreOS either. :-(

@greenship24
Copy link

Thanks all. Can confirm it only works with root and even then with only root and password (no API token.)

I guess for now I will continue to provision with an env vars for that and keep an eye on the thread.

Thread to keep an eye on is here- https://forum.proxmox.com/threads/root-pam-token-api-restricted.83866/

For now it appears there is little demand for such a case and the chance to check for those "super" privs in the token isn't present at all.

@hellraiserinchief
Copy link

I tried this git repo from a small company who posted it on proxmox's forum : https://forum.proxmox.com/threads/howto-wrapper-script-to-use-fedora-coreos-ignition-with-proxmox-cloud-init-system-for-docker-workloads.86494/

Can confirm that it works on a standalone basis. I have to tie it to the provider and make it work.

@elsbrock
Copy link

It would make sense to get args documented though.

@github-actions
Copy link

This issue is stale because it has been open for 60 days with no activity. Please update the provider to the latest version and, in the issue persist, provide full configuration and debug logs

@github-actions github-actions bot added the stale label Apr 28, 2023
@github-actions
Copy link

github-actions bot commented May 3, 2023

This issue was closed because it has been inactive for 5 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants