On Thu, Jun 2, 2016 at 12:49 AM, Manuranga Perera <[email protected]> wrote:
> Yes it is coming when running with Vagrent, but I don't think this is > vagrant only issue. When I try to run puppet agent apply after SSHing in I > still get the same error. May be I can manually run by giving differing > command line args. But for now I will downgrade to puppet 3. > Yes that's better. Please create a JIRA/Github Issue with the details. Thanks > On Fri, May 27, 2016 at 12:15 AM, Imesh Gunaratne <[email protected]> wrote: > >> >> >> On Thu, May 26, 2016 at 9:39 PM, Manuranga Perera <[email protected]> wrote: >> >>> We are using non-environment puppet mode this is not compatible with >>> puppet 4 [1] >>> >>> If manifests_path and manifest_file are specified without environments, >>>> the old non-environment mode will be used (which will fail on Puppet 4+). >>>> [2] >>> >>> >>> Are we planing to update to be compatible with puppet 4? >>> >> >> As I see this is not a compatibility issue in Puppet modules, rather this >> is about the Vagrant Puppet plugin which is used for testing Puppet >> modules. We may need to test this and update the Vagrant script in the next >> release. >> >> Did you see any issues in Puppet modules related to Puppet 4? >> >> Thanks >> >>> >>> [1] https://github.com/mitchellh/vagrant/issues/5615 >>> [2] https://www.vagrantup.com/docs/provisioning/puppet_apply.html >>> -- >>> With regards, >>> *Manu*ranga Perera. >>> >>> phone : 071 7 70 20 50 >>> mail : [email protected] >>> >> >> >> >> -- >> *Imesh Gunaratne* >> Senior Technical Lead >> WSO2 Inc: http://wso2.com >> T: +94 11 214 5345 M: +94 77 374 2057 >> W: http://imesh.io TW: @imesh >> Lean . Enterprise . Middleware >> >> > > > -- > With regards, > *Manu*ranga Perera. > > phone : 071 7 70 20 50 > mail : [email protected] >
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
