Jira (PDB-5250) Disable el-6-x86_64 builds for puppetdb
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-5250 Disable el-6-x86_64 builds for puppetdb Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.413330.1629831906000.11132.1637279100200%40Atlassian.JIRA.
Jira (PDB-5251) Disable el-6-x86_64 test pipeline for puppetdb
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-5251 Disable el-6-x86_64 test pipeline for puppetdb Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.413331.1629831908000.11133.1637279100245%40Atlassian.JIRA.
Jira (PUP-11367) Document that `tidy` does not remove managed resources
Title: Message Title Alex Vandiver updated an issue Puppet / PUP-11367 Document that `tidy` does not remove managed resources Change By: Alex Vandiver PUP-7307 / [ 0d89cb1c1f44fcb30fbf8478327c2422e8a10b90 mande |https://github.com/puppetlabs/puppet/commit/0d89cb1c1f44fcb30fbf8478327c2422e8a10b90] made `tidy` not attempt to remove managed resources, but didn't update the documentation to document this behaviour.Not removing managed resources makes perfect sense, but should be called out, as it provides n very useful way to make exceptions to `tidy`s behaviour with `recurse` is used. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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-11367) Document that `tidy` does not remove managed resources
Title: Message Title Alex Vandiver created an issue Puppet / PUP-11367 Document that `tidy` does not remove managed resources Issue Type: Bug Assignee: Unassigned Components: Docs Created: 2021/11/18 11:54 AM Priority: Normal Reporter: Alex Vandiver PUP-7307 / 0d89cb1c1f44fcb30fbf8478327c2422e8a10b90 mande `tidy` not attempt to remove managed resources, but didn't update the documentation to document this behaviour. Not removing managed resources makes perfect sense, but should be called out, as it provides n very useful way to make exceptions to `tidy`s behaviour with `recurse` is used. Add Comment
Jira (PDB-5378) Don't traverse all reports when deactivating a node
Title: Message Title Austin Blatt assigned an issue to Austin Blatt PuppetDB / PDB-5378 Don't traverse all reports when deactivating a node Change By: Austin Blatt Assignee: Austin Blatt Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.424200.1637182651000.10778.1637261100678%40Atlassian.JIRA.
Jira (PDB-5378) Don't traverse all reports when deactivating a node
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5378 Don't traverse all reports when deactivating a node Change By: Austin Blatt Sprint: HAHA/Grooming HA 2021-12-01 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.424200.1637182651000.10777.1637261100627%40Atlassian.JIRA.
Jira (PUP-11167) Provider redhat must have features 'maskable' to set 'enable' to 'mask' during rspec-puppet testing
Title: Message Title
Jarret Lavallee commented on PUP-11167
Re: Provider redhat must have features 'maskable' to set 'enable' to 'mask' during rspec-puppet testing
The method Jake posted above also worked for me. You can also add the lines below to a before block to mock the filesystem calls for /proc/1/comm. You could add these for OSes with systemd with some conditional statements.
allow(Puppet::FileSystem).to receive(:exist?).and_call_original
allow(Puppet::FileSystem).to receive(:exist?).with('/proc/1/comm').and_return(true)
allow(Puppet::FileSystem).to receive(:read).and_call_original
allow(Puppet::FileSystem).to receive(:read).with('/proc/1/comm').and_return(['systemd'])
If you use custom fact sets with the service_provider fact from [puppetlabs-stdlib|https://github.com/puppetlabs/puppetlabs-stdlib/blob/main/lib/facter/service_provider.rb,] you could use node_facts['service_provider'] in the conditional statement.
Add Comment
Jira (PUP-11366) Puppet accepts Variant as correct type
Title: Message Title Josh Cooper commented on PUP-11366 Re: Puppet accepts Variant as correct type Yeah that seems odd Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.424258.1637241847000.10525.1637251440034%40Atlassian.JIRA.
Jira (PUP-11312) Puppet creates excessive numbers of Pathname instances
Title: Message Title Josh Cooper commented on PUP-11312 Re: Puppet creates excessive numbers of Pathname instances Merged to main in https://github.com/puppetlabs/puppet/commit/5a86a5f79563abbada2b29e01bfed3b05e69db6e Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.418030.1633106573000.10523.1637251200123%40Atlassian.JIRA.
Jira (PUP-11312) Puppet creates excessive numbers of Pathname instances
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11312 Puppet creates excessive numbers of Pathname instances Change By: Josh Cooper Fix Version/s: PUP 7.13.0 Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.418030.1633106573000.10521.1637251140046%40Atlassian.JIRA.
Jira (PUP-11312) Puppet creates excessive numbers of Pathname instances
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11312 Puppet creates excessive numbers of Pathname instances Change By: Josh Cooper Release Notes: Bug Fix Release Notes Summary: Reduces the number of Pathname allocations when parsing puppet manifests. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.418030.1633106573000.10522.1637251140109%40Atlassian.JIRA.
Jira (FACT-3099) Caching UTF8 values results in "\\xCC" from ASCII-8BIT to UTF-8
Title: Message Title Steve Traylen commented on FACT-3099 Re: Caching UTF8 values results in "\\xCC" from ASCII-8BIT to UTF-8 Should have added that with facter 3.14.15 the cache is created correctly as UTF-8. ``` file /opt/puppetlabs/facter/cache/cached_facts/EC2 /opt/puppetlabs/facter/cache/cached_facts/EC2: UTF-8 Unicode text, with very long lines ``` and the returned value from cache is UTF-8. Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.424265.1637249217000.10512.1637249940059%40Atlassian.JIRA.
Jira (FACT-3099) Caching UTF8 values results in "\\xCC" from ASCII-8BIT to UTF-8
Title: Message Title
Steve Traylen updated an issue
Facter / FACT-3099
Caching UTF8 values results in "\\xCC" from ASCII-8BIT to UTF-8
Change By:
Steve Traylen
This is with the ec2_userdata fact but I expect true for any fact where the value is UTF-8 and the fact is cached.Userdata is utf-8{noformat}curl --silent http://169.254.169.254/openstack/latest/user_data | grep --color='auto' -P "[^[:ascii:]]" - [ vdb, /build1, "xfs", "nofail̦", "0", "0" ]{noformat}When this is cached via a configuration of {noformat}facts: { ttls: [ { "EC2": "7 days" } ]}{noformat}Then this results in a debug of{noformat}facter --debug ec2_userdata[2021-11-18 16:13:40.964313 ] DEBUG Facter::Util::Resolvers::Http - Request to http://169.254.169.254/latest/api/token failed with error code 404 [2021-11-18 16:13:42.090980 ] DEBUG Facter::CacheManager - EC2 facts cache file expired, missing or is corrupt [2021-11-18 16:13:42.091039 ] DEBUG Facter::CacheManager - caching values for EC2 facts Traceback (most recent call last): 15: from /opt/puppetlabs/puppet/bin/facter:10:in `' 14: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/cli/cli_launcher.rb:23:in `start' 13: from /opt/puppetlabs/puppet/lib/ruby/gems/2.7.0/gems/thor-1.1.0/lib/thor/base.rb:485:in `start' 12: from /opt/puppetlabs/puppet/lib/ruby/gems/2.7.0/gems/thor-1.1.0/lib/thor.rb:392:in `dispatch' 11: from /opt/puppetlabs/puppet/lib/ruby/gems/2.7.0/gems/thor-1.1.0/lib/thor/invocation.rb:127:in `invoke_command' 10: from /opt/puppetlabs/puppet/lib/ruby/gems/2.7.0/gems/thor-1.1.0/lib/thor/command.rb:27:in `run' 9: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/cli/cli.rb:124:in `query' 8: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter.rb:454:in `to_user_output' 7: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter.rb:521:in `resolve_facts_for_user_query' 6: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/fact_manager.rb:29:in `resolve_facts' 5: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/cache_manager.rb:38:in `cache_facts' 4: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/cache_manager.rb:166:in `write_cache' 3: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/cache_manager.rb:166:in `each' 2: from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/cache_manager.rb:175:in `block in write_cache' 1: from /opt/puppetlabs/puppet/lib/ruby/2.7.0/json/common.rb:286:in `pretty_generate'/opt/puppetlabs/puppet/lib/ruby/2.7.0/json/common.rb:286:in `generate': "\\xCC" from
Jira (FACT-3099) Caching UTF8 values results in "\\xCC" from ASCII-8BIT to UTF-8
Title: Message Title
Steve Traylen created an issue
Facter / FACT-3099
Caching UTF8 values results in "\\xCC" from ASCII-8BIT to UTF-8
Issue Type:
Bug
Affects Versions:
FACT 4.2.5
Assignee:
Unassigned
Components:
Facter 4
Created:
2021/11/18 7:26 AM
Priority:
Normal
Reporter:
Steve Traylen
This is with the ec2_userdata fact but I expect true for any fact where the value is UTF-8 and the fact is cached. Userdata is utf-8
curl --silent http://169.254.169.254/openstack/latest/user_data | grep --color='auto' -P "[^[:ascii:]]"
- [ vdb, /build1, "xfs", "nofail̦", "0", "0" ]
When this is cached via a configuration of
facts: {
Jira (PUP-11352) ToDataSerializer which loses track of the current path
Title: Message Title Dorin Pleava assigned an issue to Unassigned Puppet / PUP-11352 ToDataSerializer which loses track of the current path Change By: Dorin Pleava Assignee: Dorin Pleava Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.423439.1636986377000.10490.1637245800070%40Atlassian.JIRA.
Jira (FACT-3097) hypervisor.kvm = openstack is null for facter 4
Title: Message Title Steve Traylen commented on FACT-3097 Re: hypervisor.kvm = openstack is null for facter 4 debug log on facter 4 is [2021-11-18 14:53:07.653582 ] DEBUG Facter::Core::Execution::Posix - Executing command: virt-what [2021-11-18 14:53:07.702762 ] DEBUG Facter::Core::Execution::Posix - Executing command: lspci [2021-11-18 14:53:07.704784 ] DEBUG Facter::Core::Execution::Posix - Failed while executing 'lspci': No such file or directory - lspci [2021-11-18 14:53:07.705000 ] DEBUG Facts::Linux::Hypervisors::Vmware - No Vmware hypervisor detected. [2021-11-18 14:53:07.705066 ] DEBUG Facts::Linux::Hypervisors::Kvm - Detected product name: OpenStack Compute [2021-11-18 14:53:07.705122 ] DEBUG Facts::Linux::Hypervisors::Kvm - Detected hypervisor OpenStack Compute [2021-11-18 14:53:07.705333 ] DEBUG Facts::Linux::Hypervisors::Kvm - Detected bios vendor: SeaBIOS [2021-11-18 14:53:07.705375 ] DEBUG Facts::Linux::Hypervisors::Kvm - Detected manufacturer: RDO [2021-11-18 14:53:07.705527 ] DEBUG Facts::Linux::Hypervisors::Xen - No Xen hypervisor detected.
Jira (FACT-3098) partitions fact can break on non readable /broken filesystem
Title: Message Title
Steve Traylen commented on FACT-3098
Re: partitions fact can break on non readable /broken filesystem
Please close this. With a newer facter 4 all is good.
# facter --version && facter partitions
4.2.5
{
/dev/vda1 => {
filesystem => "xfs",
mount => "/",
size => "160.00 GiB",
size_bytes => 171797626368,
uuid => "632f04d6-0d40-44f5-ad88-8adede6434d4"
}
}
Jira (FACT-3098) partitions fact can break on non readable /broken filesystem
Title: Message Title Steve Traylen created an issue Facter / FACT-3098 partitions fact can break on non readable /broken filesystem Issue Type: Bug Affects Versions: FACT 4.0.44 Assignee: Unassigned Components: Facter 4 Created: 2021/11/18 5:28 AM Priority: Normal Reporter: Steve Traylen Actually with /opt/puppetlabs/puppet/bin/facter-ng --version 4.0.49 results in /opt/puppetlabs/puppet/bin/facter-ng partitions [2021-11-18
Jira (PUP-11366) Puppet accepts Variant as correct type
Title: Message Title
Tim Meusel created an issue
Puppet / PUP-11366
Puppet accepts Variant as correct type
Issue Type:
Bug
Affects Versions:
PUP 7.12.0
Assignee:
Unassigned
Created:
2021/11/18 5:24 AM
Priority:
Normal
Reporter:
Tim Meusel
Hi, the following code isn't a parser error:
class bar ( Variant $foo = '', ) {}
$ cat test.pp
class bar ( Variant $foo = '', ) {}
$ puppet --version
7.12.1
Jira (FACT-3097) hypervisor.kvm = openstack is null for facter 4
Title: Message Title
Steve Traylen created an issue
Facter / FACT-3097
hypervisor.kvm = openstack is null for facter 4
Issue Type:
Bug
Affects Versions:
FACT 4.2.5
Assignee:
Unassigned
Components:
Facter 4
Created:
2021/11/18 4:30 AM
Priority:
Normal
Reporter:
Steve Traylen
With facter 3.14.15
# facter hypervisors
{
kvm => {
openstack => true
}
}
Jira (PUP-11239) multiple facter implementations blogpost
Title: Message Title Gabriel Nagy assigned an issue to Gabriel Nagy Puppet / PUP-11239 multiple facter implementations blogpost Change By: Gabriel Nagy Assignee: Gabriel Nagy Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- 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.414802.1631086704000.10427.1637236320050%40Atlassian.JIRA.
