Client nodes can set the environment, so long as the server doesn't.
On Dec 14, 2010 3:21 AM, Iain Sutton iainsut...@gmail.com wrote:
We have just stumbled across this having moved to external nodes using
Foreman.
Our dev environment is where we make quick changes to manifests (and
nominally
The issue was that I was not passing the --environment flag during my
puppet run. Apparently it ignores the environment returned by the
external node classifier. Thanks for all the feedback.
-eric
On Dec 7, 10:15 am, Stefan Schulte stefan.schu...@taunusstein.net
wrote:
On Mon, Dec 06, 2010 at
On Fri, Dec 10, 2010 at 12:55 PM, Eric Snow es...@verio.net wrote:
The issue was that I was not passing the --environment flag during my
puppet run. Apparently it ignores the environment returned by the
external node classifier. Thanks for all the feedback.
Ahah. I was wondering if you'd
On Dec 6, 5:21 pm, Stefan Schulte stefan.schu...@taunusstein.net
wrote:
On Mon, Dec 06, 2010 at 01:54:40PM -0800, jcbollinger wrote:
Try changing the URL to this:
puppet:///bash/bash_profile
That is, drop the modules part of the path.
Are you sure? IIRC this is
On Dec 7, 8:11 am, jcbollinger john.bollin...@stjude.org wrote:
that makes a lot more sense then having to
put some arbitrary portion of the server's path _to the module_ into
the URL.
But of course, that's not what the modules bit is actually intended
to mean (sorry). Obviously, the file
Alas, I am running 0.25, and the fileserving mount is a required part
of the path.
-eric
On Dec 7, 7:29 am, jcbollinger john.bollin...@stjude.org wrote:
On Dec 7, 8:11 am, jcbollinger john.bollin...@stjude.org wrote:
that makes a lot more sense then having to
put some arbitrary portion of
On Mon, Dec 06, 2010 at 03:55:20PM -0800, Eric Snow wrote:
Thanks for the reply. The modules mount is okay:
[modules]
allow *
Although a short test with your snippet in my fileserver.conf worked for me:
can you try again with an empty fileserver.conf?
-Stefan
pgpKEVzcJOLu4.pgp
On Dec 6, 2:54 pm, Eric Snow es...@verio.net wrote:
Here is the error I get:
err: //.../File[/root/.bash_profile]: Failed to retrieve current state
of resource: Could not retrieve information from source(s)
puppet:///modules/bash/bash_profile at ...
However, the file is there:
# ll
On Mon, Dec 06, 2010 at 01:54:40PM -0800, jcbollinger wrote:
Try changing the URL to this:
puppet:///bash/bash_profile
That is, drop the modules part of the path.
Are you sure? IIRC this is deprecated
http://docs.puppetlabs.com/guides/file_serving.html
says that modules has to be in the
I have verified that everything has correct permissions:
# ls -la app_modules/bash/files/
drwxr-xr-x 3 root root 4096 Nov 24 05:52 .
drwxr-xr-x 5 root root 4096 Nov 24 05:52 ..
-rw-r--r-- 1 root root 402 Nov 24 05:52 bash_profile
-eric
On Dec 6, 2:23 pm, Patrick kc7...@gmail.com wrote:
On Dec
Thanks for the feedback. My understanding is that the first part of
the path has to be the location for the file server to do the lookup
(as in the /etc/puppet/fileserver.conf file). Without this the
puppetmaster would not know where to look for the files. Was this
something that works for you?
On Mon, Dec 06, 2010 at 03:31:01PM -0800, Eric Snow wrote:
Thanks for the feedback. My understanding is that the first part of
the path has to be the location for the file server to do the lookup
(as in the /etc/puppet/fileserver.conf file). Without this the
puppetmaster would not know where
Thanks for the reply. The modules mount is okay:
[modules]
allow *
I am just trying to track down why the puppetmaster can't locate the
file in question even though it is there are permissions are okay.
What would be a good place to look in the puppet code to find out what
paths it is
13 matches
Mail list logo
