PE 2.0 server and regular stock puppet client

[T.J. Yang]

Hi, All

 

I am having puppet client side error message when  building a 10 nodes PE 2.0 demo site to experience the new dashboard features.

The only puppet(+mcollective) client works is that one come with PE 2.0 installation on Ubuntu 10.04.

 

For other OSs I am getting following error message.

 

Error message:

 

Nov 22 01:52:20 oi151 puppet-agent[1871]: [ID 702911 daemon.error] Could not retrieve catalog from remote server: Error 400 on SERVER: validate_re(): "" does not match "^true$|^false$" at /opt/puppet/share/puppet/modules/pe_mcollective/manifests/init.pp:40 on node oi151.test.net

Looks like I don't have mcollective agent installed along with puppet, by default PE 2.0 expect every clients have both puppet and mcollective agents installed.

 

So the questions are,

1. How do I disable Live Management in PE 2.0 ?

    So that I can have agent without mcollective still reporting to PE 2.0 server.

2. How do I prepare an expected puppet+mcollective agents on Ubuntu ?

   

 

[Nigel Kersten]

Remove the cron job that automatically adds all your agents to the default group, which has the pe_mcollective class associated with it.

That class assumes PE agents, and deliberately fails early so you don't get half-applied manifests to non-PE agents.

http://docs.puppetlabs.com/pe/2.0/console_classes_groups.html#the-default-group

There's a cron job in /etc/cron.d which is automatically adding your nodes to this group.

 

2. How do I prepare an expected puppet+mcollective agents on Ubuntu ?

You should use the PE agent install on Ubuntu 10.0.4

[T.J. Yang]

My bad, I failed to understand the puppet-enterprise-installer is for client and/or server installation.

Thanks for the pointer, Nigel .

 

 

tj

 

[Nigel Kersten]

No worries. Glad you got it running.

--
Nigel Kersten
Product Manager, Puppet Labs

[John Burbridge]

Hello there,

I'm having exactly the same issue except I'm trying to install puppet via cloud provisioning... but I think I might have messed up something along the way.

My first install was successful except I didn't provide a certname parameter while running "puppet node init" and the default generated was appended with a long hash of some sort:

 www-dev2.home.mydomain.net-6d5aac9e-9f76-36e8-7d63-808bdf901c36 

Despite functional, that's not exactly what I wanted so I revoked the cert on the puppetmaster, re-installed, signed the new cert on the puppetmaster and now am getting the exact message described before:

root@www-dev2:~# puppet agent --test

warning: peer certificate won't be verified in this SSL session

info: Caching certificate for www-dev2

info: Retrieving plugin

info: Loading facts in facter_dot_d

info: Loading facts in facter_dot_d

err: Could not retrieve catalog from remote server: Error 400 on SERVER: validate_re(): "" does not match "^true$|^false$" at /opt/puppet/share/puppet/modules/pe_mcollective/manifests/init.pp:40 on node www-dev2

warning: Not using cache on failed catalog

err: Could not retrieve catalog; skipping run

I assume my condition is different from the original poster's given I'm attempting to spool up a new server using cloud provisioning with PE? Any thoughts on what my next steps should be?

 

[Zidane]

On my mind you need to update your puppet agent version and edit /etc/puppetlabs/puppet/puppet.conf:
[main]
    vardir = /var/opt/lib/pe-puppet
    logdir = /var/log/pe-puppet
    rundir = /var/run/pe-puppet
    modulepath = /etc/puppetlabs/puppet/modules:/opt/puppet/share/puppet/modules
    user = pe-puppet
    group = pe-puppet
    archive_files = true
    archive_file_server = puppet

[agent]
    certname = certname
    server = puppet
    report = true
    classfile = $vardir/classes.txt
    localconfig = $vardir/localconfig
    graph = true
    pluginsync = true

[Nigel Kersten]

This is getting a little far off field for puppet-users, and should probably go to pe-users as it's very PE specific.

https://groups.google.com/a/puppetlabs.com/group/pe-users/topics

but it looks like you don't have the facts text file in place in /etc/puppetlabs/facts.d that the PE installer lays down? That failure is the module validating that the required input data is there, and it's not. :)

 

 

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/dZV7EgUK2P0J.

To post to this group, send email to puppet...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.

[John Burbridge]

Thanks gents - turned out it was a networking issue. My firewall was open on port 443 but pointing at the wrong host. :)

I've subscribed to the PE users' list anyway. Thanks!