On Mon, Jan 27, 2014 at 4:40 PM, James <purpleidea@xxxxxxxxx> wrote: > On Mon, Jan 27, 2014 at 12:04 AM, Kaushal M <kshlmster@xxxxxxxxx> wrote: >> I finally got vagrant working. > Great! Now the fun stuff starts! > >> Had to roll back to v1.3.5 to get it > As suspected. I've updated my original blog post to make it more clear > to only use 1.3.5 > >> working. I can get the puppet vm up, but the provisioning step always >> fails with a puppet error [1]. Puppet complains about not finding a >> declared class. > Interesting! I don't see this error. The puppet server always builds > properly for me. Can you verify that you did these steps: > > 1) git clone --recursive https://github.com/purpleidea/puppet-gluster This. I hadn't done a recursive clone. I cloned the repo correctly again and everything works now. The vms are being provisioned as I type this. Finally, time to test puppet-gluster. > 2) cd puppet-gluster/vagrant/gluster/ > 3) vagrant up puppet > > In particular can you verify that you used --recursive and that the > puppet-gluster/vagrant/gluster/puppet/modules/ directory contains a > puppet/ folder? > > Other than those things, I'm looking into this too... It seems some of > the time, I've been getting similar errors too. I'm not quite sure > what's going on. I got the feeling that maybe the puppet server didn't > have enough memory. Now I'm not sure. Maybe there's a libvirt > networking bug? Do you get the same errors when you repeat the > process, or different errors each time? > >> This happens with and without vagrant-cachier. I'm >> using the latest box (uploaded on 22-Jan). _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users