I have puppetmaster running on RHEL4, and 2 puppet clients running on
RHEL5. All machines are running puppet version is 24.4 installed from
EPEL. The issue is that some configurations seem to be unusable by the
RHEL5 clients when the puppetmaster is running on RHEL4. However, if I
put those
quot;NEGOTIATOR_HOST =\nCONDOR_HOST =\n\n## A list of all potential
central managers in the pool.\nCOLLECTOR_HOST = host.tion debug level
\nREPLICATION_DEBUG = D_COMMAND\n## Replication log
file\nREPLICATION_LOG = $(LOG)/ReplicationLog\n"
Has anyone else seen this before?
Rob
Robert Rati wro
_COMMAND
## Replication log file
REPLICATION_LOG = $(LOG)/ReplicationLog
Andrew Shafer wrote:
> What does the template look like?
>
> On Wed, Oct 8, 2008 at 1:16 PM, Robert Rati <[EMAIL PROTECTED]
> <mailto:[EMAIL PROTECTED]>> wrote:
>
>
> I'm discover
), and running erb against the original 106 line template on the
RHEL4 machine produces the expected results.
It seems the length of the template has an effect on the results for
some reason...
Rob
Evan Hisey wrote:
> On Wed, Oct 8, 2008 at 12:42 PM, Robert Rati <[EMAIL PROTECTED]> wr
The namespaceauth.conf file seems to require FQDNs in the allow
statements, but does anyone know if 'allow puppet' (assuming a correctly
configured DNS CNAME record exists for puppet) will be accepted?
Specifically, if I have a namespaceauth.conf that contains:
[puppetrunner]
allow puppet
