Jira (PUP-8305) Git testing should consume the runtime archive rather than install system packages
Title: Message Title Josh Cooper commented on PUP-8305 Re: Git testing should consume the runtime archive rather than install system packages Waiting on a beaker-puppet release containing https://github.com/puppetlabs/beaker-puppet/commit/d700c70860335bacf30f129203b0c1bdaf6b6e15 before we can resolve this. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-459) Reboot a target and wait for it to become available.
Title: Message Title Dylan Ratcliffe commented on BOLT-459 Re: Reboot a target and wait for it to become available. As the person who wrote all of this initially some key points from customers that drove the way I implemented it and I think should be maintained: Customers shouldn't have to handle the error that the reboot task generates. I guess you could just have a plan that does it, but the UX would however be much nicer if it is smart about the way it deliberately orphans a process so that PXP/Bolt can exit cleanly without cancelling the reboot (My ruby does this) Waiting for reboots needs configurable timeouts for the following: How long to wait for the machine to go down (If it doesn't go down we don't want to be waiting forever) How to long to then wait for the machine to come back up. Bear in mind for physical servers it's realistic that it might take an hour to reboot as all services need to be brought down cleanly Remember that it needs to wait for it to explicitly disconnect and reconnect. If the server takes 10min to shut down and all you are doing is waiting for it to be connected, it will return before the server has even shut down as it will be connected the first time you check Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (FACT-1873) Custom facts that aren't suitable should not override built-in facts
Title: Message Title Jean Bond updated an issue Facter / FACT-1873 Custom facts that aren't suitable should not override built-in facts Change By: Jean Bond Labels: custom-facts customer resolved-issue-added ruby Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1873) Custom facts that aren't suitable should not override built-in facts
Title: Message Title Jean Bond updated an issue Facter / FACT-1873 Custom facts that aren't suitable should not override built-in facts Change By: Jean Bond Release Notes Summary: Custom facts conflicting with built-in facts properly fall-back to the built-in value if no custom facts resolve while also ensuring that built-in facts have precedence over 0-weight custom facts. Facter now correctly gives precedence Release note draft:Prior to the highest weighted this release, Facter overrode built-in facts available from with custom fact values, even if the set of facts that can be If custom fact had no valid implementation. Now if custom facts return an empty result in conflict with built-in facts, they now properly fall back to Facter ignores that value and returns the built-in fact value if no custom facts resolve while also ensuring that . with built-in facts have precedence over 0 , but do not resolve, the built - weight custom facts in value is returned . 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
Jira (PUP-7331) "Unable to set ownership" error with logdest on agents
Title: Message Title Kris Bosland updated an issue Puppet / PUP-7331 "Unable to set ownership" error with logdest on agents Change By: Kris Bosland Release Notes Summary: Puppet will only set the user, group, and mode of log files if Puppet creates them. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1873) Custom facts that aren't suitable should not override built-in facts
Title: Message Title Jean Bond updated an issue Facter / FACT-1873 Custom facts that aren't suitable should not override built-in facts Change By: Jean Bond Release Notes Summary: Custom facts conflicting with built-in facts properly fall-back to the built-in value if no custom facts resolve while also ensuring that built-in facts have precedence over 0-weight custom facts. Facter now correctly gives precedence to the highest weighted facts available from the set of facts that can be If custom facts conflict with built-in facts, they now properly fall back to the built-in value if no custom facts resolve while also ensuring that built-in facts have precedence over 0-weight custom facts. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4176) Fix JDK 8 testing on Mac
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4176 Fix JDK 8 testing on Mac Issue Type: Bug Assignee: Austin Blatt Created: 2018/10/31 2:08 PM Priority: Normal Reporter: Austin Blatt AdoptOpenJDK 8 does not have the correct cacert file, we will retrieve this by installing a newer JDK (>= 10) and linking JDK 8's cacert to the newer cacert. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4175) Resolve hint error for overloaded method .toArray coming from org.flatland/ordered
Title: Message Title Austin Blatt created an issue PuppetDB / PDB-4175 Resolve hint error for overloaded method .toArray coming from org.flatland/ordered Issue Type: Bug Assignee: Unassigned Created: 2018/10/31 2:05 PM Priority: Normal Reporter: Austin Blatt With Java 11, the method .toArray has been overloaded which means that clojure is erroring because it cannot decide which method it needs to call. The offending line is (I believe) here. The Java change is ticketed here Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-8687) Should log JSON in newline-delimited format
Title: Message Title Jorie Tappa assigned an issue to Jorie Tappa Puppet / PUP-8687 Should log JSON in newline-delimited format Change By: Jorie Tappa Assignee: Jorie Tappa Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9266) Only show deprecation of CA setting when it is set in the config file
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-9266 Only show deprecation of CA setting when it is set in the config file Change By: Maggie Dreyer Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-905) [SPIKE] Investigate performance issues around concurrent connections over winrm
Title: Message Title Lucy Wyman commented on BOLT-905 Re: [SPIKE] Investigate performance issues around concurrent connections over winrm https://github.com/puma/puma/issues/847 This seemed interesting Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9266) Only show deprecation of CA setting when it is set in the config file
Title: Message Title Kenn Hussey commented on PUP-9266 Re: Only show deprecation of CA setting when it is set in the config file Maggie Dreyer please provide release notes for this issue if needed, thanks! /cc Jean Bond Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9268) 5.5.7 breaks custom function
Title: Message Title Kenn Hussey commented on PUP-9268 Re: 5.5.7 breaks custom function Henrik Lindberg please provide release notes for this issue if needed, thanks! /cc Jean Bond Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9267) The members property's 'retrieve' and 'should' methods should return arrays
Title: Message Title Enis Inan commented on PUP-9267 Re: The members property's 'retrieve' and 'should' methods should return arrays Kenn Hussey Done Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9267) The members property's 'retrieve' and 'should' methods should return arrays
Title: Message Title Enis Inan updated an issue Puppet / PUP-9267 The members property's 'retrieve' and 'should' methods should return arrays Change By: Enis Inan Release Notes Summary: The members property's been fixed to have the same API for retrieve and should as it did prior to 5.5.7's breaking changes while also reporting the right change notification. Specifically, providers can now return an array for the members property getter and accept an array for the members property setter (as before). Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1873) Custom facts that aren't suitable should not override built-in facts
Title: Message Title Enis Inan commented on FACT-1873 Re: Custom facts that aren't suitable should not override built-in facts Kenn Hussey Done Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1873) Custom facts that aren't suitable should not override built-in facts
Title: Message Title Enis Inan updated an issue Facter / FACT-1873 Custom facts that aren't suitable should not override built-in facts Change By: Enis Inan Release Notes Summary: Custom facts conflicting with built-in facts properly fall-back to the built-in value if no custom facts resolve while also ensuring that built-in facts have precedence over 0-weight custom facts. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-645) Support puppet device modules in a manifest block
Title: Message Title Lucy Wyman commented on BOLT-645 Re: Support puppet device modules in a manifest block Are there links to the PRs for this / work in progress? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-942) I want to add a node to a group in inventory and use the groups transport config
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-942 I want to add a node to a group in inventory and use the groups transport config Change By: Cas Donoghue Assignee: Cas Donoghue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-956) Add wait_until_available function to Bolt
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-956 Add wait_until_available function to Bolt Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-459) Reboot a target and wait for it to become available.
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-459 Reboot a target and wait for it to become available. Change By: Michael Smith A lot of deployment workflows require a reboot step where the target will be inaccessible. There should be an option in plans to support this. This ticket should specifically cover bundling the reboot module with Bolt. Subtasks cover the following implementation. h2. Solutionthere are 3 pieces to this solutionh3.reboot task puppetlabs-reboot should be bundled with bolt. We should add Add non-ruby implementations of it the reboot task to puppetlabs-reboot .h3. wait_until_available functionA new function should be added to boltlib that can wait for a target to become available. For pcp targets it should use the orchestrator inventory endpoint. h5. questionswhat should it be called?should it retry by default or should that require opt-in?see See https://github.com/puppetlabs/puppetlabs-reboot/pull/171 for prior art.h3. reboot planWe should add a plan to the reboot module that reboots targets catching errors and then waits for targets to become available again. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-459) Reboot a target and wait for it to become available.
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-459 Reboot a target and wait for it to become available. Change By: Michael Smith A lot of deployment workflows require a reboot step where the target will be inaccessible. There should be an option in plans to support this. This ticket should specifically cover bundling the reboot module with Bolt. Subtasks cover the following implementation. h2. Solutionthere are 3 pieces to this solution h3.reboot task Add non-ruby implementations of the reboot task to puppetlabs-reboot. h3. wait_until_available function A new function should be added to boltlib that can wait for a target to become available. For pcp targets it should use the orchestrator inventory endpoint. See [ https://github.com/puppetlabs/puppetlabs-reboot/pull/171 ] for prior art. h3. reboot plan We should add a plan to the reboot module that reboots targets catching errors and then waits for targets to become available again. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-958) Bundle reboot module with Bolt
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-958 Bundle reboot module with Bolt Issue Type: Sub-task Assignee: Unassigned Created: 2018/10/31 10:09 AM Priority: Normal Reporter: Michael Smith Should include updated tasks and reboot plan. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-957) Add reboot plan that uses task to reboot and waits for targets to be available
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-957 Add reboot plan that uses task to reboot and waits for targets to be available Issue Type: Sub-task Assignee: Unassigned Created: 2018/10/31 10:08 AM Priority: Normal Reporter: Michael Smith 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
Jira (BOLT-956) Add wait_until_available function to Bolt
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-956 Add wait_until_available function to Bolt Issue Type: Sub-task Assignee: Unassigned Created: 2018/10/31 10:08 AM Priority: Normal Reporter: Michael Smith 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
Jira (BOLT-955) Add non-ruby task implementations to the reboot module
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-955 Add non-ruby task implementations to the reboot module Issue Type: Sub-task Assignee: Unassigned Created: 2018/10/31 10:07 AM Priority: Normal Reporter: Michael Smith 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
Jira (PUP-9267) The members property's 'retrieve' and 'should' methods should return arrays
Title: Message Title Kenn Hussey commented on PUP-9267 Re: The members property's 'retrieve' and 'should' methods should return arrays Enis Inan please provide release notes for this issue if needed, thanks! /cc Jean Bond Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7331) "Unable to set ownership" error with logdest on agents
Title: Message Title Kenn Hussey commented on PUP-7331 Re: "Unable to set ownership" error with logdest on agents Kris Bosland please provide release notes for this issue if needed, thanks! /cc Jean Bond Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1873) Custom facts that aren't suitable should not override built-in facts
Title: Message Title Kenn Hussey commented on FACT-1873 Re: Custom facts that aren't suitable should not override built-in facts Enis Inan please provide release notes for this issue if needed, thanks! /cc Jean Bond Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8766) puppet device fails with undefined method `loaders' for nil:NilClass when env is not production
Title: Message Title Rick Sherman commented on PUP-8766 Re: puppet device fails with undefined method `loaders' for nil:NilClass when env is not production Depending on the depth of this work, it may be a good time to look at PUP-8732 (limiting pluginsync to only remote providers w/ puppet device) Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9115) custom facts don't get compiled
Title: Message Title Jacob Helwig commented on PUP-9115 Re: custom facts don't get compiled Uwe Bartels could you file a new issue in the "Documentation (DOCUMENT)" project about changing the "Configuring a Puppet/PuppetDB connection" section title? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1873) Custom facts that aren't suitable should not override built-in facts
Title: Message Title Branan Riley updated an issue Facter / FACT-1873 Custom facts that aren't suitable should not override built-in facts Change By: Branan Riley Fix Version/s: FACT 3.12.3 Fix Version/s: FACT 3.12.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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9198) Add support for RHEL 8 in package providers
Title: Message Title Branan Riley updated an issue Puppet / PUP-9198 Add support for RHEL 8 in package providers Change By: Branan Riley Fix Version/s: PUP 6.0.4 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7331) "Unable to set ownership" error with logdest on agents
Title: Message Title Branan Riley updated an issue Puppet / PUP-7331 "Unable to set ownership" error with logdest on agents Change By: Branan Riley Fix Version/s: PUP 6.0.4 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9217) Crontab gets erased after error during agent run
Title: Message Title Branan Riley updated an issue Puppet / PUP-9217 Crontab gets erased after error during agent run Change By: Branan Riley Fix Version/s: PUP 6.0.5 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1873) Custom facts that aren't suitable should not override built-in facts
Title: Message Title Branan Riley updated an issue Facter / FACT-1873 Custom facts that aren't suitable should not override built-in facts Change By: Branan Riley Fix Version/s: FACT 3.11.6 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1873) Custom facts that aren't suitable should not override built-in facts
Title: Message Title Branan Riley updated an issue Facter / FACT-1873 Custom facts that aren't suitable should not override built-in facts Change By: Branan Riley Fix Version/s: FACT 3.12.3 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9295) Notify resource exposing Sensitive data when message is raw Sensitive data
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9295 Notify resource exposing Sensitive data when message is raw Sensitive data Change By: Henrik Lindberg Priority: Normal 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 post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9295) Notify resource exposes Sensitive data when message is a Sensitive data
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9295 Notify resource exposes Sensitive data when message is a Sensitive data Change By: Henrik Lindberg Fix Version/s: PUP 5.5.9 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9295) Notify resource exposes Sensitive data when message is a Sensitive data
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9295 Notify resource exposes Sensitive data when message is a Sensitive data Change By: Henrik Lindberg Summary: Notify resource exposing exposes Sensitive data when message is raw a Sensitive data Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9295) Notify resource exposing Sensitive data when message is raw Sensitive data
Title: Message Title
Kevin Reeuwijk created an issue
Puppet / PUP-9295
Notify resource exposing Sensitive data when message is raw Sensitive data
Issue Type:
Bug
Assignee:
Unassigned
Components:
Types and Providers
Created:
2018/10/31 8:09 AM
Priority:
Normal
Reporter:
Kevin Reeuwijk
Puppet Version: 6.0.2 Puppet Server Version: 2019.0.0 OS Name/Version: Mac OS X, also confirmed on Linux by customer The Notify{} resource will leak Sensitive data if the message is a raw value of Sensitive() type. It looks like the Notify{} resource is mishandling the processing of the message parameter if the input is a raw Sensitive datatype (not encapsulated in double quotes). Desired Behavior: No Sensitive data should be output in clear text. Actual Behavior: For example, in the following code both message 1 and 2 leak sensitive data:
$secret = Sensitive('s3cret')
notify { 'Sensitive message 1':
message => $secret,
}
Jira (PUP-9294) Error when legacy function illegally defines methods
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-9294 Error when legacy function illegally defines methods Issue Type: Bug Assignee: Henrik Lindberg Created: 2018/10/31 7:55 AM Fix Versions: PUP 6.0.5 Priority: Normal Reporter: Henrik Lindberg When a 3.x function .rb file contains calls to `def` they will end up in a place where they are not supposed to be. It is illegal to have such definitions (they used to work in 3.x because they ended up being methods on Object (i.e. it polluted every class in Ruby which is obviously horrible and unwanted). From 6.0.0, legacy functions are loaded by a new loader and it should catch these illegal definitions and raise an error. (Currently the methods are defined, but in a place where the legacy function later cannot find and call them). Add Comment
Jira (PUP-9268) 5.5.7 breaks custom function
Title: Message Title Henrik Lindberg commented on PUP-9268 Re: 5.5.7 breaks custom function I just figured out what happens with methods defined inside 3.x functions (either inside the function's code block, or outside the call to newfunction - and it is totally HORRIBLE! The horrible thing is that those methods are added as methods on Ruby Object! Thus, all instances of everything will have those methods, and they step on each other (naturally), or worse, a 3.x function using this can end up blowing up the entire system by overwriting some fundamental Object method. So, it is not only Scope that is polluted - it is every instance of everything in Ruby !!! Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9268) 5.5.7 breaks custom function
Title: Message Title Richard Pearce commented on PUP-9268 Re: 5.5.7 breaks custom function Linter sounds reasonable. Would it also be worth considering that in addition to a new configuration flag to turn on/off the new behaviour? allow_legacy_scope_pollution = true|false This allows users to discover if they are impacted and give them an opportunity to address it before the upgrade to 6. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9268) 5.5.7 breaks custom function
Title: Message Title Alexander Fisher commented on PUP-9268 Re: 5.5.7 breaks custom function rubocop-puppet? FWIW, Puppet Inc. already maintains https://github.com/puppetlabs/rubocop-i18n Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
