Displaying 20 results from an estimated 11000 matches similar to: "Installing Packages from puppet files"
2009 Dec 06
3
User Modification
I''m trying to do something like this using puppet 0.24.8.
define removeuser() {
@ user { $name:
ensure => absent
}
realize User["$name"]
}
$removelist = ["bob", "bill", "billy"]
@ removeuser { $removelist : }
It''s failing with "err: Could not retrieve catalog: Failed to realize
virtual resources User[bob] on node
2009 Dec 07
4
Require Module before Resource Type
How do I make sure a module is loaded before puppet requests a
specific resource type. For example,
node ''test'' {
include cron
cron { "my-test-cron":
}
}
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from
2009 Dec 04
3
yumrepo is missing name attribute in repo files using puppet-0.24.8-4.el5
I''m using puppet-0.24.8-4.el5 on CentOS 5.4.
My problem is yumrepo isn''t writing the "name=" field to the
repository files which causes yum to complain with the error:
Repository ''local-CentOS-5.4-x86_64'' is missing name in configuration,
using id
I get this behavior on all of my yumrepo definitions. One of them
looks like this:
yumrepo {
2011 Jul 13
1
Best way to create a repo, looking for advice and tips
What is the best way to create a repo?
I like to take baby steps, and test things as I go.
Is this kind of development style possible with puppet?
My hope was to do something like:
Have 1 ec2 vm open that will be my test vm where I will manually install
e.g. mysql or nginx, and then look at what files I will need to work with.
Make modifications to my puppet repo, then commit and apply the
2012 Nov 09
4
Usage of puppet to deploy and configuration manage software patches
I have some questions in terms of how to use puppet of configuration
management for software patches. My previous approach was it to create a
puppet module for each patch ... Like Patch1 includes (FileA, FileB,
FileC), Patch2 includes (FileD, FileE)... So far so good and that works but
now i have to create a Patch3 with lets say FileF and FileA included. As
you can see there will be a puppet
2006 Sep 21
30
Using multiple values for source, for platform/arch/host configs
Hi, in an attempt to simplify my configuration, and from a suggestion
on IRC, I was thinking of using multiple values for file { source =>
[] }. Was just currious if anyone had any comments on this.
Basically, I setup my file-server to use:
<snip>
[private]
path /var/lib/puppet/files/private/%H
allow *
[shared]
path /var/lib/puppet/files/shared
allow *
2007 Apr 26
6
Struggling to define multiple yum/rug repositories
My head hurts from trying to figure this out for the past several hours . . .
I want to determine what provider to use based on a fact (thanks for
the suse version fact btw) but I ain''t gettin it:
What''s wrong? Am I going down the completely wrong path? Is there a better way?
# suse-yum.pp
case $suse_repo_name {
#sled10-i586: {Package{ provider => rug}}
sled10-i586:
2007 Apr 12
5
Suse documentation
Hi,
I''ve writen a draft describing puppet on SuSE/opensuse linux.
http://www.reductivelabs.com/trac/puppet/wiki/PuppetSuSE
Any feedback is welcome.
Martin
2010 Oct 25
2
Multiple errors on puppet client runs: "A section with name updates already exists"
Hello,
I''m currently running Puppet 0.25.5-1 on CentOS 5.5. Everything has
been going swimmingly until a couple of weeks ago, when I began
receiving errors on one of my nodes. The node in question is also my
puppetmaster, but the errors seem client-related. The errors are:
err: //yumrepos::centosbase/Yumrepo[addons]: Failed to retrieve
current state of resource: A section with name
2011 Mar 24
6
run stages in puppet 2.6
hello guys,
I am trying to incorporate run stages into my puppet setup. I''ve been
working with this for a few days and I haven''t quite got the hang of
it yet...
When I attempt my puppet run this is the error I see:
------------------------------------------------
[root@chromews21 ~]# puppetd -t
err: Could not retrieve catalog from remote server: Error 400 on
SERVER:
2012 Jan 23
4
Another Discovered/Undocumented feature of yumrepo - and a workaround
I was working with yumrepo, defining new entried and seeing them appear in /etc/yum.repos.d
After considerable tinkering, and with the sad discovery that resource { ''yumrepo'': purge => true } does not work,
I moved my working /etc/yum.repos.d to /etc/yum.repos.d-old and re-ran my catalog.
To my surprise, the repo entried were appended to /etc/yum.conf
Long story short:
I
2011 Nov 01
4
2.7.6 yumrepo not working
Just upgraded to 2.7.6 and the yumrepo type does not write out our yum
configs correctly, anyone experiencing this? Documentation hasn''t changed
from what I can tell for this type.
# facter -version
1.6.2
# puppetd --version
2.7.6
# facter architecture
x86_64
# facter operatingsystem
Fedora
# facter operatingsystemrelease
14
==== My manifest ====
yumrepo {
2008 Feb 22
12
Yumrepo and managing the contents of /etc/yum.repos.d directory...
Puppet version: 0.22.4
facterversion => 1.3.7
rubyversion => 1.8.5
Given the following:
file { yum_repo_d:
path => "/etc/yum.repos.d",
ensure => directory,
recurse => true,
purge => true
}
yumrepo { pkg_repo:
descr => "Packages Repository",
enabled => 1,
baseurl => "http://Some/path/",
gpgcheck => 0,
2012 May 15
4
enabling a yum repository
I have a class that pulls in some yum repositories. One of the yum
repositories is disabled, but on one host I''d like to enable it.
i.e. I''d like to do something like this:
class { ''myyumrepos'': }
yumrepo { ''EPEL'': enabled => 1, }
What''s the best way to do this?
I am using an ENC.
--
Biltong
biltong@fastmail.fm
--
2010 Jul 29
5
Multiple repositories under one file
Hello All,
In all the examples that I see you configure one repo per file;
i.e:
yumrepo { "testing.com-repo":
baseurl => "http://repos.testing.com/fedora/$lsbdistrelease/",
descr => "Testing.com''s YUM repository",
enabled => 1,
gpgcheck => 0,
}
But how do I specify multiple entries to the same file?. For
instance, I just one to have one
2011 Mar 16
3
only one puppet client fails with yum
hello list..
I am sharing a yum configuration in a class (centos.pp) between two
nodes. But the yum configuration doesn''t apply at all to one node
even tho it does to another identically configured node.
## packages are failing to install via yum on one ec2 aws instance and
another identical ec2 instance works fine
[root@kromep2 ~]# cat /etc/redhat-release
CentOS release 5.5 (Final)
2007 Jan 22
3
Resource dependencies
For example, I have a bunch of package resources defined for packages
which are contained in the yum repositories defined by the yumrepo
resources. If the package is installed first, then it will fail
because the repository is not available. I know about "require". But
I would prefer not to add a direct dependency on the source
repository. Is there an easier way to do this? What
2010 Sep 28
15
YUMREPO { productname => PowerEdge 2650}
Hello All,
How do I specify a variable that has a space in it? I''m trying
to setup a yum repo that has two different baseurl''s based on the
product name ($productname). Default goes one way, but if the product
is "PowerEdge 2650" then is a different URL. The thing is, that is
only picking up the default. How should I specify the value with the
space in the
2007 Jul 17
1
Yumrepo''s subscribe ran before package require Yumrepo?
I am trying to set a "subscribe" for a Yumrepo object so that an Exec "yum
clean all" is ran immediately after a Yumrepo is changed. With the following
setup, I am not seeing the "subscribe" fire off until after Packages that
have a require pointing to the Yumrepo["custom"] are attempted to be
installed.
Is in right to expect that the subscribe on the
2012 Nov 01
7
Install RPM package via puppet
I am trying to get a package (iftop) installed on a test node using puppet
but I can''t get it to install. This seems like it should be simple, but I
can''t figure out what I am missing. Have done a lot of searching for
similar problems and the answers I found seem to be vague in the details
and explanation.
I have the package added to an internal yum repo. OS is Centos 5.4.