On 11/29/17 1:31 PM, Chase Pettet wrote:
A series of upgrades and changes have left instances
with
'role::puppetmaster::standalone' applied in a broken state. This is
unfortunate because Puppet is unable to fix itself. There is a small
manual update required.
I believe that I've now fixed all of these cases.
Chase's advice is
still valid, though, if you see a problem.
-Andrew
On the project specific puppet master (instance with
role::puppetmaster:;standalone applied):
0. Make sure your copy of the operation puppet repo is current at
/var/lib/git/operations/puppet
1. edit /etc/puppet/puppet.conf to replace 'default_manifest =
$confdir/manifests/site.pp' with 'default_manifest = $confdir/manifests/'
2. restart apache (service apache2 restart)
3. puppet agent --test
Puppet should now able to fix itself and clients should run fine.
Places where this role is applied can be found at
https://tools.wmflabs.org/openstack-browser/puppetclass/role::puppetmaster:…
--
Chase Pettet
chasemp on phabricator <https://phabricator.wikimedia.org/p/chasemp/>
and IRC
_______________________________________________
Wikimedia Cloud Services mailing list
Cloud(a)lists.wikimedia.org (formerly labs-l(a)lists.wikimedia.org)
https://lists.wikimedia.org/mailman/listinfo/cloud