Jira (PUP-4616) Smoke test mcollective on PC 1.1

Title: Message Title

John Duarte created an issue

PUP-4616

Smoke test mcollective on Puppet 4.0 AIO

Validate that `mco ping` and the mcollective puppet agent plugin function in a `puppet-agent` install.

This validation should be performed on the following platforms

Install `puppet-agent` on SUT
Install `activemq` on SUT
Copy `activemq*` files from https://github.com/richardc/mcollective-aio-beaker/tree/master/files to activemq conf directory.
Start `activemq`
Copy the following files from https://github.com/richardc/mcollective-aio-beaker/tree/master/files to mcollective conf directory `/etc/puppetlabs/mcollective`
1. server.cfg
2. client.cfg
3. ca_crt.pem
4. server.crt
5. server.key
6. client.crt
7. client.key
Create the following directory
1. `/etc/puppetlabs/mcollective/ssl-clients`
Copy the following file from https://github.com/richardc/mcollective-aio-beaker/tree/master/files/client.crt to `ssl-clients` directory created in the step above renaming it to `client.pem`
Restart the `mcollective` service

As root, execute mco ping. It should respond with 1 reply.

[root@egqjatjzwc43sqo ~]# /opt/puppetlabs/bin/mco ping

warn 2015/04/03 11:22:09: config.rb:148:in `block in loadconfig' Cannot find libdir: /opt/puppetlabs/mcollective/plugins

egqjatjzwc43sqo                          time=149.74 ms

---- ping statistics ----

1 replies max: 149.74 min: 149.74 avg: 149.74

Create a mcollective plugins directory that corresponds with the `libdir` in the mcollective `client.cfg` file.

mkdir -p /opt/puppetlabs/mcollective/plugins

Copy the mcollective-puppet-agent plugin into the plugins directory

git clone https://github.com/puppetlabs/mcollective-puppet-agent

cp -a mcollective-puppet-agent/* /opt/puppetlabs/mcollective/plugins/

/opt/puppetlabs/bin/mco puppet count

Should return sane results

[root@hj75uvrdanz3mbi ~]#  /opt/puppetlabs/bin/mco puppet count

Total Puppet nodes: 1

          Nodes currently enabled: 1

         Nodes currently disabled: 0

Nodes currently doing puppet runs: 0

          Nodes currently stopped: 1

       Nodes with daemons started: 0

    Nodes without daemons started: 1

       Daemons started but idling: 0

Add Comment

This message was sent by Atlassian JIRA

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.