This shows the Satellite lifecycle:
https://access.redhat.com/support/policy/updates/satellite
--
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
/url?q=http%3A%2F%2Fpuppetagent.com=D=1=AFQjCNERFUJgfIV7-T1L3INug28k8lFTqA>
>
> I dont find any errors here puppetdb logs
>
>
> puppetserver --version
> puppetserver version: 2.4.0
>
> puppetdb --version
> puppetdb version: 4.1.2
>
> puppet --version
> 4.5.2
>
>
&
Does puppetdb start normal now, no more errors in puppetdb.log?
--
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+unsubscr...@googlegroups.com.
To
On Friday, July 1, 2016 at 12:04:19 AM UTC+2, Virat wrote:
>
> var/log/puppetlabs/puppetdb/puppetdb.log
>
>
> 2016-06-30 17:13:54,781 ERROR [p.p.s.storage]
> *
> * PostgreSQL DB versions older than 9.4 are no longer supported. Please
> upgrade Postgres and restart
On Wednesday, June 8, 2016 at 11:03:09 AM UTC+2, Matt Larson wrote:
>
> I tried this, but where are the puppet-agent source RPMs ?
>
Indeed they are not there anymore as discussed in [1] and [2] .
[1] https://tickets.puppetlabs.com/browse/CPR-191
[2]
Have you tried using the source RPMs from here;
https://yum.puppetlabs.com/el/6/PC1/SRPMS/
On Friday, June 3, 2016 at 8:44:20 PM UTC+2, Matt Larson wrote:
>
>
> I'm trying to create an RPM from source on a stock RHEL6-based (CentOS6)
> instance, but I'm seeing errors. I also posted in
>
Hi Eric,
Think you ment these release notes:
https://docs.puppet.com/puppet/latest/reference/release_notes_agent.html
Stefan
--
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,
HI,
Maybe you check the r10k workshop [1] which will do a complete walkthrough
of r10k or just watch their video [2] of it.
[1] https://github.com/adrienthebo/r10k-workshop/blob/master/WORKSHOP.mkd
[2] https://www.youtube.com/watch?v=rQJbuqMCl9c
Stefan
On Thursday, June 2, 2016 at 2:32:46 AM
Hi,
On Saturday, January 16, 2016 at 6:38:24 AM UTC+1, François Lafont wrote:
>
> On 16/01/2016 06:14, Francois Lafont wrote:
And I have just tested in Ubuntu Trusty but it doesn't work. If I force the
> installation of a plugin, the package "puppet-agent" is removed (see the
> paste
>
Hi,
See the comment Jo made here [1], activemq and plugins will work.
[1] https://tickets.puppetlabs.com/browse/MCO-722
Stefan
--
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,
On Monday, January 4, 2016 at 8:44:12 PM UTC+1, Ryan Coleman wrote:
>
>
> The broker [1], agent [2] and client libraries [3] are open-source for
> those not running PE but I'm not aware of anything using it beyond PE (yet).
>
> And what about this [1]?
"*A little further down the line, Puppet
Hi,
What about the Google Group; Puppet Announce
Stefan
--
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+unsubscr...@googlegroups.com.
To view
Hi,
Is this a correct version?
The release notes show support from version 3.5
http://docs.puppetlabs.com/puppet/3.5/reference/release_notes.html#platform-support-updates
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this
There is a user resource attribute;
forcelocal [1]
Forces the management of local accounts when accounts are also being
managed by some other NSS
Doens't this help?
[1]
https://docs.puppetlabs.com/references/latest/type.html#user-attribute-forcelocal
On Tuesday, September 29, 2015 at
There are some jira tickets on this;
https://tickets.puppetlabs.com/browse/MCOP-516
https://tickets.puppetlabs.com/browse/MCOP-529
--
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
Nice one :)
Think the MCO plugins where forgotten with the new puppet-agent setup, the
plugin documentation still refers to the non-puppetlabs directories.
On Tuesday, September 1, 2015 at 12:34:08 AM UTC+2, Chad Thompson wrote:
> To all:
>
> This is hopefully a simple question:
>
> Prior to
On Wednesday, August 26, 2015 at 10:16:59 AM UTC+2, Fabrice Bacchella wrote:
Le 24 août 2015 à 21:59, Christopher Wood christop...@pobox.com
javascript: a écrit :
My biggest problem: there isn't any working dashboard working with Puppet
4. The puppetdb APIv4 in puppet db 3.1 is not
Hi,
For Dashboard, Aaron Stone is doing it now @
https://github.com/sodabrew/puppet-dashboard.
Looking at this issue (
https://github.com/sodabrew/puppet-dashboard/issues/320), seems that it
doens't support Puppet 4 reports yet.
Stefan
On Thursday, July 23, 2015 at 11:27:24 PM UTC+2,
Hi,
These 2 values (Store limit , Temporary Store limit) are specified in
/etc/puppetdb/conf.d/config.ini
and matched against your local diskspace.
Q: should it be an ERROR of just a WARN like the 'Store Limit' message.
And the puppetdb port (8081) isn't running
There should be messages in
Hi,
Received the same kind of error with a different message, using Puppet
3.7.2 with future parser;
Error: Could not retrieve catalog from remote server: Error 400 on SERVER:
Syntax error at '[' at
/etc/puppet/environments/tst/modules/managesoft/manifests/install.pp:41:23
on node fqdn
Had
Hi Phil,
checkout the resource ordering docs;
https://docs.puppetlabs.com/learning/ordering.html
Stefan.
--
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
Hi Stella,
Out of the box there is no support for this.
You can write your own MCollective discovery plugin to do this or use my basic
version [1] and enhance it
Stefan
[1] https://github.com/sheijmans/mcollective-discovery
--
You received this message because you are subscribed to the
, July 31, 2014 1:55:32 AM UTC-4, Stefan Heijmans wrote:
Hi,
However those classes on my puppet master are not being parsed into the
dashboard. There is no classed shown in dashboard, even I am sure I
downloaded a few modules.
You mean, you have not added classes manually to the Dashboard
Hi,
However those classes on my puppet master are not being parsed into the
dashboard. There is no classed shown in dashboard, even I am sure I
downloaded a few modules.
You mean, you have not added classes manually to the Dashboard?
If so, you do need to do this. Modules available on your
config/initializers/app_version_init.rb
Sets the URL based on VERSION file
app/views/shared/_global_nav.html.haml
Think that this is the html page
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop
Hi John/Felix,
thanks for the suggestions, will try them out next week and come back with
the results
Stefan
--
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
anyone?
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
Hi,
the difference is in the /etc/sysctl.conf;'
Puppet module with all resources in 1 file
===
After; /etc/sysctl.conf
-rw-r--r--. 1 root root 2679 Jun 19 12:54 /etc/sysctl.conf
fs.aio-max-nr = 1048576
fs.file-max = 6815744
kernel.core_uses_pid = 1
Hello,
I've got 'something strange' with a Puppet module, using augeasproviders
(v1.2.0 or master branch of today) on Puppet 3.6.2
Below a stripped version of it with the same results as the full version;
It installs an Oracle preinstall rpm which also updates /etc/sysctl.conf
settings and
Hi Josh,
On Tuesday, June 17, 2014 6:35:19 PM UTC+2, Joshua Partlow wrote:
Is that the issue you are seeing?
Sorry for the confustion but I had the deprecation warning from the package
type; allow_virtual parameter.
Fixed it yesterday, had disable_warnings in the wrong location.
Stefan
Aha, experienced the same thing last week, didn't have time to look into it
yet...
On Monday, June 16, 2014 3:30:31 PM UTC+2, Byron Miller wrote:
Running puppet 3.6.2 and disable_warnings = deprecations appears to make
no difference to prohibiting the alert about environments.
--
You
In 3.6.1 facts are also loaded twice when environmentpath is set in
main-section of puppet.conf , see
https://tickets.puppetlabs.com/browse/PUP-2651
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop
Hi Josh,
Thanks for your email.
but isn't the facts loaded from both modulepath and var lib dir just a
consequence of having pluginsync'd on the master?
I mentioned it, as this behaviour didn't happen with 3.4.3.
I'll wait for the 3.6.1 release before testing any further.
Stefan
--
Hello,
Just upgraded Puppet from 3.4.3 to 3.6.0 in our sandbox, noticed the
following.
- directory environments
Documentation says; Set environmentpath = $confdir/environments in the
puppet master’s puppet.conf (in the [master] or [main] section).
Except environmentpath does not work in the
configuration issue
Aha, if you could dig this up, that would be nice.
Stefan
On Friday, May 16, 2014 12:44:13 PM UTC+2, Felix.Frank wrote:
On 05/16/2014 11:20 AM, Stefan Heijmans wrote:
- directory environments
Documentation says; Set environmentpath = $confdir/environments
Hi,
how about using augeasprovider to manage PAM?
http://augeasproviders.com/documentation/examples.html#pam-provider
Stefan
--
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,
this one?
http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html#using-dashboard-for-node-classification
--
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
Hi,
Have you defined any classes *in* Puppet Dashbaord and assigned them
node1.example.com?
Stefan
--
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
Hi,
You could also use the augeasproviders module [1] from the forge.
Checkout the sshd_config_provider examples here [2].
Stefan
[1] http://forge.puppetlabs.com/domcleal/augeasproviders
[2]
http://augeasproviders.com/documentation/examples.html#sshd_config_provider
--
You received this
I was looking for a way to group the servers dynamically
Don't know about this but how about making use of the provided rake tasks,
like;
rake nodegroup:add # Add a new node group
rake nodegroup:add_all_nodes # Automatically adds all
nodes to a
+1 schreef kaustubh chaudhari:
Thanks for the Reply Stefan!
I did looked into these options, but i dint find a way to add only windows
systems to windows group and linux system to linux group.
-Kaustubh
On Tuesday, January 28, 2014 4:15:39 AM UTC-5, Stefan Heijmans wrote:
I was looking
With Warm Regards
Kaustubh.A.Chaudhari
(M)-09373102619
On Tue, Jan 28, 2014 at 6:35 AM, Stefan Heijmans
heij...@rechtspraak.nljavascript:
wrote:
Do you have MCollective running?
You could use this to generate a list based on specified facts (mco find
--wf fact) to use in those rake tasks
Hi,
The Exec['installCassandra'] executed correctly immediately prior to the
attempt to create the file['cassandraEnv'] resource. So I know the
appropriate information is available from the file system.
It is a new server, so exec['installCassandra'] will install it but after
that, your
Hi,
mco puppet --help
says the following for tags;
--tags, --tag TAGRestrict the run to specific tags
mco puppet runonce --noop --tags mysql::master
So, it would be correct that this runs over all puppet nodes, except the
Puppet run will only process mysql::master.
--tags
Hello,
We are looking into using hiera with hiera-gpg, installed puppet 3.1.1
hiera 1.2.0 with rpm's.
Installing the hiera-gpg gem, it also depends on the hiera gem (used
version 1.2.0).
The hiera rpm installs under /usr/lib/ruby/site_ruby/1.8/
The hiera gem installs under
You could use sourceselect in source;
http://docs.puppetlabs.com/references/stable/type.html#file
or use parameter in the source statement;
source = puppet:///modules/syslog/syslog.conf_${::$lsbmajdistrelease},
and create 2 syslog.conf files in the files directory;
syslog.conf_5
syslog.conf_6
bad cp;
source = puppet:///modules/syslog/syslog.conf_${::lsbmajdistrelease},
--
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
Or checkout this one from Ken Barber; modern module development
http://www.slideshare.net/PuppetLabs/modern-module-development-ken-barber-2012-edinburgh-puppet-camp
http://www.youtube.com/watch?v=zNXSKv6987g
--
You received this message because you are subscribed to the Google Groups
Puppet
Hello,
we run Puppet Dashboard 1.2.23 in our sandbox and get an error deleting a
node.
- first time we press the delete button nothing happens
- second time we press the delete button we get the following error;
ActiveRecord::StatementInvalid in NodesController#destroy
Mysql::Error: Lock
Hi, better try the Cobbler email list @
https://lists.fedorahosted.org/mailman/listinfo/cobbler
Op donderdag 7 februari 2013 09:27:05 UTC+1 schreef kavitha...@gmail.com
het volgende:
Hello,
I have cobbler 2.0.X installed in my system. I want t update it to
2.2.3 .
And I don't want to
This might help, watch/read this from Ken Barber; Modern Module Development
http://youtu.be/zNXSKv6987g
http://www.slideshare.net/PuppetLabs/modern-module-development-ken-barber-2012-edinburgh-puppet-cam
--
You received this message because you are subscribed to the Google Groups
Puppet Users
on what OS are you, read that for instance debian uses a different location
for config files
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/RRZ1lRxtVuIJ.
And if you create new settings.yml from settings.yml.example. Seems like like
settings_reader.rb falls back to setings.yml.example if parameters are not
correct in settings.yml. http://projects.puppetlabs.com/issues/14371
Or enable inventory in settings.yml.example?
--
You received this
I mean regardless of what settings are set shouldn't I at least be able
to see the inventory tab if enable_inventory_service is set to true?
Yes if you mean the one on top of the screen
If you click on a node when it's not configured correctly it shows;
Inventory
Could not retrieve facts from
/railties/lib/tasks/rails.rb:10)
/snip
Il giorno lunedì 19 novembre 2012 19:37:43 UTC+1, Stefan Heijmans ha
scritto:
Yes, I noticed it in 1.2.13 (
https://groups.google.com/d/msg/puppet-users/-s07XIymxCo/Yp3DpRU4t6EJ)
but not in 1.2.14.
Fixed it by running the mentioned 'rake
Yes, I noticed it in 1.2.13 (
https://groups.google.com/d/msg/puppet-users/-s07XIymxCo/Yp3DpRU4t6EJ) but
not in 1.2.14.
Fixed it by running the mentioned 'rake gems:refresh_specs'
Stefan
On Monday, November 19, 2012 10:11:35 AM UTC+1, Jacob wrote:
Hello all,
I am quite new to the puppet
No, i's not, it is correct,
see http://docs.puppetlabs.com/guides/scope_and_puppet.html
At the moment you 'include mysql' only the top scope package variable is
known, so there fore mysql package will be installed.
swap them around and mysql-server package will get installed.
class
or here; http://docs.puppetlabs.com/puppet/2.7/reference/lang_scope.html
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/hVzytyGJ6rUJ.
To post to this group,
el5 was not supported, as it has an dependency on ruby 1.8.7 and el5 comes
default with ruby 1.8.5.
now that they deliver ruby 1.8.7 with puppet 3 for el5, they perhaps can
also build them for el5.
Op vrijdag 9 november 2012 14:11:52 UTC+1 schreef Heriyanto het volgende:
Great..!
Its
Matthaus,
I also noticed the following messages with the 1.2.13 db:migrate rake task,
haven't seem them before;
# rake db:migrate RAILS_ENV=production
config.gem: Unpacked gem rspec-1.3.2 in vendor/gems has no specification
file. Run 'rake gems:refresh_specs' to fix this.
config.gem: Unpacked
http://docs.puppetlabs.com/puppet/3/reference/release_notes.html#puppet-master-web-server-changes
This needs to be changed to Puppet::Util::CommandLine
but also the require seems to have changed
from require 'puppet/application/master'
to require 'puppet/util/command_line'
Op donderdag 4
How about switching to the gem version of passenger;
gem install passenger
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/A8FERt3aTbIJ.
To post to this
Hi Matthew,
We are on Red Hat and do the following with config files which will be
updated after yum update.
- our own customized config files of the rpm are in Puppet with an addon
for rpm nameversion (for instance; files/lvm.conf_lvm2-2.02.88-7.el5)
- we have a custom facter which
Op vrijdag 13 juli 2012 02:05:29 UTC+2 schreef Jo het volgende:
Where is the documentation for this feature? How do I invoke it?
The maintaining page still just says to create a cron job.
the maintaining page also mentions;
If you run ‘rake reports:prune’ without any arguments, it
Op vrijdag 13 juli 2012 08:50:07 UTC+2 schreef Stefan Heijmans het
volgende:
the maintaining page also mentions;
If you run ‘rake reports:prune’ without any arguments, it will display
further usage instructions.
my bad, that's not the one.
# rake cron:cleanup
ln -sf
/usr/share
Op vrijdag 13 juli 2012 18:36:41 UTC+2 schreef Jo het volgende:
Hm, yes. What does that have to do with my question about the new rake job
to install a cron script?
absolutely nothing, as stated in my 2nd post about it :)
--
You received this message because you are subscribed to the
Op vrijdag 15 juni 2012 14:30:03 UTC+2 schreef Sans het volgende:
Hi guys,
Just wondering, if any one can tell me it it's a certificate related
issue. Still can't find any thing obvious. Cheers!
did you check/follow this page?
http://docs.puppetlabs.com/dashboard/inventory_support.html
Hi,
What will be the option(s) for Puppet users with no internet connection
(not allowed), if things start to depend more on PMT and Puppet Forge?
Will we be able to make a local repo and do something like a 'puppet module
localinstall' ?
--
You received this message because you are
Hello,
We are running Puppet 2.7.11-2 on RHEL57 x86_64 with MCollective (on client
and server);
On the client;
# rpm -qa|grep -e puppet -e mcollective
mcollective-common-1.2.1-1.el5
puppet-2.7.11-2.el5
mcollective-1.2.1-1.el5
#
with kernel;
Linux hostname 2.6.18-274.18.1.el5 #1 SMP Fri Jan 20
Looks likes this bug at
http://projects.puppetlabs.com/issues/11210
Op zaterdag 10 maart 2012 03:39:31 UTC+1 schreef Romeo Theriault het
volgende:
On Fri, Mar 9, 2012 at 12:05, Jeff McCune j...@puppetlabs.com wrote:
On Wed, Mar 7, 2012 at 8:22 PM, Romeo Theriault
romeo.theria...@maine.edu
Matthaus, thanks for the new rpm's.
Small question; what is the difference between these versions;
.noarch.rpm
.el5.noarch.rpm
As the .noarch.rpm are not updated, they are still on 2.7.11-1.noarch.rpm.
--
You received this message because you are subscribed to the Google Groups
Puppet Users
same is for RHEL5 (binary rpm), I see that the rpm on yum.puppetlabs.com is
from 22-Feb-2012 and the http://projects.puppetlabs.com/issues/12572 is
closed 17hours ago, thats later then the released rpm.
# rpm -q puppet puppet-server
puppet-2.7.11-1.el5
puppet-server-2.7.11-1.el5
#
#vim
Check http://projects.puppetlabs.com/issues/7270
puppet.conf doesn't support that face configuration options yet.
I use the command line option;
You can override database setting on the command line:
--adapter mysql --host 127.0.0.1 --database dashboard --username user
--password password
the
Op dinsdag 24 januari 2012 17:42:08 UTC+1 schreef Salty Old Cowdawg het
volgende:
so... I gotta get 1.8.7 on the box? EL6 is not an option at this point
as this is not a new box and does more than just puppet...
There is a topic about this from Jo Rhett;
Op maandag 9 januari 2012 19:40:00 UTC+1 schreef Jo het volgende:
2. Are there some database cleanup scripts which I have managed to
overlook that need to be run?
have you tried this?
Cleaning old
reports http://docs.puppetlabs.com/dashboard/manual/1.2/maintaining.html
perhaps also give
Op vrijdag 6 januari 2012 01:53:31 UTC+1 schreef Michael Stanhke het
volgende:
One more thing to keep in mind is that EL5 only has about 2 years of
life left on it. It launched in 2007.
That's only for RHEL5 production phase 3 (31 March 2014), End of Extended
Life Cycle is on 31 March
It's to be future proof, you can read about @
http://docs.puppetlabs.com/guides/scope_and_puppet.html
Stefan
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To view this discussion on the web visit
Op zondag 11 december 2011 19:01:14 UTC+1 schreef Nigel Kersten het
volgende:
I've cc'd Dan and Kelsey, who have both been working on a Dashboard Puppet
Face for command-line control. Although the rake tasks are totally useful,
we'd like to be able to have all this functionality under a
Is the custom fact perhaps based on a environment variable?
I had something similar a while ago, check this post;
https://groups.google.com/d/msg/puppet-users/2gjjaWFJm4Q/uANKwM-xWQ4J
Stefan
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To
Hello,
I've added an extra rake task (node:listfull) to node.rake which displays
the nodes (all or by match) with defined groups classes on it, like;
Nodename = node
Groups = group1,group2,group3
Classes = class1,class2,class3
For groups I use;
NodeGroup.find(node.node_groups).each
Ok, will create a feature request for this.
On 11 nov, 18:58, Peter Meier peter.me...@immerda.ch wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/07/2011 08:55 PM, Stefan Heijmans wrote:
The sorting in the log tab on a node report seems to be on the
level column, which is hard
The sorting in the log tab on a node report seems to be on the level
column, which is hard to read when multiple changes take place, as
notice and info of the actions are on the top and bottom of the log.
Can this be adjusted so its displayed as 'puppet agent --test' does
(sort on time and line
On 4 nov, 23:06, Matthaus Litteken matth...@puppetlabs.com wrote:
-- Fix #10270 dashboard-workers init script should check the right pid files
puppet-dashboard/ext/packaging/redhat/puppet-dashboard-workers.init
uses DASHBOARD_ROOT
this is not set in puppet-dashboard/ext/packaging/redhat/puppet-
Hello,
I've mcollective 1.2.1 with puppet 2.6.12 on rhel5.6, facter 1.6.2
setup from
http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML.
Now I've create a custom fact in /usr/lib/ruby/site_ruby/1.8/facter/
customer_status.rb.
On the client;
Running facter
On Nov 1, 10:00 pm, R.I.Pienaar r...@devco.net wrote:
- Original Message -
you should be using pluginsync to copy out custom facts:
http://docs.puppetlabs.com/guides/plugins_in_modules.html
Ok, enabled pluginsync, customer_status.rb is now copied to the client
in
Which version of dashboard are you running, 1.2x?
I'm running puppet 2.6.6 (from EPEL5) and dashboard 1.1.1 with
passenger 3.0.8 on RHEL 5.6 with ruby 1.8.5.
You could try this ruby 1.8.7 package from
http://rpm.aegisco.com/aegisco/rhel/5Server/x86_64/
They are Allowed Contributors to Chef
On
Am using dashboard 1.1.1 with the use_file_bucket_diffs option.
When clicking on the links within a report it will show the old md5
file (on the left) but not the new md5 file (on the right)
like;
content content changed '{md5}26a3112822d01f2ce6b3f052bf2809de' to
87 matches
Mail list logo
