Jira (PUP-11631) Purging SSH keys on a user resource fails when alias is used
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-11631 Purging SSH keys on a user resource fails when alias is used Change By: Jarret Lavallee Team: Phoenix Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.469398.1663952875000.36186.1663952940433%40Atlassian.JIRA.
Jira (PUP-11631) Purging SSH keys on a user resource fails when alias is used
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-11631 Purging SSH keys on a user resource fails when alias is used Change By: Jarret Lavallee Zendesk Ticket Count: 1 Zendesk Ticket IDs: 49722 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.469398.1663952875000.36187.1663952940481%40Atlassian.JIRA.
Jira (PUP-11631) Purging SSH keys on a user resource fails when alias is used
Title: Message Title Jarret Lavallee created an issue Puppet / PUP-11631 Purging SSH keys on a user resource fails when alias is used Issue Type: Improvement Affects Versions: PUP 6.28.0 Assignee: Unassigned Components: Types and Providers Created: 2022/09/23 10:07 AM Priority: Normal Reporter: Jarret Lavallee When using the purge_ssh_keys parameter on a user resource with an alias metaparameter, the catalog application will fail when purging unmanaged ssh keys. The following error is shown. Error: /Stage[main]/Main/Node[default]/User[username]: Failed to generate additional resources using 'generate': Parameter alias failed on Ssh_authorized_key[u...@example.com]: Munging failed for value ["useralias"] in class alias: Cannot add aliases without a catalog The metaparameters are passed into the resource used to purge ssh_authorized_keys when using the user resource. Since this happens in the type, and not during catalog compilation, the agent cannot alias the resources to be purged and fails catalog application. This is likely due to this https://github.com/puppetlabs/puppet/blob/6.28.0/lib/puppet/type/user.rb#L815
Jira (FACT-3141) Add mountpoints as an array to partitions fact
Title: Message Title Jarret Lavallee updated an issue Facter / FACT-3141 Add mountpoints as an array to partitions fact Change By: Jarret Lavallee Priority: Normal Minor Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.463294.1660922564000.20278.1661285940069%40Atlassian.JIRA.
Jira (PUP-11595) puppet lookup fails to resolve topscope variables from node classifier
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-11595 puppet lookup fails to resolve topscope variables from node classifier Change By: Jarret Lavallee Team: Phoenix Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.456630.165875490.2766.1658758680101%40Atlassian.JIRA.
Jira (PUP-11595) puppet lookup fails to resolve topscope variables from node classifier
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-11595 puppet lookup fails to resolve topscope variables from node classifier Change By: Jarret Lavallee Method Found: Needs Assessment Customer Feedback Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.456630.165875490.2765.1658758680051%40Atlassian.JIRA.
Jira (PUP-11595) puppet lookup fails to resolve topscope variables from node classifier
Title: Message Title
Jarret Lavallee commented on PUP-11595
Re: puppet lookup fails to resolve topscope variables from node classifier
I suspect that the environment will need to be passed into the find when Puppet.settings.set_by_cli?('environment'). The initial thought was that either trusted facts were missing from the nc query or that it was being forced to :plain, but I don't know this code well enough to say what the correct fix should be.
Add Comment
This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
--
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.456630.165875490.2764.1658758620036%40Atlassian.JIRA.
Jira (PUP-11522) Allow Puppet::HTTP::Client to connect to a server requiring client cert authentication and whose server cert is issued by a CA in the 'ssl_trust_store'
Title: Message Title Jarret Lavallee commented on PUP-11522 Re: Allow Puppet::HTTP::Client to connect to a server requiring client cert authentication and whose server cert is issued by a CA in the 'ssl_trust_store' joshThanks for the information and getting a PR up for this. The clarification on the difference of the system context filled some gaps for me. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.444827.1650996743000.24494.1651757700049%40Atlassian.JIRA.
Jira (FACT-1858) Provide an option to disable legacy facts so they are not sent to the master from the agent
Title: Message Title Jarret Lavallee updated an issue Facter / FACT-1858 Provide an option to disable legacy facts so they are not sent to the master from the agent Change By: Jarret Lavallee Team: Night's Watch Phoenix Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.253867.1527713421000.19578.1651154280129%40Atlassian.JIRA.
Jira (FACT-1858) Provide an option to disable legacy facts so they are not sent to the master from the agent
Title: Message Title Jarret Lavallee commented on FACT-1858 Re: Provide an option to disable legacy facts so they are not sent to the master from the agent I am reopening this ticket as there was no reason listed for this ticket to be closed and it should still be considered. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.253867.1527713421000.19577.1651154280062%40Atlassian.JIRA.
Jira (PUP-11522) Allow Puppet::HTTP::Client to connect to a server the puppet certificate for client authentication and 'ssl_trust_store'
Title: Message Title
Jarret Lavallee commented on PUP-11522
Re: Allow Puppet::HTTP::Client to connect to a server the puppet certificate for client authentication and 'ssl_trust_store'
The problem with {{post(url, options: { include_system_store } )}} is that it uses the system SSL context, which does include the CA certs in Puppet[:ssl_trust_store], but does not include the client certificates. https://github.com/puppetlabs/puppet/blob/main/lib/puppet/http/client.rb#L461-L470 As a part of this, the HTTP::Client will probably need to be updated to use create_context or load_context with the include_system_store and ssl_trust_store options that are added/modified. Is there a use case for using the system context and not the client context within HTTP::Client?
Add Comment
This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d)
--
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.444827.1650996743000.18688.1651077120034%40Atlassian.JIRA.
Jira (PUP-11522) Allow Puppet::HTTP::Client to connect to a server the puppet certificate for client authentication and 'ssl_trust_store'
Title: Message Title Jarret Lavallee created an issue Puppet / PUP-11522 Allow Puppet::HTTP::Client to connect to a server the puppet certificate for client authentication and 'ssl_trust_store' Issue Type: Bug Affects Versions: PUP 6.27.0, PUP 7.16.0 Assignee: Unassigned Created: 2022/04/26 11:12 AM Priority: Normal Reporter: Jarret Lavallee Puppet Version: 6.27.0 and 7.16.0 Puppet Server Version: N/A OS Name/Version: Any PUP-11471 enabled using the system CA store when using HTTP::Client, however, it did not enable users to use the 'ssl_trust_store' Puppet.conf option with client SSL authentication. After PUP-11471 a user can use 'create_context' or 'load_context' to use client based authentication with 'include_system_store: true' to load the trusted CA certificates from '/opt/puppetlabs/puppet/ssl/certs/' and '/opt/puppetlabs/puppet/ssl/cert.pem'. It does not enable a user to use 'create_context' or 'load_context' to use client based authentication with 'include_system_store: true' to load the trusted CA certificates from the 'ssl_trust_store' Puppet.conf option. The 'ssl_trust_store' Puppet.conf option removes the requirement of using 'c_rehash' or appending the CA bundle to '/opt/puppetlabs/puppet/ssl/cert.pem', which is overwritten on any agent upgrade. When 'include_system_store: true' is passed, 'create_context' should load 'Puppet[:ssl_trust_store]' the same way that 'create_system_context` does here: https://github.com/puppetlabs/puppet/blob/d894861565aa95bd6f4f1cb85fe44ab62cc37854/lib/puppet/ssl/ssl_provider.rb#L73-L89 Desired Behavior: 'create_context' should load the certificates from 'Puppet[:ssl_trust_store]' with 'include_system_store: true'. Actual Behavior: There is no way to load the certificates from 'Puppet[:ssl_trust_store]' with 'create_context'. Using the system context is not an option in this scenario as it does not use the client certificates for authentication. Examples: We would expect the following to use client certificates and load the
Jira (PUP-7409) Knockout prefix does not remove an entire key:value entry from a hash
Title: Message Title Jarret Lavallee commented on PUP-7409 Re: Knockout prefix does not remove an entire key:value entry from a hash It looks like the issue here is that the knockout prefix does not remove entries across different hiera layers. Here is an example. Here is an example of it working fine within the environment layer. # cat common.yaml --- mymodule::test: - a - b - c # cat nodes/pe-2019810-master.puppetdebug.vlan.yaml --- lookup_options: mymodule::test: merge: strategy: deep knockout_prefix: '--'
Jira (PUP-7409) Knockout prefix does not remove an entire key:value entry from a hash
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-7409 Knockout prefix does not remove an entire key:value entry from a hash Change By: Jarret Lavallee Zendesk Ticket Count: 1 Zendesk Ticket IDs: 47851 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.183329.1490869783000.250.1648138920045%40Atlassian.JIRA.
Jira (PUP-11452) puppetserver_gem doesn't install gems when they are loaded by facter
Title: Message Title Jarret Lavallee commented on PUP-11452 Re: puppetserver_gem doesn't install gems when they are loaded by facter Thanks for reviewing this josh. I opened up https://github.com/puppetlabs/puppet/pull/8872 with the changes. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.434448.1644247869000.12179.1644420420085%40Atlassian.JIRA.
Jira (PUP-11452) puppetserver_gem doesn't install gems when they are loaded by facter
Title: Message Title
Jarret Lavallee updated an issue
Puppet / PUP-11452
puppetserver_gem doesn't install gems when they are loaded by facter
Change By:
Jarret Lavallee
The {{puppetserver_gem}} package provider fails to list the correct gem list in puppetserver when there is a gem installed with `puppet_gem` and added by a `require` during the agent run or apply. In this scenario, the gem is listed as already installed by the {{puppetserver_gem}} provider when it is not installed in the puppetserver gem space.*Logs*The gem is only installed into the puppet gem space{code}# puppetserver gem list aws-sdk-s3*** LOCAL GEMS ***# /opt/puppetlabs/puppet/bin/gem list aws-sdk-s3*** LOCAL GEMS ***aws-sdk-s3 (1.112.0){code}Running the agent or apply shows the gem is prefetched in the {{puppetserver_gem}} provider{code}# puppet apply install.pp --debug |& grep aws-sdk-s3Debug: /Package[aws-sdk-s3]: Provider puppetserver_gem does not support features targetable; not managing attribute commandDebug: /Package[aws-sdk-s3]: Provider puppetserver_gem does not support features install_only; not managing attribute install_onlyDebug: /Package[aws-sdk-s3]: Provider puppetserver_gem does not support features virtual_packages; not managing attribute allow_virtualDebug: Puppet::Type::Package::ProviderPuppetserver_gem: Prefetched instance: aws-sdk-s3 via command: default{code}*Reproduction* # 1) On a 7.x Puppetserver - PE 2021.4.0 in this example # 2) Install the gem using the `puppet_gem` provider: {{puppet resource package aws-sdk-s3 ensure=installed provider=puppet_gem}} # 3) Add the following fact into the environment and ensure it is downloaded with {{puppet plugin download}}{code}Facter.add(:testing) do setcode dorequire 'aws-sdk-s3'Aws::S3::GEM_VERSION endend{code} # 4) Apply the following manifest to observe that the {{puppetserver_gem}} package is not installed {code} package{'aws-sdk-s3': ensure => installed, provider => puppetserver_gem}{code} *Potential Fix*This looks to be an issue due to the {{puppetserver_gem}} not forking the gem list command, so the [loaded gems are listed in these lines|https://github.com/puppetlabs/puppet/blob/main/lib/puppet/provider/package/puppetserver_gem.rb#L162-L170].If I replace those lines with one that uses the {{/opt/puppetlabs/puppet/bin/gem}} command, the issue no longer appears. For example:{code}output = execute_gem_command(Puppet::Type::Package::ProviderPuppet_gem.provider_command, ["list","--local"], gem_env)gem_list = output.lines.reject { |gem| gem =~ / \(default\: / }{code}There is a significant difference in the number of gems listed between the two outputs.{code}# The current implementation> sio_out.string.lines.reject { |gem| gem =~ / \(default\: / }.length=> 56# Shelling out to `gem`> output.lines.reject { |gem| gem =~ / \(default\: / }.length=> 25{code}This aligns with the `puppetserver gem list` and `gem list` commands.{code}# puppetserver gem list |grep -v default | wc -l25# /opt/puppetlabs/puppet/bin/gem list |grep -v default | wc
Jira (PUP-11452) puppetserver_gem doesn't install gems when they are loaded by facter
Title: Message Title
Jarret Lavallee updated an issue
Puppet / PUP-11452
puppetserver_gem doesn't install gems when they are loaded by facter
Change By:
Jarret Lavallee
The {{puppetserver_gem}} package provider fails to list the correct gem list in puppetserver when there is a gem installed with `puppet_gem` and added by a `require` during the agent run or apply. In this scenario, the gem is listed as already installed by the {{puppetserver_gem}} provider when it is not installed in the puppetserver gem space.*Logs*The gem is only installed into the puppet gem space{code}# puppetserver gem list aws-sdk-s3*** LOCAL GEMS ***# /opt/puppetlabs/puppet/bin/gem list aws-sdk-s3*** LOCAL GEMS ***aws-sdk-s3 (1.112.0){code}Running the agent or apply shows the gem is prefetched in the {{puppetserver_gem}} provider{code}# puppet apply install.pp --debug |& grep aws-sdk-s3Debug: /Package[aws-sdk-s3]: Provider puppetserver_gem does not support features targetable; not managing attribute commandDebug: /Package[aws-sdk-s3]: Provider puppetserver_gem does not support features install_only; not managing attribute install_onlyDebug: /Package[aws-sdk-s3]: Provider puppetserver_gem does not support features virtual_packages; not managing attribute allow_virtualDebug: Puppet::Type::Package::ProviderPuppetserver_gem: Prefetched instance: aws-sdk-s3 via command: default{code}*Reproduction* 1) On a 7.x Puppetserver - PE 2021.4.0 in this example 2) Install the gem using the `puppet_gem` provider: {{puppet resource package aws-sdk-s3 ensure=installed provider=puppet_gem}} 3) Add the following fact into the environment and ensure it is downloaded with {{puppet plugin download}} {code}Facter.add(:testing) do setcode dorequire 'aws-sdk-s3'Aws::S3::GEM_VERSION endend{code} 4) Apply the following manifest to observe that the {{puppetserver_gem}} package is not installed {code} package{'aws-sdk-s3': ensure => installed, provider => puppetserver_gem}{code} *Potential Fix*This looks to be an issue due to the {{puppetserver_gem}} not forking the gem list command, so the [loaded gems are listed in these lines|https://github.com/puppetlabs/puppet/blob/main/lib/puppet/provider/package/puppetserver_gem.rb#L162-L170].If I replace those lines with one that uses the {{/opt/puppetlabs/puppet/bin/gem}} command, the issue no longer appears. For example:{code}output = execute_gem_command(Puppet::Type::Package::ProviderPuppet_gem.provider_command, ["list","--local"], gem_env)gem_list = output.lines.reject { |gem| gem =~ / \(default\: / }{code}There is a significant difference in the number of gems listed between the two outputs.{code}# The current implementation> sio_out.string.lines.reject { |gem| gem =~ / \(default\: / }.length=> 56# Shelling out to `gem`> output.lines.reject { |gem| gem =~ / \(default\: / }.length=> 25{code}This aligns with the `puppetserver gem list` and `gem list` commands.{code}# puppetserver /opt/puppetlabs/puppet/bin/ gem list |grep -v default | wc - l25 l56 # /opt/puppetlabs/puppet/bin/
Jira (PUP-11452) puppetserver_gem doesn't install gems when they are loaded by facter
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-11452 puppetserver_gem doesn't install gems when they are loaded by facter Change By: Jarret Lavallee Zendesk Ticket Count: 1 Zendesk Ticket IDs: 47197 Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.434448.1644247869000.9811.1644248160182%40Atlassian.JIRA.
Jira (PUP-11452) puppetserver_gem doesn't install gems when they are loaded by facter
Title: Message Title Jarret Lavallee created an issue Puppet / PUP-11452 puppetserver_gem doesn't install gems when they are loaded by facter Issue Type: Bug Affects Versions: PUP 7.13.1 Assignee: Unassigned Components: Types and Providers Created: 2022/02/07 7:31 AM Priority: Normal Reporter: Jarret Lavallee The puppetserver_gem package provider fails to list the correct gem list in puppetserver when there is a gem installed with `puppet_gem` and added by a `require` during the agent run or apply. In this scenario, the gem is listed as already installed by the puppetserver_gem provider when it is not installed in the puppetserver gem space. Logs The gem is only installed into the puppet gem space # puppetserver gem list aws-sdk-s3 *** LOCAL GEMS ***
Jira (PUP-11032) Pluginsync Improvements
Title: Message Title Jarret Lavallee commented on PUP-11032 Re: Pluginsync Improvements Please consider SERVER-2298 for this epic. It's tough to diagnose a duplicate file name that causes irregular plugin sync behavior and catalog compilations. Add Comment This message was sent by Atlassian Jira (v8.20.2#820002-sha1:829506d) -- 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.397460.161963485.7117.1639669680050%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 (FACT-3094) DEBUG Facter::Resolvers::Aix::Mountpoints - Could not resolve mountpoints
Title: Message Title Jarret Lavallee updated an issue Facter / FACT-3094 DEBUG Facter::Resolvers::Aix::Mountpoints - Could not resolve mountpoints Change By: Jarret Lavallee Team: Night's Watch 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.423320.1636725775000.5917.1636732380033%40Atlassian.JIRA.
Jira (PDB-5364) Enabling log-queries in 7.7.1 causes JSON serialization failures
Title: Message Title
Jarret Lavallee created an issue
PuppetDB / PDB-5364
Enabling log-queries in 7.7.1 causes JSON serialization failures
Issue Type:
Bug
Affects Versions:
PDB 7.7.1
Assignee:
Unassigned
Components:
PuppetDB
Created:
2021/11/11 8:59 AM
Priority:
Normal
Reporter:
Jarret Lavallee
In PDB 7.7.1, if log-queries = true some PDB queries will fail with Cannot JSON encode object of class: class org.postgresql.jdbc.PgArray. This was working in 7.5.2. Disabling log-queries alleviates the issue. Reproduction
Install 7.7.1 or PE 2021.4.0
Set log-queries = true in the jetty.ini
Run the following query and observe the error
# curl -G http://localhost:8080/pdb/query/v4/facts --data-urlencode 'query=["extract", ["certname", "name", "value"], ["and", ["or", ["in", "certname", ["array", ["somenode", ["in", "name", ["array", ["aio_agent_version"]'
Cannot JSON encode object of class: class org.postgresql.jdbc.PgArray: {"somenode"}
Jira (PUP-9369) Parsedfile produces a undefined method each for nil:NilClass
Title: Message Title Jarret Lavallee commented on PUP-9369 Re: Parsedfile produces a undefined method each for nil:NilClass Thanks for implementing this Josh Cooper 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.289473.1545254652000.56916.1623772860048%40Atlassian.JIRA.
Jira (PUP-9563) Using max_queued_requests, agents return to originally scheduled run times
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-9563 Using max_queued_requests, agents return to originally scheduled run times Change By: Jarret Lavallee CS Priority: Reviewed Needs Priority 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.299686.1552405921000.178385.1617199620059%40Atlassian.JIRA.
Jira (PUP-10946) Recursive file resources generate dangerous numbers of resource events
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-10946 Recursive file resources generate dangerous numbers of resource events Change By: Jarret Lavallee CS Rank: 7580 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.389668.1614728039000.156160.1614788100300%40Atlassian.JIRA.
Jira (PUP-10946) Recursive file resources generate dangerous numbers of resource events
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-10946 Recursive file resources generate dangerous numbers of resource events Change By: Jarret Lavallee CS Priority: Needs Priority Major 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.389668.1614728039000.156093.1614785760083%40Atlassian.JIRA.
Jira (PUP-10946) Recursive file resources generate dangerous numbers of resource events
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-10946 Recursive file resources generate dangerous numbers of resource events Change By: Jarret Lavallee CS Priority: Needs Priority 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.389668.1614728039000.155745.1614736260040%40Atlassian.JIRA.
Jira (PUP-10922) The fqdn_rand() function should not assume case-consistency in the fqdn fact
Title: Message Title Jarret Lavallee commented on PUP-10922 Re: The fqdn_rand() function should not assume case-consistency in the fqdn fact Changing the case may cause changes across customers that have standardized uppercase hostnames. To avoid a large changeset, a `certname_rand` could be implemented as the certname should always be lowercase and should not change without a certificate regeneration. 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.387597.1613401978000.142423.1613486220035%40Atlassian.JIRA.
Jira (PDB-4389) Query for deactivated nodes
Title: Message Title
Jarret Lavallee commented on PDB-4389
Re: Query for deactivated nodes
Austin Blatt Would it be possible to get node_state documented into the query parameters of https://puppet.com/docs/puppetdb/6.3/api/query/v4/nodes.html#query-fields? I think that is auto generated from https://github.com/puppetlabs/puppetdb/blob/6.x/documentation/api/query/v4/nodes.markdown I suspect we can close this ticket out if customers can find it in the docs. It would be nice to have an example in https://puppet.com/docs/puppetdb/6.3/api/query/examples-pql.html. The example could help customers identify expired nodes.
nodes[certname] { node_state = "inactive" and expired is not null }
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-10844) Agent failures with server_list when one puppetserver fails
Title: Message Title Jarret Lavallee commented on PUP-10844 Re: Agent failures with server_list when one puppetserver fails Josh Cooper and Dorin Pleava Thank you for looking into this deeper and providing some great analysis. I think you are correct with the desired behavior and we should close this ticket. 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.381638.1608653215000.124613.1611677640119%40Atlassian.JIRA.
Jira (PUP-10857) User resource with forcelocal uses getent for groups
Title: Message Title Jarret Lavallee created an issue Puppet / PUP-10857 User resource with forcelocal uses getent for groups Issue Type: Improvement Affects Versions: PUP 6.19.1 Assignee: Unassigned Components: Types and Providers Created: 2021/01/19 7:34 AM Priority: Normal Reporter: Jarret Lavallee *Description* When using the useradd provider with the user resource with forcelocal => true, the groups are still pulled from gentent. This causes LDAP/NIS groups to be detected instead of just the local groups. *Desired Behavior* The forcelocal => true parameter should force all options to be local. With the parameter set, the user is looked up from /etc/passwd. The groups should be looked up locally as well. *Actual Behavior* The forcelocal => true results in the user being looked up locally, but the groups are looked up through getgrent *Additional Notes* It falls back to using https://github.com/puppetlabs/puppet/blob/main/lib/puppet/util/posix.rb#L14-L33 from https://github.com/puppetlabs/puppet/blob/main/lib/puppet/provider/nameservice.rb#L235-L237 as it is not implemented in https://github.com/puppetlabs/puppet/blob/main/lib/puppet/provider/user/useradd.rb
Jira (PUP-10844) Agent failures with server_list when one puppetserver fails
Title: Message Title Jarret Lavallee created an issue Puppet / PUP-10844 Agent failures with server_list when one puppetserver fails Issue Type: Bug Affects Versions: PUP 6.15.0 Assignee: Unassigned Created: 2020/12/22 8:06 AM Priority: Normal Reporter: Jarret Lavallee Puppet Version: 6.15.0+ Puppet Server Version: 6.x OS Name/Version: Any After the changes in 6.15.0 the server_list setting has different behavior. Previously when server_list was configured and the first puppetserver in the list failed, the agent would continue to run by connecting to the next puppetserver on the list. In 6.15.0, if the primary puppetserver fails while an agent is running, it results in a failed agent run. Desired Behavior: When the first puppetserver in the server_list goes offline, the agents should automatically try to connect to the second puppetserver in the server_list even if it is mid agent run. Actual Behavior: The agent run fails if the first puppetserver in the server_list goes offline while the agent is in the middle of a run. Some failures are below. Could not evaluate: Could not retrieve file metadata for puppet:///pe_packages/2019.8.1/windows-x86_64/puppet-agent-x64.msi: Request to https://primary.example.com:8140/puppet/v3/file_metadata/pe_packages/2019.8.1/windows-x86_64/puppet-agent-x64.msi?links=manage_type=sha256lite_permissions=ignore=windows_testing failed after 21.011 seconds: Failed to open TCP connection to primary.example.com:8140 (A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. - connect(2) for
Jira (PDB-4975) PDB will not start when sync is configured and garbage collection is disabled
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-4975 PDB will not start when sync is configured and garbage collection is disabled Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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.379880.1607038552000.94587.1607526660031%40Atlassian.JIRA.
Jira (PDB-4975) PDB will not start when sync is configured and garbage collection is disabled
Title: Message Title Jarret Lavallee created an issue PuppetDB / PDB-4975 PDB will not start when sync is configured and garbage collection is disabled Issue Type: Bug Affects Versions: PDB 6.13.1 Assignee: Unassigned Components: PuppetDB Created: 2020/12/03 3:35 PM Priority: Normal Reporter: Jarret Lavallee PuppetDB hangs indefinately when starting in 6.13.1 when sync is enabled and garbage collection is disabled. This looks to have been caused by https://tickets.puppetlabs.com/browse/PDB-4938. PuppetDB stops logging and stays in maintenance mode. The last logs output are as follows. 2020-12-03T13:03:26.752-06:00 INFO [c.z.h.HikariDataSource] PDBReadPool - Start completed. 2020-12-03T13:03:26.850-06:00 INFO [c.z.h.HikariDataSource] PDBWritePool - Starting... 2020-12-03T13:03:26.851-06:00 INFO [c.z.h.HikariDataSource] PDBWritePool - Start completed.
Jira (PUP-10778) User resource is not idempotent on AIX
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-10778 User resource is not idempotent on AIX Change By: Jarret Lavallee Release Notes: Bug Fix Release Notes Summary: The AIX user resource now allows for `password` lines with arbitrary whitespace in the `passwd` file. 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.377931.1605112736000.83977.1605884820026%40Atlassian.JIRA.
Jira (PUP-10778) User resource is not idempotent on AIX
Title: Message Title Jarret Lavallee commented on PUP-10778 Re: User resource is not idempotent on AIX https://github.com/puppetlabs/puppet/pull/8438 has been opened for this. 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.377931.1605112736000.77808.1605198360028%40Atlassian.JIRA.
Jira (PUP-10778) User resource is not idempotent on AIX
Title: Message Title
Jarret Lavallee created an issue
Puppet / PUP-10778
User resource is not idempotent on AIX
Issue Type:
Bug
Assignee:
Unassigned
Created:
2020/11/11 8:38 AM
Priority:
Normal
Reporter:
Jarret Lavallee
Puppet Version: 6.17 Puppet Server Version: 6.12.1 OS Name/Version: AIX 7.2 When using a user resource on AIX and setting the password, the password is updated every agent run. This happens when a user stanza contains a tab in the password line. This is because the regex in https://github.com/puppetlabs/puppet/blob/main/lib/puppet/provider/user/aix.rb#L181 does not account for tabs or multiple spaces. Reproduction: 1. In an AIX 7.2 node add a user resource.
user{'testing':
ensure => present,
password => 'test',
}
2. Edit the /etc/security/passwd file to add a tab to the password line.
Jira (PDB-4628) Fields in group_by queries aren't properly quoted/escaped
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-4628 Fields in group_by queries aren't properly quoted/escaped Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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.342668.1579529055000.73530.1604618460537%40Atlassian.JIRA.
Jira (PDB-4871) Investigate queries using two Hikari connections per request
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-4871 Investigate queries using two Hikari connections per request Change By: Jarret Lavallee CS Priority: Major 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.370205.1598390523000.73466.1604617920033%40Atlassian.JIRA.
Jira (PDB-4871) Investigate queries using two Hikari connections per request
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-4871 Investigate queries using two Hikari connections per request Change By: Jarret Lavallee CS Priority: Needs Priority 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.370205.1598390523000.73424.1604616720041%40Atlassian.JIRA.
Jira (PDB-4871) Investigate queries using two Hikari connections per request
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-4871 Investigate queries using two Hikari connections per request Change By: Jarret Lavallee CS Priority: Needs Priority 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.370205.1598390523000.72273.1604545260035%40Atlassian.JIRA.
Jira (PUP-8094) Lookup ignores environment from the classifier when using rule with trusted facts
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-8094 Lookup ignores environment from the classifier when using rule with trusted facts Change By: Jarret Lavallee CS Business Value: 5 - $$ CS Frequency: 3 - 25-50% of Customers CS Impact: Similar to PUP-7479 this issue makes it difficult to troubleshoot hiera issues using `puppet lookup`. Users expect that with the correct set of switches they can get lookup to perfectly emulate what the agent will do at runtime. CS Priority: Needs Priority Reviewed CS Severity: 3 - Serious Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Jira (PUP-8094) Lookup ignores environment from the classifier when using rule with trusted facts
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-8094 Lookup ignores environment from the classifier when using rule with trusted facts Change By: Jarret Lavallee CS Rank: 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.214573.1507141532000.25765.1598571900040%40Atlassian.JIRA.
Jira (PUP-8094) Lookup ignores environment from the classifier when using rule with trusted facts
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-8094 Lookup ignores environment from the classifier when using rule with trusted facts Change By: Jarret Lavallee CS Priority: Major Needs Priority 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.214573.1507141532000.25766.1598571900225%40Atlassian.JIRA.
Jira (PUP-10604) Include the puppetserver_gem package provider with core Puppet
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-10604 Include the puppetserver_gem package provider with core Puppet Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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.367865.1596151607000.8178.1596560340097%40Atlassian.JIRA.
Jira (PDB-4832) Partitioned reports table can result in slower PDB queries
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-4832 Partitioned reports table can result in slower PDB queries Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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.367556.1595978337000.5794.1596148980026%40Atlassian.JIRA.
Jira (PUP-5823) Puppet agent with splay on windows begets random interval between runs
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-5823 Puppet agent with splay on windows begets random interval between runs Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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.115341.1454671876000.5793.1596148920027%40Atlassian.JIRA.
Jira (PDB-4832) Partitioned reports table can result in slower PDB queries
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-4832 Partitioned reports table can result in slower PDB queries Change By: Jarret Lavallee CS Priority: Needs Priority 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.367556.1595978337000.3662.1595978460090%40Atlassian.JIRA.
Jira (PUP-10600) Unable to run puppet commands via AWS Session Manager on Windows Server 2019
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-10600 Unable to run puppet commands via AWS Session Manager on Windows Server 2019 Change By: Jarret Lavallee 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.367242.1595613997000.1374.1595614440028%40Atlassian.JIRA.
Jira (PUP-10581) Puppet lookup --compile issues in PE2019.8
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-10581 Puppet lookup --compile issues in PE2019.8 Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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.365394.1594311475000.104629.1594337640080%40Atlassian.JIRA.
Jira (FACT-2666) Puppet lookup CLI loads external Facts on the initiating node
Title: Message Title Jarret Lavallee updated an issue Facter / FACT-2666 Puppet lookup CLI loads external Facts on the initiating node Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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.363107.1592385941000.104604.1594336200035%40Atlassian.JIRA.
Jira (PUP-5823) Puppet agent with splay on windows begets random interval between runs
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-5823 Puppet agent with splay on windows begets random interval between runs Change By: Jarret Lavallee CS Priority: Needs Priority 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.115341.1454671876000.102827.1594223640243%40Atlassian.JIRA.
Jira (PUP-10532) Puppet fetches metadata for files with "ensure => absent"
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-10532 Puppet fetches metadata for files with "ensure => absent" Change By: Jarret Lavallee 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.359734.1590173269000.101136.1593733500047%40Atlassian.JIRA.
Jira (PUP-10532) Puppet fetches metadata for files with "ensure => absent"
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-10532 Puppet fetches metadata for files with "ensure => absent" Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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.359734.1590173269000.101137.1593733500098%40Atlassian.JIRA.
Jira (FACT-2666) Puppet lookup CLI loads external Facts on the initiating node
Title: Message Title Jarret Lavallee commented on FACT-2666 Re: Puppet lookup CLI loads external Facts on the initiating node Marty Ewings Is the desired outcome from this ticket to not pull the local facts from facter when the --node flag is passed into puppet lookup? 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.363107.1592385941000.100959.1593722520092%40Atlassian.JIRA.
Jira (BOLT-1545) ERROR Facter::ClassDiscoverer - There is no module named Ol
Title: Message Title Jarret Lavallee updated an issue Puppet Task Runner / BOLT-1545 ERROR Facter::ClassDiscoverer - There is no module named Ol Change By: Jarret Lavallee CS Priority: Reviewed 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.355530.1586897311000.68014.1590101100061%40Atlassian.JIRA.
Jira (PUP-10310) Compress Agent Reports
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-10310 Compress Agent Reports Change By: Jarret Lavallee CS Priority: Reviewed 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.347373.158256860.63187.1589499780031%40Atlassian.JIRA.
Jira (BOLT-1540) Exit code handling in Tasks
Title: Message Title Jarret Lavallee updated an issue Puppet Task Runner / BOLT-1540 Exit code handling in Tasks Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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.349116.1583793174000.57203.153160079%40Atlassian.JIRA.
Jira (BOLT-1541) Bolt docs improvement regarding example code
Title: Message Title Jarret Lavallee updated an issue Puppet Task Runner / BOLT-1541 Bolt docs improvement regarding example code Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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.349117.1583793508000.57202.153160036%40Atlassian.JIRA.
Jira (BOLT-1539) Local fact-cache functionality
Title: Message Title Jarret Lavallee updated an issue Puppet Task Runner / BOLT-1539 Local fact-cache functionality Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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.348950.1583609276000.57201.153100130%40Atlassian.JIRA.
Jira (PUP-10417) Custom Ruby functions that define a JSON module can ambiguate its scope and break Puppet
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-10417 Custom Ruby functions that define a JSON module can ambiguate its scope and break Puppet Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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.354928.1586391583000.35437.1586474640037%40Atlassian.JIRA.
Jira (HI-223) Hiera 'deeper' merge knockout only knocks out from closest array
Title: Message Title Jarret Lavallee updated an issue Hiera / HI-223 Hiera 'deeper' merge knockout only knocks out from closest array Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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.28166.1394139949000.35430.1586474160041%40Atlassian.JIRA.
Jira (PUP-10417) Custom Ruby functions that define a JSON module can ambiguate its scope and break Puppet
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-10417 Custom Ruby functions that define a JSON module can ambiguate its scope and break Puppet Change By: Jarret Lavallee CS Priority: Needs Priority 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.354928.1586391583000.34492.1586392620026%40Atlassian.JIRA.
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-4642 Puppet 2019.3 upgrade failure from 2019.2.2 Change By: Jarret Lavallee CS Rank: 1500 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.344931.1580780081000.17871.1581035940347%40Atlassian.JIRA.
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-4642 Puppet 2019.3 upgrade failure from 2019.2.2 Change By: Jarret Lavallee CS Priority: Needs Priority Major 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.344931.1580780081000.17861.1581035580771%40Atlassian.JIRA.
Jira (PUP-9602) puppet 6 apply fails if puppet types have been generated
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-9602 puppet 6 apply fails if puppet types have been generated Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.302978.1554294806000.17817.1581034261091%40Atlassian.JIRA.
Jira (PDB-4642) Puppet 2019.3 upgrade failure from 2019.2.2
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-4642 Puppet 2019.3 upgrade failure from 2019.2.2 Change By: Jarret Lavallee CS Priority: Needs Priority 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.344931.1580780081000.12984.1580835660311%40Atlassian.JIRA.
Jira (PDB-2423) Limit initial sync to catalogs, factsets, and deactivate node commands
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-2423 Limit initial sync to catalogs, factsets, and deactivate node commands Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.116056.1455149697000.57965.1575592500468%40Atlassian.JIRA.
Jira (FACT-2096) Windows system32 environment variable issue after installation of "RDS-RD-Server"
Title: Message Title Jarret Lavallee updated an issue Facter / FACT-2096 Windows system32 environment variable issue after installation of "RDS-RD-Server" Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.332946.1572508394000.42515.1574377200386%40Atlassian.JIRA.
Jira (PUP-10097) Protect against binary diffs
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-10097 Protect against binary diffs Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.328673.1570644934000.16052.1572565680239%40Atlassian.JIRA.
Jira (PUP-9978) dnf package provider should support modularity streams
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-9978 dnf package provider should support modularity streams Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.322208.1566835009000.139602.1570751400354%40Atlassian.JIRA.
Jira (PDB-4506) Don't hang on C-c during migration
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-4506 Don't hang on C-c during migration Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.324995.156873961.139606.1570751460262%40Atlassian.JIRA.
Jira (PDB-2487) Allow for a "resource-events-ttl" to reduce the number of days of events that are stored
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-2487 Allow for a "resource-events-ttl" to reduce the number of days of events that are stored Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.119255.1456852336000.139555.1570751281244%40Atlassian.JIRA.
Jira (PDB-4514) Document case-insensitive regular expressions
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-4514 Document case-insensitive regular expressions Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.326619.1569433817000.139462.1570749540473%40Atlassian.JIRA.
Jira (PUP-8094) Lookup ignores environment from the classifier when using rule with trusted facts
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-8094 Lookup ignores environment from the classifier when using rule with trusted facts Change By: Jarret Lavallee CS Rank: 2 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.214573.1507141532000.138829.1570740421679%40Atlassian.JIRA.
Jira (PDB-2487) Allow for a "resource-events-ttl" to reduce the number of days of events that are stored
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-2487 Allow for a "resource-events-ttl" to reduce the number of days of events that are stored Change By: Jarret Lavallee CS Priority: Normal Needs Priority 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.119255.1456852336000.98617.1568416261131%40Atlassian.JIRA.
Jira (PUP-9996) Stdlib : ensure_resources function does not throw an error if dependent resource type is missing
Title: Message Title Jarret Lavallee commented on PUP-9996 Re: Stdlib : ensure_resources function does not throw an error if dependent resource type is missing Patrick Grant Does the replication require the module to have been installed at some point and then removed? Are you able to reproduce it if you restart puppetserver after removing the module? Can you reproduce it with code manager/environment isolation configured? It seems like this could simply be due to Jruby caching the ruby types and would not be seen with environment isolation in place. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323404.1567607979000.96811.1568332380177%40Atlassian.JIRA.
Jira (PUP-9996) Stdlib : ensure_resources function does not throw an error if dependent resource type is missing
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-9996 Stdlib : ensure_resources function does not throw an error if dependent resource type is missing Change By: Jarret Lavallee Team: Coremunity Modules 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323404.1567607979000.96806.1568332140200%40Atlassian.JIRA.
Jira (PUP-10017) Collapse dependency failures into Class level failures
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-10017 Collapse dependency failures into Class level failures Change By: Jarret Lavallee Team: Night's Watch 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.324379.1568220393000.96782.1568331660628%40Atlassian.JIRA.
Jira (PUP-10017) Collapse dependency failures into Class level failures
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-10017 Collapse dependency failures into Class level failures Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.324379.1568220393000.96786.1568331660647%40Atlassian.JIRA.
Jira (PDB-4502) PuppetDB command size metrics are missing
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-4502 PuppetDB command size metrics are missing Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323996.156781861.96764.1568331000363%40Atlassian.JIRA.
Jira (PUP-9996) Stdlib : ensure_resources function does not throw an error if dependent resource type is missing
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-9996 Stdlib : ensure_resources function does not throw an error if dependent resource type is missing Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323404.1567607979000.96754.1568330820198%40Atlassian.JIRA.
Jira (PUP-10011) Tidy resource remove files even dependencies are failed
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-10011 Tidy resource remove files even dependencies are failed Change By: Jarret Lavallee CS Priority: Minor Reviewed 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323802.1567763238000.96751.1568330700338%40Atlassian.JIRA.
Jira (PUP-10011) Tidy resource remove files even dependencies are failed
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-10011 Tidy resource remove files even dependencies are failed Change By: Jarret Lavallee CS Priority: Needs Priority Minor 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323802.1567763238000.96749.1568330700329%40Atlassian.JIRA.
Jira (FACT-2004) cloud fact does not detect Azure with NetworkManager
Title: Message Title Jarret Lavallee updated an issue Facter / FACT-2004 cloud fact does not detect Azure with NetworkManager Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed Method Found: Needs Assessment Customer Feedback 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.322752.1567082147000.96736.1568330220634%40Atlassian.JIRA.
Jira (PUP-10017) Collapse dependency failures into Class level failures
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-10017 Collapse dependency failures into Class level failures Change By: Jarret Lavallee CS Priority: Needs Priority 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.324379.1568220393000.93936.1568224080190%40Atlassian.JIRA.
Jira (PDB-4478) posgresql crashed with glibc detected DELETE: double free or corruption (!prev) PE 2018.1.4.1 on PostgreSQL 9.6.10
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-4478 posgresql crashed with glibc detected DELETE: double free or corruption (!prev) PE 2018.1.4.1 on PostgreSQL 9.6.10 Change By: Jarret Lavallee Zendesk Ticket IDs: 35750 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.320500.156561791.60296.1566197040291%40Atlassian.JIRA.
Jira (PDB-4478) posgresql crashed with glibc detected DELETE: double free or corruption (!prev) PE 2018.1.4.1 on PostgreSQL 9.6.10
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-4478 posgresql crashed with glibc detected DELETE: double free or corruption (!prev) PE 2018.1.4.1 on PostgreSQL 9.6.10 Change By: Jarret Lavallee From zendesk: [https://puppetlabs.zendesk.com/agent/tickets/35750] Postgresql crashed but recovered with the titled error.The customer was looking to know the reason for the crash and if it could be avoided. Also, if there was any data that might need to be rectified.Some highlights from the logs[^pe-amer2pg1_crash.txt] 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.320500.156561791.60291.1566196980343%40Atlassian.JIRA.
Jira (FACT-1933) Include more chassis IDs in facter
Title: Message Title Jarret Lavallee updated an issue Facter / FACT-1933 Include more chassis IDs in facter Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314629.1561725724000.12857.1562875080438%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9754) Log resident configuration upon daemon launch
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-9754 Log resident configuration upon daemon launch Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312512.1560543853000.56181.1561073700256%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1767) AIX processor facts return "mismatched processor frequencies found; facter will only report one of them" on every puppet run
Title: Message Title Jarret Lavallee updated an issue Facter / FACT-1767 AIX processor facts return "mismatched processor frequencies found; facter will only report one of them" on every puppet run Change By: Jarret Lavallee CS Severity: 2 - Annoyance 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.213798.1506692618000.56135.1561072920969%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1767) AIX processor facts return "mismatched processor frequencies found; facter will only report one of them" on every puppet run
Title: Message Title Jarret Lavallee updated an issue Facter / FACT-1767 AIX processor facts return "mismatched processor frequencies found; facter will only report one of them" on every puppet run Change By: Jarret Lavallee CS Business Value: 1 - ? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.213798.1506692618000.56139.1561072921157%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1767) AIX processor facts return "mismatched processor frequencies found; facter will only report one of them" on every puppet run
Title: Message Title Jarret Lavallee updated an issue Facter / FACT-1767 AIX processor facts return "mismatched processor frequencies found; facter will only report one of them" on every puppet run Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.213798.1506692618000.56144.1561072921392%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1767) AIX processor facts return "mismatched processor frequencies found; facter will only report one of them" on every puppet run
Title: Message Title Jarret Lavallee updated an issue Facter / FACT-1767 AIX processor facts return "mismatched processor frequencies found; facter will only report one of them" on every puppet run Change By: Jarret Lavallee CS Frequency: 1 - 1-5% of Customers 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.213798.1506692618000.56130.1561072860460%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9754) Log resident configuration upon daemon launch
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-9754 Log resident configuration upon daemon launch Change By: Jarret Lavallee CS Priority: Needs Priority 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312512.1560543853000.48083.156050199%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4305) "null?" query of facts against the query/v4/nodes endpoint results in "Value does not match schema" errors
Title: Message Title Jarret Lavallee updated an issue PuppetDB / PDB-4305 "null?" query of facts against the query/v4/nodes endpoint results in "Value does not match schema" errors Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300026.1552508578000.46881.1560467280568%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1298) manage_membership for unix groups provider
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-1298 manage_membership for unix groups provider Change By: Jarret Lavallee Team: Platform OS Puppet Romania 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.22682.1388437397000.10248.1558050841094%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1298) manage_membership for unix groups provider
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-1298 manage_membership for unix groups provider Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.22682.1388437397000.10208.1558050480563%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9697) Solaris Crontabs -> puppet resource cron only returns root account
Title: Message Title Jarret Lavallee updated an issue Puppet / PUP-9697 Solaris Crontabs -> puppet resource cron only returns root account Change By: Jarret Lavallee CS Priority: Needs Priority Reviewed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308025.155742000.10170.1558049821284%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
