Jira (PDB-1084) Store variables set at classification along with facts in PuppetDB
Title: Message Title Chris Butler commented on PDB-1084 Re: Store variables set at classification along with facts in PuppetDB The specific use case is from customers who are using the node classifier to set variables describing nodes' application role, logical environment, organizational unit, etc, and then want to use puppetdbquery functions in their modules and mcollective filtering against puppetdb. I have this exact use-case in my setup, just wondering if this issue is on the roadmap at all? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1875) Unable to use "confine" with structured facts -- documentation is incorrect
Title: Message Title Chris Butler commented on FACT-1875 Re: Unable to use "confine" with structured facts -- documentation is incorrect For anyone paying attention, I realised my error with the "code block" style confine check as soon as I pressed submit (typical!). However it still seems like the Facter.value method mentioned in the docs doesn't work, unless I'm also missing something there! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1875) Unable to use "confine" with structured facts -- documentation is incorrect
Title: Message Title
Chris Butler updated an issue
Facter / FACT-1875
Unable to use "confine" with structured facts -- documentation is incorrect
Change By:
Chris Butler
I've been attempting to {{confine}} some facts using structured facts, as described in [the documentation here|https://puppet.com/docs/facter/3.11/custom_facts.html#confining-facts]. However, neither the first method described in the docs seems documentation using Facter.value does not seem to actually work with the current version of facter :{code} ==> oscheck_codeblock.rb <== Facter.add(:oscheck_codeblock) do confine :os do |os| os['id'] == 'Debian' end setcode do 'fact value' endend== > oscheck_factervalue.rb <==Facter.add(:oscheck_factervalue) do confine Facter.value(:os)[' distro'][' id'] => 'Debian' setcode do 'fact value' endend{code}Running facter with FACTERLIB pointed at the location of the above two files file gives:{code}2018-08-17 13: 21 28 : 09 22 . 126211 140537 INFO puppetlabs.facter - executed with command line: --debug oscheck_codeblock oscheck_factervalue.2018-08-17 13: 21 28 : 09 22 . 126619 140979 DEBUG leatherman.ruby:504 - ruby was found at "/usr/bin/ruby".2018-08-17 13: 21 28 : 09 22 . 126762 141139 DEBUG leatherman.execution:93 - executing command: /usr/bin/ruby -e print(['libdir', 'archlibdir', 'sitearchlibdir', 'bindir'].find do |name|dir = RbConfig::CONFIG[name];next unless dir;file = File.join(dir, RbConfig::CONFIG['LIBRUBY_SO']);break file if File.exist? file;false end)2018-08-17 13: 21 28 : 09 22 . 242077 295315 DEBUG | - /usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3.02018-08-17 13: 21 28 : 09 22 . 242280 295528 DEBUG leatherman.execution:559 - process exited with status code 0.2018-08-17 13: 21 28 : 09 22 . 246717 299951 INFO leatherman.ruby:137 - ruby loaded from "/usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3.0".2018-08-17 13: 21 28 : 09 22 . 247314 300503 DEBUG leatherman.dynamic_library:77 - symbol rb_data_object_alloc not found in library /usr/lib/x86_64-linux-gnu/libruby-2.3.so.2.3.0, trying alias rb_data_object_wrap.2018-08-17 13: 21 28 : 09 22 . 357056 418246 INFO leatherman.ruby:186 - using ruby version 2.3.32018-08-17 13: 21 28 : 09 22 . 357220 418408 INFO puppetlabs.facter - requested queries: oscheck_codeblock oscheck_factervalue.2018-08-17 13: 21 28 : 09 22 . 357303 418488 DEBUG puppetlabs.facter - fact "facterversion" has resolved to "3.11.3".2018-08-17 13: 21 28 : 09 22 . 357678 418857 DEBUG leatherman.file_util:65 - Error reading file: No such file or directory2018-08-17 13: 21 28 : 09 22 . 358390 419635 DEBUG puppetlabs.facter - loading all custom facts.2018-08-17 13: 21 28 : 09 22 . 358435 419683 DEBUG puppetlabs.facter - loading custom fact directories from config file2018-08-17 13: 21 28 : 09 22 . 358494 419733 DEBUG puppetlabs.facter - searching for custom facts in /home/chrisb.2018-08-17 13: 21 28 : 09 22 . 358649 419890 INFO puppetlabs.facter - loading custom facts from /home/chrisb/ oscheck_codeblock.rb.2018-08-17 13:21:09.358964
Jira (FACT-1875) Unable to use "confine" with structured facts -- documentation is incorrect
Title: Message Title Chris Butler updated an issue Facter / FACT-1875 Unable to use "confine" with structured facts -- documentation is incorrect Change By: Chris Butler Summary: Unable to use "confine" with structured facts -- documentation error is incorrect Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1875) Unable to use "confine" with structured facts -- documentation error
Title: Message Title Chris Butler created an issue Facter / FACT-1875 Unable to use "confine" with structured facts -- documentation error Issue Type: Bug Affects Versions: FACT 3.11.3 Assignee: Unassigned Created: 2018/08/17 5:25 AM Environment: Tested with Facter 3.6.7 running on VirtuozzoLinux 7 Also tested with Facter 3.11.3 on Debian Stretch Priority: Normal Reporter: Chris Butler I've been attempting to confine some facts using structured facts, as described in the documentation here. However, neither method described in the docs seems to actually work with the current version of facter: ==> oscheck_codeblock.rb <== Facter.add(:oscheck_codeblock) do confine :os do |os| os['id'] == 'Debian'
Jira (PUP-6082) ignore-disabled option for puppet agent runs by hand
Title: Message Title Chris Butler commented on PUP-6082 Re: ignore-disabled option for puppet agent runs by hand I'd like to add a vote for at least allowing --noop runs with a disabled agent. Such a feature would allow us to preview the changes the agent is about to make, giving us confidence that we are in fact ready to re-enable the agent. Our main use-case for disabling the agent is where we've had to apply a hot-fix outside of Puppet to react to a problem and restore service in prod faster than we could otherwise do by updating the manifests. We obviously then go back and apply the fix "properly" through the normal roll-out process. In this situation we'd like to be able to do a no-op run after deploying the proper fix to the production environment before we re-enable the agent. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7120) systemd service provider treats "active (exited)" status as "running"
Title: Message Title Chris Butler created an issue Puppet / PUP-7120 systemd service provider treats "active (exited)" status as "running" Issue Type: Bug Affects Versions: PUP 4.7.0 Assignee: Unassigned Created: 2017/01/20 3:54 AM Environment: Debian Jessie Priority: Normal Reporter: Chris Butler In systemd, a service can end up with the status "active (exited)", in cases where the service was started but exited with a zero exit code. Unfortunately, Puppet doesn't treat a service in this state as "stopped", which I think it should. I see this when installing pgbouncer on Debian Jessie. After the package has been installed but before it's been configured, the service ends up in a "active (exited)" state: # systemctl status pgbouncer
Jira (HI-419) Unhelpful Hiera Error
Title: Message Title Chris Butler commented on HI-419 Re: Unhelpful Hiera Error The only mention in the puppetserver log file is the same error message, no stack trace has been logged: 2016-11-18 15:48:02,070 ERROR [qtp25401-5818] [p.r.core] Internal Server Error: org.jruby.exceptions.RaiseException: (Exception) Hiera type mismatch: expected Array and got Hash Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-419) Unhelpful Hiera Error
Title: Message Title Chris Butler commented on HI-419 Re: Unhelpful Hiera Error I'm seeing this with Puppet 4.8.0: Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Internal Server Error: org.jruby.exceptions.RaiseException: (Exception) Hiera type mismatch: expected Array and got Hash Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
