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
Describe the bug
When deploying a virtual machine with ansible, if an error occured in libvirt, the error message is not shown by ansible. Instead, it say msg: '''libvirtError'' object has no attribute ''message'''
To Reproduce
Steps to reproduce the behavior:
On a Yocto machine (standalone)
Create the inventory vm.yml (see below)
Launch the playbook deploy_vm_standalone.yaml to deploy the vm.
An error occured during the step "Create VMs"
The log of the error is incorrect : "msg: '''libvirtError'' object has no attribute ''message'''"
Expected behavior
In such situation, the correct libvirt error is visible when running journalctl -u libvirtd on the hypervisor : libvirtd[627]: missing target information for device /var/lib/libvirt/images/guest.qcow2
This error should be visible in ansible logs.
I think I already see that also on a debian version, but I wasn't able to reproduce.
In cluster mode, it seems that a check is applied on xml before creating the virtual machines and this check catch the bug.
See if it is possible to run the check on a standalone machine too ?
Describe the bug
When deploying a virtual machine with ansible, if an error occured in libvirt, the error message is not shown by ansible. Instead, it say
msg: '''libvirtError'' object has no attribute ''message'''
To Reproduce
Steps to reproduce the behavior:
vm.yml
(see below)deploy_vm_standalone.yaml
to deploy the vm.Expected behavior
In such situation, the correct libvirt error is visible when running
journalctl -u libvirtd
on the hypervisor :libvirtd[627]: missing target information for device /var/lib/libvirt/images/guest.qcow2
This error should be visible in ansible logs.
I think I already see that also on a debian version, but I wasn't able to reproduce.
In cluster mode, it seems that a check is applied on xml before creating the virtual machines and this check catch the bug.
See if it is possible to run the check on a standalone machine too ?
The inventory
vm.yaml
The associated xml "guest_false.xml" :
The error I injected is the missing target info in the disk part.
The text was updated successfully, but these errors were encountered: