similar to: Unsupported osfamily: Linux operatingsystem: Amazon

I''ve run into an odd one on one of my new RHEL 6 boxes. Puppet and Facter seem to disagree about the value of a fact. Puppet version: 2.7.9 Facter version: 1.6.4 Module: puppetlabs-apache apache::params falls through its if structure: if $::osfamily == ''redhat'' or $::operatingsystem == ''amazon'' { ... } elsif $::osfamily ==

I''ve written and deployed a simple Linux SSH module. But I need to modify to include support for FreeBSD and AIX. On top of that, I need to include some conditionals in there that (for example) if (/etc/file1 contains string abc) ; then install sshd-config-x & ssh-config-x elsif (/etc/file1 contains string xyz); then install sshd_config-y & ssh_config-y else install

Hi I am new in Puppet and i have one error when i test Postgresql module in infrastructure mode. I''m using Puppet 3.1.0 in Debian squeeze or 6.0.7 i tape the next command puppetd -t -v and this is the error info: Retrieving plugin info: Loading facts in pe_version info: Loading facts in postgres_default_version info: Loading facts in iptables info: Loading facts in puppet_vardir

Hi , I am trying to install jdk thru puppet . i am getting the force-yes error . err: /Stage[main]/Apiserver::Java/Package[sun-java6-jdk]/ensure: change from purged to present failed: Execution of ''/usr/bin/apt-get - q -y -o DPkg::Options::=--force-confold install sun-java6-jdk'' returned 100: Reading package lists... Please share your idea''s to fix this issue, --

my base/default includes this ntp manifest # cat modules/ntp/manifests/ntp.pp # ntp.pp class ntp { case $operatingsystem { centos, redhat: { $service_name = ''ntpd'' $conf_file = ''ntp.conf.el'' } debian, ubuntu: { $service_name = ''ntp'' $conf_file = ''ntp.conf.debian'' } } package {

In resolving bug 15980, the pip package provider was changed to recognize the RedHat osfamily fact and use the executable name "pip-python" in those environments. This does not take into account environments where pip has been installed via easy_install or by custom rpm providers. In those environments (such as mine) this osfamily change breaks the pip provider, requiring as a

Hi I largely copied the example in http://docs.puppetlabs.com/learning/modules1.html. But I''m getting an error when running the following from the client: puppet agent --server puppetmaster --waitforcert 60 --test err: /Stage[main]/Ntp/File[ntp.conf]: Could not evaluate: Could not retrieve information from environment production source(s) file:/etc/puppet/modules/ntp/files/ntp.conf

Hi, I am able to install my RPM via this puppet code ... [root@agent1 ~]# puppet apply -v install_named_conf.pp info: Loading facts in /opt/puppet/share/puppet/modules/stdlib/lib/facter/facter_dot_d.rb info: Loading facts in /opt/puppet/share/puppet/modules/stdlib/lib/facter/puppet_vardir.rb info: Loading facts in /opt/puppet/share/puppet/modules/stdlib/lib/facter/root_home.rb info: Loading

Hello, I''m running Puppet agent stand-alone on Windows. I got data-in-modules working. However, no matter what I put into the module hiera.yaml, I can only override the defaults from common.yaml by osfamily (and not, e.g., by environment). In the setup below the following command outputs: >puppet apply --binder -e "notice lookup (''my_key'')"

So set up new node, ran on the client puppetd --server puppetmaster --waitforcert 60 --test on the puppetmaster itself I ran puppetca --list saw the hostname and then ran: puppetca --sign hostname.domain.com and on the puppet node itself I went back and ran puppetd -tv and get the following error: err: Could not retrieve catalog from remote server: certificate verify failed warning: Not

Hello I have this fly::create_dir { "/usr/share/mysql-zrm/pkgs" : mode => 0755, owner => bin, group => bin } ==> creates the directory and parents .. it just does a mkdir -p with couple test so I have file { "$client_package_file" : path => "/usr/share/mysql-zrm/pkgs/$client_package_file",

hello, Till now hiera-puppet was the only way I know that allowed hiera data to be loaded from inside a module. The problem with this was that it was still subject to the site specific hierarchy which means a module author had a pretty hard time to store his data in a proper way in his module thus perpetuating the use of the params classes pattern. Now that Puppet 3 is out and it''s gem

Hi all, If you take a look at the service.rb file in the win32-service repository (the new one in the toplevel repository path), I''ve got this bit of code, which succeeds, but I can''t seem to unpack the data structure properly. Did I pack it wrong to begin with? I should know this but I''m spacing out. proc_status =

Hello, I''m having some trouble. I keep getting the following warnings when trying to run: $ puppet master --no-daemonize /usr/local/build/puppet-bundle/vendor/gems/ruby/1.9.1/gems/ puppet-2.7.12/lib/puppet/external/pson/pure.rb:7:in `<module:PSON>'': iconv will be deprecated in the future, use String#encode instead. Could not load confine test

Hello lovelies, Our team is deliberating a few different options for the hierification of our modules; and wanted to poll the collective genius before making our decision. As we all know, there are certain attributes of a package which are, by default, consistent on an OS... say, the name of a package..... class foobar { include foobar::params $package = $foobar::params::package Package

In the documentation, there is an example such as this: case $operatingsystem { sunos: { include solaris } # apply the solaris class redhat: { include redhat } # apply the redhat class default: { include generic } # apply the generic class } I''ve seen the $operatingsystem variable used elsewhere. What actually puts the value into the $operatingsystem variable? Does

Hi list, We've been looking into updating? operatingSystem and operatingSystemVersion attributes automatically and periodically (so version remains correct after OS upgrades) but quickly found out the machine account principal does not have enough permissions as it would error out with INSUFF_ACCESS_RIGHTS. As Windows /is /able to update those attributes I've been doing some

When Samba joins to AD, net creates 'Computer' object in target AD. Object 'Computer' has attributes operatingSystem and operatingSystemVersion, which automatically setup in properly value, when native Windows join to AD. I offer a patch to utils/net_ads.c to do similar way - set up operatingSystem to "Samba" and operatingSystemVersion to Samba version, when Samba

Hello, Documentation mentions that Windows service resource provider "can start, stop, enable, and disable services". Is it possible to create (register) a service using this provider? I''m running stand-alone Puppet agent 3.4.2 on Windows. Thanks, Igor. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To

If I have something like this in my node file: daemontools_service::setup { ''carbon-cache'': service_name => ''carbon-cache'', .... extra_envs => { "GRAPHITE_STORAGE_DIR" => "/mnt/statsd-data/graphite-storage" "SOMETHING_ELSE" =>