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
This module looks like a terrific piece of work and I would like to get actively involved, if I may. However I am having problems getting my first VM going using this module. Both my puppet master and client are running Fedora (16 and 15, respectively) and have had no problems creating VMs manually.
When I run my 'puppetd --test' for the first time, I get:
err: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not autoload virt: Could not autoload /etc/puppet/modules/puppet-virt/lib/puppet/provider/virt/openvz.rb: Sorry, this provider is not supported for your Operation System, yet :) at /etc/puppet/modules/doubledog/manifests/classes/droopy-f15.pp:31 on node droopy-f15.doubledog.org
Repeated runs result in no errors, but no VM is created either. I am not sure why I only see the error just the first time -- unless I restart the puppetmaster service. However, I am most confused as to why openvz.rb is involved if libvirt is supposed to be my provider. Is this a bug or mistake/misunderstanding that I have? Any help would be most appreciated.
The text was updated successfully, but these errors were encountered:
Hi Carla,
This module looks like a terrific piece of work and I would like to get actively involved, if I may. However I am having problems getting my first VM going using this module. Both my puppet master and client are running Fedora (16 and 15, respectively) and have had no problems creating VMs manually.
I have this in my node's class:
When I run my 'puppetd --test' for the first time, I get:
Repeated runs result in no errors, but no VM is created either. I am not sure why I only see the error just the first time -- unless I restart the puppetmaster service. However, I am most confused as to why openvz.rb is involved if libvirt is supposed to be my provider. Is this a bug or mistake/misunderstanding that I have? Any help would be most appreciated.
The text was updated successfully, but these errors were encountered: