similar to: Suse documentation

Displaying 20 results from an estimated 2000 matches similar to: "Suse documentation"

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:
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
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 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 {
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)
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
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,
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
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.
2007 Aug 22
7
Frustrating warning/error from puppetd
Greetings all, (Hopefully this won''t be a HTML mail.) I''ve picked up puppet as a tool to manage a fairly small network of RHEL servers, and I''m really liking what I see so far. However, I''m having a pile of trouble with a class definition for a yum controller: # $Id$ class yum-rhel5 { file { "/etc/yum.conf": mode => 644,
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 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 --
2020 Aug 23
2
Mock config error
Hi, I am trying to create a mock configuration file that points to my local dnf repo. I have the following in the mock config template: [local-repo] name=my-Local baseurl=http://yumrepo.example.com/yum-repository/local/centos/8/x86_64/ failovermethod=priority skip_if_unavailable=False When I try to run mock I get the following error: (vgeppetto3 pts18) $ mock -v -r epel-8-x86_64
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 *
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 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 Oct 18
1
Managing Yum repositories
I''m trying to use Puppet 0.19.3 to manage Yum repositories, using the ''yumrepo'' type. Our repository configuration files currently have a line baseurl=file:///net/yum/CentOS4.1/$basearch/ where "$basearch" gets interpreted by ''yum''. I''ve tried the line baseurl => "file:///net/yum/CentOS4.1/$basearch/" in my
2021 Jul 13
3
Microsoft Teams on CentOS 7. Does the latest version work?
Does anyone else run Microsoft Teams on CentOS 7? I've used it for a while now, and it's generally worked reasonably well. However, after upgrading to the latest version from the Microsoft repos, it doesn't start up properly. Processes start and remain active until I give up and kill them, but I can't see a window or a tray icon or anything. Has anyone else seen this? Is there
2008 Aug 21
1
YumRepo Warning: not using ftp, http[s], or file for repos, skipping - 5 is not a valid release or hasnt been released yet
Hi all Does anyone know what causes this error? I have setup a local CentOS repository, with mrepo, and can succesfully use it for updates & installation of just about anything. Yet, this error comes up. Here's my /etc/yum.conf: # PUT YOUR REPOS HERE OR IN separate files named file.repo # in /etc/yum.repos.d [base-local] name=CentOS-$releasever - Base #mirrorlist=
2007 Jan 04
4
yumrepo err
I am just starting with puppet to replace a ''homegrown'' config distribution system and it is looking very promising, i will be playing with the templating next. I have run into an error when attempting to disable the shipped repo''s with CentOS 4.4. See the relevant info below. This is obviously a problem when repo definitions include multi-line baseurl''s.