Jira (FACT-3188) Error on on Solaris non-global zone after upgrading to PE2021.7.2
Title: Message Title Josh Cooper updated an issue Facter / FACT-3188 Error on on Solaris non-global zone after upgrading to PE2021.7.2 Change By: Josh Cooper Sprint: Phoenix 2023-06-21 Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.481890.1677480699000.5307.1686092940032%40Atlassian.JIRA.
Jira (PUP-11869) Retry failed CA & CRL refreshes sooner than the next interval
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11869 Retry failed CA & CRL refreshes sooner than the next interval Change By: Josh Cooper Sprint: Phoenix 2023-06-21 Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.486486.1686076476000.5305.1686092820032%40Atlassian.JIRA.
Jira (PUP-11869) Retry failed CA & CRL refreshes sooner than the next interval
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11869 Retry failed CA & CRL refreshes sooner than the next interval Change By: Josh Cooper Fix Version/s: PUP 8.2.0 Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.486486.1686076476000.5306.1686092820094%40Atlassian.JIRA.
Jira (PUP-11871) crl refresh spec test overwrites the crl fixture
Title: Message Title Josh Cooper moved an issue Puppet / PUP-11871 crl refresh spec test overwrites the crl fixture Change By: Josh Cooper Key: PA PUP - 4944 11871 Project: Puppet Agent Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.481513.1676478593000.5296.1686090420042%40Atlassian.JIRA.
Jira (PUP-11849) CRL authorityKeyIdentifier is not printed in puppet8
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11849 CRL authorityKeyIdentifier is not printed in puppet8 Change By: Josh Cooper Story Points: 1 Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.485441.1683744464000.5281.1686088320028%40Atlassian.JIRA.
Jira (FACT-1902) Confirm Facter 4 validates that external/custom/executable facts output proper UTF-8
Title: Message Title Josh Cooper updated an issue Facter / FACT-1902 Confirm Facter 4 validates that external/custom/executable facts output proper UTF-8 Change By: Josh Cooper Fix Version/s: FACT 4.4.1 Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.290197.1546471789000.5280.1686088200030%40Atlassian.JIRA.
Jira (PUP-11869) Retry failed CA & CRL refreshes sooner than the next interval
Title: Message Title Josh Cooper updated an issue Puppet / PUP-11869 Retry failed CA & CRL refreshes sooner than the next interval Change By: Josh Cooper Story Points: 1 Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.486486.1686076476000.5279.1686088080037%40Atlassian.JIRA.
Jira (FACT-3206) Facter::Core::Execution.exec strips leading and trailing NULL bytes
Title: Message Title Kai Burghardt commented on FACT-3206 Re: Facter::Core::Execution.exec strips leading and trailing NULL bytes I see. Thank you for linking the other issue. This is grabbing data (a set of numbers) via a binary interface. The information is also available in human-readable form. It is just less of a hassle to take and process four 8-byte sequences (if they were available via Facter::Core::Execution.exec), instead of processing the human-readable output and separating textual labels/suffixes etc. from the actual numbers, and let’s not forget the round-trip conversion (binary number → string → back to a binary number). Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.486429.1685816622000.5254.1686084420075%40Atlassian.JIRA.
Jira (PUP-11867) Documentation: default is now strict=error
Title: Message Title Michael Hashizume assigned an issue to Michael Hashizume Puppet / PUP-11867 Documentation: default is now strict=error Change By: Michael Hashizume Assignee: Michael Hashizume Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.486430.1685854485000.5242.1686082740035%40Atlassian.JIRA.
Jira (PUP-11867) Documentation: default is now strict=error
Title: Message Title Michael Hashizume assigned an issue to Parker Leach Puppet / PUP-11867 Documentation: default is now strict=error Change By: Michael Hashizume Assignee: Michael Hashizume Parker Leach Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.486430.1685854485000.5243.1686082740082%40Atlassian.JIRA.
Jira (PUP-11868) New default strict=error breaks all deprecation warnings
Title: Message Title Michael Hashizume updated an issue Puppet / PUP-11868 New default strict=error breaks all deprecation warnings Change By: Michael Hashizume Epic Link: PA-5411 Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.486431.1685855267000.5241.1686082680041%40Atlassian.JIRA.
Jira (FACT-3207) Don't rescue NoMethodError
Title: Message Title Michael Hashizume updated an issue Facter / FACT-3207 Don't rescue NoMethodError Change By: Michael Hashizume Epic Link: PUP-11660 Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.486477.1686064209000.5238.1686082140090%40Atlassian.JIRA.
Jira (PUP-11869) Retry failed CA & CRL refreshes sooner than the next interval
Title: Message Title Michael Hashizume updated an issue Puppet / PUP-11869 Retry failed CA & CRL refreshes sooner than the next interval Change By: Michael Hashizume Epic Link: PE-34949 Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.486486.1686076476000.5236.1686082020026%40Atlassian.JIRA.
Jira (PUP-11870) Modify CRLs and CAs "last updated" attribute after successful update instead of before
Title: Message Title Tony Vu created an issue Puppet / PUP-11870 Modify CRLs and CAs "last updated" attribute after successful update instead of before Issue Type: Improvement Assignee: Unassigned Created: 2023/06/06 11:48 AM Priority: Normal Reporter: Tony Vu Currently, we update the CA and CRL `last_updated` time before we try to actually acquire them from the server; if a problem occurs and the actual crl/ca does not successfully update, puppet will not try again until we hit the interval for updates. We initially wrote it this way to prevent possible churn in errors if we somehow errored out prior to updating/touching the files on disk. Now that the code has been proven to be more stable after release, we could change the update time to happen after successfully updating the CA/CRL. This way, if puppet does error out during a run and not update the CA/CRL successfully, it will try again on the subsequent puppet run, and not wait for the respective refresh intervals. Add Comment
Jira (PUP-11869) Retry failed CA & CRL refreshes sooner than the next interval
Title: Message Title Josh Cooper created an issue Puppet / PUP-11869 Retry failed CA & CRL refreshes sooner than the next interval Issue Type: Improvement Assignee: Unassigned Created: 2023/06/06 11:34 AM Priority: Normal Reporter: Josh Cooper If a CRL refresh fails, then the agent won't try again until another crl_refresh_interval has elapsed. This was intentionally done during the initial implementation so that we didn't overload puppetserver in the event of failed refreshes. But now that the code has been proven and we have confirmation that conditional GET requests for the CRL are don't have a significant performance impact, we want to be more robust in the event of transient network issues. If the agent fails to refresh the CRL, then it should continue retrying the next time it runs, and continue retrying until it succeeds. This is also an issue for CA refresh (see PUP-10639) Add Comment
Jira (PDB-5593) Generating report data
Title: Message Title Joshua Partlow commented on PDB-5593 Re: Generating report data Pez had failed I think due to the openssl issue breaking cast for postgres. Rekicked as that is resolved now, to get this into PE main. Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.481308.1676309116000.5173.1686071760023%40Atlassian.JIRA.
Jira (FACT-3207) Don't rescue NoMethodError
Title: Message Title
Josh Cooper updated an issue
Facter / FACT-3207
Don't rescue NoMethodError
Change By:
Josh Cooper
The base resolver rescues NoMethodError, which hides bugs in resolvers. For example, if I disable the rescue, exposing it exposes a bug in the dmi resolver:{noformat}$ bundle exec facter --debug[2023-06-06 08:07:21.541262 ] DEBUG Facter::Resolvers::Linux::DmiBios - Resolving fact product_serial, but got undefined method `encode' for nil:NilClass .encode('UTF-8', invalid: :replace) ^^^ at /home/josh/work/facter/lib/facter/resolvers/dmi.rb:39:in `read_facts' {noformat}
Add Comment
This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8)
--
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 (FACT-3207) Don't rescue NoMethodError
Title: Message Title
Josh Cooper created an issue
Facter / FACT-3207
Don't rescue NoMethodError
Issue Type:
Bug
Assignee:
Unassigned
Created:
2023/06/06 8:10 AM
Priority:
Normal
Reporter:
Josh Cooper
The base resolver rescues NoMethodError, which hides bugs in resolvers. For example, if I disable the rescue, exposing a bug in the dmi resolver:
$ bundle exec facter --debug
[2023-06-06 08:07:21.541262 ] DEBUG Facter::Resolvers::Linux::DmiBios - Resolving fact product_serial, but got undefined method `encode' for nil:NilClass
.encode('UTF-8', invalid: :replace)
^^^ at /home/josh/work/facter/lib/facter/resolvers/dmi.rb:39:in `read_facts'
Jira (PUP-11846) The --no-preprocess_deferred option breaks deferring of Sensitive file content
Title: Message Title Marty Ewings commented on PUP-11846 Re: The --no-preprocess_deferred option breaks deferring of Sensitive file content we have seem to have it this in operational dashboards in Puppet 8 PE versions https://github.com/puppetlabs/puppet_operational_dashboards/actions/runs/5178402785/jobs/9329861774 as this is a supported module id like to see if we cant increase the priority of this ticket Add Comment This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8) -- 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.485142.1683044961000.5070.1686051840029%40Atlassian.JIRA.
