Jira (HI-257) Dynamic hierarchy based on fact/variable
Title: Message Title
William Leese commented on an issue
Re: Dynamic hierarchy based on fact/variable
Ping Jeremy Adams. This is exactly what I meant at PuppetCamp Tokyo when I was trying to convince you that Roles (as opposed to Profiles) are configuration data (collections of profiles and parameters) and as such would be a great match for storing in Hiera.
Add Comment
Hiera / HI-257
Dynamic hierarchy based on fact/variable
Take the following hierarchy example: - hiera/%{::variable}/common let's say $variable is an array: $variable = [a, b, c] Hiera understands that $variable is an array and it would then build an hierarchy as follows: - hiera/a/common - hiera/b/common - hiera/c/common Both these examples find real work scenarios. Let's say a machine a...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-2648) Error On upgrading augeas-libs
Title: Message Title Stephane M commented on an issue Re: Error On upgrading augeas-libs The package won't upgrade himself. (2.6.18-371.8.1.el5) : == Package Arch Version Repository Size == Updating: augeas-libs x86_64 1.1.0-2.el5 puppetlabs-dependencies-x86_64-el5 356 k Transaction Summary == Install 0 Package(s) Upgrade 1 Package(s) Total download size: 356 k Is this ok [y/N]: y Downloading Packages: augeas-libs-1.1.0-2.el5.x86_64.rpm | 356 kB 00:00 Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Check Error: file /usr/share/augeas/lenses/dist/anacron.aug from install of augeas-libs-1.1.0-2.el5.x86_64 conflicts with file from package augeas-libs-1.0.0-1.el5.i386 ... Add Comment Puppet / PUP-2648 Error On upgrading augeas-libs Hello, Since 2 days, puppet can't terminate correctly the puppet agent -t command because there a conflict to upgrade the augeas-libs packet.Error: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install augeas-libs' returned 1: Transaction Check Error: file /usr/share/augeas/lenses/dist/anacron.aug from install of augeas-libs-1.1.0...
Jira (HI-257) Dynamic hierarchy based on fact/variable
Title: Message Title
Tom Scholten commented on an issue
Re: Dynamic hierarchy based on fact/variable
As commented through the twitter thread already working on getting our quick code out to git or likewise. It's based on pushing (makeshift) array data to hiera and have hiera sift through (again in hiera and/or hiera_hash/hiera_array capability) a dynamic set of yamls (we went for the easy ones first).
Will update once we have the code out
Add Comment
Hiera / HI-257
Dynamic hierarchy based on fact/variable
Take the following hierarchy example: - hiera/%{::variable}/common let's say $variable is an array: $variable = [a, b, c] Hiera understands that $variable is an array and it would then build an hierarchy as follows: - hiera/a/common - hiera/b/common - hiera/c/common Both these examples find real work scenarios. Let's say a machine a...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-2635) user purge_ssh_keys not purged
Title: Message Title
Doug Byrne commented on an issue
Re: user purge_ssh_keys not purged
The following manifest shows the original issue:
keytest.pp
package {'python-dev': ensure = present, }
ssh_authorized_key { 'doug':
ensure = present,
key= 'B3NzaC1yc2EDAQABAAABAQC81jWIxrZpzL+IFE9S4yJNMrANeOJke0CbFmk8pBz4rI8RZ+1JBZdD5aZnO15nLVYZlQq1D8BLHy3F02EhfmQBINHUPA373SUedEUPqByQBOslp11sK/u0Op0X7hhW902hOFRszb9VODJifWnkB2bj4FDED6zQf8cIeTIO15CyYxPPeT/EBZ9G4RJsAItXf2ktwWaO94FGcnNYMUzvpsJCMwI4XY8ArqQBsRSrGnauhBD3e1MuqnLF4ujOqLYBwfZ5gw5VSar5i/oSsGswgwjKxmuO0hfTxDVROoIn24AHSTm38lF34djEWIASELEWxDjnFDamawfU2Dpm2MK90Jk/',
type = 'ssh-rsa',
user = 'ubuntu',
}
user { 'ubuntu':
purge_ssh_keys = true,
home = '/home/ubuntu',
}
I tried multiple packages, all of them appear to have the same behavior.
Agent output:
ubuntu@keytest:~$ sudo puppet apply keytest.pp --noop -d
Info: Loading facts in /var/lib/puppet/lib/facter/iptables_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/rabbitmq_erlang_cookie.rb
Info: Loading facts in /var/lib/puppet/lib/facter/ip6tables_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/concat_basedir.rb
Info: Loading facts in /var/lib/puppet/lib/facter/windows_common_appdata.rb
Info: Loading facts in /var/lib/puppet/lib/facter/puppi_projects.rb
Info: Loading facts in /var/lib/puppet/lib/facter/rvm_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/os_maj_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/doolli_pem.rb
Info: Loading facts in /var/lib/puppet/lib/facter/syslog.rb
Info: Loading facts in /var/lib/puppet/lib/facter/last_run.rb
Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb
Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/iptables_persistent_version.rb
Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb
Info: Loading facts in /var/lib/puppet/lib/facter/rvm_installed.rb
Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb
Debug: Failed to load library 'selinux' for feature 'selinux'
Notice: Compiled catalog for keytest.doolli.com in environment production in 0.35 seconds
Debug: Puppet::Type::Package::ProviderPorts: file /usr/local/sbin/portupgrade does not exist
Debug: Puppet::Type::Package::ProviderRug: file /usr/bin/rug does not exist
Debug: Puppet::Type::Package::ProviderPkgin: file pkgin does not exist
Debug: Puppet::Type::Package::ProviderZypper: file /usr/bin/zypper does not exist
Debug: Puppet::Type::Package::ProviderPortupgrade: file /usr/local/sbin/portupgrade does not exist
Debug: Puppet::Type::Package::ProviderFreebsd: file /usr/sbin/pkg_delete does not exist
Debug: Puppet::Type::Package::ProviderPortage: file /usr/bin/emerge does not exist
Debug: Puppet::Type::Package::ProviderOpenbsd: file pkg_delete does not exist
Debug: Puppet::Type::Package::ProviderOpkg: file opkg does not exist
Debug: Puppet::Type::Package::ProviderRpm: file rpm does not exist
Debug: Puppet::Type::Package::ProviderAptrpm: file rpm does not exist
Debug: Puppet::Type::Package::ProviderSunfreeware: file pkg-get does not exist
Debug: Puppet::Type::Package::ProviderUp2date: file /usr/sbin/up2date-nox does not exist
Debug: Puppet::Type::Package::ProviderAix:
Jira (PUP-2659) Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
Title: Message Title
Henrik Lindberg commented on an issue
Re: Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
Are you using passenger or webrick ? Any other add ons to puppet ?
It would be great to get a stack-trace of the no environments found error
Add Comment
Puppet / PUP-2659
Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
After upgrading puppet to version 3.6.1, the following error occurs: {noformat} Attempted to pop, but already at root of the context stack. {noformat} And afterwards log is flooded with following message: {noformat} no 'environments' in {:root_environment=#Puppet::Node::Environment:0x7fe1930f5a38 @manifest=/, @modulepath=[], @name=:*root*...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit
Jira (PDB-178) Extend reports query parameters and search capabilities
Title: Message Title Dominic Cleal commented on an issue Re: Extend reports query parameters and search capabilities Great, very cool Ken, thanks for the update. Regarding an ID for retrieving a single report, it really wouldn't matter from my PoV. I'd expect a UUID generated by PDB or similar though, I don't recall an ID being present in the report itself. Add Comment PuppetDB / PDB-178 Extend reports query parameters and search capabilities While looking (quickly) at what sort of query operators would be useful to support PuppetDB's report backend instead of Foreman's own ActiveRecord backend, I made a few notes. Hopefully these may help influence the future of the reports query endpoint. * report query filter on received-time * report query filter on environment * report query filter ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PUP-2659) Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
Title: Message Title
Wojciech Urbański commented on an issue
Re: Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
I am using no addons, clean puppet-only installation.
I have attached a stack trace. Sorry for the size, but this time the crash happened after a pretty long time.
Add Comment
Puppet / PUP-2659
Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
After upgrading puppet to version 3.6.1, the following error occurs: {noformat} Attempted to pop, but already at root of the context stack. {noformat} And afterwards log is flooded with following message: {noformat} no 'environments' in {:root_environment=#Puppet::Node::Environment:0x7fe1930f5a38 @manifest=/, @modulepath=[], @name=:*root*...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to
Jira (PUP-2659) Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
Title: Message Title Wojciech Urbański updated an issue Puppet / PUP-2659 Puppet stops working with error 'Attempted to pop, but already at root of the context stack.' tar-gzed stack trace, Error was logged at 19:33:40 Change By: Wojciech Urbański Attachment: trace.tgz Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2659) Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
Title: Message Title
Rob Payne commented on an issue
Re: Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
I am also using no add-ons, and webrick.
Add Comment
Puppet / PUP-2659
Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
After upgrading puppet to version 3.6.1, the following error occurs: {noformat} Attempted to pop, but already at root of the context stack. {noformat} And afterwards log is flooded with following message: {noformat} no 'environments' in {:root_environment=#Puppet::Node::Environment:0x7fe1930f5a38 @manifest=/, @modulepath=[], @name=:*root*...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-257) Dynamic hierarchy based on fact/variable
Title: Message Title
Matteo Cerutti commented on an issue
Re: Dynamic hierarchy based on fact/variable
Hey guys,
thanks for commenting on this request.
Since I needed this very urgently, I implemented it for myself.
I've actually opened a pull request for this on Sat, https://github.com/puppetlabs/hiera/pull/193. In reality, the pull request was really to discuss the change.
Look forward to have this feature implemented in Hiera soon!
Add Comment
Hiera / HI-257
Dynamic hierarchy based on fact/variable
Take the following hierarchy example: - hiera/%{::variable}/common let's say $variable is an array: $variable = [a, b, c] Hiera understands that $variable is an array and it would then build an hierarchy as follows: - hiera/a/common - hiera/b/common - hiera/c/common Both these examples find real work scenarios. Let's say a machine a...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups
Jira (HI-257) Dynamic hierarchy based on fact/variable
Title: Message Title
Tom Scholten commented on an issue
Re: Dynamic hierarchy based on fact/variable
I think we looked at interpolate code but in the end we solved it differently - still trying to have our sample code up tomorrowish
Add Comment
Hiera / HI-257
Dynamic hierarchy based on fact/variable
Take the following hierarchy example: - hiera/%{::variable}/common let's say $variable is an array: $variable = [a, b, c] Hiera understands that $variable is an array and it would then build an hierarchy as follows: - hiera/a/common - hiera/b/common - hiera/c/common Both these examples find real work scenarios. Let's say a machine a...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2365) Puppet module tool on windows cannot connect to the forge
Title: Message Title
Louis Mayorga commented on an issue
Re: Puppet module tool on windows cannot connect to the forge
It seems that is happening on the latest release of Puppet for Windows 3.6.1
vagrant provision
== default: Running provisioner: shell...
default: Running: c:\tmp\vagrant-shell.bat
== default: C:\Windows\system32netsh advfirewall set allprofiles state off
== default: Running provisioner: shell...
default: Running: c:\tmp\vagrant-shell.bat
== default: C:\Windows\system32puppet module install puppetlabs-reboot --force
== default:
== default: Notice: Preparing to install into C:/ProgramData/PuppetLabs/puppet/etc/modules ...
== default: Notice: Created target directory C:/ProgramData/PuppetLabs/puppet/etc/modules
== default: Notice: Downloading from https://forgeapi.puppetlabs.com ...
== default:
== default: Error: Could not connect via HTTPS to https://forgeapi.puppetlabs.com
== default: Unable to verify the SSL certificate
== default: The certificate may not be signed by a valid CA
An error occurred executing a remote WinRM command.
Shell: powershell
Command: c:\tmp\vagrant-shell.bat
Message: Command execution failed with an exit code of 1
Vagrant: 1.6.2 Puppet: 3.6.1
Add Comment
Puppet / PUP-2365
Puppet module tool on windows cannot connect to the forge
Due to heartbleed, operations obtained a wildcard SSL certificate issued by {code}Issuer: C=US, ST=UT, L=Salt Lake City, O=The USERTRUST Network, OU=http://www.usertrust.com, CN=UTN-USERFirst-Hardware{code} This certificate is not installed by default on Windows hosts, as a result the PMT cannot make an authenticated SSL connection to the forge: {code}...
Jira (PUP-2365) Puppet module tool on windows cannot connect to the forge
Title: Message Title Louis Mayorga updated an issue Puppet / PUP-2365 Puppet module tool on windows cannot connect to the forge Change By: Louis Mayorga Affects Version/s: 3.6.1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2659) Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
Title: Message Title
Raffael Link commented on an issue
Re: Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
We have the same issue here on Debian Wheezy starting with Puppet 3.6.1. Also, the second error message looks a little bit different:
Error 400 on SERVER: no 'environments' in {:current_environment=*root*, :root_environment=*root*} at top of [[0, nil, nil]]
Add Comment
Puppet / PUP-2659
Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
After upgrading puppet to version 3.6.1, the following error occurs: {noformat} Attempted to pop, but already at root of the context stack. {noformat} And afterwards log is flooded with following message: {noformat} no 'environments' in {:root_environment=#Puppet::Node::Environment:0x7fe1930f5a38 @manifest=/, @modulepath=[], @name=:*root*...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2635) user purge_ssh_keys not purged
Title: Message Title
Felix Frank commented on an issue
Re: user purge_ssh_keys not purged
Thanks again Doug Byrne. I can now reproduce. The good news is, the manifest also reproduces the issue using puppet apply. Pretty bizarre behavior - removing the package resource makes the error disappear.
Debugging away...
Add Comment
Puppet / PUP-2635
user purge_ssh_keys not purged
I'm using Puppet 3.6.0 on Ubuntu 12.04 and I'm trying to purge unmanaged ssh authorized keys. I've added this code to my manifest: {code} user { 'ubuntu': purge_ssh_keys = true, home = '/home/ubuntu', } {code} However, no keys are purged. I do see the following lines in the agent debug output: {noformat} Debug: /Stage[main]/Role...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PUP-2659) Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
Title: Message Title
Henrik Lindberg commented on an issue
Re: Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
The trace I am interested in is the Ruby stacktrace that is logged as part of the 400 error being returned to the client. In case you have trouble finding this, you may be able to reproduce this by running the master in non daemon mode (shut down the deamon first, then start master from command line), then look at the output. You can also try turning on --debug and --verbose, but I think errors are always shown without these.
Sorry I tricked you into doing a trace of the Ruby virtual machine
Add Comment
Puppet / PUP-2659
Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
After upgrading puppet to version 3.6.1, the following error occurs: {noformat} Attempted to pop, but already at root of the context stack. {noformat} And afterwards log is flooded with following message: {noformat} no 'environments' in {:root_environment=#Puppet::Node::Environment:0x7fe1930f5a38 @manifest=/, @modulepath=[], @name=:*root*...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2348) Puppet run randomly fails with Unknown function function at manifest on node node
Title: Message Title Francois Conil updated an issue Puppet / PUP-2348 Puppet run randomly fails with Unknown function function at manifest on node node Change By: Francois Conil Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2348) Puppet run randomly fails with Unknown function function at manifest on node node
Title: Message Title Francois Conil updated an issue Puppet / PUP-2348 Puppet run randomly fails with Unknown function function at manifest on node node Change By: Francois Conil Affects Version/s: 3.6.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-481) Infinite loop if EC2 metadata server times out
Title: Message Title Kurt Wall assigned an issue to Unassigned Facter / FACT-481 Infinite loop if EC2 metadata server times out Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-481) Infinite loop if EC2 metadata server times out
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Facter / FACT-481 Infinite loop if EC2 metadata server times out Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-257) Dynamic hierarchy based on fact/variable
Title: Message Title
William Leese commented on an issue
Re: Dynamic hierarchy based on fact/variable
https://github.com/puppetlabs/hiera/pull/48
Here's an older PR. Just adding for reference.
Add Comment
Hiera / HI-257
Dynamic hierarchy based on fact/variable
Take the following hierarchy example: - hiera/%{::variable}/common let's say $variable is an array: $variable = [a, b, c] Hiera understands that $variable is an array and it would then build an hierarchy as follows: - hiera/a/common - hiera/b/common - hiera/c/common Both these examples find real work scenarios. Let's say a machine a...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2404) Merge puppet 3.6 into pe-puppet 3.3.x
Title: Message Title Kylo Ginsberg commented on an issue Re: Merge puppet 3.6 into pe-puppet 3.3.x I looked at these test results: http://jenkins-enterprise.delivery.puppetlabs.net/job/PE%20Puppet%20Acceptance%20Tests/83/#showFailuresLink There were 65 failures. 56 of them were a failure in tests/modules/lists/with_supported_pe_version.rb which we agreed via Hipchat was doing a warning check that none of the other PE tests were filtering on. I just committed a change to clean that up. I haven't triaged the remaining 9 failures. Add Comment Puppet / PUP-2404 Merge puppet 3.6 into pe-puppet 3.3.x pe-puppet/3.3.x is based on puppet 3.6.x This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop
Jira (FACT-483) Explore extracting FACT-185 fix for use in 1.7.x
Title: Message Title Eric Sorenson commented on an issue Re: Explore extracting FACT-185 fix for use in 1.7.x Not feasible based on engineering assessment. Closing as wontfix. Add Comment Facter / FACT-483 Explore extracting FACT-185 fix for use in 1.7.x There have been a number of customer requests for the EC2 VPC fixes that are in Facter 2. Since PE will be on 1.7.x for a while longer, it'd be nice to make these changes available in a way that customers can make use of. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1904) Host resource type corrupts /etc/hosts
Title: Message Title B W assigned an issue to B W Puppet / PUP-1904 Host resource type corrupts /etc/hosts Change By: B W Assignee: BW Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-566) PR (125): Ensure db and db users created before validation - rickerc
Title: Message Title
gepetto-bot commented on an issue
Re: PR (125): Ensure db and db users created before validation - rickerc
lathiat commented:
This happens for me too. What does it for me:
class profile::puppetmaster { include ::apache class {'::puppetdb': }
class {'::puppetdb::master::config': puppet_service_name = 'apache2', }
class { '::puppet': server = true, server_reports = 'puppetdb', server_external_nodes = '', }
}
Add Comment
PuppetDB / PDB-566
PR (125): Ensure db and db users created before validation - rickerc
h2. Ensure db and db users created before validation * Author: Chris Ricker * Company: * Github ID: [rickerc|https://github.com/rickerc] * [Pull Request 125 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/125] * [Pull Request 125 File Diff|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/125/files] h2. Pull Request Descr...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
Jira (PDB-566) PR (125): Ensure db and db users created before validation - rickerc
Title: Message Title Trent Lloyd updated an issue PuppetDB / PDB-566 PR (125): Ensure db and db users created before validation - rickerc Change By: Trent Lloyd h2.Ensuredbanddbuserscreatedbeforevalidation *Author:ChrisRicker *Company: *GithubID:[rickerc|https://github.com/rickerc] *[PullRequest125Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/125] *[PullRequest125FileDiff|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/125/files] h2.PullRequestDescription EnsurethatforPostgreSQLbackends,thedatabasevalidationfunctionsarenotrununtiltheinitialdatabasecreationanduserrolecreationhasbeencompleted.Closes-Bug:#1298605 (webhooks-id:41e568bdfcce5ae289fd20d1205a2413) Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1904) Host resource type corrupts /etc/hosts
Title: Message Title B W commented on an issue Re: Host resource type corrupts /etc/hosts Is mint your Linux system, when you see the problem? Could you please give details, such as the operation system, master/agent in same server or not? Add Comment Puppet / PUP-1904 Host resource type corrupts /etc/hosts Hello, It seems when /etc/hosts has a syntax error, Puppet only reports the error, and start over with an empty file, only adding the new resource. It essentially erases all original entries to the file. When file syntax is OK, everything seems to work fine. I had problems with this situation in production systems, where, due to a human error, there... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-566) PR (125): Ensure db and db users created before validation - rickerc
Title: Message Title
Trent Lloyd commented on an issue
Re: PR (125): Ensure db and db users created before validation - rickerc
Log excerpt from failing run with above test case (copied from Github/lathiat)
Notice: /Stage[main]/Postgresql::Server::Config/Postgresql::Server::Pg_hba_rule[allow localhost TCP access to postgresql user]/Concat::Fragment[pg_hba_rule_allow localhost TCP access to postgresql user]/File[/var/lib/puppet/concat/_etc_postgresql_9.3_main_pg_hba.conf/fragments/003_pg_hba_rule_allow localhost TCP access to postgresql user]/ensure: created Notice: /Stage[main]/Postgresql::Server::Config/Concat[/etc/postgresql/9.3/main/pg_hba.conf]/Exec[concat_/etc/postgresql/9.3/main/pg_hba.conf]/returns: executed successfully Notice: /Stage[main]/Postgresql::Server::Config/Concat[/etc/postgresql/9.3/main/pg_hba.conf]/Exec[concat_/etc/postgresql/9.3/main/pg_hba.conf]: Triggered 'refresh' from 8 events Notice: /Stage[main]/Postgresql::Server::Config/Concat[/etc/postgresql/9.3/main/pg_hba.conf]/File[/etc/postgresql/9.3/main/pg_hba.conf]/content: content changed ' {md5}7694a77a71d01d43944f0ec2aa3fb165' to '{md5}
43ca2364f5669316995401a7f8eef77e' Notice: /Stage[main]/Postgresql::Server::Config/Concat[/etc/postgresql/9.3/main/pg_hba.conf]/File[/etc/postgresql/9.3/main/pg_hba.conf]/owner: owner changed 'postgres' to 'root' Notice: /Stage[main]/Postgresql::Server::Reload/Exec[postgresql_reload]: Triggered 'refresh' from 1 events Notice: /Stage[main]/Postgresql::Server::Service/Anchor[postgresql::server::service::begin]: Triggered 'refresh' from 1 events Notice: /Stage[main]/Postgresql::Server::Service/Service[postgresqld]: Triggered 'refresh' from 1 events Notice: /Stage[main]/Postgresql::Server::Service/Postgresql::Validate_db_connection[validate_service_is_running]/Exec[validate postgres connection for /postgres]: Triggered 'refresh' from 1 events Notice: /Stage[main]/Postgresql::Server::Service/Anchor[postgresql::server::service::end]: Triggered 'refresh' from 1 events Notice: /Stage[main]/Puppetdb::Database::Postgresql/Postgresql::Server::Db[puppetdb]/Postgresql::Server::Database[puppetdb]/Postgresql_psql[Check for existence of db 'puppetdb']/command: command changed '' to 'SELECT 1' Notice: /Stage[main]/Puppetdb::Database::Postgresql/Postgresql::Server::Db[puppetdb]/Postgresql::Server::Database[puppetdb]/Exec[/usr/lib/postgresql/9.3/bin/createdb --owner='postgres' --template=template0 'puppetdb']: Triggered 'refresh' from 1 events Notice: /Stage[main]/Puppetdb::Database::Postgresql/Postgresql::Server::Db[puppetdb]/Postgresql::Server::Database[puppetdb]/Postgresql_psql[REVOKE CONNECT ON DATABASE puppetdb FROM public]: Triggered 'refresh' from 1 events
Notice: /Stage[main]/Puppetdb::Server::Validate_db/Postgresql::Validate_db_connection[validate puppetdb postgres connection]/Exec[validate postgres connection for localhost/puppetdb]/returns: Unable to connect to defined database using: /usr/bin/psql --tuples-only --quiet -h localhost -U puppetdb -p 5432 --dbname puppetdb Error: echo 'Unable to connect to defined database using: /usr/bin/psql --tuples-only --quiet -h localhost -U puppetdb -p 5432 --dbname puppetdb ' false returned 1 instead of one of [0] Error: /Stage[main]/Puppetdb::Server::Validate_db/Postgresql::Validate_db_connection[validate puppetdb postgres connection]/Exec[validate postgres connection for localhost/puppetdb]/returns: change from notrun to 0 failed: echo 'Unable to connect to defined database using: /usr/bin/psql --tuples-only --quiet -h localhost -U puppetdb -p 5432 --dbname puppetdb ' false returned 1 instead of one of [0] Notice: /Stage[main]/Puppetdb::Database::Postgresql/Postgresql::Server::Db[puppetdb]/Postgresql::Server::Role[puppetdb]/Postgresql_psql[CREATE ROLE puppetdb ENCRYPTED PASSWORD 'X'
Jira (HI-257) Dynamic hierarchy based on fact/variable
Title: Message Title
William Leese commented on an issue
Re: Dynamic hierarchy based on fact/variable
..and another github project trying to achieve the same: https://github.com/neillturner/puppet_roles_hiera_parameters
Add Comment
Hiera / HI-257
Dynamic hierarchy based on fact/variable
Take the following hierarchy example: - hiera/%{::variable}/common let's say $variable is an array: $variable = [a, b, c] Hiera understands that $variable is an array and it would then build an hierarchy as follows: - hiera/a/common - hiera/b/common - hiera/c/common Both these examples find real work scenarios. Let's say a machine a...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2659) Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
Title: Message Title
Sharon Tickell commented on an issue
Re: Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
I am seeing this issues as well: on Ubuntu 12.04, using webrick. My environments are still set up with the old-style config file sections, and I had to delete the $confidir/environments directory on my puppetmaster to get puppet agents to connect successfully at all (as per http://www.clarksys.com/blog/2014/05/25/puppet-environment-errors/)
My currently installed versions of the puppet and puppetmaster packages are both 3.6.1-1puppetlabs1, and I'm running puppetdb 2.0.0-1puppetlabs1
Add Comment
Puppet / PUP-2659
Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
After upgrading puppet to version 3.6.1, the following error occurs: {noformat} Attempted to pop, but already at root of the context stack. {noformat} And afterwards log is flooded with following message: {noformat} no 'environments' in {:root_environment=#Puppet::Node::Environment:0x7fe1930f5a38 @manifest=/, @modulepath=[], @name=:*root*...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2659) Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
Title: Message Title
Sharon Tickell commented on an issue
Re: Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
... and I've now updated my environment configuration to use directory environments, but am still seeing this issue.
Add Comment
Puppet / PUP-2659
Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
After upgrading puppet to version 3.6.1, the following error occurs: {noformat} Attempted to pop, but already at root of the context stack. {noformat} And afterwards log is flooded with following message: {noformat} no 'environments' in {:root_environment=#Puppet::Node::Environment:0x7fe1930f5a38 @manifest=/, @modulepath=[], @name=:*root*...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more
