similar to: puppet_dashboard.rb keeps getting deleted by puppet agent

Hello, I have been following through some of the documentation trying to make use of puppet in a test environment. I went ahead and tried to install puppet-passenger and puppet dashboard. I think i have succesfully done this, because at mymaster.local:3000/ I get the dashboard webpage (albeit with no nodes or anything reporting) and at https://mymaster.local:8140 I get a cert trying to be

Hi all. I''m unable to integrate puppet dashboard as I keep getting the following error: No report named ''puppet_dashboard'' Relevant configuration (names changed to protect the innocent).. ==== /etc/puppet/puppet.conf [puppetd] libdir=$vardir/lib libdir=/var/www/puppet-dashboard/lib/puppet [puppetmasterd] reports = puppet_dashboard

Hi all, i planned for a startup to install one of this gui tools. But if i look in the documentation, or google it, i find no results which helps. If i would like to install the rpm package i get the following dependencies problems rpm -i puppet-dashboard-1.2.3-1.el6.noarch.rpm warning: puppet-dashboard-1.2.3-1.el6.noarch.rpm: Header V4 RSA/SHA1 signature: NOKEY, key ID 4bd6ec30 error: Failed

Hi, I have noticed that when a typo is introduced or a module is plain broken, puppet will run using a cached catalog. This is logged as an error on the local client, however, it is not logged as an error on Puppet Dashboard. How can I change this behavior, so that using the cached catalog will result in a warning/error being displayed on Puppet Dashboard? Foreman does this. I''ve

Hi everyone, I''m trying to figure out what is the best way to handle a single system that dual boots with a puppet client running in each. In this case we are talking about Ubuntu 12.04 and Windows 8. Should I just copy the certificate from one OS to the other? Should I have a different certificate for each OS? In this case can they have the same hostname, as it is the same IP

Hello All, I don''t seem to be able to get reports to display on the foreman interface. I copied extras/puppet/foreman/files/foreman-report.rb to / usr/lib/ruby/site_ruby/1.8/puppet/reportsforeman.rb, instead of /usr/ lib/ruby/1.8/puppet/reports/foreman.rb. Config: Centos5.4, Apache/ Passenger, Puppet 0.25.4. The reports are coming from the clients, because I can see them in

Hello All, I''m happy to announce the next stable release of Foreman (0.1-2), main new features include: - General - LDAP / AD Authentication support. - Audit Log - keeps information about changed host values (e.g. host environment, external node parameters etc). - Added Puppet module for installing/managing foreman - Puppet Reports - Added a basic

I''m trying to figure out if there is a common/working setup that people are using to host puppet in remote sites. At first our setup was that we have several puppetmasters (PM) in site A and a couple in our smaller site B. In site A we are also hosting Foreman and our mysql DB for storeconfigs. site A and B are connected via a WAN that is fairly slow. With this setup the issue I

I''m playing around with foreman for the moment. I can''t seem to figure out how to make the dashboard look like in this screenshot http://theforeman.org/wiki/foreman/Screenshots#Dashboard In order for those statistics to work what should be done? I have activated the rrdgraph reports in puppetd, uncommented the line ":rrd_report_url: report/" in config/settings.yaml

I''m pleased to announce the release of Foreman 0.3 Download from: Source: http://theforeman.org/attachments/download/237/foreman-0.3.tar.bz2 RPM: http://yum.theforeman.org/stable/RPMS/foreman-0.3-1.noarch.rpm It is recommended to upgrade your foreman smart proxy to the latest version as well. Highlights of this release include: SearchingAn extensive rewrite of the search system was

Hi Guys, I''m reading about dashboard and foreman, and I''m wondering if there is anyone who made a comparison of the two? Can anyone help me decide which one to use? It feels like foreman is ''ahead'' for now? cheers, Walter Heck Engineer @ OlinData (http://olindata.com) -- You received this message because you are subscribed to the Google Groups "Puppet

I''ve been trying to find information, suggestions, etc. for how to combine scaling Puppet with the use of management tools like Dashboard/Foreman and MCollective. Our current thinking for an initial deployment is two VMs as Puppet Master worker nodes fronted by a pair of NetScalers. However, I''m not sure how to go about implementing Dashboard or Foreman and MCollective servers in

Excuse me When I add node from the dashboard is there any possibility to push puppet-agent to the client ?? Thank you in advance!!! Francesco -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com. To post to this

Hi puppet users, We''ve got a puppet (0.24.8) implementation with two environments, called production and testing. We''ve also got a Puppet Dashboard (1.0) instance up and running, which is receiving and displaying reports from hosts in both of the environments. We would like to start using the dashboard as an external node classification tool, so I''ve taken the example

Hey, I''m exploring puppet-dashboard right now and I want to get the live aggregation running. But somehow I''m already failing at the puppet.conf entries ;) The Dashboard readme says: ### Live report aggregation To enable report aggregation in Puppet Dashboard, the file `lib/puppet/ puppet_dashboard.rb` must be available in Puppet''s lib path. The easiest way to do this

Greetings: Sorry for cross-posting this question, but I haven''t gotten any love over on the Google Forum for Foreman users<https://groups.google.com/forum/#!forum/foreman-users> (their forum isn''t as active as this one). I only recently learned about The Foreman and I''d like to deploy it on a 64-bit Ubuntu 12.04 LTS workstation to provision/manage a bunch of

the puppetmaster conf file is: [main] logdir = /var/log/puppet rundir = /var/run/puppet ssldir = $vardir/ssl reports = store, http, foreman reporturl = http://localhost:3000/reports/upload [agent] classfile = $vardir/classes.txt localconfig = $vardir/localconfig the puppet client conf file is: [main] logdir = /var/log/puppet rundir = /var/run/puppet

Is there any way to pass puppet run details to an ENC. Most importantly I want to know the Environment value the puppet Agent is asking for. More generally is it possible to query the puppet configuration values? One thought I had is to turn the puppet config into FACTS. Then the ENC can get the latest values from either Inventory Services or Foreman. But off hand I don''t know how

Hi, I created a centOS6 EC2 instance last night and ran the foreman puppet module but it came back with a few years. Was hoping somebody could help me understand these errors. [root@ip-10-170-77-129 config]# echo include foreman | puppet --modulepath /root/puppet-foreman/ err: /Stage[main]/Foreman::Config::Enc/File[/var/lib/puppet/yaml/foreman]/ensure: change from absent to directory failed:

An error I managed to hit today, trying to migrate puppet dashboard from 1.2.2 to 1.2.4 (after upgrading the master to puppet 2.7.9 seemed to prevent the dashboard from importing new reports). I''m trying to re-run it now, but as you might guess, the DB is pretty huge and the process takes a while to execute. Executed from the puppet-dashboard directory: sudo rake db:migrate