similar to: Multiple Case statements

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 {

Hi. I have the following facts available: # facter | grep oper operatingsystem => CentOS operatingsystemrelease => 6.2 Now, if I wish to use conditionals on these facts, I have to do it like this: case $operatingsystem {} case $::operatingsystemrelease {} I''m puzzled as to why can''t I just use $operatingsystemrelease, and what do these two semicolons mean? Thank

Hi, i want to use Puppet to install all packages from a webserver (no repository) . Therefore I wrote following Script: class install_package { case "$operatingsystem" { SLES: { notify {"${operatingsystem} ${operatingsystemrelease} detected":} notify {"Installing $packagename now:":}

Hi all, I''ve finally gotten around to releasing Facter 1.5. As the version bump implies, this is a relatively significant release (for a 2.3k line program, anyway). Mostly, the biggest change is refactoring the code internally so that all of the functionality is split into separate classes in separate files. Also, the facts are all loaded on-demand, which provides dramatic

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

Hi I''m having the following problem and tried already several workarounds, as well benp- tried to help me on irc. I copied the ntp modul from DavidS repo and adapted it in the Service part to run as well under openbsd. Which was just adding some binary if openbsd is the operatingsystem. However then I wanted to run it as well on a gentoo system (on centos, debian and openbsd it was

Hello Puppet list, I am taking over the puppet configuration of a sysadmin who left, and am having troubles deploying puppet to a new node. We are using puppet v2.7.3 both on the client and the puppetmaster, on Ubuntu 10.10. The node asks for a certificate fine, and I signed it on the puppetmaster. For the following logs extract I ve replaced the FQDN of my node by puppet.example.com. When doing

Hi all, I''m looking at changing the operatingsystemrelease fact for Red Hat. Linux currently just uses the kernel release as the operating system release, but I''ve got a client who wants the release to have both the specific distro (e.g., AS or EL) and the release (e.g., 3 or 4). Will this particularly annoy anyone? Anyone want to help make the release string work on

I have 2 RHEL 5.4 systems where all facter lsb* items are missing. Any ideas? Sanitized facter output: architecture => i386 domain => missyou.edu facterversion => 1.5.7 fqdn => broken.missyou.edu hardwareisa => i686 hardwaremodel => i686 hostname => broken id => root interfaces => eth0,sit0 ipaddress => 1.2.1.5 ipaddress_eth0 => 1.2.1.5 is_virtual => true

From looking at the Facter code, it looks like the ''operatingsystemrelease'' fact is currently a mirror of the ''kernelrelease'' fact. I''d like to implement this fact so that it returns the major version of the operating system, eg: Debian Sarge: operatingsystemrelease => 3.1 Debian Etch: operatingsystemrelease => 4.0 RHEL3 update 8:

Currently, facter returns the kernel version as both the kernel and operatingsystemrelease facts. I would like to change that so that on Fedora, operatingsystemrelease is the release number (5,6,7 etc.) or ''Rawhide'' ... are there any objections to making that change ? David

Hello guys :), I''m kind of new to Puppet and stuck in defining a conditional statement. Here my problem: I want to provide different apt/source.list for different versions of Debian, 6.0.x and 7.0.x, which also run different versions of Puppet, 2.7.x and 3.2.x. My first idea was to use facters variable operatingsystemmajrelease and define like this: file {

Hello, I am running puppet server version 0.25.4-2, and since Debian squeeze is the new stable release I would like to adapt some of my modules. I have a syslog-ng module, I would like to specify another template for my squeeze server. I changed my init.pp as follow : if ($operatingsystemrelease <= 5.0.8) { $syslog_template = "syslog/syslog-ng.conf.erb" } else {

Hi all, I''m trying to work with hiera database in puppet and i''m having problems using %{variables} because they don''t get the values and i don''t know why. file hiera.yaml: cat hiera.yaml --- :backends: - yaml - puppet :hierarchy:- nodes/%{domain}/%{hostname} - os/%{operatingsystem}/%{operatingsystemrelease} -

For the benefit of those running OEL (Oracle Enterprise Linux) or OVS, be aware that under 2.6.0rc4 facter doesn''t properly recognize OEL in /usr/lib/ruby/site_ruby/1.8/facter/operatingsystemrelease.rb. A diff for a fix is below; probably not the best fix but if you need it work now, this''ll do it for you. I''ve already filed a bug:

I''m re-posting this because I''m not sure that it got through the first time. If someone could at least echo back that this is reaching the list, I''d appreciate it. (I''m new to the list.) Sometimes (with variable frequency) storeconfigs stores the wrong data in the fact_values table. This has the end result that exported resources, when collected, have

Hello, I try to install puppet on freebsd 6.X. All is well but i cannot get the certificte to install and be recognized. I run .19.3. I run the puppetd --test --waitforcert 60 then sign and then i got: err: No certificate; running with reduced functionality. info: Creating a new SSL key at /usr/local/.aqadmin/puppet/conf/ssl/private_keys/xxxxxxxxxxxxxx.pem info: Creating a new certificate

Hello! I try to use foreman. It''s successfuly import current nodes from puppet storeconfig. Nodes hostname stored in short form, without domain. After that, i run puppet on newly created additional 5 nodes. They shows in foreman with full fqdn. Os, environment, architecture for this nodes not shown. How can i fix this issue? -- You received this message because you are subscribed to

Hi, I want to introduce "Proxmox" as new value in $::operatingsystem. "Proxmox" is based on Debian, so the normal value is currently "Debian". To change that, I just write a custom fact based on the facter fact "operatingsystem" Facter.add(:operatingsystem) do > ... > setcode do > ... > elsif

Hello, I have a file which varies depending on which OS/version it''s running. I tried to make a nested source parameter like this, but it didn''t work: source => $operatingsystem ? { Debian => "puppet://myserver.com/files/os/debian/etc/ssh/sshd_config", Gentoo => "puppet://myserver.com/files/os/gentoo/etc/ssh/sshd_config", RedHat =>