I have a couple of parallel Vms on my Mac, and I'm trying to establish a simple connection between them as a puppet master and a puppet client.
- Puppet Master (on CentOs 6.2)
- Puppet Client (on Ubuntu 12.1 server)
when trying to connect a client using the following command.
puppet agent --server 192.168.1.103 --waitforcert 60 --test --verbose
He is trying to connect with the next output
warning: peer certificate won't be verified in this SSL session
info: Caching certificate for ca
warning: peer certificate won't be verified in this SSL session
warning: peer certificate won't be verified in this SSL session
info: Creating a new SSL certificate request for puppet1.localdomain
info: Certificate Request fingerprint (md5) : 2E:C6:D2:C2:........
warning: peer certificate won't be verified in this SSL session
warning: peer certificate won't be verified in this SSL session
warning: peer certificate won't be verified in this SSL session
warning: peer certificate won't be verified in this SSL session
notice: Did not receive certificate
On the server side, I have a debug puppet wizard listening with the following output:
notice: Starting Puppet master version 2.7.14
err: Could not resolve 192.168.1.101: no name for 192.168.1.101
info: access[^/catalog/([^/]+)$]: allowing 'method' find
info: access[^/catalog/([^/]+)$]: allowing $1 access
info: access[^/node/([^/]+)$]: allowing 'method' find
info: access[^/node/([^/]+)$]: allowing $1 access
info: access[/certificate_revocation_list/ca]: allowing 'method' find
info: access[/certificate_revocation_list/ca]: allowing * access
info: access[/report]: allowing 'method' save
info: access[/report]: allowing * access
info: access[/file]: allowing * access
info: access[/certificate/ca]: adding authentication any
info: access[/certificate/ca]: allowing 'method' find
info: access[/certificate/ca]: allowing * access
info: access[/certificate/]: adding authentication any
info: access[/certificate/]: allowing 'method' find
info: access[/certificate/]: allowing * access
info: access[/certificate_request]: adding authentication any
info: access[/certificate_request]: allowing 'method' find
info: access[/certificate_request]: allowing 'method' save
info: access[/certificate_request]: allowing * access
info: access[/]: adding authentication any
info: Inserting default '/status' (auth true) ACL because none were found in '/etc/puppet/auth.conf'
err: Could not resolve 192.168.1.101: no name for 192.168.1.101
info: Could not find certificate for 'puppet1.localdomain'
err: Could not resolve 192.168.1.101: no name for 192.168.1.101
info: Could not find certificate_request for 'puppet1.localdomain'
err: Could not resolve 192.168.1.101: no name for 192.168.1.101
notice: puppet1.localdomain has a waiting certificate request
err: Could not resolve 192.168.1.101: no name for 192.168.1.101
info: Could not find certificate for 'puppet1.localdomain'
err: Could not resolve 192.168.1.101: no name for 192.168.1.101
info: Could not find certificate for 'puppet1.localdomain'
err: Could not resolve 192.168.1.101: no name for 192.168.1.101
info: Could not find certificate for 'puppet1.localdomain'
err: Could not resolve 192.168.1.101: no name for 192.168.1.101
info: Could not find certificate for 'puppet1.localdomain'
Is it possible to set up a simple puppet configuration without using host permission and a simple IP address?
Any help?
source
share