Puppet Master server migration and problem? 2.6 to 2.7

[MF]

Hello,

I am setting up a new master server and migrating my configuration
from my current master server. I am also upgrading from 2.6 to 2.7.
I have the new server built and integrated with Apache, Passenger, and
Dashboard just like on my current server. I moved over all my modules
in /etc/puppet/modules as well as my site and node manifests in /etc/
puppet/manifests. I did not move over the entire /var/lib/puppet/ssl
dir. At this point I am just testing with two nodes. The two clients
connect fine and have their certs verified and can connect to puppet
and be seen in dashboard. But when I try to add one of my existing
module/class to the nodes the configuration is never updated.

The puppet agent runs fine and says finished catalog run but the
configuration is not modified. I see no errors on either the server
or the client and the certs seem to be just fine.

Anyone have any suggestions?

Thanks in advance for your help.

[vagn scott]

Maybe you need to do this:

touch /etc/puppet/manifests/site.pp

[MF]

Thanks. I tried to touch sites.pp and nodes.pp but still no luck.

[Nan Liu]

Dashboard data is retrieved from an ENC script configured in
puppet.conf [master] section:

node_terminus = exec
external_nodes = /etc/puppetlabs/puppet-dashboard/external_node

If you run this script with the node name it should reflect the
changes made in dashboard:
/etc/puppetlabs/puppet-dashboard/external_node hostname

If it's not retrieving the correct data, check the script and make
sure it connecting to the right system:
ENC_BASE_URL="https://localhost:443/nodes"

HTH,

Nan

[MF]

Thanks for taking the time to respond, but I just figured out I had a
typo in my puppet.conf file. What a difference a day makes.