Jira (PUP-9470) Add note to logs about which value we're getting the server from
Title: Message Title Josh Cooper commented on PUP-9470 Re: Add note to logs about which value we're getting the server from We have a few tickets around displaying which server the agent tries to connect to, eg PUP-8769, let's sync up about that. About the nested behavior, yes, it's crazy, but is unfortunately how the default validator works, and why I've been working to untangle that. The default validator can lookup the ssl host, while trying to make a connection, which can cause nested connections and leads to "bad things". That will all go away soon, once everything is switched over to passing an explicit ssl_context to Puppet::Network::HttpPool.connection. 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-9470) Add note to logs about which value we're getting the server from
Title: Message Title Melissa Stone commented on PUP-9470 Re: Add note to logs about which value we're getting the server from Try to retrieve the ca cert without any of the previously determined server information that we had collected before. Josh Cooper I added a bunch of debug statements to just figure out what's happening. I noticed we have this section of code that gets repeated, which is odd. Debug: from lib/puppet/indirector/rest.rb, line 69 Debug: Dynamically-bound server lookup failed, falling back to ca_server setting: puppet Debug: from lib/puppet/indirector/rest.rb, line 108 Debug: Dynamically-bound port lookup failed; falling back to ca_port setting Debug: from lib/puppet/indirector/request.rb, line 206 Debug: Dynamically-bound server lookup failed, falling back to server setting: puppet Debug: from lib/puppet/indirector/request.rb, line 218 Debug: Dynamically-bound server lookup failed, falling back to the masterport setting: 8140 Debug: from lib/puppet/indirector/request.rb, line 226 Debug: from lib/puppet/indirector/rest.rb, line 69 Debug: Dynamically-bound server lookup failed, falling back to ca_server setting: puppet
Jira (PUP-9457) Add HttpPool method for creating connections using an SSLContext
Title: Message Title Kris Bosland commented on PUP-9457 Re: Add HttpPool method for creating connections using an SSLContext Merged into master at ec56c73. 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-9041) AIX nim provider can't be used on a NIM master
Title: Message Title Sean McDonald assigned an issue to Unassigned Puppet / PUP-9041 AIX nim provider can't be used on a NIM master Change By: Sean McDonald Assignee: Sean McDonald 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-9041) AIX nim provider can't be used on a NIM master
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9041 AIX nim provider can't be used on a NIM master Change By: Sean McDonald Sprint: PR - Triage 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-1884) Add NIM master detection
Title: Message Title Sean McDonald updated an issue Facter / FACT-1884 Add NIM master detection Change By: Sean McDonald Team: Platform OS Puppet Romania Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9041) AIX nim provider can't be used on a NIM master
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9041 AIX nim provider can't be used on a NIM master Change By: Sean McDonald Team: Platform OS Puppet Romania Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1884) Add NIM master detection
Title: Message Title Sean McDonald updated an issue Facter / FACT-1884 Add NIM master detection Change By: Sean McDonald Sprint: PR - Triage 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-9511) Debug logging for Exec resources should include 'creates' checks
Title: Message Title Kris Bosland commented on PUP-9511 Re: Debug logging for Exec resources should include 'creates' checks Merged to master in 35311da. 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-9511) Debug logging for Exec resources should include 'creates' checks
Title: Message Title Kris Bosland updated an issue Puppet / PUP-9511 Debug logging for Exec resources should include 'creates' checks Change By: Kris Bosland Fix Version/s: PUP 6.4.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-9357) Noop exec debug logging should include the command
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9357 Noop exec debug logging should include the command Change By: Josh Cooper Fix Version/s: PUP 6.4.0 Fix Version/s: PUP 6.0.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-2644) Code Formatter
Title: Message Title Jesse Hathaway commented on PUP-2644 Re: Code Formatter Would it be possible to reopen this feature request? Tools like `gofmt` have quickly become an industry standard and the lack of such a tool as part of puppet makes it very difficult to bring consistent style to a large code base. Would it be possible to extend `puppet validate` with a new command, perhaps `puppet format`, which would output a puppet file adhering to the style guide? 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-1161) Reconcile git commits, JIRA tickets, and versions (Bolt 1.14.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1161 Reconcile git commits, JIRA tickets, and versions (Bolt 1.14.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/03/05 11:06 AM Due Date: 2019/03/07 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-03-07) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=Bolt and fixVersion="Bolt x.y.z"' in JIRA. Add Comment
Jira (BOLT-1165) Send release announcements (Bolt 1.14.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1165 Send release announcements (Bolt 1.14.0) Issue Type: Sub-task Assignee: Melissa Amos Created: 2019/03/05 11:06 AM Due Date: 2019/03/07 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-03-07) Once docs have finished building (check that all links resolve appropriately) - Create an e-mail announcement with the subject "Bolt 1.14.0 now available". Include a summary of the release and links to the installation instructions and release notes. In the From: field, enter the Google account Puppet Product Updates (puppet-product-upda...@puppet.com). In the Bcc: field, enter the following addresses. Send a separate message to each: internal-puppet-product-upda...@puppet.com, puppet-us...@googlegroups.com, puppet-...@googlegroups.com, and puppet-annou...@googlegroups.com. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. If you want, make a PSA on IRC and/or Slack, something along the lines of "PSA: Bolt 1.14.0 is now available".
Jira (BOLT-1164) Docs for bolt release (Bolt 1.14.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1164 Docs for bolt release (Bolt 1.14.0) Issue Type: Sub-task Assignee: Melissa Amos Created: 2019/03/05 11:06 AM Due Date: 2019/03/07 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-03-07) Release notes and docs changes for bolt 1.14.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1163) Update homebrew-puppet (Bolt 1.14.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1163 Update homebrew-puppet (Bolt 1.14.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/03/05 11:06 AM Due Date: 2019/03/07 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-03-07) Until we automate this, you'll also need to update the version and SHA hashes of https://github.com/puppetlabs/homebrew-puppet/blob/master/Casks/puppet-bolt.rb. To do this please Create a fork of the homebrew-puppet repo Create a new branch on that fork Run "rake 'brew:cask[puppet-bolt]'" Verify Casks/puppet-bolt.rb was updated to the correct version Put up a PR to homebrew-puppet and request review Add Comment
Jira (BOLT-1162) Kick off release pipeline (Bolt 1.14.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1162 Kick off release pipeline (Bolt 1.14.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/03/05 11:06 AM Due Date: 2019/03/07 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-03-07) With our shiny new automated builds pipeline, all you have to do is Go to https://jenkins-master-prod-1.delivery.puppetlabs.net/view/bolt/job/platform_bolt-vanagon_bolt-release-init_bolt-release/ Click "Build with Parameters" Check the PUBLIC checkbox Enter the version in the NEW_TAG box (x.y.z format) Click build! And make sure the pipeline is green! Add Comment
Jira (BOLT-1160) Bolt 1.14.0 2019-03-07 Release
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1160 Bolt 1.14.0 2019-03-07 Release Issue Type: Task Assignee: Cas Donoghue Created: 2019/03/05 11:06 AM Priority: Normal Reporter: Cas Donoghue Bolt 1.14.0 2019-03-07 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1159) Investigate BoltSpec compatibility with beaker
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1159 Investigate BoltSpec compatibility with beaker Issue Type: Bug Assignee: Unassigned Created: 2019/03/05 10:58 AM Priority: Normal Reporter: Cas Donoghue The Modules team filed https://tickets.puppetlabs.com/browse/MODULES-8717 describing an issue where requiring bolt_spec/run after beaker causes an error like: 02:34:34 An error occurred while loading ./spec/acceptance/init_spec.rb. 02:34:34 Failure/Error: require 'bolt_spec/run' 02:34:34 NameError: 02:34:34 Rename parameter 'assert' as it shadows an existing method. 02:34:34 02:34:34 # ./.bundle/gems/gems/bindata-2.4.4/lib/bindata/params.rb:111:in `block in ensure_valid_names'
Jira (BOLT-1158) Publish bash helper library
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1158 Publish bash helper library Issue Type: Bug Assignee: Unassigned Created: 2019/03/05 10:32 AM Priority: Normal Reporter: Cas Donoghue Build up some bash helpers similar to the ruby,python_task_helper s. Given the limitations of bash the helpers will not be as fully featured. One idea that has come up is to build a solution for handling the `null` string value when the JSON representation of nil/null is coerced to a string in the process of "envifying" parameters. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1152) Execute a simple plan
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1152
Execute a simple plan
Change By:
Alex Dreyer
{{bolt plan run}} should be able to run a simple plan.validate plan parametersReference plan parameters as "targets" and "parameters".return undef{noformat}---parameters: nodes:description: "The nodes to act on"type: "TargetSpec" package: description: "The name of the package to upgrade" type: "String" version:description: "The version of the package to install"steps: - name: "upgrade" task: package target: $nodesparameters: action: "install" name: $package version: $version - name: "restart" task: servicetarget: $nodesparameters: action: restart name: $package{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
Jira (BOLT-1152) Execute a simple plan
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1152
Execute a simple plan
Change By:
Alex Dreyer
{{bolt plan run}} should be able to run a simple plan.validate plan parametersReference plan parameters as "targets" and "parameters".return undef{noformat}---parameters: nodes:description: "The nodes to act on"type: "TargetSpec" package: description: "The name of the package to upgrade" type: "String" version:description: "The version of the Task package to run install "steps: - name: "upgrade "target: $nodesparameters: action: "install" name: $ package version: $version - name: "restart"
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-1152) Execute a simple plan
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1152
Execute a simple plan
Change By:
Alex Dreyer
{{bolt plan run}} should be able to run a simple plan. validate plan parameters Reference plan parameters as "targets" and "parameters".return undef {noformat}---parameters: nodes:description: "The nodes to act on"type: "TargetSpec" version:description: "The version of the Task to run"steps: - name: "upgrade package
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-1119) SPIKE - understand why bolt is so slow on windows
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-1119 SPIKE - understand why bolt is so slow on windows Change By: David Kramer Team: Bolt 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-1103) Linux implementation of the service task returns incorrect status output
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1103 Linux implementation of the service task returns incorrect status output Change By: Cas Donoghue Sprint: Bolt Ready for Grooming 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 (BOLT-1152) Execute a simple plan
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-1152 Execute a simple plan Change By: David Kramer Sprint: Bolt Ready for Grooming 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 (BOLT-1152) Execute a simple plan
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1152
Execute a simple plan
Change By:
Alex Dreyer
{{bolt plan run}} should be able to run a simple plan. Reference plan parameters as "targets" and "parameters".return undef
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-1119) SPIKE - understand why bolt is so slow on windows
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet Task Runner / BOLT-1119 SPIKE - understand why bolt is so slow on windows Change By: Ethan Brown Assignee: Ethan Brown 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-1119) SPIKE - understand why bolt is so slow on windows
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-1119 SPIKE - understand why bolt is so slow on windows Change By: David Kramer 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 (BOLT-1157) Target instances can't be passed across an apply() boundary
Title: Message Title
Nick Lewis created an issue
Puppet Task Runner / BOLT-1157
Target instances can't be passed across an apply() boundary
Issue Type:
Bug
Assignee:
Unassigned
Created:
2019/03/05 9:37 AM
Priority:
Normal
Reporter:
Nick Lewis
Due to the simple JSON serialization we use to pass state from a plan into the catalog compiler, variables with complex object types like Target can't be references inside an apply block. For example:
plan test(TargetSpec $nodes) {
$targets = $nodes.get_targets
apply($nodes) {
notice($targets[0].type)
}
}
Jira (BOLT-1104) Linux implementation of the package task returns incorrect status output
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1104 Linux implementation of the package task returns incorrect status output Change By: Cas Donoghue 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 (BOLT-1052) Support run-as for shell localhost transport.
Title: Message Title David Kramer updated an issue Puppet Task Runner / BOLT-1052 Support run-as for shell localhost transport. Change By: David Kramer 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-1152) Execute a simple plan
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1152 Execute a simple plan 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-1052) Support run-as for shell localhost transport.
Title: Message Title Lucy Wyman assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-1052 Support run-as for shell localhost transport. Change By: Lucy Wyman Assignee: 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1909) facter os prints family linux when it's VirtuozzoLinux
Title: Message Title Boris commented on FACT-1909 Re: facter os prints family linux when it's VirtuozzoLinux It also looks like the default provider got set to pip3. 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-9479) "Failed to initialize ACL: The parameter is incorrect" errors when changing windows permissions.
Title: Message Title Gheorghe Popescu commented on PUP-9479 Re: "Failed to initialize ACL: The parameter is incorrect" errors when changing windows permissions. Paul H Cannot reproduce the issues We tried to reproduce this issue(on puppet 4.9.4) with Domain Controller(default configuration) and above steps but have failed to encounter the error. Steps: install puppet 4.9.4 setup the Domain Controller(default config) apply the first manifest from ` Code before issue appeared` - success apply the second manifest from `Code after issue appeared` - success Can you share more details? Or highlight if there are any issues in our approach? 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-1909) facter os prints family linux when it's VirtuozzoLinux
Title: Message Title
Boris updated an issue
Facter / FACT-1909
facter os prints family linux when it's VirtuozzoLinux
Change By:
Boris
Hi,we are currently ongoing to migrate from Puppet5 to Puppet6 an ran into the issue that the os family is printed as "Linux" instead of "RedHat".I get why you changed os name, but why os family? { { noformat} # facter os }} { {{}} {{ architecture => "x86_64", }} {{ family => "Linux", }} {{ hardware => "x86_64", }} {{ name => "VirtuozzoLinux", }} {{ release => { }} {{ full => "3.10.0-862.9.1.vz7.63.3", }} {{ major => "3", }} {{ minor => "10" }} {{ }, }} {{ selinux => { }} {{ enabled => false }} {{ } }} } { { noformat } }} Cheers Boris
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
Jira (FACT-1909) facter os prints family linux when it's VirtuozzoLinux
Title: Message Title
Boris created an issue
Facter / FACT-1909
facter os prints family linux when it's VirtuozzoLinux
Issue Type:
Bug
Affects Versions:
FACT 3.13.0
Assignee:
Unassigned
Created:
2019/03/05 6:18 AM
Priority:
Normal
Reporter:
Boris
Hi, we are currently ongoing to migrate from Puppet5 to Puppet6 an ran into the issue that the os family is printed as "Linux" instead of "RedHat". I get why you changed os name, but why os family? # facter os {{{}} {{ architecture => "x86_64",}} {{ family => "Linux",}} {{ hardware => "x86_64",}} {{ name => "VirtuozzoLinux",}} {{ release => {}} {{ full => "3.10.0-862.9.1.vz7.63.3",}} {{ major => "3",}} {{ minor => "10"}} {{ },}} {{ selinux => {}} {{ enabled => false}} {{ }}} } Cheers Boris
Add Comment
Jira (PUP-9331) Puppet Runs fail if leftovers in /var/spool/cron are present
Title: Message Title Sebastian commented on PUP-9331 Re: Puppet Runs fail if leftovers in /var/spool/cron are present maybe change "error" to "warning", that might not confuse people so hard. Karthikeyan Kanagaraj The run still finishes as expected. 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-9331) Puppet Runs fail if leftovers in /var/spool/cron are present
Title: Message Title
Karthikeyan Kanagaraj commented on PUP-9331
Re: Puppet Runs fail if leftovers in /var/spool/cron are present
Enis Inan one of our customer hit the same issue. Please advise. _ {{[root@pe-201815-master cron]# puppet agent -t Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Retrieving locales Info: Loading facts Info: Caching catalog for pe-201815-master.puppetdebug.vlan Info: Applying configuration version '1551771722' Error: Could not prefetch cron provider 'crontab' target 'root.backup': Could not read crontab for root.backup: Execution of 'crontab -u root.backup -l' returned 1: crontab: user `root.backup' unknown. Treating as empty Error: Could not prefetch cron provider 'crontab' target 'root_backup': Could not read crontab for root_backup: Execution of 'crontab -u root_backup -l' returned 1: crontab: user `root_backup' unknown. Treating as empty Notice: Applied catalog in 15.61 seconds [root@pe-201815-master cron]#}}_ {{}}
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.
