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
Tested by applying a volume and then destroying it on leap and didn't gave me an error but I wonder if it is necessary to use the volume before being able to reproduce. Here is my libvirt version
$ virsh --version
1.2.18.2
Also I remember having a similar issue when using pennyworth and making sure sure my libvirt.conf user and group matched with the /var/lib/libvirt/qemu owner.
This avoids the problem where the Ignition file is remote to
the host on which the libvirt domain is being created. We've
added a "libvirt_ignition" resource which manages the Ignition
file in the libvirt volume - creates it, and destroys it. The
"coreos_ignition" field in the libvirt_domain definition must
point to the Id of a "libvirt_ignition" resource.
The code is modelled on that used for CloudInit.
The text was updated successfully, but these errors were encountered: