packer creating a template in proxmox environment is giving errors.

[AkhilaGarlapally]

When filing a bug, please include the following headings if possible. Any
example text in this template can be deleted.

Overview of the Issue

facing error as proxmox: Error creating VM: Error creating VM: 400 Parameter verification failed., error status: {"errors":{"net0":"invalid format - unable to parse network options\n","scsi0":"invalid format - unable to parse drive options\n"},"data":null} (params: map[agent:0 boot: cores:2 cpu:kvm64 description:Packer ephemeral build VM hotplug: ide2:local:iso/CentOS-8.3.2011-x86_64-dvd1.iso,media=cdrom kvm:false memory:2048 name:packer-60be4925-9e43-cbc6-b9d2-3266279a731c net0:e1000=D2:08:62:1A:5F:E2,bridge=vmbr0,tag=10,firewall=false numa:false onboot:false ostype:l26 scsi0:vmpool:8,iothread=false scsihw:lsi sockets:1 tags: vmid:106])

Reproduction Steps

Steps to reproduce this issue

Packer version

I'm using packer 1.7.2

Simplified Packer Buildfile

I have taken the sample template from a github and have modified the variable according to our environment. Below is the input json file
"builders": [
{
"type": "proxmox",
"username": "{{user proxmox_username}}",
"password": "{{user proxmox_password}}",
"proxmox_url": "{{ user proxmox_url}}",
"insecure_skip_tls_verify": true,
"node": "{{user proxmox_node}}",
"os": "l26",
"boot_command": [
" text ks=http://{{ .HTTPIP }}:{{ .HTTPPort }}/ks.cfg"
],
"network_adapters": [
{
"bridge": "vmbr0",
"model": "e1000",
"vlan_tag": 10
}
],
"disks": [
{
"type": "scsi",
"disk_size": "8G",
"storage_pool": "{{user proxmox_storage_pool}}",
"storage_pool_type": "{{user proxmox_storage_pool_type}}",
"format": "{{user proxmox_storage_format}}",
"cache_mode": "none"
}
],
"scsi_controller": "lsi",
"iso_file": "{{user proxmox_iso_pool}}/{{user centos_image}}",
"boot_wait": "10s",
"cores": "2",
"memory": "2048",
"http_directory": "centos7",
"ssh_username": "root",
"ssh_password": "Packer",
"ssh_port": 22,
"ssh_timeout": "15m",
"unmount_iso": true,
"template_name": "{{user template_name}}",
"template_description": "{{user template_description}}",
"qemu_agent": false,
"disable_kvm": true

}

],
"provisioners": [
{
"type": "shell",
"inline": [
"yum install -y cloud-init qemu-guest-agent cloud-utils-growpart gdisk",
"shred -u /etc/ssh/_key /etc/ssh/_key.pub",
"rm -f /var/run/utmp",
">/var/log/lastlog",
">/var/log/wtmp",
">/var/log/btmp",
"rm -rf /tmp/* /var/tmp/",
"unset HISTFILE; rm -rf /home//.*history /root/.*history",
"rm -f /root/*ks",
"passwd -d root",
"passwd -l root"
],
"only": ["proxmox"]
}
]
}

Operating system and Environment details

we are using proxmox 4.1 version and i'm trying to build centos

[sylviamoss]

Hey there, could you provide more of your logs so that we can know in which step the error is occurring?

[ghost]

This issue has been automatically migrated to hashicorp/packer-plugin-proxmox#21 because it looks like an issue with that plugin. If you believe this is not an issue with the plugin, please reply to hashicorp/packer-plugin-proxmox#21.

[AkhilaGarlapally]

Hi , That is the output I got from packer build command how can I get more logs. Could you please let me know is there any other command to know the logs in detail??

…

On Tue, Jun 8, 2021 at 10:20 AM hashibot[bot] ***@***.***> wrote: This issue has been automatically migrated to hashicorp/packer-plugin-proxmox#21 <hashicorp/packer-plugin-proxmox#21> because it looks like an issue with that plugin. If you believe this is *not* an issue with the plugin, please reply to hashicorp/packer-plugin-proxmox#21 <hashicorp/packer-plugin-proxmox#21>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#11071 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHAHEJOFRF2W5OINDNUGFXTTRYRKNANCNFSM46IA7HBQ> .

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.