Hi List,
I''m using puppet 0.23.2 (tarball) on Debian sarge as server and the
same
version on an etch client. When I try to use the following class :
class base {
$puppet = "security01.mydomain.com"
# bashrc file for global shell settings. file depends on used OS
version (etch, sarge etc).
file {
"/etc/bash.bashrc":
ensure => present,
source => [
"puppet://$puppet/files/bash/bash.bashrc.$lsbdistcodename",
"puppet://$puppet/files/bash/bash.bashrc" ]
;
}
}
I get the following error message
puppet://security01.mydomain.com/files/bash/bash.bashrc failed: Could
not connect to puppet on port 8140
It seems that puppet wants to connect to "puppet" instead of
security01.mydomain.com.
If I use as $puppet above only "security01", the puppet client tries
to
connect to security01 and can also find it (I have a search mydomain.com
in resolv.conf) but I get a certificate mismatch because i have the FQDN
in the CN field:
Could not describe /files/bash/bash.bashrc.etch: Certificates were not
trusted: hostname was not match with the server certificate
For me it seems that I cannot put an FQDN as the server in a puppet://
URI. I would prefer to keep everything with FQDNs.
Am I missing something? Which is the right way to keep a file up to date
with the most recent version on the puppet server?
Thank you,
Daniel
I use fully qualified names everywhere for everything (no exceptions) and I
haven''t run into this at all. Though all of my fileserver puppet urls
look
like:puppet:///${module_name}/...
If you don''t specify the server explicitly puppet will use whatever the
value of $server is in puppet.conf (which I where I set everything)
C
On 11/29/07, Daniel Mayer [COUGA.net] <mayer@couga.net>
wrote:>
> Hi List,
>
> I''m using puppet 0.23.2 (tarball) on Debian sarge as server and
the same
> version on an etch client. When I try to use the following class :
>
> class base {
> $puppet = "security01.mydomain.com"
>
> # bashrc file for global shell settings. file depends on used OS
> version (etch, sarge etc).
> file {
> "/etc/bash.bashrc":
> ensure => present,
> source => [
> "puppet://$puppet/files/bash/bash.bashrc.$lsbdistcodename",
> "puppet://$puppet/files/bash/bash.bashrc"
]
> ;
> }
>
> }
>
> I get the following error message
> puppet://security01.mydomain.com/files/bash/bash.bashrc failed: Could
> not connect to puppet on port 8140
> It seems that puppet wants to connect to "puppet" instead of
> security01.mydomain.com.
>
> If I use as $puppet above only "security01", the puppet client
tries to
> connect to security01 and can also find it (I have a search mydomain.com
> in resolv.conf) but I get a certificate mismatch because i have the FQDN
> in the CN field:
> Could not describe /files/bash/bash.bashrc.etch: Certificates were not
> trusted: hostname was not match with the server certificate
>
>
> For me it seems that I cannot put an FQDN as the server in a puppet://
> URI. I would prefer to keep everything with FQDNs.
>
> Am I missing something? Which is the right way to keep a file up to date
> with the most recent version on the puppet server?
>
> Thank you,
> Daniel
> _______________________________________________
> Puppet-users mailing list
> Puppet-users@madstop.com
> https://mail.madstop.com/mailman/listinfo/puppet-users
>
--
stickm@gmail.com
-==< Stick >==-
_______________________________________________
Puppet-users mailing list
Puppet-users@madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users
Hi,
Hm, the strange thing is that using this setting:
file {
"/etc/bash.bashrc":
source => [
"puppet://security01.mydomain.com/files/bash/bash.bashrc.$lsbdistcodenam
e",
"puppet://security01.mydomain.com/files/bash/bash.bashrc" ]
;
}
Everything gets transferred if the file does not exists. But as soon as
the first bash.bashrc is present and I change the file on the server to
retransfer it to the client I get:
err: //web07.mydomain.com/server/base/File[/etc/bash.bashrc]/source:
change from {md5}639f56cd58cffe7f7e5c7ee12a2d7dcd to
puppet://security01.mydomain.com/files/bash/bash.bashrc.etch
puppet://security01.mydomain.com/files/bash/bash.bashrc failed: Could
not connect to puppet on port 8140
During the first and second transfer no setting on any side was changed
so I assume the connection works. But for some reason when the file
already exists the client tries to connect to puppet instead of the host
I specified. Is that possible? I actually see a DNS request for
puppet.mydomain.com in a tcpdump.
Ideas?, Thanks,
Daniel
PS: Sorry for HTML email but I could not respond in plaintext to an html
email L
From: puppet-users-bounces@madstop.com
[mailto:puppet-users-bounces@madstop.com] On Behalf Of Chris MacLeod
Sent: Thursday, November 29, 2007 11:28 AM
I use fully qualified names everywhere for everything (no exceptions)
and I haven''t run into this at all. Though all of my fileserver puppet
urls look like:
puppet:///${module_name}/...
If you don''t specify the server explicitly puppet will use whatever the
value of $server is in puppet.conf (which I where I set everything)
C
On 11/29/07, Daniel Mayer [COUGA.net] <mayer@couga.net> wrote:
Hi List,
I''m using puppet 0.23.2 (tarball) on Debian sarge as server and the
same
version on an etch client. When I try to use the following class :
class base {
$puppet = " security01.mydomain.com
<http://security01.mydomain.com> "
# bashrc file for global shell settings. file depends on used OS
version (etch, sarge etc).
file {
"/etc/bash.bashrc":
ensure => present,
source => [
"puppet://$puppet/files/bash/bash.bashrc.$lsbdistcodename",
"puppet://$puppet/files/bash/bash.bashrc" ]
;
}
}
I get the following error message
puppet://security01.mydomain.com/files/bash/bash.bashrc failed: Could
not connect to puppet on port 8140
It seems that puppet wants to connect to "puppet" instead of
security01.mydomain.com.
If I use as $puppet above only "security01", the puppet client tries
to
connect to security01 and can also find it (I have a search mydomain.com
in resolv.conf) but I get a certificate mismatch because i have the FQDN
in the CN field:
Could not describe /files/bash/bash.bashrc.etch: Certificates were not
trusted: hostname was not match with the server certificate
For me it seems that I cannot put an FQDN as the server in a puppet://
URI. I would prefer to keep everything with FQDNs.
Am I missing something? Which is the right way to keep a file up to date
with the most recent version on the puppet server?
Thank you,
Daniel
_______________________________________________
Puppet-users mailing list
Puppet-users@madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users