similar to: Facter incorrectly detecting Virtual status on Windows VM

Hi, i recently updated our windows 2008 r2 servers to puppet 3.3.0 . Im getting the following error* (only on our exchange 2010 db servers)*ever since: LevelMessageSourceFileLineTimeerrCould not retrieve local facts: undefined method `gsub'' for nil:NilClassPuppet13.09.2013 15:12 CESTerrFailed to apply catalog: Could not retrieve local facts: undefined method `gsub'' for

Hi, I configured puppet open source with the chocolatey module and one windows client. When the puppet agent run as a service (not the interactive version) I can see in the windows event log some errors like Fault bucket 1734820220, type 5 Event name: PowerShell Fault bucket , type 0 Event name: PowerShell I tried to google it but I did not find anything relevant apart from some

Hello, I have a fresh install of puppet 3.2.3. on windows 8. I try to install the iis module (https://forge.puppetlabs.com/simondean/iis) with the command: puppet module install simondean/iis and it gives me *C:\Program Files (x86)\Puppet Labs\Puppet>puppet module install simondean/iis* *Notice: Preparing to install into C:/ProgramData/PuppetLabs/puppet/etc/modules .* *..* *Notice:

When I deploy a module I wrote with couple of custom facts, those facts do not show up in factor. But when I point FACTORLIB to the directory with those factor, they work just fine. I am running a masterless puppet version 2.7.22 and factor 1.7.1 The module structure looks like so: -license ---lib -----facter -------license.rb -------hardware_serial.rb -----puppet Any idea what is causing

The facter 1.6.18 tarball has many issues. First, the ext/osx/createpackage.sh script still uses packagemaker, which is deprecated. And even if it used that, there are a few references to files in the now-deleted conf/osx/ directory. So it''s pretty difficult to create a Mac pkg from this, but after some tweaking of the createpackage.sh script, I managed to do it! I ran the package it

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

I am working on building a facter tag based node classifier similar to https://github.com/jordansissel/puppet-examples/tree/master/nodeless-puppet/. However, I have run into an issue where I cannot use puppet''s require file ability to push the yaml file containing the facts file to the client because it would require two runs of puppet to pickup changes. Consequently, I have written into

I have download recent version puppet.3.3.0.msi from PuppetLab and trying to install it on Windows 7. The MSI package throws out the following error message, This also happen on Puppet enterprise MSI package. So I wonder if anybody encounter this problem, and what''s the solution for it? Thanks, Chengkai -- You received this message because you are subscribed to the Google

Hello I am entertaining the idea of putting some time and effort into making Facter and Puppet run on MS Windows. Call me crazy ... Does anyone know anything about the issues that I''m likely to face? What are the major stumbling blocks? Initially I''d be happy just getting File to work, this would be of tremendous value. I''m guessing that Facter will require the

Hi all, I have been working on a configuration of a Masterless configuration on Windows. I am able to get individual jobs to run like: puppet apply <path to my puppet .pp file> However, I would like to spin up the Vagrant box off a base VM, and have a puppet manifest file in a location where puppet knows to look and provision based off that file. The obvious place seems to be

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'')"

Hi guys, Currently the windows package provider does not support versions (like ensure => 1.2.3). Even though most packages set a DisplayVersion key in the registry - so the version is often available. Now I need to upgrade my puppet clients from v3.1.1 to v3.2.3-rc1 (to get facts.d support on windows) - and I was wondering if any of you had a suggestion as to how to handle it, until

I have Gentoo host where `ifconfig -a` prints long interface names truncated to 9 chars (there is closed bug report [1]). Unfortunately, `facter` uses `ifconfig -a` output to get list of interface names and because of truncation it generates `interfaces` fact with incorrect interface names. Also it fails to retrieve individual interface information with following message for each interface with

I''ve installed facter-1.6.0 and puppet-2.7.3 on a number of SLES 10 hardware nodes (HP DL580) running the Virtuozzo hosting software. Well, facter correctly identifies such a machine as a hardware node ("virtual => openvzhn") but somehow concludes that the hardware node is in fact virtual. ("is_virtual => true") This breaks some rather important logic. If

tl;dr: Windows manages permissions in a way that doesn''t always translate well to mode. We''re putting together a solution for this. Jump in the discussion. I wanted to get this conversation started. We''ve put a lot of thought into how the model should look and focused on ease of use up to more advanced scenarios. However I don''t feel that what we have is

I could swear this worked fine earlier.. Now facter, and hence puppet, do not see the domain name anymore: What could cause this? C:\Temp>facter --version 1.6.2 C:\Temp>facter | findstr kernel kernel => windows kernelmajversion => 6.1 kernelrelease => 6.1.7601 kernelversion => 6.1.7601 C:\Temp>facter fqdn NCS-VDI-05.none C:\Temp>facter hostname NCS-VDI-05

Hi, I''m rookie puppet user and I trying to establish simple Server-Client connection on configuration: Server: *Fedora F18*, Puppet 3.1.1 (installed by yum), Ruby 1.8.7 Client: *Debian 6.0.6*, Puppet 3.1.1 (installed by guide<http://shapeshed.com/setting-up-puppet-on-ubuntu-10-04/>), Ruby 1.8.7 Server sign client certificate with success but now I''m struggle with apply

Hello, I''m trying to install facter latest on OEL 5.5 but can''t because virt-what doesn''t appear to be in the oracle repositories or EPEL. Can anyone confirm/deny this? Thanks, Spencer Krum -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it,

Hello! I''m just getting started working with Puppet and testing on a Windows 2003 server. When I run facter on this server it returns a wrong value for the ipaddress (should be 10.10.0.203, but facter sets ipaddress=10.0.0.203). As you can see from the following ipconfig output, facter is looking at the TELECOM Ethernet adapter instead of the adapter used for the local domain

Hi, I run into problems with the ipaddress fact using the latest Facter gem (1.6.4, 1.6.5) on SLES11. The versions and gems I use work perfectly fine on SLES10 SP3. The problem: running "facter" without arguments results in an error, even though the erroring fact "ipaddress" is ok. test:~ # cat /etc/SuSE-release SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL