Hi Olivia, I think this error is coming from Vagrant. The guest VM is not getting to the point where Puppet can run on it. What virtualization provider are you using (vmware / fusion / virtualbox)? Next time you see it can you add '--debug' to your 'vagrant up' command?
--eric0 On Dec 3, 2014, at 1:28 PM, Olivia Zhang <[email protected]> wrote: > I’m working with Vagrant puppet provisioner, from time to time, it would have > these issues: > > ==> influxdbChild1: Successfully installed puppet-3.7.2 > > ==> influxdbChild1: 4 gems installed > > ==> influxdbChild1: Successfully installed CFPropertyList-2.2.8 > > ==> influxdbChild1: 1 gem installed > > ==> influxdbChild1: Running provisioner: puppet... > > Guest-specific operations were attempted on a machine that is not > > ready for guest communication. This should not happen and a bug > > should be reported. > > The break down is not consistent — sometimes it’s working pretty well but > sometimes there is such issue. Is this a bug and do we have a way to get > around this? > > Thanks! > > > -- > You received this message because you are subscribed to the Google Groups > "Puppet Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-dev/61ea3a20-c4bf-4a3d-ac74-f0599b8f866e%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. Eric Sorenson - [email protected] - freenode #puppet: eric0 puppet platform // coffee // techno // bicycles -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-dev/30174A91-D040-4D2F-8CB8-F6B80E125306%40puppetlabs.com. For more options, visit https://groups.google.com/d/optout.
