search for: lsbmajdistrelease

Hi all, I''ve noticed that facter version superior from epel do not display lsbmajdistrelease fact: # facter lsbmajdistrelease 5 # rpm -qa|grep facter facter-1.5.5-1.el5 # cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.5 (Tikanga) # facter lsbmajdistrelease # cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.5 (Tikanga) # rpm -qa|grep facter facter-...

...common.pp:: class rhnds::common inherits rhnsd { if ($operatingsystem != ''RedHat'') { fail("${fqdn} is not an RedHat OS, it is $ {operatingsystem}. Unable to apply module RHN, since it is only used on RedHat based systems") } if ($lsbmajdistrelease != ''5'') { fail("${fqdn} is not a 5-major release from RedHat. Puppet modules for other major releases have not been made yet.") } $rhn_client_requirements = $lsbmajdistrelease ? { 5 => [ ''yum'', '...

I''m running puppet 0.24.6 on CentOS 5.2 from a puppetmaster on a virtual server to a variety of client servers both virtual and metal running either CentOS 5.2 or Fedora Core 10. I want to extend this to servers running RHEL 5 (and 6) in the near future. My problem is I have puppet set up with all repositories (mirrored locally using cobbler) included in one file in

Hi All, In the example42 modules, I noticed the following is done: # Calculate OS version (without using lsb facts) $ossplit=split($operatingsystemrelease, ''[.]'') $osver=$ossplit[0] I''ve been using $lsbmajdistrelease in all my configs. Is there any particular reason why I might want to use the above instead? (apart from the dependency on redhat-lsb, which is always installed) Regards, Gonzalo -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post...

...Hat Enterprise Linux Server release 6.3 (Santiago)" - architecture: x86_64 boardmanufacturer: "Intel Corporation" + architecture: x86_64 type: Other serialnumber: "VMware-42 26 2c 7e 64 54 65 e5-bd 53 81 d7 56 02 2e e4" - processorthreadcount: "1" lsbmajdistrelease: "6" + processorthreadcount: "1" title: "mcollective::server" lsbdistcodename: Santiago mcollective_serverpackage: mcollective id: root At first I was thinking of just changing the template so that the the yaml output is sorted by key order (http://www...

...wn hardwaremodel => x86_64 id => root is_virtual => true kernel => Linux kernelmajversion => 2.6 kernelrelease => 2.6.26-2-amd64 kernelversion => 2.6.26 lsbdistcodename => n/a lsbdistdescription => Debian GNU/Linux 6.0 (n/a) lsbdistid => Debian lsbdistrelease => 6.0 lsbmajdistrelease => 6 Cheers, Steph -- 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 this group, send email to puppet-users+unsubscribe@googlegroups.com. For more...

...ed so each fact resolution can specify a separate timeout, but the default is still 0.5. Refactered ipmess.rb and util/ip.rb to support separate *BSD logic for *BSD aliased interfaces. Updated dmidecode facts fixing ticket #60 Added AIX support for some facts Add lsbmajdistrelease fact for CentOS and Red Hat Updated Red Hat spec file for new version The ''facter'' executable now has an option (-p|--puppet) for loading the Puppet libraries, which gives it access to Puppet''s facts. Added autoloading to Facter with a default of n...

...nto lowercase because people that use the server rather like lowercase hostnames... I did some basic work : Template : $ cat /var/puppet/templates/rh-network.erb # WARNING this file is autogenered by puppet. Any change there will # be overwritten every 30 minutes # NETWORKING=yes <% if lsbmajdistrelease == "5" %> NETWORKING_IPV6=no <% end %> HOSTNAME="<%= myfqdn %>" Class used : $ cat rh-hostname.pp class hostnameclean { #$myfqdn = downcase ($fqdn) $fqdn.downcase => $myfqn case $operatingsystem { "Redhat" : {...

...l architecture: &id001 x86_64 hardwareisa: x86_64 hardwaremodel: *id001 kernelrelease: 2.6.18-274.17.1.el5xen clientversion: *id002 kernelversion: 2.6.18 lsbdistcodename: Final lsbdistdescription: CentOS release 5.8 (Final) lsbdistid: CentOS lsbdistrelease: "5.8" lsbmajdistrelease: "5" I did some debugging on the IRB. On the commandline I do get the expected format. To me it seems the to_yaml is not working for me in combination with inline template. What is causing the extra leading spaces? irb irb(main):001:0> h = { "a" => 1 , "b" =&...

Just started a rollout of centos 6.x across our Puppet deployment (100-odd servers). what fact would people suggest I use to distinguish 5.x from 6.x (quite a lot of subsystems are different between major releases)? lsb* facts don''t seem to be present on centos 6 - is this an EPEL bug, or have they just been removed in Facter? Thanks! -- You received this message because you are

Does anyone have any insight into this error message? err: Could not retrieve catalog from remote server: Error 400 on SERVER: The fact named fact_stomp_server does not appear to be a valid hostname. The value of '''' does not match ''^[a-zA-Z0-9.-]+$''. A common cause of this problem is running puppet agent as a normal user instead of root, or the fact is