Jira (PUP-8650) Repository error message uri is missing part of the path
Title: Message Title Matthew commented on PUP-8650 Re: Repository error message uri is missing part of the path I can confirm this also effects 5.3.2 and 5.5.6. I upgraded my puppet enterprise trying to work around this issue. I also tried to mess with my Apache settings. This bug cost me at least 3 hours tonight. 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-9179) Add exists? method to Windows::Service
Title: Message Title Kenn Hussey commented on PUP-9179 Re: Add exists? method to Windows::Service Enis Inan please close this issue once the changes have been merged up to master and passed CI. 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-6822) Windows agents should be able to apply a 'stopped' service resource even if the service doesn't exist
Title: Message Title Kenn Hussey commented on PUP-6822 Re: Windows agents should be able to apply a 'stopped' service resource even if the service doesn't exist Enis Inan please close this issue once the changes have been merged up to master and passed CI. 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-9194) REGRESSION exec cwd is not respected for unless or onlyif commands in 6.0.1
Title: Message Title Kenn Hussey commented on PUP-9194 Re: REGRESSION exec cwd is not respected for unless or onlyif commands in 6.0.1 Enis Inan please close this issue once the changes have been merged up to master and passed CI. 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-9194) REGRESSION exec cwd is not respected for unless or onlyif commands in 6.0.1
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-9194 REGRESSION exec cwd is not respected for unless or onlyif commands in 6.0.1 Change By: Kenn Hussey Flagged: Impediment 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-4133) Test merge master
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4133 Test merge master Issue Type: Bug Assignee: Unassigned Created: 2018/10/04 5:55 PM Priority: Normal Reporter: gepetto-bot 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.
Jira (PUP-9207) puppet lookup --compile returns incorrect results when trusted facts define environment
Title: Message Title Thomas Kishel commented on PUP-9207 Re: puppet lookup --compile returns incorrect results when trusted facts define environment This does not involve a transition from one environment to another: repeated testing (including puppet agent runs and the above puppet lookups) returns the same results. Empirically, it appears that trusted facts are not in scope when using "puppet lookup --compile" ... causing the (environment) node group rule (based upon a trusted fact != a specific value, in the example: "pp_role != ppserver") ... to include the node instead of excluding it ... changing the environment of the node in the context of the lookup ... resulting in the lookup reading from different environment than would be read during a puppet agent run. 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-877) Provide cross platform bolt install script
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-877 Provide cross platform bolt install script Change By: Alex Dreyer Sprint: Bolt Ready for Grooming 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-901) Improve Plan Logging with apply
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-901
Improve Plan Logging with apply
Change By:
Alex Dreyer
ProblemI want useful human readable output showing the metrics from each targets apply during a plan.SolutionWhen the format is human and plan_logging is active every run action should trigger the same output it would if the action was run on it's own from the CLI.* {{plan_logging}}: is only part of the human format and plan logging messages are printed on stdout not stderr* info level logging is primarily about logging full input/output of each action from a plan. * notice level logging is only used initially with the {{notice}} function from plans.* {{plan_logging}} messages should be indented to make it easier to scan* Individual node results should be output as part of plan logging when there are fewer than {{n}} targets for an action.Questions:* How can we show human readable verbose apply output( ie event logs from an apply report )?* Do we need to expose access to print human readable messages to stdout as a plan function ? Is or is {{ notice }} enough? (defer and build if needed) * Do we need to show progress of actions when the format is json?(not initially defer and build later if needed)* Do we need an option for the bolt user (rather then the author) to suppress individual node results from the human format?(defer and build later if needed)* How will this work with BoltSpec? (defer and build later if needed. pass a noop outputter to executor for now)
Add Comment
Jira (BOLT-877) Provide cross platform bolt install script
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-877 Provide cross platform bolt install script Change By: Alex Dreyer Sprint: Bolt Kanban 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-9209) Don't support the home property on Windows users
Title: Message Title Enis Inan updated an issue Puppet / PUP-9209 Don't support the home property on Windows users Change By: Enis Inan The current Windows user provider supports the home property of the User resource, which delegates to getting/setting the HomeDirectory property of the IADS User with WinNT as the provider ([here's|https://github.com/puppetlabs/puppet/blob/6.0.0/lib/puppet/provider/user/windows_adsi.rb#L111-L117] the code). The home property does not make sense on Windows, because the user's profile (which is the home 's directory) will always be in C:\Users -- we already create/delete the user profile via. the managehome property. Furthermore, the HomeDirectory property does not seem to do anything useful from Puppet's perspective.Thus, we should stop supporting the 'home' property for our Windows user provider. There are several paths we can take here:* Fail fast in terms of implementing the property validation code (i.e. the validate block)* Associate a feature with the home property of (e.g. sets_home_directory) and apply that feature to the current User resource providers that support the home property . and more. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9209) Don't support the home property on Windows users
Title: Message Title Enis Inan updated an issue Puppet / PUP-9209 Don't support the home property on Windows users Change By: Enis Inan The current Windows user provider supports the home property of the User resource, which delegates to getting/setting the HomeDirectory property of the IADS User with WinNT as the provider ([here's|https://github.com/puppetlabs/puppet/blob/6.0.0/lib/puppet/provider/user/windows_adsi.rb#L111-L117] the code). The home property does not make sense on Windows, because the user's profile (which is the home's directory) will always be in C:\Users -- we already create/delete the user profile via. the managehome property. Furthermore, the HomeDirectory property does not seem to do anything useful in terms of implementing the home property of the User resource. 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
Jira (PUP-9209) Don't support the home property on Windows users
Title: Message Title Enis Inan updated an issue Puppet / PUP-9209 Don't support the home property on Windows users Change By: Enis Inan Fix Version/s: PUP 7.0.0 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-9209) Don't support the home property on Windows users
Title: Message Title Enis Inan created an issue Puppet / PUP-9209 Don't support the home property on Windows users Issue Type: Improvement Assignee: Unassigned Created: 2018/10/04 2:49 PM Priority: Normal Reporter: Enis Inan The current Windows user provider supports the home property of the User resource, which delegates to getting/setting the HomeDirectory property of the IADS User with WinNT as the provider (here's the code). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-901) Improve Plan Logging with apply
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-901 Improve Plan Logging with apply Change By: Alex Dreyer Summary: Print a summary metrics for each target of an aply at info level Improve Plan Logging with apply 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-901) Print a summary metrics for each target of an aply at info level
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-901
Print a summary metrics for each target of an aply at info level
Change By:
Alex Dreyer
ProblemI want useful human readable output during a plan.SolutionWhen the format is human and plan_logging is active every run action should trigger the same output it would if the action was run on it's own from the CLI.* {{plan_logging}}: is only part of the human format and plan logging messages are printed on stdout not stderr* info level logging is primarily about logging full input/output of each action from a plan. * notice level logging is only used initially with the {{notice}} function from plans.* {{plan_logging}} messages should be indented to make it easier to scan * Individual node results should be output as part of plan logging when there are fewer than {{n}} targets for an action. Questions:* How can we show human readable verbose apply output(event logs)?* Do we need to expose access to print human readable messages to stdout as a plan function? Is notice enough?* Do we need to show progress of actions when the format is json?
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-904) Future work for PE Bolt Server
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-904 Future work for PE Bolt Server Change By: Lucy Wyman Epic Colour: ghx-label- 1 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 (BOLT-904) Future work for PE Bolt Server
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-904 Future work for PE Bolt Server Change By: Lucy Wyman Epic Colour: ghx-label- 2 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 (BOLT-904) Future work for PE Bolt Server
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-904 Future work for PE Bolt Server Change By: Lucy Wyman Epic Colour: ghx-label- 4 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 (BOLT-904) Future work for PE Bolt Server
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-904 Future work for PE Bolt Server Issue Type: Epic Assignee: Unassigned Created: 2018/10/04 2:39 PM Priority: Normal Reporter: Lucy Wyman 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-884) Clean up bolt known issues
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-884 Clean up bolt known issues Change By: Alex Dreyer Fix Version/s: BOLT Next 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-875) Review and remove deprecated functionality from bolt
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-875 Review and remove deprecated functionality from bolt Change By: Alex Dreyer Release Notes Summary: This removes deprecated functionality from bolt- local validation of parameters when running tasks over pcp nodes is no longer supported- the file_upload plan function has been removed. 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-903) Add configurable log rotation to bolt-server
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-903 Add configurable log rotation to bolt-server Issue Type: Task Assignee: Unassigned Created: 2018/10/04 2:36 PM Priority: Normal Reporter: Lucy Wyman Bolt-server should rotate it's logs, and the rotation cadence should be configurable Questions: 1. What's a reasonable default? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-159) Bolt commands on Powershell require triple quoting
Title: Message Title Michael Smith commented on BOLT-159 Re: Bolt commands on Powershell require triple quoting https://github.com/chef/chef/issues/3026#issuecomment-85229208 is not encouraging. 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-901) Print a summary metrics for each target of an aply at info level
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-901
Print a summary metrics for each target of an aply at info level
Change By:
Alex Dreyer
ProblemI want useful human readable output during a plan.SolutionWhen the format is human and plan_logging is active every run action should trigger the same output it would if the action was run on it's own from the CLI.* {{plan_logging}}: is only part of the human format and plan logging messages are printed on stdout not stderr* info level logging is primarily about logging full input/output of each action from a plan. * notice level logging is only used initially with the {{notice}} function from plans. * {{plan_logging}} messages should be indented to make it easier to scan Questions:* How can we show human readable verbose apply output(event logs)?* Do we need to expose access to print human readable messages to stdout as a plan function? Is notice enough?* Do we need to show progress of actions when the format is json?
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-901) Print a summary metrics for each target of an aply at info level
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-901
Print a summary metrics for each target of an aply at info level
Change By:
Alex Dreyer
ProblemI want useful human readable output during a plan.SolutionWhen the format is human and plan_logging is active every run action should trigger the same output it would if the action was run on it's own from the CLI. Requirements: * Nothing new {{plan_logging}}: is only part of the human format and plan logging messages are printed to on stdout when format is json not stderr * No duplicate notice log messages and info level logging is primarily about logging full input/ output when format of each action from a plan. * notice level logging is human only used initially with the {{notice}} function from plans. Questions:* Will plan users want How can we show human readable verbose apply output(event logs)?* Do we need to limit how much is logged when running expose access to print human readable messages to stdout as a plan on many nodes function ? We'll Is notice enough? * What log messages do Do we need on st to show progress of actions when the format is json?
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-884) Clean up bolt known issues
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-884 Clean up bolt known issues 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-884) Clean up bolt known issues
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-884 Clean up bolt known issues 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-875) Review and remove deprecated functionality from bolt
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet Task Runner / BOLT-875 Review and remove deprecated functionality from 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 (FACT-1888) 'os.release' values not correct for VZ7
Title: Message Title Kenn Hussey commented on FACT-1888 Re: 'os.release' values not correct for VZ7 Could this be a duplicate of FACT-1886? 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-9202) Prepare release announcement (Puppet Platform 6.0.2)
Title: Message Title Kenn Hussey commented on PUP-9202 Re: Prepare release announcement (Puppet Platform 6.0.2) Thanks Eric Sorenson! 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-9202) Prepare release announcement (Puppet Platform 6.0.2)
Title: Message Title Eric Sorenson commented on PUP-9202 Re: Prepare release announcement (Puppet Platform 6.0.2) I'd like to see us default to publicly visible communication for these wherever possible, so both internal and external should say "puppet-dev Google group". 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-9207) puppet lookup --compile returns incorrect results when trusted facts define environment
Title: Message Title Henrik Lindberg commented on PUP-9207 Re: puppet lookup --compile returns incorrect results when trusted facts define environment At present lookup will use a node's current environment as the intent when this was implemented was to answer questions why a value ended up in the catalog. That in contrast to the value it will have when compiling a new catalog. There is another ticket about changing this to always use the "what-will-be-environment" value instead of "what-you-got-last-environment". Is that what is at play here? Or something else? (Can be determined if the problematic behaviour is observed when node is in one env now and will be in another when it makes its nest request for a catalog). 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-9202) Prepare release announcement (Puppet Platform 6.0.2)
Title: Message Title Kenn Hussey commented on PUP-9202 Re: Prepare release announcement (Puppet Platform 6.0.2) Thanks, Michelle Fredette. Barring any last minute copy edits (which I'll leave to you) I think these are ready to go. 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-9202) Prepare release announcement (Puppet Platform 6.0.2)
Title: Message Title Kenn Hussey assigned an issue to Michelle Fredette Puppet / PUP-9202 Prepare release announcement (Puppet Platform 6.0.2) Change By: Kenn Hussey Assignee: Kenn Hussey Michelle Fredette 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-875) Review and remove deprecated functionality from bolt
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-875 Review and remove deprecated functionality from bolt Change By: Michael Smith Fix Version/s: BOLT Next 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-886) C:\Program Files\Puppet Labs\Bolt\bin\bolt.bat is non-functional
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-886 C:\Program Files\Puppet Labs\Bolt\bin\bolt.bat is non-functional Change By: Michael Smith Fix Version/s: BOLT Next 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-875) Review and remove deprecated functionality from bolt
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-875 Review and remove deprecated functionality from bolt Change By: Michael Smith Release Notes: Deprecation 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-886) C:\Program Files\Puppet Labs\Bolt\bin\bolt.bat is non-functional
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-886 C:\Program Files\Puppet Labs\Bolt\bin\bolt.bat is non-functional Change By: Michael Smith 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-875) Review and remove deprecated functionality from bolt
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-875 Review and remove deprecated functionality from bolt Change By: Michael Smith Labels: docs 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-9202) Prepare release announcement (Puppet Platform 6.0.2)
Title: Message Title Kenn Hussey assigned an issue to Kenn Hussey Puppet / PUP-9202 Prepare release announcement (Puppet Platform 6.0.2) Change By: Kenn Hussey Assignee: Michelle Fredette Kenn Hussey 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-4132) Test merge master
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4132 Test merge master Issue Type: Bug Assignee: Unassigned Created: 2018/10/04 11:48 AM Priority: Normal Reporter: gepetto-bot 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.
Jira (BOLT-902) Bolt should be usable from cmd.exe after package install
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-902 Bolt should be usable from cmd.exe after package install Issue Type: Improvement Assignee: Unassigned Created: 2018/10/04 11:39 AM Priority: Normal Reporter: Michael Smith The Getting Started With Puppet training tells students (on Windows) to install the MSI and then they should be able to just run Bolt. So there is an expectation that it 'just works' after installation. It does on Linux, and it does in PowerShell as well since the additional PowerShell module gets auto-imported. If adding Bolt to the path is not done automatically, the MSI installer should finish with a message about this. E.g.: Bolt has now been installed and will work immediately in PowerShell, just type: bolt If you want to use Bolt in the standard Command Prompt as well, it's best to add to your PATH variable in Advanced System Settings. Add Comment
Jira (BOLT-875) Review and remove deprecated functionality from bolt
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet Task Runner / BOLT-875 Review and remove deprecated functionality from 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-886) C:\Program Files\Puppet Labs\Bolt\bin\bolt.bat is non-functional
Title: Message Title Michael Smith commented on BOLT-886 Re: C:\Program Files\Puppet Labs\Bolt\bin\bolt.bat is non-functional I'm going to make that a separate ticket. 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-901) Print a summary metrics for each target of an aply at info level
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-901 Print a summary metrics for each target of an aply at info level Change By: Alex Dreyer ProblemI want useful human readable output during a plan.SolutionWhen the format is human and plan_logging is active every run action should trigger the same output it would if the action was run on it's own from the CLI.Requirements:* Nothing new is printed to stdout when format is json* No duplicate notice log messages and output when format is humanQuestions:* Will plan users want to limit how much is logged when running a plan on many nodes? We'll* What log messages do we need on st 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 (PUP-9197) Windows file system ACL reported change is not always correct
Title: Message Title
Erick Banks updated an issue
Puppet / PUP-9197
Windows file system ACL reported change is not always correct
Change By:
Erick Banks
As per [~ethan]'s comment here: [https://github.com/puppetlabs/puppet/pull/7088#issuecomment-426700386]The change we're reporting is not correct, but the behavior/state of the system is. Were stating {{An attempt to set mode 488}} when in fact we're trying to set a mode to 750. [~glenn.sarti]'s comments here: [https://github.com/puppetlabs/puppet/pull/7088#issuecomment-426842268]
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
Jira (BOLT-901) Print a summary metrics for each target of an aply at info level
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-901 Print a summary metrics for each target of an aply at info level Change By: Alex Dreyer Issue Type: Task New Feature 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-4131) Merge 6.0.x -> master
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4131 Merge 6.0.x -> master Issue Type: Bug Assignee: Unassigned Created: 2018/10/04 11:21 AM Priority: Normal Reporter: gepetto-bot 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 (PUP-9208) Requesting new feature for notify messages
Title: Message Title Patrick Mayes commented on PUP-9208 Re: Requesting new feature for notify messages That works as long as we can have a custom message, in one case we only want to provide a custom status message when it fails stating 'This failed as expected' for testing, other times we want to post something saying for example 'This node facts['fqdn'] doesn't have any classes attached, email x...@abc.com' 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-866) Better summary message for apply statement
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-866
Better summary message for apply statement
Change By:
Alex Dreyer
Release Notes Summary:
When a ResultSet is returned from a plan the human outtput format no longer prints the JSON object it formats it in a similar fashion to how it outputs {{bolt task run}} or {{bolt command run}}.There is now an _output injected into ApplyResults and a {{.message}} method on them.
Fix Version/s:
BOLT 0.25.0
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-866) Better summary message for apply statement
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-866 Better summary message for apply statement Change By: Michael Smith Release Notes: New Feature 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-866) Better summary message for apply statement
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-866 Better summary message for apply statement Change By: Michael Smith Fix Version/s: BOLT Next 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-9208) Requesting new feature for notify messages
Title: Message Title Michael Smith commented on PUP-9208 Re: Requesting new feature for notify messages That sounds like something akin to a resource that always fails, rather than a function. 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-866) Better summary message for apply statement
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-866
Better summary message for apply statement
Change By:
Alex Dreyer
The summary message for the apply statement should include information about the events in the catalog. This should be stored as the '_output' of the ApplyResult and be logged by the executor in place of "finshed " message human outputtter when the ResultSet is returned from a plan. Something like{noformat}Finished: "0 failed 0 changed 16 unchanged 0 skipped 0 noop"{noformat}
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-901) Print a summary metrics for each target of an aply at info level
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-901 Print a summary metrics for each target of an aply at info level Issue Type: Task Assignee: Unassigned Created: 2018/10/04 10:56 AM Priority: Normal Reporter: Alex Dreyer 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 (BOLT-900) Deprecated functions in stdlib result in Evaluation Error
Title: Message Title Henrik Lindberg commented on BOLT-900 Re: Deprecated functions in stdlib result in Evaluation Error I suppose that makes sense as you need to be using code that already exists. I turned on the more strict modes by default because I figured people would be writing new code. It is fine to make them configurable since there is a clear purpose for 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 (PUP-9207) puppet lookup --compile returns incorrect results when trusted facts define environment
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-9207 puppet lookup --compile returns incorrect results when trusted facts define environment Change By: Charlie Sharpsteen 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9208) Requesting new feature for notify messages
Title: Message Title Patrick Mayes commented on PUP-9208 Re: Requesting new feature for notify messages Because warning doesn't show up as a failure in the puppet reports that get displayed by the puppet console. 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-9208) Requesting new feature for notify messages
Title: Message Title Henrik Lindberg commented on PUP-9208 Re: Requesting new feature for notify messages How about issuing a warning instead? 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-9202) Prepare release announcement (Puppet Platform 6.0.2)
Title: Message Title Michelle Fredette commented on PUP-9202 Re: Prepare release announcement (Puppet Platform 6.0.2) Internal draft: (Kenn - info needed, and also, is this the level of detail we want to include?) To: puppet-product-upda...@puppet.com Subject: Puppet Platform 6.0.2 now available Hello All, Puppet Platform 6.0.2 is a minor Puppet release now available broadly. This release fixes a regression that shipped as part of Puppet Platform 6.0.1 earlier this week. The issue was that unless and onlyif attributes of the exec resource did not respect the specified cwd (directory from which to run the command). This is now fixed. This release also contains a new Windows method, and a bug fix. Download Puppet 6.0.2: Read more in the release notes (https://puppet.com/docs/puppet/6.0/release_notes.html#puppet-602). We welcome your feedback: Thanks to these contributors, who made this release possible: 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-9202) Prepare release announcement (Puppet Platform 6.0.2)
Title: Message Title Michelle Fredette commented on PUP-9202 Re: Prepare release announcement (Puppet Platform 6.0.2) (external draft - tbd) 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-8002) "Attempt to redefine entity" caused by using a resource collector
Title: Message Title Henrik Lindberg commented on PUP-8002 Re: "Attempt to redefine entity" caused by using a resource collector It (PR 2389 to PDB) had not been merged when Thomas made the comment from what I can tell. Looking at the code, there are no changes made in the collector - it just relies on the Resource being created to load its type - and it seems to go to the autoloader - then it probably ends up recursing while loading a previously not loaded type and ends up biting itself in the a**. 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-896) Send release announcements (Bolt 0.25.0)
Title: Message Title Kate Lopresti commented on BOLT-896 Re: Send release announcements (Bolt 0.25.0) Michael Smith There's a new address we need to add to this list: puppet-product-upda...@puppet.com. Can you update the template used to generate these "Send release announcements" ticket. Details: https://confluence.puppetlabs.com/display/PM/Sending+Product+Release+Announcements 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-4130) merge 5.2.x -> 6.0.x
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4130 merge 5.2.x -> 6.0.x Issue Type: Bug Assignee: Unassigned Created: 2018/10/04 10:17 AM Priority: Normal Reporter: gepetto-bot 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 (PUP-9203) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.0.2)
Title: Message Title Kenn Hussey commented on PUP-9203 Re: Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.0.2) Conducted go/no-go in HipChat, we are a GO! 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-8002) "Attempt to redefine entity" caused by using a resource collector
Title: Message Title Eric Sorenson commented on PUP-8002 Re: "Attempt to redefine entity" caused by using a resource collector Thomas Hallgren when you say "this needs to happen"... does that mean the change you linked to needs to go into additional places? since that PR seems to be merged and released. 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-1888) 'os.release' values not correct for VZ7
Title: Message Title Kilian Engelhardt updated an issue Facter / FACT-1888 'os.release' values not correct for VZ7 Change By: Kilian Engelhardt Affects Version/s: FACT 3.12.0 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-1888) 'os.release' values not correct for VZ7
Title: Message Title
Kilian Engelhardt created an issue
Facter / FACT-1888
'os.release' values not correct for VZ7
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/10/04 9:19 AM
Priority:
Normal
Reporter:
Kilian Engelhardt
Facter 3.12.0 ships d9c30e5 which adds support for VirtuozzoLinux. This breaks parsing the release information. Instead, as a fallback, kernel version will be returned: Version 3.12.0:
os => {
architecture => "x86_64",
family => "Linux",
hardware => "x86_64",
name => "VirtuozzoLinux",
release => {
full => "3.10.0-693.17.1.vz7.43.10",
Jira (PDB-4072) HA out-of-sync after restart
Title: Message Title Austin Blatt commented on PDB-4072 Re: HA out-of-sync after restart Ok, I'm going to investigate the possibility that the massive resource titles are somehow affecting sync. The other ticket to follow is PDB-3742, I don't think it should affect this case, but you never know. 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-6828) Simplify agent SSL initialization
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-6828 Simplify agent SSL initialization Change By: Maggie Dreyer Team/s: Coremunity, Server 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-8706) HTTPClient in Puppet
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8706 HTTPClient in Puppet Change By: Maggie Dreyer Team/s: Server Coremunity 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-8002) "Attempt to redefine entity" caused by using a resource collector
Title: Message Title Steve Quin commented on PUP-8002 Re: "Attempt to redefine entity" caused by using a resource collector Eric Sorenson cc Neil Binney Is this something we can add to the Puppets backlog? Thanks, Steve 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-9208) Requesting new feature for notify messages
Title: Message Title
Patrick Mayes created an issue
Puppet / PUP-9208
Requesting new feature for notify messages
Issue Type:
New Feature
Assignee:
Unassigned
Components:
PE
Created:
2018/10/04 5:34 AM
Environment:
RHEL6, 7, Centos7
Priority:
Normal
Reporter:
Patrick Mayes
Currently there is not a good way to have a catalog fail but continue compiling the catalog. The options we have been given are to either use one of the 2 options which isn't ideal This will come back with an error but would like to have a notify value that provides an error, this is for testing and also if a new node doesn't get provisioned properly:
notify { 'this should fail': }
-> exec { '/bin/false': }
The following will come back with an error 500 and stops compiling
