After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 592018 - puppet client daemon not working on puppet
puppet client daemon not working on puppet
Status: RESOLVED OBSOLETE
Product: sysadmin
Classification: Infrastructure
Component: Puppet
unspecified
Other Linux
: Normal normal
: ---
Assigned To: GNOME Sysadmins
GNOME Sysadmins
Depends on:
Blocks:
 
 
Reported: 2009-08-16 23:13 UTC by Owen Taylor
Modified: 2013-11-21 14:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Owen Taylor 2009-08-16 23:13:39 UTC 
The last I checked, puppetd was not properly working on the 'puppet' machine itself, and puppet configuration changes aren't being automatically applied.

Running puppetd --test manually did work.

(Currently the puppet VM doesn't have a public IP, see http://live.gnome.org
/Sysadmin/Puppet for notes about how to get logged in by port forwarding.)

The puppet::master class is probably interfering in some way with the puppet class it inherits, or maybe puppet.conf-master doesn't include all the content from puppet.conf.

This needs to be:

 - Tested 
 - Diagnosed
 - Fixed
Comment 1 Andrea Veri 2013-11-21 14:57:29 UTC 
The GNOME Infrastructure Team is currently migrating its bug / issue tracker away from Bugzilla to Request Tracker and therefore all the currently open bugs have been closed and marked as OBSOLETE.

The following move will also act as a cleanup for very old and ancient tickets that were still living on Bugzilla. If your issue still hasn't been fixed as of today please report it again on the relevant RT queue.

More details about the available queues you can report the bug against can be found at https://wiki.gnome.org/Sysadmin/RequestTracker.

Thanks for your patience,

the GNOME Infrastructure Team