True! I didn't show that it actually installed from the command line but it does/did. After a bit digging, I found a rather strange issue - that was the very first installation just after spinning up the instance and puppet needed an *apt-get update* first to carry-on with installation, whilst it was just fine from the CLI, without issuing *update* first. It happened on a number of nodes in my cluster, so I tested several times. Any further thought/comments on that?
-San On Thursday, October 10, 2013 3:06:40 PM UTC+1, jcbollinger wrote: > > > I don't think you've demonstrated that it does run fine from the command > line. It appears to me that the error reported by Puppet would not > manifest on the command line until after the point where your transcript > cuts off. > > Anyway, if a command succeeds when run from the command line but fails > when executed by Puppet then the usual problem is a difference in execution > environment, typically in the environment variables. Puppet intentionally > provides a very sparse environment to external commands it executes. Your > case is unusual in that the command seems to mostly work. Could it be that > you need a proxy server configured for FTP, but not for HTTP? > > > John > > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
