You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed a few problems when trying to create a lxc with this module:
disk_volume is currently passed to proxmoxer. However, the correct variable name in proxmoxer name is rootfs.
Changing disk_volume=module.params["disk_volume"], to rootfs=module.params["disk_volume"], fixes this issue.
storage is currently marked mutually exclusive with disk_volume. However, disk_volume.storage does not seem to be honored and the module tries to create the rootfs on the default local.
Making storage no longer mutually exclusive with disk_volume allows the lxc to be properly created. So disk_volume.storage is unneeded and unused. Atleast I think so. In the proxmox api docs, rootfs doesn't have a storage field.
But there is a lot of logic for transforming the input variables into what is actually passed to proxmoxer. So maybe the intention is to use disk_volume.storage and its just a bug that its not used.
disk_volume.size is not honored. The module always creates a 4 GB disk.
Summary
I noticed a few problems when trying to create a lxc with this module:
disk_volume
is currently passed to proxmoxer. However, the correct variable name in proxmoxer name isrootfs
.Changing
disk_volume=module.params["disk_volume"],
torootfs=module.params["disk_volume"],
fixes this issue.storage
is currently marked mutually exclusive withdisk_volume
. However,disk_volume.storage
does not seem to be honored and the module tries to create the rootfs on the defaultlocal
.Making
storage
no longer mutually exclusive withdisk_volume
allows the lxc to be properly created. Sodisk_volume.storage
is unneeded and unused. Atleast I think so. In the proxmox api docs,rootfs
doesn't have astorage
field.But there is a lot of logic for transforming the input variables into what is actually passed to proxmoxer. So maybe the intention is to use
disk_volume.storage
and its just a bug that its not used.disk_volume.size
is not honored. The module always creates a 4 GB disk.Issue Type
Bug Report
Component Name
proxmox
Ansible Version
Community.general Version
Configuration
OS / Environment
Client: Custom Podman container based on Debian 12
Proxmox Server: pve-manager/8.2.7/3e0176e6bb2ade3b (running kernel: 6.8.8-4-pve)
Steps to Reproduce
Expected Results
The lxc is created properly.
Actual Results
no changes made:
if
disk_volume
is passed to proxmoxer asrootfs
andstorage
is unset:if
storage
is made not mutually exclusive and then value changed:the container is created successfully but the rootfs disk is only 4 GB.
Code of Conduct
The text was updated successfully, but these errors were encountered: