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

"memory.hugepages" / "cpu.affinity" have invalid values #422

Open
andrewcfitz opened this issue Oct 16, 2024 · 2 comments
Open

"memory.hugepages" / "cpu.affinity" have invalid values #422

andrewcfitz opened this issue Oct 16, 2024 · 2 comments
Labels
bug Something isn't working potential-upstream-issue The issue is potentially upstream

Comments

@andrewcfitz
Copy link

I am using the provider to make a full clone of a template. Everything works correctly the first run, and the vm works as expected.

However, the next time I run a preview I am met with the following errors:

error: proxmoxve:VM/virtualMachine:VirtualMachine resource 'dev' has a problem: expected hugepages to be one of ["1024" "2" "any"], got . Examine values at 'dev.memory.hugepages'.
error: proxmoxve:VM/virtualMachine:VirtualMachine resource 'dev' has a problem: invalid value for affinity (must contain numbers or number ranges separated by ','). Examine values at 'dev.cpu.affinity'.

I've tried ignoring memory.hugepages and cpu.affinity, but that doesn't help. I am not setting any properties in memory or cpu at all.

Is this a problem with the pulumi provider or the terraform provider?

@muhlba91
Copy link
Owner

generally speaking, this looks like an upstream issue to me where the retrieved values are not mapped properly (anymore). i raised one such issue upstream in the past because it broke the pulumi provider. could you please raise this issue upstream as well?

however, there was a property which raised a similar issue for me once. my workaround was to set the property in pulumi to its default value. did you try if this would solve your issue intermediary?

@muhlba91 muhlba91 changed the title Is this an upstream issue? "memory.hugepages" / "cpu.affinity" have invalid values Oct 16, 2024
@muhlba91 muhlba91 added bug Something isn't working potential-upstream-issue The issue is potentially upstream labels Oct 16, 2024
@Lewis-software
Copy link

I'm having the same bug. No matter what value I set, it gives me back the same error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working potential-upstream-issue The issue is potentially upstream
Projects
None yet
Development

No branches or pull requests

3 participants