similar to: Virt-what on OEL 5

Displaying 20 results from an estimated 10000 matches similar to: "Virt-what on OEL 5"

2013 Nov 05
5
Deployed custom facts with module do not show up
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
2013 May 31
22
ruby issue
Hi, I am having problems installing Puppet Server. My gem list follows and then the attempt to install puppet-server. The specific errors are: Error: Package: puppet-3.2.1-1.el6.noarch (puppetlabs) Requires: ruby-augeas Error: Package: hiera-1.2.1-1.el6.noarch (puppetlabs) Requires: rubygem-json Error: Package: puppet-3.2.1-1.el6.noarch (puppetlabs)
2013 Apr 18
4
fact_stomp_server
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
2013 Jul 15
1
facter 1.6.18 tarball has a dangerous mac preflight script
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
2013 Apr 15
1
Fedora 16 leaving yum.puppetlabs.com
Fedora 16 reached end of life on 2013-02-12 [1], so we are no longer building new packages for it and will remove it from our yum repository on Monday, May 6. [1] - https://lists.fedoraproject.org/pipermail/announce/2013-February/003144.html -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop
2013 Sep 13
27
[windows server 2008 r2] puppet errors in 3.3.0 on exchange database servers
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
2013 Nov 12
1
Own Package Installscript
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:":}
2013 Oct 08
3
Facter incorrectly detecting Virtual status on Windows VM
Ran into a problem with Facter on a Windows 2008 R2 system running on a proxmox server. Facter reports the machine as being physical. This is due to the WMI query used in the virtual.rb file is being return "Bochs" as the Manufacturer and Model. Adding an additional "When" statement to the Ruby file (virtual.rb) corrected the check coming back as physical. -- You
2013 Jan 29
7
Seriously, am I the only one having trouble with the RHEL puppetlabs repos?
This is the third time I''ve sent a message about this. Does anybody know what''s going on? I''m going to file a bug if this isn''t fixed soon. RHEL6: http://yum.puppetlabs.com/el/6/products/x86_64/repodata/primary.sqlite.bz2: [Errno -1] Metadata file does not match checksum Trying other mirror. Error: failure: repodata/primary.sqlite.bz2 from
2013 Nov 01
1
HELP!!! puppet-enterprise-3.1.0-el-6-i386 master/agent test fails
** I installed PE Master on one VM and Agents on two VMs pointing to master . Agent1 VM 64 bit works fine , but agent2 VM 32 bit fails with below error. Only difference is architecture. One more note both the agent nodes were accepted from Dashboard,so master has both the certificates. Any help will be greatly appreciated. puppet-enterprise-3.1.0-el-6-i386]# puppet agent --test Info:
2010 Jul 19
1
facter fails to recognize OEL/OVS in operatingsystemrelease.rb
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:
2013 Mar 21
3
Announce: Puppet Dashboard 1.2.23 Available
Puppet Dashboard 1.2.23 is a maintenance release of the 1.2 series of Puppet Dashboard with bug fixes and minor features. This release is available for download at: https://downloads.puppetlabs.com/dashboard/puppet-dashboard-1.2.23.tar.gz Available in native package format in the Puppet Labs yum and apt repositories at: http://yum.puppetlabs.com and http://apt.puppetlabs.com Please report
2013 Jan 29
7
stuck installing puppet in RHEL 5
Hi All, Im trying to install but with no luck. Any idea what I did wrong ? ** mkdir -p /var/log/pe-console-auth ** touch /var/log/pe-console-auth/cas.log ** touch /var/log/pe-console-auth/auth.log ** chmod 770 /var/log/pe-console-auth ** chmod 660 /var/log/pe-console-auth/auth.log ** touch /var/log/pe-console-auth/cas_client.log ** chmod 660 /var/log/pe-console-auth/cas_client.log ** chown -R
2013 Jan 17
5
puppetlabs-products yum checksum failing
I''m reasonably confident that the problem I''m having here is upstream. RHEL5: # yum repolist | grep puppet puppetlabs-deps Puppet Labs Dependencies El 5 - x86_64 45 puppetlabs-products Puppet Labs Products El 5 - x86_64 161 # yum clean all Loaded plugins: security Cleaning up Everything # yum repolist 2>&1 | grep puppet
2013 May 25
1
Error: Could not find dependency Yumrepo[puppetlabs-products] for Package[puppet]
I have installed puppet from puppet-labs yum repository on OEL familiy of Red Hat Enterprise Linux Server release 5.9 (Tikanga) ---------------------------------------------------------------------------- [root@oel-puppet-master modules]# yum list facter Loaded plugins: rhnplugin, security This system is not registered with ULN. You can use up2date --register to register. ULN support will be
2012 May 16
2
Announce: Facter 2.0.0rc1 Available
Facter 2.0.0rc1 is a feature release candidate with bug fixes, features and other improvements. Facter 2.0 is designed to accompany the upcoming Puppet 3.0 release and has breaking changes from Facter 1.6.x. Facter 2.0 is not backwards compatible with Puppet 2.6 or 2.7. It includes contributions from the following people: Chris Price, Daniel Black, Daniel Pittman, Garrett Honeycutt, Gary Larizza,
2013 Jul 16
14
"puppet module install simondean/iis" gives error "Error: cert already in hash table"
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:
2013 Jul 22
11
chocolatey, windows, powershell and fault bucket
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
2012 Oct 09
6
upgrade to 3.0, ruby and rhel 5
Hi all, I wanted to upgrade today the clients to 3.0 but, for RHEL 5, ruby 1.8.7 is not in the official repos. If we upgrade from the official (1.8.5) package to the puppetlabs provided one, there is a good chance that we will lose support for several applications that we are running. Is there a way around this? (except upgrading to PE, which will come next year :D ) Thanks. -- You received
2013 Aug 15
1
Announce: Puppet 3.2.4 Available [ Security Release ]
Puppet 3.2.4 is now available. 3.2.4 addresses two security vulnerabilties discovered in the 3.x series of Puppet. These vulnerabilities have been assigned Mitre CVE numbers CVE-2013-4956 and CVE-2013-4761. All users of Puppet 3.2.3 and earlier are strongly encouraged to upgrade to 3.2.4. For more information on these vulnerabilities, please visit http://puppetlabs.com/security/cve/cve-2013-4761