roumano
commented
3 years ago Hi,
i wanted to use the type=volume but see my details in the issue opened #61 , it's not working
So, it why you see my proposed PR...
I have tested (again) with these variables :
- For libvirt-host
libvirt_host_pools: - name: lvm_pool
type: logical
source: lvm_pool
target: /dev/lvm_pool
- For the libvirt-vm
libvirt_vms: - state: present
name: 'test2'
memory_mb: 1024
vcpus: 1
volumes:
- name: 'lv_test2' type: 'volume' capacity: '10GB' pool: 'lvm_pool' format: 'raw' interfaces:
- network: 'test'
The role is crashing with this error (it's was in verbose mode)TASK [ansible-role-libvirt-vm : Ensure the VM is running and started at boot] ** The full traceback is: Traceback (most recent call last): File "/tmp/ansible_virt_payload_WOQYt6/ansible_virt_payload.zip/ansible/modules/cloud/misc/virt.py", line 593, in main File "/tmp/ansible_virt_payload_WOQYt6/ansible_virt_payload.zip/ansible/modules/cloud/misc/virt.py", line 497, in core File "/tmp/ansible_virt_payload_WOQYt6/ansible_virt_payload.zip/ansible/modules/cloud/misc/virt.py", line 405, in start File "/tmp/ansible_virt_payload_WOQYt6/ansible_virt_payload.zip/ansible/modules/cloud/misc/virt.py", line 238, in create File "/usr/lib/python2.7/dist-packages/libvirt.py", line 1080, in create if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self) libvirtError: internal error: qemu unexpectedly closed the monitor: 2020-09-14T14:34:57.397375Z qemu-system-x86_64: -drive file=/dev/lvm_pool/lv_test2,format=raw,if=none,id=drive-virtio-disk0: Could not open '/dev/lvm_pool/lv_test2': Permission denied fatal: [epnkvmext4]: FAILED! => { "changed": false, "invocation": { "module_args": { "autostart": true, "command": null, "name": "test2", "state": "running", "uri": "qemu:///system", "xml": null } }, "msg": "internal error: qemu unexpectedly closed the monitor: 2020-09-14T14:34:57.397375Z qemu-system-x86_64: -drive file=/dev/lvm_pool/lv_test2,format=raw,if=none,id=drive-virtio-disk0: Could not open '/dev/lvm_pool/lv_test2': Permission denied" }
On the destination server, the lv is created :
lvs |grep lv_test2
lv_test2 lvm_pool -wi-a----- <9.32gAnd the pool is correctly reconize by virsh
virsh pool-info lvm_pool
Name: lvm_pool
UUID: 3f71157d-8145-45ed-a6de-ae8a077eae2d
State: running
Persistent: yes
Autostart: yes
Capacity: 3.27 TiB
Allocation: 37.27 GiB
Available: 3.24 TiB
virsh vol-list lvm_pool
Name Path
------------------------------------
lv_test1 /dev/lvm_pool/lv_test1
lv_test2 /dev/lvm_pool/lv_test2
lv_vm1 /dev/lvm_pool/lv_vm1
lv_vm3 /dev/lvm_pool/lv_vm3- I'm not sure, as i'm not a libvirt expert but look like it's need to set it as block device :
virsh vol-info --pool lvm_pool lv_test2 Name: lv_test2 Type: block Capacity: 9.32 GiB Allocation: 9.32 GiB
markgoddard
Fix #61