Re: [Puppet Users] multiple puppet masters, multiple puppetdb's
The problem is that the puppetdb certificate is not for localhost, but for puppetdb hostname. You have two options: 1. Set in /etc/hosts puppetdb as alias of localhost 2. Generate a new certificate for the puppetdb with an alias for local host as valid hostname. I would prefer option 1. Regards, El 13/06/2014 02:29, Chris dmag...@gmail.com escribió: Hi all, I'm trying to set up something that will have multiple puppet masters (with one as the CA) and multiple puppet db's (they will be geographically dispersed). The multi-masters stuff all works fine, but I'm struggling with multiple puppet db's. Ideally I'd like puppet db to live on the same server as the puppet master for a particular region (so a master + puppetdb in US, one in UK, one in AU for starters) but I'm not sure if that's supported at all. I've got puppetdb on the master CA server and that works fine, but if I point the other masters to 'localhost' (in puppetdb.conf) I get ssl errors on the agent runs: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit 'replace facts' command for client1.local to PuppetDB at localhost:8081: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [certificate revoked for /CN=puppetmaster1.local] I saw in the puppetdb docs about using postgres replication to do things but if an agent has to go back to the main server for every run to report, I don't understand why you'd want to do that. Any help or ideas would be great. Cheers, Chris. -- Postgresql php tutorials http://www.designmagick.com/ -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/ msgid/puppet-users/539A45DF.2070100%40gmail.com. For more options, visit https://groups.google.com/d/optout. -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAF_B3ddhPWixU7H3Kfx2Y7qaSm_hLA_6_uFUZ1cFTJJduXxkVw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Exception LoadErrror with Passenger and Apache httpd
Hi, you really ought to try and get rid of that gem. gem clean won't cut it. Try gem uninstall puppet. HTH, Felix On 06/10/2014 07:47 PM, Brian Wilkins wrote: I have been running my puppetmaster with passenger and apache httpd successfully for sometime now. During a recent upgrade to Puppet 3.6.1, I am seeing this following exception in /var/log/httpd/error_log : *** Exception LoadError in PhusionPassenger::Rack::ApplicationSpawner (no such file to load -- rack) (process 3072, thread #Thread:0x7f2d85cfb368): I tried setting my gem environment in the config.ru, but that didn't seem to help. I see that the puppet 3.6.1 gem is installed. I installed puppet 3.6.1 via RPM not gem. I also ran gem clean to no avail. Any idea how to get past this error? I see that the puppet 3.6.1 gem has a rack - maybe it can't be found in my path? -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/539AB69E.1090205%40alumni.tu-berlin.de. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] How's life with 3.6.2?
This was in the dev environment (not vagrant, just a separate set of VMs with
their own set of puppetmasters). If things are fine for a few days I'll roll up
through staging and production.
On Fri, Jun 13, 2014 at 03:37:20PM +1000, Pete Brown wrote:
Nice report.
Thanks.
I have a dev environment i build with vagrant every day. I even
managed to bootstrap a puppetmaster in there for testing exported
resources.
Highly recommend using Vagrant because it forces you to fix those
dependency errors you would normally not see on live servers that have
been running for a while.
All my code gets the bugs tested out of it on base vms before it gets
pushed into production.
On 13 June 2014 02:38, Christopher Wood christopher_w...@pobox.com wrote:
Verdict: Went fine with the usual upgrade teething troubles. (Once I
figured those out I reverted to my pre-upgrade VM snapshot on the first
upgraded host and there was no hassle the second time.) I went from 3.4.3
to 3.6.2.
The procedure was to upgrade the following rpms on each host (daemon
restarts were included), reading logs as I went:
for i in mcollective-puppet-agent hiera facter puppet mcollective; do mco
package $i update -F hostname=$SERVER; done
Upgrading mcollective this way meant the last mco package never returned
since the daemon was restarted, I'm fine with that.
Then this for the puppetmasters to ensure the passenger-based puppetmasters
were restarted:
mco service httpd restart -F hostname=$SERVER; done
These three issues, unfixed, would have been blockers for me doing an
upgrade:
1) yumrepo mirrorlist vs baseurl (fixed in puppet 3.5.1)
https://tickets.puppetlabs.com/browse/PUP-2155 (dupe)
https://tickets.puppetlabs.com/browse/PUP-2150
I was using mirrorlist, it was past time to use baseurl anyway. I never saw
an error since I was on 3.4.3.
Solution: use baseurl.
2) datacat module 0.4.2 incompatible with puppet = 3.5 (fixed in datacat
0.5.0)
https://github.com/richardc/puppet-datacat/issues/12
I saw this sort of error on the puppetmaster:
Jun 12 09:48:15 puppetmaster1dev puppet-master[4552]: undefined method
`module' for production:String at
/etc/puppet/environments/production/modules/datacat/manifests/init.pp:59 on
node puppetmaster1dev.company.com
Solution: upgrade the datacat module to 0.5.0
3) mcollective service/package trouble with puppet 3.5 (fixed in
mcollective-puppet-agent 1.7.1)
https://tickets.puppetlabs.com/browse/MCOP-23
I saw the following errors when checking package status after the initial
aborted upgrade of mcollective only, not any mcollective plugins.
a) First, this after a plain upgrade (but without restarting the puppet
agent):
$ mco package mcollective status -F hostname=puppetmaster1dev
* [ == ] 1 / 1
puppetmaster1dev.company.com: Could not autoload puppet/type/package: no
'environments' in
{:root_environment=#Puppet::Node::Environment:0x7fc087f1d070
@manifest=/tmp, @modulepath=[], @watching=true, @name=:*root*,
@config_version=nil,
:current_environment=#Puppet::Node::Environment:0x7fc087f1d070
@manifest=/tmp, @modulepath=[], @watching=true, @name=:*root*,
@config_version=nil} at top of [[0, nil, nil]]
Summary of Arch:
No aggregate summary could be computed
Summary of Ensure:
No aggregate summary could be computed
Finished processing 1 / 1 hosts in 46.00 ms
b) Second, after restarting both mcollective and puppet:
$ mco package mcollective status -F hostname=puppetmaster1dev
* [ == ] 1 / 1
puppetmaster1dev.company.com: undefined method `properties' for
nil:NilClass
Summary of Arch:
No aggregate summary could be computed
Summary of Ensure:
No aggregate summary could be computed
Finished processing 1 / 1 hosts in 31.84 ms
Solution: upgrade mcollective-puppet-agent before upgrading/restarting
mcollective and puppet
Editorially, this was very relaxing and I should have saved it for Friday
afternoon.
On Thu, Jun 12, 2014 at 07:48:24AM -0400, Christopher Wood wrote:
That's why I'm upgrading (otherwise 3.4.3 works for me), but I will have a
hard time justifying any upgrade that leads to breakage. They're in
profile::base for me too.
Well, on with my testing!
On Thu, Jun 12, 2014 at 10:36:07AM +1000, Pete Brown wrote:
I decided to put puppet,hiera and facter versions into my base profile
so upgrades are tested in my dev environment and then pushed out to
production when I am happy.
3.6.2 is also a security release so I (and you very likely) want it
(and the relevant ssl fixes) pushed out asap.
I also just added a versioned ssl class to my profiles to make that even
easier.
On 12 June
Re: [Puppet Users] SuSe SLES: error when refreshing puppet yum repository
Thanks for this! zypper refresh with this repo is now successful. But now I get another error: myserver:~ # zypper --non-interactive install --repo puppet puppet Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides rubygems needed by rubygem-ruby-shadow-2.3.4-21.1.x86_64 Solution 1: do not ask to install a solvable providing puppet Solution 2: break rubygem-ruby-shadow by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c] (c): c Am Donnerstag, 12. Juni 2014 18:09:14 UTC+2 schrieb Darin Perusich: build.opensuse.org is the OBS project location where the packages are managed/built. Successfully built packages are published at download.opensuse.org, so for SLES use the below repo URL. http://download.opensuse.org/repositories/systemsmanagement:/puppet/SLE_11_SP3/ -- Later, Darin -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/18f47009-68f3-4eb3-9ff4-375da38d7d94%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] SuSe SLES: error when refreshing puppet yum repository
rubygem-ruby-shadow is available in the repo so I don't know what
could be causing that.
I just added that repo to a SLES box, installed puppet and it pulled
down the dependencies without issue, the the output below.
What the output you get from zypper info rubygem-ruby-shadow and
zypper lr -d ?
slestest:~ # zypper ar
http://download.opensuse.org/repositories/systemsmanagement:/puppet/SLE_11_SP3
puppet
Adding repository 'puppet' [done]
Repository 'puppet' successfully added
Enabled: Yes
Autorefresh: No
GPG check: Yes
URI:
http://download.opensuse.org/repositories/systemsmanagement:/puppet/SLE_11_SP3
slestest:~ # zypper in puppet
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following NEW packages are going to be installed:
facter puppet ruby rubygem-hiera rubygem-json_pure
rubygem-ruby-shadow rubygems
7 new packages to install.
Overall download size: 4.9 MiB. After the operation, additional 17.8
MiB will be used.
Continue? [y/n/? shows all options] (y):
Retrieving package ruby-1.8.7.p357-0.9.15.1.x86_64 (1/7), 1.8 MiB (6.4
MiB unpacked)
Retrieving: ruby-1.8.7.p357-0.9.15.1.x86_64.rpm [done]
Retrieving package facter-2.0.1-2.1.x86_64 (2/7), 80.0 KiB (222.0 KiB unpacked)
Retrieving: facter-2.0.1-2.1.x86_64.rpm [done]
Retrieving package rubygems-1.8.15-0.14.1.x86_64 (3/7), 181.0 KiB
(558.0 KiB unpacked)
Retrieving: rubygems-1.8.15-0.14.1.x86_64.rpm [done]
Retrieving package rubygem-ruby-shadow-2.3.4-21.1.x86_64 (4/7), 23.0
KiB (89.0 KiB unpacked)
Retrieving: rubygem-ruby-shadow-2.3.4-21.1.x86_64.rpm [done]
Retrieving package rubygem-json_pure-1.8.1-28.12.x86_64 (5/7), 276.0
KiB (759.0 KiB unpacked)
Retrieving: rubygem-json_pure-1.8.1-28.12.x86_64.rpm [done]
Retrieving package rubygem-hiera-1.2.1-11.11.x86_64 (6/7), 46.0 KiB
(115.0 KiB unpacked)
Retrieving: rubygem-hiera-1.2.1-11.11.x86_64.rpm [done]
Retrieving package puppet-3.6.2-2.1.x86_64 (7/7), 2.6 MiB (9.6 MiB unpacked)
Retrieving: puppet-3.6.2-2.1.x86_64.rpm [done (1.0 MiB/s)]
Installing: ruby-1.8.7.p357-0.9.15.1 [done]
Installing: facter-2.0.1-2.1 [done]
Installing: rubygems-1.8.15-0.14.1 [done]
Installing: rubygem-ruby-shadow-2.3.4-21.1 [done]
Installing: rubygem-json_pure-1.8.1-28.12 [done]
Installing: rubygem-hiera-1.2.1-11.11 [done]
Installing: puppet-3.6.2-2.1 [done]
Additional rpm output:
%{1} puppet.service
warning: /etc/puppet/puppet.conf saved as /etc/puppet/puppet.conf.rpmorig
%{1} puppet.service
--
Later,
Darin
On Fri, Jun 13, 2014 at 6:03 AM, Torsten Kleiber
torsten.klei...@googlemail.com wrote:
Thanks for this!
zypper refresh with this repo is now successful.
But now I get another error:
myserver:~ # zypper --non-interactive install --repo puppet puppet
Loading repository data...
Reading installed packages...
Resolving package dependencies...
Problem: nothing provides rubygems needed by
rubygem-ruby-shadow-2.3.4-21.1.x86_64
Solution 1: do not ask to install a solvable providing puppet
Solution 2: break rubygem-ruby-shadow by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/c] (c): c
Am Donnerstag, 12. Juni 2014 18:09:14 UTC+2 schrieb Darin Perusich:
build.opensuse.org is the OBS project location where the packages are
managed/built. Successfully built packages are published at
download.opensuse.org, so for SLES use the below repo URL.
http://download.opensuse.org/repositories/systemsmanagement:/puppet/SLE_11_SP3/
--
Later,
Darin
--
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, send an
email to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/18f47009-68f3-4eb3-9ff4-375da38d7d94%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CADaviKvH5dAy%3DRybHqGbrjv-2RE%2B2G49bdgcoo%3Dyj4XgUEq5aQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Grant user SELECT on pg_stat_database?
How do I grant a user SELECT privileges on the pg_stat_database catalog? Using the normal postgresql::server::database_grant approach just returns: 'ERROR: database pg_stat_database does not exist -Chris -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/cfe4fa21-e6f1-4bc4-92ce-cbf4706ba389%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Could not find or load main class com.puppetlabs.puppetdb.core
Hello, I'm attempting to build puppetdb-2.0.0 from source and the resulting jar fails to start and errors with Could not find or load main class com.puppetlabs.puppetdb.core. When inspecting the puppetdb.jar it doesn't contain any of the classes so it would appear that 'lein uberhar' is failing to build said classes. When listing the content of puppetdb-2.0.0-standalone.jar the do not exist. Also compiling the source, 'lein compile' doesn't appear to be compiling the classes, no Compiling com.puppetlabs.puppetdb.core or Compiling clj-time.core output like when I build 1.6.3 and nothing created under target/classes. Any thoughts on what might be causing this? This system is openSUSE 13.1, puppet-3.0.2, and Oracle java 1.7.0_55-b13. To recreate do: wget https://github.com/puppetlabs/puppetdb/archive/2.0.0/puppetdb-2.0.0.tar.gz tar -zxf puppetdb-2.0.0.tar.gz cd puppetdb-2.0.0/ echo 2.0.0 version lein uberjar Check for puppetdb.core in resulting jar: jar tf target/puppetdb-2.0.0-standalone.jar |grep puppetdb.core com/puppetlabs/puppetdb/core.clj -- Later, Darin -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CADaviKv3z69S86eJBzaE%2B5dK%2BOWmGEX_Mc2DQ0O_mV8Yo1tokw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Re: Puppet Dashboard port
You will find this works great. http://devsops.blogspot.ca/2013/04/installing-puppet-dashboard.html On Thursday, June 5, 2014 2:15:48 PM UTC-4, Don Dorman wrote: I almost have it figured out, and of course I will share the information On Thursday, June 5, 2014 11:55:35 AM UTC-4, Kwame Bahena wrote: Ah, Can you please then share your config and the steps you are following? Cheers! On Thu, Jun 5, 2014 at 10:15 AM, Don Dorman donn...@gmail.com wrote: Thanks so much for the link, but I am testing the opensource version of Puppet. A lot of the directory structure is much different. On Thursday, June 5, 2014 10:27:56 AM UTC-4, Don Dorman wrote: Good morning Everyone. I have been struggling to change the default port for Dashboard access from port 3000 to use SSL port 443. My Dashboard version is 1.2.34 if I am not mistaken. My OS is RHEL 6.4, Puppet Master 3.42-1 Any directions would be great. -- 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, send an email to puppet-users...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/85a2e004-f502-4c73-a74e-8226d111d730%40googlegroups.com https://groups.google.com/d/msgid/puppet-users/85a2e004-f502-4c73-a74e-8226d111d730%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/19cafabe-0cd5-4d2f-b853-7b9ad852aad4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] multiple puppet masters, multiple puppetdb's
I'm trying to set up something that will have multiple puppet masters (with one as the CA) and multiple puppet db's (they will be geographically dispersed). The multi-masters stuff all works fine, but I'm struggling with multiple puppet db's. Ideally I'd like puppet db to live on the same server as the puppet master for a particular region (so a master + puppetdb in US, one in UK, one in AU for starters) but I'm not sure if that's supported at all. The design would be driven by your requirements. If you don't care about having data visible across both DC's, then you can certainly configure a puppetdb instance with its own database in each region. However if you expect data visibility across both data centres you'll need to setup some sort of data replication. I saw in the puppetdb docs about using postgres replication to do things but if an agent has to go back to the main server for every run to report, I don't understand why you'd want to do that. At a higher level replication is going to give you: * Ability to use exported resources across both DC's * Ability to use puppetdbquery to generate data within your Puppet manifests across both DC's * Ability to simply have 1 console to view reports across all DC's The key point here being the 'view across both DC's' from a data perspective. Now the PuppetDB service can be configured to specify 1 database to be used for reads, and another database for read/write functionality (storage of reports/facts/catalogs basically). See this link for the details on how to configure this: http://docs.puppetlabs.com/puppetdb/2.0/configure.html#read-database-settings This can allow the possibility to keep a read/write postgresql instance in 1 DC, and a local read-only copy in the other, but yes - this does mean that ultimately all writes go back to the 1 DC, so if that DC or that DB is down remediation will be required for writes, but reads should continue for the other DC. This is an okay setup, but can get complex when you have multiple DC's. I certainly do know of a few cases where users have configured 1 central database for writes, and then multiple read-only db's in each DC, so its workable. For PDB we deal with DB outages by queueing up any requests inside the PDB instance for when the 'downed' database is returned to service. This acts as a good buffer for faults or when you want to take remediation (such as failing database functions perhaps). I guess the problem then becomes one of general PostgreSQL replication, which is a tricky topic but with PostgreSQL 9.3 and above the process is much easier than in the past. I've got puppetdb on the master CA server and that works fine, but if I point the other masters to 'localhost' (in puppetdb.conf) I get ssl errors on the agent runs: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to submit 'replace facts' command for client1.local to PuppetDB at localhost:8081: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [certificate revoked for /CN=puppetmaster1.local] Kind of a separate topic to replication ... SSL is its own kind of pain. The error certificate revoked for /CN=puppetmaster1.local seems to indicate that the SSL certificate you have configured on the PuppetDB has been revoked according to the client. These are the certs specified in your /etc/puppetdb/conf.d/jetty.ini file. Now PuppetDB normally (with the use of puppetdb ssl-setup) just grabs the SSL certs from the Puppet agent on the localhost to use. If you have renewed these certificates yourself, then you should redo the setup step (puppetdb ssl-setup -f for example). I'd try running puppetdb ssl-setup and see what it gives you, if the certs don't match then try it again with the -f switch. If neither of this helps, provide the output to the list and we'll take a look. ken. -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAE4bNT%3D3DJ66y7ok7VaXSRAgHiYOmw4ejAHBgAB4WB28%3DFyfYg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Could not find or load main class com.puppetlabs.puppetdb.core
I'm attempting to build puppetdb-2.0.0 from source and the resulting jar fails to start and errors with Could not find or load main class com.puppetlabs.puppetdb.core. The way we execute the clojure code has changed, we no longer use AOT compilation so the syntax for invoking PDB from the jar has changed somewhat: java -cp puppetdb.jar clojure.main -m com.puppetlabs.puppetdb.core services -c config.ini Basically now we're invoked in the clojure.main class, and passing in parameters so that it knows what initial clojure file to invoke with the -m switch. In the past, we invoked the com.puppetlabs.puppetdb.core class directly, which no longer works. You can see examples of the new invocation litter in the ext/templates directory for the various distros. When inspecting the puppetdb.jar it doesn't contain any of the classes so it would appear that 'lein uberhar' is failing to build said classes. When listing the content of puppetdb-2.0.0-standalone.jar the do not exist. Also compiling the source, 'lein compile' doesn't appear to be compiling the classes, no Compiling com.puppetlabs.puppetdb.core or Compiling clj-time.core output like when I build 1.6.3 and nothing created under target/classes. This is intentional, we no longer compile these class files up front. ken. -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAE4bNTmg3bZV%3DO8LarZBB-CjpLPeEzw1i0yg007QEaXsTkye5g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] modelling languages puppet
Hi everyone, I have developed a puppet script for automating openstack configurations. Now i have to make UML diagrams to model my puppet script. I need to make a class diagram. But i didn't figure how because i have modules and not packages, i have defines and not functions... So my question is what is the suitable way to modeling puppet script? If we can use An UML class diagram, how is that possible and is there an example? Thanks. -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAE4v-KFcQEDNDxG%3DyOFb7nfH0O0OC-_knHVuSAM78Pc31dbPCQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] having issue when trying to install java using rpm
Hi,
I am getting the issue when i modifyied the code like this
class java_rpm::install {
$version = hiera(javaversion)
package { $version:
provider = rpm,
source = puppet:///development/java_rpm/files/$version,
ensure = installed,
}
}
MY file is here:
pwd
/etc/puppetlabs/puppet/environments/development/modules/java_rpm/files
*In my /var/lib/hiera*
classes:
- 'cis'
- 'java_versions'
- 'java_rpm'
javaversion: jdk-7u25-linux-x64.rpm
*Error: Execution of '/bin/rpm -i
puppet:///development/java_rpm/files/jdk-7u25-linux-x64.rpm' returned 1:
error: open of puppet:///development/java_rpm/files/jdk-7u25-linux-x64.rpm
failed: No such file or directory*
*Error:
/Stage[main]/Java_rpm::Install/Package[jdk-7u25-linux-x64.rpm]/ensure:
change from absent to present failed: Execution of '/bin/rpm -i
puppet:///development/java_rpm/files/jdk-7u25-linux-x64.rpm' returned 1:
error: open of puppet:///development/java_rpm/files/jdk-7u25-linux-x64.rpm
failed: No such file or directory*
Let me know
--
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, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/c25a25f1-2aaa-4596-a8d9-b66a8331fcbc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Issues with RHEL7
Hey folks, I'm having some issues installing puppet on a brand new RHEL7 server VM and I was wondering if any of you has ran into the same kinds of issues. This is what I'm getting: - yum install puppet Loaded plugins: langpacks, product-id, subscription-manager epel/x86_64/metalink | 9.3 kB 00:00:00 epel | 3.7 kB 00:00:00 rhel-7-server-rpms | 3.7 kB 00:00:00 epel/x86_64/primary_db | 1.8 MB 00:00:01 Resolving Dependencies -- Running transaction check --- Package puppet.noarch 0:3.6.0-1.el7 will be installed -- Processing Dependency: hiera = 1.0.0 for package: puppet-3.6.0-1.el7.noarch -- Processing Dependency: facter = 1.6.6 for package: puppet-3.6.0-1.el7.noarch -- Processing Dependency: rubygem(rgen) for package: puppet-3.6.0-1.el7.noarch -- Processing Dependency: ruby(selinux) for package: puppet-3.6.0-1.el7.noarch -- Running transaction check --- Package facter.x86_64 0:2.0.1-2.el7 will be installed --- Package hiera.noarch 0:1.3.4-1.el7 will be installed --- Package puppet.noarch 0:3.6.0-1.el7 will be installed -- Processing Dependency: ruby(selinux) for package: puppet-3.6.0-1.el7.noarch --- Package rubygem-rgen.noarch 0:0.6.6-2.el7 will be installed -- Finished Dependency Resolution Error: Package: puppet-3.6.0-1.el7.noarch (epel) Requires: ruby(selinux) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest - And yet - yum info libselinux Loaded plugins: langpacks, product-id, subscription-manager Installed Packages Name: libselinux Arch: x86_64 Version : 2.2.2 Release : 6.el7 Size: 159 k Repo: installed From repo : anaconda Summary : SELinux library and simple utilities URL : http://oss.tresys.com/git/selinux.git License : Public Domain and Installed Packages Name: epel-release Arch: noarch Version : 7 Release : 0.1 Size: 22 k Repo: installed Summary : Extra Packages for Enterprise Linux repository configuration URL : http://download.fedoraproject.org/pub/epel License : GPLv2 -- What gives? -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/056939d3-f51c-4cb3-a246-9c26a76018aa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Upper case Key in hiera hash
Hi, Can i have upper case key in hiera? I have a setenv_sh class that will take a key:value defined in hiera and put it in setenv.sh file test.yaml: class::subclass1::setenv_sh: INSTALL_SCRIPT: value: '/opt/install.sh' Thanks, RG -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/dcd5d455-974e-4306-bba1-3eb29dc55437%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] SuSe SLES: error when refreshing puppet yum repository
Could it be related to the fact, that I'm on patchset 1 or that old puppet
2.6 seems to exist in one of the other repositories?
Here is the outpput:
myserver:~ # zypper info rubygem-ruby-shadow
Loading repository data...
Reading installed packages...
Information for package rubygem-ruby-shadow:
Repository: puppet
Name: rubygem-ruby-shadow
Version: 2.3.4-21.1
Arch: x86_64
Vendor: obs://build.opensuse.org/systemsmanagement
Support Level: unknown
Installed: No
Status: not installed
Installed Size: 89.0 KiB
Summary: *nix Shadow Password Module
Description:
This module provides access to shadow passwords on Linux, OSX, FreeBSD,
OpenBSD, and Solaris
myserver:~ # zypper lr -d
# | Alias|
Name | Enabled | Refresh |
Priority | Type |
URI
| Service
--+--+--+-+-+--+++
1 | SUSE-Linux-Enterprise-Server-11-SP1_11.1.1-1.152 |
SUSE-Linux-Enterprise-Server-11-SP1 11.1.1-1.152 | Yes | Yes |
99 | yast2 |
nfs://sdu10078/install/sles/11.1/DVD1
|
2 | puppet |
puppet | Yes | No |
100 | rpm-md |
http://download.opensuse.org/repositories/systemsmanagement:/puppet/SLE_11_SP3
|
3 | sle-11-x86_64|
sle-11-x86_64| Yes | Yes |
99 | rpm-md |
nfs://sdu10078/install/sles/mirror/SLES11-SP1-Updates/sle-11-x86_64
|
Kind regards
Torsten
Am Freitag, 13. Juni 2014 14:47:19 UTC+2 schrieb Darin Perusich:
rubygem-ruby-shadow is available in the repo so I don't know what
could be causing that.
I just added that repo to a SLES box, installed puppet and it pulled
down the dependencies without issue, the the output below.
What the output you get from zypper info rubygem-ruby-shadow and
zypper lr -d ?
slestest:~ # zypper ar
http://download.opensuse.org/repositories/systemsmanagement:/puppet/SLE_11_SP3
puppet
Adding repository 'puppet' [done]
Repository 'puppet' successfully added
Enabled: Yes
Autorefresh: No
GPG check: Yes
URI:
http://download.opensuse.org/repositories/systemsmanagement:/puppet/SLE_11_SP3
slestest:~ # zypper in puppet
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following NEW packages are going to be installed:
facter puppet ruby rubygem-hiera rubygem-json_pure
rubygem-ruby-shadow rubygems
7 new packages to install.
Overall download size: 4.9 MiB. After the operation, additional 17.8
MiB will be used.
Continue? [y/n/? shows all options] (y):
Retrieving package ruby-1.8.7.p357-0.9.15.1.x86_64 (1/7), 1.8 MiB (6.4
MiB unpacked)
Retrieving: ruby-1.8.7.p357-0.9.15.1.x86_64.rpm [done]
Retrieving package facter-2.0.1-2.1.x86_64 (2/7), 80.0 KiB (222.0 KiB
unpacked)
Retrieving: facter-2.0.1-2.1.x86_64.rpm [done]
Retrieving package rubygems-1.8.15-0.14.1.x86_64 (3/7), 181.0 KiB
(558.0 KiB unpacked)
Retrieving: rubygems-1.8.15-0.14.1.x86_64.rpm [done]
Retrieving package rubygem-ruby-shadow-2.3.4-21.1.x86_64 (4/7), 23.0
KiB (89.0 KiB unpacked)
Retrieving: rubygem-ruby-shadow-2.3.4-21.1.x86_64.rpm [done]
Retrieving package rubygem-json_pure-1.8.1-28.12.x86_64 (5/7), 276.0
KiB (759.0 KiB unpacked)
Retrieving: rubygem-json_pure-1.8.1-28.12.x86_64.rpm [done]
Retrieving package rubygem-hiera-1.2.1-11.11.x86_64 (6/7), 46.0 KiB
(115.0 KiB unpacked)
Retrieving: rubygem-hiera-1.2.1-11.11.x86_64.rpm [done]
Retrieving package puppet-3.6.2-2.1.x86_64 (7/7), 2.6 MiB (9.6 MiB
unpacked)
Retrieving: puppet-3.6.2-2.1.x86_64.rpm [done (1.0 MiB/s)]
Installing: ruby-1.8.7.p357-0.9.15.1 [done]
Installing: facter-2.0.1-2.1 [done]
Installing: rubygems-1.8.15-0.14.1 [done]
Installing: rubygem-ruby-shadow-2.3.4-21.1 [done]
Installing: rubygem-json_pure-1.8.1-28.12 [done]
Installing: rubygem-hiera-1.2.1-11.11 [done]
Installing: puppet-3.6.2-2.1 [done]
Additional rpm output:
%{1} puppet.service
warning: /etc/puppet/puppet.conf saved as /etc/puppet/puppet.conf.rpmorig
%{1} puppet.service
--
Later,
Darin
--
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, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/48b16d52-e995-45ee-bf82-5e6459b15a91%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Upper case Key in hiera hash
On 6/13/14, 2:06 PM, RG wrote: Hi, Can i have upper case key in hiera? I have a setenv_sh class that will take a key:value defined in hiera and put it in setenv.sh file test.yaml: class::subclass1::setenv_sh: INSTALL_SCRIPT: value: '/opt/install.sh' Thanks, RG Hi, Yes, but your indentation needs to be corrected. class::subclass1::setenv_sh: 'INSTALL_SCRIPT': value: '/opt/install.sh' Br, -g -- Garrett Honeycutt @learnpuppet Puppet Training with LearnPuppet.com Mobile: +1.206.414.8658 -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/539B3EF2.3090401%40garretthoneycutt.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] SuSe SLES: error when refreshing puppet yum repository
BTW: I try to install via following command, because of the double puppet in another repository: zypper --non-interactive install --repo puppet puppet -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/a5992e0f-f5f6-4e1e-a66a-7fe45b9c389e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] Upper case Key in hiera hash
For some reason its not working, puppet debug message saying it got created but i don't see it in setnv.sh file Hiera[class::subclass1::setenv_sh]/class::subclass1::Setenv_sh[INSTALL_SCRIPT]/Ini_setting[/opt/application/setenv.sh/INSTALL_SCRIPT]/ensure: created On Friday, June 13, 2014 11:12:17 AM UTC-7, Garrett Honeycutt wrote: On 6/13/14, 2:06 PM, RG wrote: Hi, Can i have upper case key in hiera? I have a setenv_sh class that will take a key:value defined in hiera and put it in setenv.sh file test.yaml: class::subclass1::setenv_sh: INSTALL_SCRIPT: value: '/opt/install.sh' Thanks, RG Hi, Yes, but your indentation needs to be corrected. class::subclass1::setenv_sh: 'INSTALL_SCRIPT': value: '/opt/install.sh' Br, -g -- Garrett Honeycutt @learnpuppet Puppet Training with LearnPuppet.com Mobile: +1.206.414.8658 -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/87aaa272-bafc-455c-aa60-ef6fd7fec176%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: Issues with RHEL7
Answering my own question. :) libselinux-ruby seems to not be distributed with libselinux. However it's found in the server-optional channel. subscription-manager repos --enable rhel-7-server-optional-rpm fixes this. On Friday, June 13, 2014 1:49:44 PM UTC-4, Arkandel wrote: Hey folks, I'm having some issues installing puppet on a brand new RHEL7 server VM and I was wondering if any of you has ran into the same kinds of issues. This is what I'm getting: - yum install puppet Loaded plugins: langpacks, product-id, subscription-manager epel/x86_64/metalink | 9.3 kB 00:00:00 epel | 3.7 kB 00:00:00 rhel-7-server-rpms | 3.7 kB 00:00:00 epel/x86_64/primary_db | 1.8 MB 00:00:01 Resolving Dependencies -- Running transaction check --- Package puppet.noarch 0:3.6.0-1.el7 will be installed -- Processing Dependency: hiera = 1.0.0 for package: puppet-3.6.0-1.el7.noarch -- Processing Dependency: facter = 1.6.6 for package: puppet-3.6.0-1.el7.noarch -- Processing Dependency: rubygem(rgen) for package: puppet-3.6.0-1.el7.noarch -- Processing Dependency: ruby(selinux) for package: puppet-3.6.0-1.el7.noarch -- Running transaction check --- Package facter.x86_64 0:2.0.1-2.el7 will be installed --- Package hiera.noarch 0:1.3.4-1.el7 will be installed --- Package puppet.noarch 0:3.6.0-1.el7 will be installed -- Processing Dependency: ruby(selinux) for package: puppet-3.6.0-1.el7.noarch --- Package rubygem-rgen.noarch 0:0.6.6-2.el7 will be installed -- Finished Dependency Resolution Error: Package: puppet-3.6.0-1.el7.noarch (epel) Requires: ruby(selinux) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest - And yet - yum info libselinux Loaded plugins: langpacks, product-id, subscription-manager Installed Packages Name: libselinux Arch: x86_64 Version : 2.2.2 Release : 6.el7 Size: 159 k Repo: installed From repo : anaconda Summary : SELinux library and simple utilities URL : http://oss.tresys.com/git/selinux.git License : Public Domain and Installed Packages Name: epel-release Arch: noarch Version : 7 Release : 0.1 Size: 22 k Repo: installed Summary : Extra Packages for Enterprise Linux repository configuration URL : http://download.fedoraproject.org/pub/epel License : GPLv2 -- What gives? -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/4746bdca-f219-4c3b-8130-8c26d53e0e5f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] puppetlabs_spec_helper 0.5.x breaks puppet-lint's ignore_paths ?
Version 0.5.x of puppetlabs_spec_helper seems to make it impossible to add additional paths to be ignored using PuppetLint.configuration.ignore_paths. If I pin my module to ~ 0.4.0 for puppetlabs_spec_helper, the ignore_paths defined in my Rakefile are respected. Commit 4ca208bde329aa6861094ccefa07fc8338de6691 added PuppetLint.configuration.ignore_paths to the puppetlabs_spec_helper lint task, but wasn't till today that my modules began using puppetlabs_spec_helper 0.5.x. An example of the Rakefile I use on dozens of Puppet modules, https://github.com/treydock/puppet-zfsonlinux/blob/master/Rakefile. Is this user error on my part or an actual bug? The problem I'm hitting is that the pkg directory is making the autoload tests fail because my PuppetLint.configuration.ignore_paths in the Rakefile are seemingly ignored. Thanks - Trey -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/6891176a-b735-43e4-9a6f-07a701e8199b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] puppetlabs-java: installing oracle-jdk on ubuntu trusty 14.04
Hi Dirk,
thank you for confirming. Guess I should submit a but to puppetlabs-java..
Anyway, here's a simple class that installs it from ppa:webupd8team:
class java {
$package = 'oracle-java7-installer'
file { '/tmp/java.preseed':
content = 'oracle-java7-installer shared/accepted-oracle-license-v1-1
select true
oracle-java7-installer shared/accepted-oracle-license-v1-1 seen true',
mode = '0600',
backup = false,
}
include apt
apt::ppa { 'ppa:webupd8team/java': }
package { $package:
responsefile = '/tmp/java.preseed',
require = [
Apt::Ppa['ppa:webupd8team/java'],
File['/tmp/java.preseed']
],
}
}
On Tuesday, June 10, 2014 8:11:55 AM UTC+2, Dirk Heinrichs wrote:
Am 10.06.2014 07:35, schrieb Milan Simonović:
I'm still trying to figure out how to install java *just using*
puppetlabs-java module.
You can't. There is no package oracle-jdk on Ubuntu.
Bye...
Dirk
--
*Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
*Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
*Tel*: +49 2226 159 (Ansage) 1149
*Email*: d...@recommind.com javascript:
*Skype*: dirk.heinrichs.recommind
www.recommind.com
--
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, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/9dd9ad58-60a1-4402-b7a3-5a73a556a42c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] modelling languages puppet
On 2014-13-06 18:36, cheniour ghassen wrote: Hi everyone, I have developed a puppet script for automating openstack configurations. Now i have to make UML diagrams to model my puppet script. I need to make a class diagram. But i didn't figure how because i have modules and not packages, i have defines and not functions... So my question is what is the suitable way to modeling puppet script? If we can use An UML class diagram, how is that possible and is there an example? Thanks. Depends on what you want a model of. There are basically two things of interest - the manifests (the instructions), and the resulting catalog (for a given node). Short answer: You can get some diagrams, but not UML without coding, if you want actual UML output you need to write code in Java or Ruby, and when doing so requires a fair bit of Puppet knowledge and at least intermediate modeling knowledge (EMF, Ecore, UML, XMI, etc.) Longer answer: Without coding, you can get a diagram of the source and its dependencies - there is a sample service called wham that you can try out at wham.cloudsmith.com - here is a sample output for the puppetlabs/apache module http://wham.cloudsmith.com/#puppetlabs/apache (you can download the result as an .svg vector image). That diagrams shows dependencies between modules, and what is being used. It can also render a complete configuration. Catalogs can be obtained in JSON format, and can be transformed to a graph. Puppet has a rudimentary dot renderer that gives you the content in graphviz dot format which can then be rendered. If you want some other graphical representation you have to write code. If you want the catalog in UML, there are a number of things you need to do. - define a mapping to UML (how to represent puppet hostclass, resource, puppet modules, etc). - transform the catalog (in Json) to the UML model - serialize it as XMI - open the model with a UML diagramming tool - do the layout/formatting There is an Ecore model of the Catalog in the Geppetto Project (IIRC), and I also believe it contains the ability to deserialize a catalog in Json to this model. The next step would be to transform that model to an ecore reprsentation and serialize as XMI. All of the Geppetto code is written in Java. If you consider doing this you can get some help on the Geppetto google group. There is currently no corresponding Catalog model in Ruby. For source, the future parser in Puppet is built using modeling techology, and you can obtain an ecore model per source file (that you can transform into something else, serialize etc.) To do this you need to write code in Ruby. Having a standard UML representation of Puppet logic would be a cool thing to have, but I don't see that happening in the standard Puppet code base for quite some time. Regards - henrik Visit my Blog Puppet on the Edge http://puppet-on-the-edge.blogspot.se/ -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/lnfsnh%246nh%241%40ger.gmane.org. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Question on directory environments and environment.conf - Puppet Version 3.6.2
Hi List, I am starting to play with directory environments on a test box. I am using puppet apply (without a master) to get a feel for how it all comes together. Key files: puppet.conf - 10:35 - root@dna: bootstrap/puppet $ cat /root/tmp/bootstrap/puppet/puppet.conf [main] #Turn on the new smarter directory envrionments envrionmentpath= $confdir/environments #Need to set this here for playing with repo as environment.conf does not allow setting hiera.yaml location hiera_config= $confdir/$environment/hiera.yaml - environment.conf - 10:35 - root@dna: bootstrap/puppet $ cat /root/tmp/bootstrap/puppet/environments/production/environment.conf #Use relative paths within environment directory modulepath = site-modules:modules - puppet config print does not show show the modulepath with the environment.conf details - 10:38 - root@dna: tmp/bootstrap $ puppet config print --confdir /root/tmp/bootstrap/puppet --environment production | grep modulepath basemodulepath = /root/tmp/bootstrap/puppet/modules:/usr/share/puppet/modules modulepath = /root/tmp/bootstrap/puppet/modules:/usr/share/puppet/modules - I have also tried to use puppet apply in case it was an issue with puppet config: - 10:38 - root@dna: tmp/bootstrap $ FACTER_hostname=dna FACTER_domain=mgnt.local FACTER_fqdn=dna.mgnt.local FACTER_machine_role=puppetmaster puppet apply --verbose --confdir /root/tmp/bootstrap/puppet -e include roles::puppetmaster --debug Error: Could not find class roles::puppetmaster for dna.mgnt.local on node dna.mgnt.local Error: Could not find class roles::puppetmaster for dna.mgnt.local on node dna.mgnt.local - site-modules does contain the puppetmaster file in the correct location - 10:40 - root@dna: bootstrap/puppet $ ls /root/tmp/bootstrap/puppet/environments/production/site-modules/roles/manifests/ puppetmaster.pp - My question is why isn't the environment.conf file being picked up? Is this something that will only work if I am running a puppetmaster? Have I missed something obvious? Thanks, Peter -- 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, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/d2537caf-5438-4627-9ef0-089adb9c7623%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
