Jira (PUP-10719) Puppet's feature detection can leave rubygems in a bad state
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10719 Puppet's feature detection can leave rubygems in a bad state Change By: Josh Cooper Team: Coremunity Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374990.1602706184000.56191.1602721500136%40Atlassian.JIRA.
Jira (PUP-10719) Puppet's feature detection can leave rubygems in a bad state
Title: Message Title Josh Cooper commented on PUP-10719 Re: Puppet's feature detection can leave rubygems in a bad state One option is to call Gem.clear_paths if a feature fails to load. That causes a slow down because we end up repeatedly failing and retrying for gems that really aren't there, like msgpack. Or rescue the exception when calling Gem::Specifications.latest_specs That means we're still loading the full gemspec unnecessarily. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374990.1602706184000.56189.1602721500047%40Atlassian.JIRA.
Jira (PUP-10719) Puppet's feature detection can leave rubygems in a bad state
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10719 Puppet's feature detection can leave rubygems in a bad state Change By: Josh Cooper Sprint: Platform Core KANBAN Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374990.1602706184000.56190.1602721500091%40Atlassian.JIRA.
Jira (PUP-10719) Puppet's feature detection can leave rubygems in a bad state
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10719 Puppet's feature detection can leave rubygems in a bad state Change By: Josh Cooper Fix Version/s: PUP 6.20.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374990.1602706184000.56186.1602721320030%40Atlassian.JIRA.
Jira (PUP-10719) Puppet's feature detection can leave rubygems in a bad state
Title: Message Title Josh Cooper commented on PUP-10719 Re: Puppet's feature detection can leave rubygems in a bad state Interestingly, the feature that enables puppet to load extensions from gems causes the number of file I/O operations to increase by ~2.5 times during catalog compilation using the pupetserver perf control repo. Seems completely unnecessary for the rubygems cache to be cleared during compilation. [root@unheeded-statue ~]# strace -e trace=file -o trace.log -- puppet catalog compile -E perf_control > /dev/null [root@unheeded-statue ~]# grep /opt/puppetlabs/puppet/lib/ruby/gems/2.5.0 trace.log | wc -l 13743 [root@unheeded-statue ~]# strace -e trace=file -o trace-nogems.log -- puppet catalog compile -E perf_control > /dev/null ... [root@unheeded-statue ~]# grep /opt/puppetlabs/puppet/lib/ruby/gems/2.5.0 trace-nogems.log | wc -l 5518 Add Comment
Jira (PUP-10473) Remove legacy auth.conf support
Title: Message Title Josh Cooper commented on PUP-10473 Re: Remove legacy auth.conf support Passed CI in 9b985858f5 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356946.1588032295000.56094.1602710880028%40Atlassian.JIRA.
Jira (PUP-10719) Puppet's feature detection can leave rubygems in a bad state
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10719
Puppet's feature detection can leave rubygems in a bad state
Change By:
Josh Cooper
If a gem is managed by a native package manager (rpm, etc), and it is updated during a puppet run, it is possible for rubygems to be left in a bad state causing the run to fail.This can be reproduced using:{code:ruby}require 'fileutils'require 'rubygems'if File.exist?("/tmp/thor-1.0.1.gemspec") FileUtils.mv("/tmp/thor-1.0.1.gemspec", "/opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/specifications/thor-1.0.1.gemspec")endGem.clear_pathsbegin require 'msgpack'rescue LoadError => eendFileUtils.mv("/opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/specifications/thor-1.0.1.gemspec", "/tmp/thor-1.0.1.gemspec")Gem::Specification.latest_specs{code}Rubygems monkey patches {{Kernel.require}} so that if the gem fails to load, it will try to activate it. This has the side effect of caching the stub specifications for all gems.If the gemspec is then removed via rpm upgrade, then the cached stub specification will refer to a gemspec that no longer exists.If we later try to load the full specifications (such as when autoloading a terminus), then rubygems will raise:{noformat}/opt/puppetlabs/puppet/lib/ruby/2.5.0/rubygems/specification.rb:743:in `_all': pid: 9272 nil spec! included in [...#...]{noformat} It can also be reproduced in puppet using:{code:ruby}require 'fileutils'require 'puppet' if File.exist?("/tmp/thor-1.0.1.gemspec") FileUtils.mv("/tmp/thor-1.0.1.gemspec", "/opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/specifications/thor-1.0.1.gemspec")end Puppet.initialize_settingsPuppet[:log_level] = 'debug' Puppet.features.msgpack?FileUtils.mv("/opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/specifications/thor-1.0.1.gemspec", "/tmp/thor-1.0.1.gemspec")Puppet::FileBucket::File.indirection.terminus(:rest){code}
Add Comment
Jira (PUP-10719) Puppet's feature detection can leave rubygems in a bad state
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10719
Puppet's feature detection can leave rubygems in a bad state
Change By:
Josh Cooper
If a gem is managed by a native package manager (rpm, etc), and it is updated during a puppet run, it is possible for rubygems to be left in a bad state causing the run to fail.This can be reproduced using:{code:ruby}require 'fileutils'require 'rubygems' if File.exist?("/tmp/thor-1.0.1.gemspec") FileUtils.mv("/tmp/thor-1.0.1.gemspec", "/opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/specifications/thor-1.0.1.gemspec")endGem.clear_pathsbegin require 'msgpack'rescue LoadError => eendFileUtils.mv("/opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/specifications/thor-1.0.1.gemspec", "/tmp/thor-1.0.1.gemspec")Gem::Specification.latest_specs{code}Rubygems monkey patches {{Kernel.require}} so that if the gem fails to load, it will try to activate it. This has the side effect of caching the stub specifications for all gems.If the gemspec is then removed via rpm upgrade, then the cached stub specification will refer to a gemspec that no longer exists.If we later try to load the full specifications (such as when autoloading a terminus), then rubygems will raise:{noformat}/opt/puppetlabs/puppet/lib/ruby/2.5.0/rubygems/specification.rb:743:in `_all': pid: 9272 nil spec! included in [...#...]{noformat}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-10719) Puppet's feature detection can leave rubygems in a bad state
Title: Message Title Josh Cooper commented on PUP-10719 Re: Puppet's feature detection can leave rubygems in a bad state One option is to call Gem.clear_paths if a feature fails to load. Or rescue the exception when calling Gem::Specifications.latest_specs, calling Gem.clear_paths and then retry once. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374990.1602706184000.56049.1602706320025%40Atlassian.JIRA.
Jira (PUP-10719) Puppet's feature detection can leave rubygems in a bad state
Title: Message Title
Josh Cooper created an issue
Puppet / PUP-10719
Puppet's feature detection can leave rubygems in a bad state
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/10/14 1:09 PM
Priority:
Normal
Reporter:
Josh Cooper
If a gem is managed by a native package manager (rpm, etc), and it is updated during a puppet run, it is possible for rubygems to be left in a bad state causing the run to fail. This can be reproduced using:
require 'fileutils'
require 'rubygems'if File.exist?("/tmp/thor-1.0.1.gemspec")
FileUtils.mv("/tmp/thor-1.0.1.gemspec", "/opt/puppetlabs/puppet/lib/ruby/gems/2.5.0/specifications/thor-1.0.1.gemspec")
end
Gem.clear_paths
begin
Jira (PUP-10688) tidy resource does not honor schedule metaparameter
Title: Message Title Michael Luck commented on PUP-10688 Re: tidy resource does not honor schedule metaparameter Josh Cooper Ran some debug runs on two computers...looks like it works properly on one but not another. Computer A: ... ←[0;36mDebug: Loaded state in 0.02 seconds←[0m ←[0;36mDebug: /Stage[main]/Windows_patch_mgmt2/Tidy[C:\ProgramData\os_patching]: Tidying File[C:/ProgramData/os_patching/os_patching_fact_generation-2020_10_08-01_48_45.log]←[0m ←[0;36mDebug: /Stage[main]/Windows_patch_mgmt2/Tidy[C:\ProgramData\os_patching]: Tidying File[C:/ProgramData/os_patching/os_patching_fact_generation-2020_10_08-13_46_10.log]←[0m ←[mNotice: /Stage[main]/Windows_patch_mgmt2/Tidy[C:\ProgramData\os_patching]: Tidying 2 files←[0m ←[0;36mDebug: Loaded transaction store file in 0.04 seconds←[0m ←[0;32mInfo: Applying configuration version '1602700361'←[0m ... Computer B: ... Debug: /Stage[main]/Windows_patch_mgmt2/Tidy[C:\ProgramData\InstalledUpdates]: Not scheduled Debug: /Stage[main]/Windows_patch_mgmt2/Tidy[C:\ProgramData\InstalledUpdates]: Resource is being skipped, unscheduling all events Debug: /Stage[main]/Windows_patch_mgmt2/Tidy[C:\ProgramData\os_patching]: Not scheduled Debug: /Stage[main]/Windows_patch_mgmt2/Tidy[C:\ProgramData\os_patching]: Resource is being skipped, unscheduling all events ... Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit
Jira (PUP-10688) tidy resource does not honor schedule metaparameter
Title: Message Title Michael Luck commented on PUP-10688 Re: tidy resource does not honor schedule metaparameter Josh Cooper That is interesting...here is my output from Puppet DB. It should only be running on Sundays but it is not for some reason. Oct 14 2020 - 14:03:41 /Stage[main]/Windows_patch_mgmt/Tidy[C:\ProgramData\os_patching] notice, tidy, class, windows_patch_mgmt, node, default Tidying 1 files /etc/puppetlabs/code/environments/production/manifests/patch_mgmt.pp:84 Oct 14 2020 - 14:04:40 /Stage[main]/Windows_patch_mgmt/File[C:/ProgramData/os_patching/os_patching_fact_generation-2020_10_07-13_46_02.log]/ensure notice, file, tidy, class, windows_patch_mgmt, node, default removed Oct 14 2020 - 14:06:59 Puppet notice Applied catalog in 198.57 seconds Add Comment
Jira (PUP-10687) file resource with ensure => absent on an existing directory reports out of sync and changed without making any changes
Title: Message Title univerio commented on PUP-10687 Re: file resource with ensure => absent on an existing directory reports out of sync and changed without making any changes Josh Cooper Agreed that erroring out would be an acceptable outcome, but it doesn't actually error out: failed: false skipped: false Compare this with the output from an `ensure => file` on an existing directory: File[/foo]: title: "/foo" file: "/etc/puppet/manifests/hello.pp" line: 1 resource: File[/foo] resource_type: File provider_used: posix containment_path: - Stage[main] - Main
Jira (PUP-10687) file resource with ensure => absent on an existing directory reports out of sync and changed without making any changes
Title: Message Title Josh Cooper commented on PUP-10687 Re: file resource with ensure => absent on an existing directory reports out of sync and changed without making any changes From puppet's perspective, it was told to remove a directory that it can't, so it is an error, and the report reflects that. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374050.1602005236000.55949.1602698520175%40Atlassian.JIRA.
Jira (PUP-10713) Fine grained environment timeout issues
Title: Message Title Josh Cooper commented on PUP-10713 Re: Fine grained environment timeout issues Added to platform_7 so that we can delete the clear and clear_all methods (so all manual cache eviction is handled through the REST API). Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374883.1602635146000.55941.1602697860375%40Atlassian.JIRA.
Jira (PUP-10713) Fine grained environment timeout issues
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10713 Fine grained environment timeout issues Change By: Josh Cooper Team: Coremunity Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374883.1602635146000.55942.1602697860419%40Atlassian.JIRA.
Jira (PUP-10713) Fine grained environment timeout issues
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10713 Fine grained environment timeout issues Change By: Josh Cooper Labels: platform_7 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374883.1602635146000.55933.1602697800036%40Atlassian.JIRA.
Jira (PUP-10688) tidy resource does not honor schedule metaparameter
Title: Message Title
Josh Cooper commented on PUP-10688
Re: tidy resource does not honor schedule metaparameter
I can't reproduce this:
C:\Users\josh\projects\puppet>type tidy.pp
schedule { 'cleanup_window':
weekday => 'Sunday'
}
tidy { 'C:\tmp\tidy':
age => '1w',
matches => '*.log',
recurse => true,
schedule=> 'cleanup_window'
}
C:\Users\josh\projects\puppet>bundle exec puppet apply --debug tidy.pp
...
Debug: Creating default schedules
Jira (PUP-10718) Hiera5 mapped_paths should permit glob expansion
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10718
Hiera5 mapped_paths should permit glob expansion
Change By:
Josh Cooper
It would be helpful for breaking out files into more manageable chunks, if hiera's mapped_paths option would permit use of globs for expansion.For example: { { code:yaml} - name: Examplemapped_paths: [services, tmp, "service/%\{tmp}/*.yaml" ]{code } }
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371891.1600185467000.55923.1602697380195%40Atlassian.JIRA.
Jira (PUP-10718) Hiera mapped_paths should permit glob expansion
Title: Message Title Josh Cooper moved an issue Puppet / PUP-10718 Hiera mapped_paths should permit glob expansion Change By: Josh Cooper Key: HI PUP - 620 10718 Project: Hiera Puppet Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371891.1600185467000.55921.1602697380106%40Atlassian.JIRA.
Jira (PUP-10718) Hiera5 mapped_paths should permit glob expansion
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10718 Hiera5 mapped_paths should permit glob expansion Change By: Josh Cooper Summary: Hiera Hiera5 mapped_paths should permit glob expansion Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.371891.1600185467000.55922.1602697380151%40Atlassian.JIRA.
Jira (PUP-10673) Call simple server status endpoint
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10673 Call simple server status endpoint Change By: Josh Cooper Labels: platform_7 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.372044.1600212887000.55865.1602696780179%40Atlassian.JIRA.
Jira (PUP-10673) Call simple server status endpoint
Title: Message Title Josh Cooper commented on PUP-10673 Re: Call simple server status endpoint Merged to main in https://github.com/puppetlabs/puppet/commit/e0746ca619fac312b86e26b4a1f73db70b146947 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.372044.1600212887000.55861.1602696720218%40Atlassian.JIRA.
Jira (PUP-10714) remove "master_used" report parameter in puppet 7
Title: Message Title Josh Cooper commented on PUP-10714 Re: remove "master_used" report parameter in puppet 7 Merged to main in https://github.com/puppetlabs/puppet/commit/8e5ebbf13f0af07deee8b9c7aa81e07453b74cbb Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374886.1602655032000.55854.1602696660054%40Atlassian.JIRA.
Jira (PUP-10714) remove "master_used" report parameter in puppet 7
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10714 remove "master_used" report parameter in puppet 7 Change By: Josh Cooper Fix Version/s: PUP 7.0.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374886.1602655032000.55855.1602696660099%40Atlassian.JIRA.
Jira (PUP-10714) remove "master_used" report parameter in puppet 7
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10714 remove "master_used" report parameter in puppet 7 Change By: Josh Cooper Labels: platform_7 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374886.1602655032000.55856.1602696660143%40Atlassian.JIRA.
Jira (PUP-8014) Create a setting to clear short-lived puppet environments from memory
Title: Message Title Josh Cooper commented on PUP-8014 Re: Create a setting to clear short-lived puppet environments from memory Passed master CI in fe73adb224 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.214193.1506980344000.55839.1602696420041%40Atlassian.JIRA.
Jira (PUP-8014) Create a setting to clear short-lived puppet environments from memory
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8014 Create a setting to clear short-lived puppet environments from memory Change By: Josh Cooper Fix Version/s: PUP 7.0.0 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.214193.1506980344000.55840.1602696420054%40Atlassian.JIRA.
Jira (PUP-10619) Remove `environment_timeout_mode` setting
Title: Message Title Josh Cooper updated an issue Puppet / PUP-10619 Remove `environment_timeout_mode` setting Change By: Josh Cooper Summary: Remove ` environment_timeout environment_timeout_mode ` setting in favor of `environment_ttl` Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.369236.1597429036000.55632.1602692220038%40Atlassian.JIRA.
Jira (PUP-10619) Remove `environment_timeout_mode` setting
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-10619
Remove `environment_timeout_mode` setting
Change By:
Josh Cooper
The {{environment_timeout}} setting is a less-than-ideal way of dealing with environment purging, because it doesn't take into account the actual usage patterns for any given environment, and forces the user to make a call on whether to accept longer load times (timeout of 0), inconsistent state between JRubies (a timeout between 0 and unlimited), and high memory usage (unlimited timeout).The {{environment_timeout_mode}} setting was added in PUP-8014, and this ticket is to change the remove the setting and change the default (and only) behavior so that puppet evicts environments that haven't been used for a certain amount of time.
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
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
Jira (PDB-4931) Incrementally drop partitions oldest-first
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-4931 Incrementally drop partitions oldest-first Change By: Rob Browning Summary: Incrementally drop partitions oldest- firsti first Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374925.1602690481000.55595.1602690720029%40Atlassian.JIRA.
Jira (PDB-4931) Incrementally drop partitions oldest-firsti
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4931 Incrementally drop partitions oldest-firsti Issue Type: Bug Assignee: Rob Browning Created: 2020/10/14 8:48 AM Fix Versions: PDB 6.12.3 Priority: Normal Reporter: Rob Browning Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs"
Jira (FACT-2759) Linux Mint 20 os version bug
Title: Message Title Luchian Nemes updated an issue Facter / FACT-2759 Linux Mint 20 os version bug Change By: Luchian Nemes Fix Version/s: FACT 3.14.14 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.370126.1598354554000.55530.1602688680138%40Atlassian.JIRA.
Jira (FACT-2751) Facter reports wrong Windows build
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-2751 Facter reports wrong Windows build Change By: Mihai Buzgau Fix Version/s: FACT 3.14.14 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.369870.1597934847000.55496.1602686880032%40Atlassian.JIRA.
Jira (PUP-10715) Make show action the default one for puppet facts
Title: Message Title Bogdan Irimie updated an issue Puppet / PUP-10715 Make show action the default one for puppet facts Change By: Bogdan Irimie Sprint: ready for triage ghost-21.10 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374906.1602680047000.55476.1602684360275%40Atlassian.JIRA.
Jira (FACT-2827) option store unit test does not mock facter.conf
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2827 option store unit test does not mock facter.conf Change By: Bogdan Irimie Sprint: ghost-14.10 , ready for triage 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.373983.160199322.55467.1602684240479%40Atlassian.JIRA.
Jira (PUP-10717) When query for a specific fact with puppet facts show there are 3 additional puppet specific facts displayed
Title: Message Title Bogdan Irimie updated an issue Puppet / PUP-10717 When query for a specific fact with puppet facts show there are 3 additional puppet specific facts displayed Change By: Bogdan Irimie Sprint: ready for triage ghost-21.10 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374909.1602681076000.55478.1602684360363%40Atlassian.JIRA.
Jira (FACT-2834) Hardcoded proc0 processor name in resolvers/aix/architecture_resolver.rb and related files
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2834 Hardcoded proc0 processor name in resolvers/aix/architecture_resolver.rb and related files Change By: Bogdan Irimie Sprint: ready for triage ghost-21.10 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374371.1602155342000.55475.1602684360231%40Atlassian.JIRA.
Jira (FACT-1846) inconsistent results between facter and puppet facts
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-1846 inconsistent results between facter and puppet facts Change By: Bogdan Irimie Sprint: ready for triage ghost-21.10 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.246793.1524245996000.55474.1602684360177%40Atlassian.JIRA.
Jira (PUP-10716) Fix json output of puppet facts show action
Title: Message Title Bogdan Irimie updated an issue Puppet / PUP-10716 Fix json output of puppet facts show action Change By: Bogdan Irimie Sprint: ready for triage ghost-21.10 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374908.160268028.55477.1602684360319%40Atlassian.JIRA.
Jira (FACT-2836) Release 4.0.44
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2836 Release 4.0.44 Change By: Bogdan Irimie Sprint: ready for triage ghost-21.10 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374911.1602682654000.55479.1602684360407%40Atlassian.JIRA.
Jira (FACT-2835) Acceptance test on puppetlabs-docker fail with puppet 7 nightly
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2835 Acceptance test on puppetlabs-docker fail with puppet 7 nightly Change By: Bogdan Irimie Sprint: ghost-14.10 , ready for triage 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374739.1602573029000.55473.1602684240743%40Atlassian.JIRA.
Jira (FACT-2158) Fix for tests/options/puppet_facts.rb
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2158 Fix for tests/options/puppet_facts.rb Change By: Bogdan Irimie Sprint: ghost-14.10 , ready for triage 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.337943.1575539697000.55466.1602684240435%40Atlassian.JIRA.
Jira (FACT-2705) Blog post for Facter 4
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2705 Blog post for Facter 4 Change By: Bogdan Irimie Sprint: ghost-14.10 , ready for triage 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.365211.1594212543000.55461.1602684240214%40Atlassian.JIRA.
Jira (FACT-2826) Implement Facter.flush
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2826 Implement Facter.flush Change By: Bogdan Irimie Sprint: ghost-14.10 , ready for triage 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.373811.1601648662000.55465.1602684240390%40Atlassian.JIRA.
Jira (FACT-2815) Timing on cached facts is inconsistent, sometime it is displayed, others it is not
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2815 Timing on cached facts is inconsistent, sometime it is displayed, others it is not Change By: Bogdan Irimie Sprint: ghost-7.10, ghost-14.10 , ready for triage 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.372973.1600962322000.55470.1602684240612%40Atlassian.JIRA.
Jira (FACT-2833) Investigate performance for hypervisor fact
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2833 Investigate performance for hypervisor fact Change By: Bogdan Irimie Sprint: ghost-14.10 , ready for triage 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374205.1602078248000.55462.1602684240259%40Atlassian.JIRA.
Jira (FACT-2819) (experimental) Revert parallel resolution of facts
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2819 (experimental) Revert parallel resolution of facts Change By: Bogdan Irimie Sprint: ghost-7.10, ghost-14.10 , ready for triage 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.373483.1601475251000.55469.1602684240567%40Atlassian.JIRA.
Jira (FACT-2829) partition fact missing "mount" field
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2829 partition fact missing "mount" field Change By: Bogdan Irimie Sprint: ghost-14.10 , ready for triage 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.373994.160199671.55464.1602684240347%40Atlassian.JIRA.
Jira (FACT-2813) Show backtrace in CI for acceptance test errors
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2813 Show backtrace in CI for acceptance test errors Change By: Bogdan Irimie Sprint: ghost-7.10, ghost-14.10 , ready for triage 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.372970.1600961477000.55471.1602684240655%40Atlassian.JIRA.
Jira (FACT-2811) Refactor unit tests so they can be run with --order rand
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2811 Refactor unit tests so they can be run with --order rand Change By: Bogdan Irimie Sprint: ghost-7.10, ghost-14.10 , ready for triage 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.372636.1600698609000.55468.1602684240523%40Atlassian.JIRA.
Jira (FACT-2643) Timeout on resolution
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2643 Timeout on resolution Change By: Bogdan Irimie Sprint: ghost-7.10, ghost-14.10 , ready for triage 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.360290.1590667491000.55472.1602684240699%40Atlassian.JIRA.
Jira (FACT-2832) Fix AIX performance
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-2832 Fix AIX performance Change By: Bogdan Irimie Sprint: ghost-14.10 , ready for triage 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374200.1602077563000.55463.1602684240303%40Atlassian.JIRA.
Jira (FACT-2836) Release 4.0.44
Title: Message Title Sebastian Miclea created an issue Facter / FACT-2836 Release 4.0.44 Issue Type: Task Assignee: Bogdan Irimie Created: 2020/10/14 6:37 AM Priority: Normal Reporter: Sebastian Miclea Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit
Jira (PUP-10717) When query for a specific fact with puppet facts show there are 3 additional puppet specific facts displayed
Title: Message Title Sebastian Miclea updated an issue Puppet / PUP-10717 When query for a specific fact with puppet facts show there are 3 additional puppet specific facts displayed Change By: Sebastian Miclea Story Points: 2 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374909.1602681076000.55456.1602682560025%40Atlassian.JIRA.
Jira (PUP-10716) Fix json output of puppet facts show action
Title: Message Title Sebastian Miclea updated an issue Puppet / PUP-10716 Fix json output of puppet facts show action Change By: Sebastian Miclea Story Points: 3 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374908.160268028.55455.1602682260029%40Atlassian.JIRA.
Jira (PUP-10715) Make show action the default one for puppet facts
Title: Message Title Sebastian Miclea updated an issue Puppet / PUP-10715 Make show action the default one for puppet facts Change By: Sebastian Miclea Story Points: 1 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374906.1602680047000.55452.1602682020026%40Atlassian.JIRA.
Jira (FACT-2834) Hardcoded proc0 processor name in resolvers/aix/architecture_resolver.rb and related files
Title: Message Title Sebastian Miclea updated an issue Facter / FACT-2834 Hardcoded proc0 processor name in resolvers/aix/architecture_resolver.rb and related files Change By: Sebastian Miclea Story Points: 3 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374371.1602155342000.55451.1602681780027%40Atlassian.JIRA.
Jira (FACT-1846) inconsistent results between facter and puppet facts
Title: Message Title Sebastian Miclea updated an issue Facter / FACT-1846 inconsistent results between facter and puppet facts Change By: Sebastian Miclea Story Points: 1 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.246793.1524245996000.55447.1602681300047%40Atlassian.JIRA.
Jira (PUP-10717) When query for a specific fact with puppet facts show there are 3 additional puppet specific facts displayed
Title: Message Title Oana Tanasoiu updated an issue Puppet / PUP-10717 When query for a specific fact with puppet facts show there are 3 additional puppet specific facts displayed Change By: Oana Tanasoiu Summary: When query for a specific fact with puppet facts show there are 3 additional puppet specific facts displayed Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374909.1602681076000.55446.1602681240025%40Atlassian.JIRA.
Jira (PUP-10717) When query for a specific fact with puppet facts show there are 3 additional puppet specific facts
Title: Message Title
Oana Tanasoiu updated an issue
Puppet / PUP-10717
When query for a specific fact with puppet facts show there are 3 additional puppet specific facts
Change By:
Oana Tanasoiu
* . Puppet Version: main branch* *Puppet Server Version:* *OS Name/Version: all*After resolving the requested facts, in puppet are added 3 additional local facts: "clientcert", "clientversion" and "clientnoop". `puppet facts show` action should display only the requested facts without the additional facts.*Desired Behavior:*For 'timezone' query (puppet facts show timezone) the output should be:{"timezone":"EEST"}*Actual Behavior:*For 'timezone' query (puppet facts show timezone) the output is:{"timezone":"EEST","clientcert":"macbookpro.local","clientversion":"6.14.0","clientnoop":false}
Add Comment
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails
Jira (PUP-10717) When query for a specific fact with puppet facts show there are 3 additional puppet specific facts
Title: Message Title
Oana Tanasoiu created an issue
Puppet / PUP-10717
When query for a specific fact with puppet facts show there are 3 additional puppet specific facts
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/10/14 6:11 AM
Priority:
Normal
Reporter:
Oana Tanasoiu
Puppet Version: main branch Puppet Server Version: OS Name/Version: all After resolving the requested facts, in puppet are added 3 additional local facts: "clientcert", "clientversion" and "clientnoop". `puppet facts show` action should display only the requested facts without the additional facts. Desired Behavior: For 'timezone' query (puppet facts show timezone) the output should be: {"timezone":"EEST"} Actual Behavior: For 'timezone' query (puppet facts show timezone) the output is: {"timezone":"EEST","clientcert":"macbookpro.local","clientversion":"6.14.0","clientnoop":false}
Add Comment
Jira (PUP-10716) Fix json output of puppet facts show action
Title: Message Title Oana Tanasoiu updated an issue Puppet / PUP-10716 Fix json output of puppet facts show action Change By: Oana Tanasoiu Team: Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374908.160268028.55440.1602680400120%40Atlassian.JIRA.
Jira (PUP-10716) Fix json output of puppet facts show action
Title: Message Title
Oana Tanasoiu created an issue
Puppet / PUP-10716
Fix json output of puppet facts show action
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/10/14 5:58 AM
Priority:
Normal
Reporter:
Oana Tanasoiu
Puppet Version: main branch Puppet Server Version: OS Name/Version: All By default puppet facts show output is rendered as json. The json output is not pretty printed. Desired Behavior: `"os": { "name": "Darwin", "hardware": "x86_64", "architecture": "x86_64", "family": "Darwin", "release": { "full": "18.7.0", "major": "18", "minor": "7" }, "macosx": { "build": "18G95", "product": "Mac OS X", "version": { "full": "10.14.6", "major": "10.14", "minor": "6" } }}` Actual Behavior: The output for os query : `{"os":{"architecture":"x86_64","family":"Darwin","hardware":"x86_64","macosx":{"build":"18G95","product":"Mac OS X","version":{"full":"10.14.6","major":"10.14","minor":"6"}},"name":"Darwin","release":{"full":"18.7.0","major":"18","minor":"7"}}}`
Add Comment
Jira (PUP-10715) Make show action the default one for puppet facts
Title: Message Title Oana Tanasoiu created an issue Puppet / PUP-10715 Make show action the default one for puppet facts Issue Type: Task Assignee: Unassigned Created: 2020/10/14 5:54 AM Priority: Normal Reporter: Oana Tanasoiu Currently the default action for puppet facts application is `find` and it should be changed to `show` action. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (FACT-2823) SPIKE - Investigate turning facter into a single binary
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Facter / FACT-2823 SPIKE - Investigate turning facter into a single binary Change By: Gheorghe Popescu Assignee: Gheorghe Popescu Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.373494.1601481425000.55424.1602677700078%40Atlassian.JIRA.
Jira (FACT-1846) inconsistent results between facter and puppet facts
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1846 inconsistent results between facter and puppet facts Change By: Mihai Buzgau Sprint: ready for triage Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.246793.1524245996000.55423.1602676500072%40Atlassian.JIRA.
Jira (FACT-1846) inconsistent results between facter and puppet facts
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1846 inconsistent results between facter and puppet facts Change By: Mihai Buzgau Sub-team: ghost Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.246793.1524245996000.55422.1602676500068%40Atlassian.JIRA.
Jira (FACT-1846) inconsistent results between facter and puppet facts
Title: Message Title Mihai Buzgau updated an issue Facter / FACT-1846 inconsistent results between facter and puppet facts Change By: Mihai Buzgau Team: Platform OS Night's Watch Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.246793.1524245996000.55421.1602676500050%40Atlassian.JIRA.
Jira (PUP-10712) Provide a JSON terminus for node and report
Title: Message Title Dorin Pleava assigned an issue to Dorin Pleava Puppet / PUP-10712 Provide a JSON terminus for node and report Change By: Dorin Pleava Assignee: Dorin Pleava Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374770.1602599183000.55414.1602675720030%40Atlassian.JIRA.
Jira (PDB-4874) regression on resource query performance on upgrade to 6.11.3 from 5.1
Title: Message Title Julian Taylor commented on PDB-4874 Re: regression on resource query performance on upgrade to 6.11.3 from 5.1 As the issue keeps reoccuring we have performed some more tests on the query running following before each query: VACUUM ANALYZE resource_params; SELECT attname, n_distinct, avg_width, correlation, array_to_string(most_common_vals, E'\n'), array_to_string(most_common_freqs, E'\n') FROM pg_stats WHERE tablename = 'resource_params' AND attname = 'name'; The query performance seems to become slow when the frequency of the job_name value of the name colume in resource_params is lower than 0.0012 There is no correlation with the n_distinct or correlation value. Other values in the frequency table should be irrelevant as only name and value are used and value has a high distinct count. A workaround is probably to increase the statistics sampling of the table to reduce the probability that the job_name frequency is underestimated or to disable the autovacuum which was added in the new version (and the reason why this appeared as a regression) after good statistics have been created. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.370482.1598537549000.55340.1602665040023%40Atlassian.JIRA.
Jira (PUP-10712) Provide a JSON terminus for node and report
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10712 Provide a JSON terminus for node and report Change By: Mihai Buzgau Sprint: NW - 2020-10-28 Story Points: 3 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374770.1602599183000.55339.1602664380029%40Atlassian.JIRA.
Jira (PUP-10711) Create numeric and port setting types and update existing port settings
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10711 Create numeric and port setting types and update existing port settings Change By: Mihai Buzgau Story Points: 3 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374478.1602246841000.55335.1602663900041%40Atlassian.JIRA.
Jira (PUP-10711) Create numeric and port setting types and update existing port settings
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10711 Create numeric and port setting types and update existing port settings Change By: Mihai Buzgau Sprint: PR NW - Triage 2020-10-28 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374478.1602246841000.55336.1602663900096%40Atlassian.JIRA.
Jira (PDB-4930) Investigate PG deadlocks with latest_report_id
Title: Message Title Austin Boyd updated an issue PuppetDB / PDB-4930 Investigate PG deadlocks with latest_report_id Change By: Austin Boyd Zendesk Ticket Count: 1 Zendesk Ticket IDs: 41188 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374800.160261184.55334.1602663420092%40Atlassian.JIRA.
Jira (PDB-4930) Investigate PG deadlocks with latest_report_id
Title: Message Title Austin Boyd updated an issue PuppetDB / PDB-4930 Investigate PG deadlocks with latest_report_id Change By: Austin Boyd Labels: jira_escalated Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374800.160261184.55333.1602663420037%40Atlassian.JIRA.
Jira (FACT-2829) partition fact missing "mount" field
Title: Message Title Andrei Filipovici assigned an issue to Andrei Filipovici Facter / FACT-2829 partition fact missing "mount" field Change By: Andrei Filipovici Assignee: Andrei Filipovici Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.373994.160199671.55306.1602661620117%40Atlassian.JIRA.
Jira (PUP-10673) Call simple server status endpoint
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-10673 Call simple server status endpoint Change By: Mihai Buzgau Sprint: NW - 2020-10-14 , NW - 2020-10-28 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.372044.1600212887000.55277.1602661140029%40Atlassian.JIRA.
Jira (PUP-9051) Refactor the SMF provider to implement enableable semantics
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9051 Refactor the SMF provider to implement enableable semantics Change By: Mihai Buzgau Sprint: NW - 2020-10-28 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.270546.1533855292000.55276.1602661080100%40Atlassian.JIRA.
Jira (PUP-9051) Refactor the SMF provider to implement enableable semantics
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9051 Refactor the SMF provider to implement enableable semantics Change By: Mihai Buzgau Story Points: 3 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.270546.1533855292000.55275.1602661080045%40Atlassian.JIRA.
Jira (FACT-2835) Acceptance test on puppetlabs-docker fail with puppet 7 nightly
Title: Message Title Florin Dragos commented on FACT-2835 Re: Acceptance test on puppetlabs-docker fail with puppet 7 nightly We should log as debug, not warn to prevent polluting the stderr: https://github.com/puppetlabs/facter/pull/2139 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374739.1602573029000.55262.1602659700039%40Atlassian.JIRA.
Jira (PUP-10669) Create "server" section and add alias
Title: Message Title Dorin Pleava updated an issue Puppet / PUP-10669 Create "server" section and add alias Change By: Dorin Pleava Release Notes: New Feature Release Notes Summary: As master section is replaced with server section, for nowmaster section is still allowed in puppet.conf, but whenadding/updating a setting from the master section, the actionwill be done on the server section instead, and the setting from [master]will be removed. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.372040.1600212479000.55261.1602659640028%40Atlassian.JIRA.
Jira (FACT-2643) Timeout on resolution
Title: Message Title Oana Tanasoiu commented on FACT-2643 Re: Timeout on resolution Facter 3 doesn't support timeout option for custom facts, it logs a warning message when a user tries to set that option. We decided to keep the mechanism that sets timeout on resolution on Facter 4 and to add an acceptance test to verify that the behaviour is indeed as expected. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.360290.1590667491000.55258.1602658620029%40Atlassian.JIRA.
Jira (PUP-10714) remove "master_used" report parameter in puppet 7
Title: Message Title Ciprian Badescu updated an issue Puppet / PUP-10714 remove "master_used" report parameter in puppet 7 Change By: Ciprian Badescu Summary: delete remove "master_used" report parameter in puppet 7 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.374886.1602655032000.55248.1602655380088%40Atlassian.JIRA.
