not 100% sure if the policy is at vault or something changed while the policy was updated. Issue was observed before the newest libvirt release (i.e. 20231103 -> libvirt 9.9.0)