Not implemented error when creating VM

[alexwaibel]

Overview of the Issue

I was previously using the built in proxmox builder and am attempting to migrate to the latest release from this repo. I was able to init packer fine with the new required_plugins config but when I try to run the build it fails on the "Creating VM" step with a not implemented error. I don't see this error when using the builtin "proxmox" builder, only when I switch to using "proxmox-iso", but I need to switch to take advantage of the new efi_config options.

Reproduction Steps

I have a public repo with my packer files here.

Plugin and Packer version

Packer v1.8.5
Proxmox plugin v 1.1.1
Proxmox VE 7.3-4

Simplified Packer Buildfile

Gist with simplified buildfile.

Operating system and Environment details

Running packer in ubuntu 20.04.4 in wsl2

Log Fragments and crash.log files

Gist with logs

[sebastian-de]

Please note that there are still issues with the new efi_config parameter: #145

Regarding your issue: Can you try running your configuration with an already present iso_file instead of iso_url?
Uploading ISOs via the Proxmox API has always been problematic for me.

[zarichard]

I ran into the same issue using additional_iso_files with cd_files. Removing the additional_iso_files made it work (using iso_file option for the os iso so no other copying), or downgrading the plugin to 1.1.0 without any other changes also fixed it (ie, still using the additional_iso_files).

So to me it looks like something that was introduced in the latest release of the plugin.

[alexwaibel]

Thanks for the heads up about efi_config and the speedy response @sebastian-de. Switching to iso_file did resolve the error. I also tried downgrading to v1.1.0 per @zarichard suggestion and this also got past the error so I agree, seems to be a regression with iso handling introduced in the most recent release.

[sebastian-de]

Since the code for file upload didn't change since the last version of this plugin, this issue has to be related to updating proxmox-api-go. I suspect this is because of the introduction of HTTP headers.

[sebastian-de]

Wasn't easy to find the root cause of this, but it indeed was because of wrong HTTP headers.
I created a PR for proxmox-api-go: Telmate/proxmox-api-go#232
Once it's merged, I'll open a PR here to get the API updated.