Jira (BOLT-1117) Powershell task helper library
Title: Message Title Ethan Brown commented on BOLT-1117 Re: Powershell task helper library The most useful thing that I can think of at the moment is around making a more formal structure / contract around the task output during failure / success. With a common idiom it makes it easier to plumb together tasks as plans. https://github.com/puppetlabs/puppetlabs-bootstrap/blob/master/tasks/windows.ps1#L213-L240 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-1117) Powershell task helper library
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1117 Powershell task helper library Issue Type: New Feature Assignee: Unassigned Created: 2019/02/06 4:19 PM Priority: Normal Reporter: Alex Dreyer We have ruby and python task helpers. Powershell tasks don't have to worry about parsing input and generating output but there may be other helper code that is useful. ideas: Generate proper error format. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9025) Filebucket resources fail when using server_list
Title: Message Title Melissa Stone commented on PUP-9025 Re: Filebucket resources fail when using server_list Jean Bond how do I edit the docs page mentioned in this 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 (PUP-7052) Calls to the ENC terminus should use a configurable timeout
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-7052 Calls to the ENC terminus should use a configurable timeout Change By: Charlie Sharpsteen Affects Version/s: PUP 4.10.12 Affects Version/s: PUP 5.5.10 Affects Version/s: PUP 6.2.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-7052) Calls to the ENC terminus should use a configurable timeout
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-7052 Calls to the ENC terminus should use a configurable timeout Change By: Charlie Sharpsteen Team: 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-9479) "Failed to initialize ACL: The parameter is incorrect" errors when changing windows permissions.
Title: Message Title
Paul H updated an issue
Puppet / PUP-9479
"Failed to initialize ACL: The parameter is incorrect" errors when changing windows permissions.
Change By:
Paul H
Pertinent information: -I've personally confirmed that this affects the following OS versions: Windows Server 2008 SP1 Windows Server 2008 SP2 Windows Windows Server 2008 R2 SP1 Windows Server 2012 Windows Server 2012 R2-Puppet version: 4.9.4 -Scope: This behavior has affected hundred of windows hosts throughout our environment. -Summary: After pushing an update to change the group of a powershell script from "Administrator" to "Administrators", a large number of managed hosts started to fail with "Failed to initialize ACL: The parameter is incorrect." errors. I'm speculating that this might be related to an sid conflict, as all of our hosts are joined to a domain and there is an administrators group with an sid that matches what appears for local groups. Code before issue appeared: {code:java}file { 'c:/os_config/scripts/configureWinRM.ps1': ensure => 'file', owner => 'Administrator', group => 'Administrator', content => template('fakepathforexample/configureWinRM.erb'), } {code}Code after issue appeared: {code:java}file { 'c:/os_config/scripts/configureWinRM.ps1': ensure => 'file', owner => 'Administrator', group => ' Administrator Administrators ', content => template('fakepathforexample/configureWinRM.erb'), }{code} SID comparison: {code:java}PS C:\Users\phansen_alt> Get-ADGroup -Identity Administrators DistinguishedName : CN=Administrators,CN=Builtin,DC=REDACTED,DC=comGroupCategory : SecurityGroupScope: DomainLocalName : AdministratorsObjectClass : groupObjectGUID: d2afeac8-ee3f-4bae-8458-27f4a05e6e85SamAccountName: AdministratorsSID : S-1-5-32-544PS C:\Users\phansen_alt> (Get-Localgroup -Name Administrators).sidBinaryLength AccountDomainSid Value - 16 S-1-5-32-544{code}Error message: {code:java}Error: Failed to set owner to 'S-1-5-21-3450263623-690944591-812587964-500': Failed to initialize ACL: The parameter is incorrect. Error: /Stage[main]/REDACTED::Winrm/File[c:/os_config/scripts/configureWinRM.ps1]/owner: change from BUILTIN\Administrators to \Administrator failed: Failed to set owner to 'S-1-5-21-3450263623-690944591-812587964-500': Failed to initialize ACL: The parameter is incorrect. Error: Failed to set group to 'S-1-5-32-544': Failed to initialize ACL: The parameter is incorrect. Error: /Stage[main]/REDACTED::Winrm/File[c:/os_config/scripts/configureWinRM.ps1]/group: change from NT AUTHORITY\SYSTEM to BUILTIN\Administrators failed: Failed to set group to 'S-1-5-32-544': Failed to initialize ACL: The parameter is incorrect.{code} Things to note: -Initial deployments of this file work without issue, the error only appears when the permissions are being changed -Modifying the permissions with powershell or the gui works without issue -I've developed a powershell exec workaround for
Jira (PUP-9479) "Failed to initialize ACL: The parameter is incorrect" errors when changing windows permissions.
Title: Message Title Paul H commented on PUP-9479 Re: "Failed to initialize ACL: The parameter is incorrect" errors when changing windows permissions. Please see the attached file (puppetrun.txt) for a puppet run with debug on. 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
Paul H updated an issue
Puppet / PUP-9479
"Failed to initialize ACL: The parameter is incorrect" errors when changing windows permissions.
Change By:
Paul H
Pertinent information: -I've personally confirmed that this affects the following OS versions: Windows Server 2008 SP1 Windows Server 2008 SP2 Windows Windows Server 2008 R2 SP1 Windows Server 2012 Windows Server 2012 R2-Puppet version: 4.9.4 -Scope: This behavior has affected hundred of windows hosts throughout our environment. -Summary: After pushing an update to change the group of a powershell script from "Administrator" to "Administrators", a large number of managed hosts started to fail with "Failed to initialize ACL: The parameter is incorrect." errors. I'm speculating that this might be related to an sid conflict, as all of our hosts are joined to a domain and there is an administrators group with an sid that matches what appears for local groups. Code before issue appeared: {code:java}file { 'c:/os_config/scripts/configureWinRM.ps1': ensure => 'file', owner => 'Administrator', group => 'Administrator', content => template('fakepathforexample/configureWinRM.erb'), } {code}Code after issue appeared: {code:java}file { 'c:/os_config/scripts/configureWinRM.ps1': ensure => 'file', owner => 'Administrator', group => 'Administrator', content => template('fakepathforexample/configureWinRM.erb'), }{code} SID comparison: {code:java}PS C:\Users\phansen_alt> Get-ADGroup -Identity Administrators DistinguishedName : CN=Administrators,CN=Builtin,DC=REDACTED,DC=comGroupCategory : SecurityGroupScope: DomainLocalName : AdministratorsObjectClass : groupObjectGUID: d2afeac8-ee3f-4bae-8458-27f4a05e6e85SamAccountName: AdministratorsSID : S-1-5-32-544PS C:\Users\phansen_alt> (Get-Localgroup -Name Administrators).sidBinaryLength AccountDomainSid Value - 16 S-1-5-32-544{code}Error message: {code:java}Error: Failed to set owner to 'S-1-5-21-3450263623-690944591-812587964-500': Failed to initialize ACL: The parameter is incorrect. Error: /Stage[main]/REDACTED::Winrm/File[c:/os_config/scripts/configureWinRM.ps1]/owner: change from BUILTIN\Administrators to \Administrator failed: Failed to set owner to 'S-1-5-21-3450263623-690944591-812587964-500': Failed to initialize ACL: The parameter is incorrect. Error: Failed to set group to 'S-1-5-32-544': Failed to initialize ACL: The parameter is incorrect. Error: /Stage[main]/REDACTED::Winrm/File[c:/os_config/scripts/configureWinRM.ps1]/group: change from NT AUTHORITY\SYSTEM to BUILTIN\Administrators failed: Failed to set group to 'S-1-5-32-544': Failed to initialize ACL: The parameter is incorrect.{code} Things to note: -Initial deployments of this file work without issue, the error only appears when the permissions are being changed -Modifying the permissions with powershell or the gui works without issue -I've developed a powershell exec workaround for this, and I
Jira (PUP-9479) "Failed to initialize ACL: The parameter is incorrect" errors when changing windows permissions.
Title: Message Title Paul H updated an issue Puppet / PUP-9479 "Failed to initialize ACL: The parameter is incorrect" errors when changing windows permissions. Change By: Paul H Attachment: puppetrun.txt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To 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
Paul H updated an issue
Puppet / PUP-9479
"Failed to initialize ACL: The parameter is incorrect" errors when changing windows permissions.
Change By:
Paul H
Pertinent information: -I've personally confirmed that this affects the following OS versions: Windows Server 2008 SP1Windows Server 2008 SP2Windows Windows Server 2008 R2 SP1Windows Server 2012Windows Server 2012 R2-Puppet version:4.9.4-Scope:This behavior has affected hundred of windows hosts throughout our environment. -Summary: After pushing an update to change the group of a powershell script from "Administrator" to "Administrators", a large number of managed hosts started to fail with "Failed to initialize ACL: The parameter is incorrect." errors. I'm speculating that this might be related to an sid conflict, as all of our hosts are joined to a domain and there is an administrators group with an sid that matches what appears for local groups. Code before issue appeared: {code:java} file { 'c:/os_config/scripts/configureWinRM.ps1': ensure => 'file', owner => 'Administrator', group => 'Administrator', content => template('fakepathforexample/configureWinRM.erb'), } {code}Code after issue appeared: {code:java} file { 'c:/os_config/scripts/configureWinRM.ps1': ensure => 'file', owner => 'Administrator', group => 'Administrator', content => template('fakepathforexample/configureWinRM.erb'), }{code} SID comparison: {code:java} PS C:\Users\phansen_alt> Get-ADGroup -Identity Administrators DistinguishedName : CN=Administrators,CN=Builtin,DC=REDACTED,DC=comGroupCategory : SecurityGroupScope: DomainLocalName : AdministratorsObjectClass : groupObjectGUID: d2afeac8-ee3f-4bae-8458-27f4a05e6e85SamAccountName: AdministratorsSID : S-1-5-32-544PS C:\Users\phansen_alt> (Get-Localgroup -Name Administrators).sidBinaryLength AccountDomainSid Value - 16 S-1-5-32-544{code}Error message: {code:java} Error: Failed to set owner to 'S-1-5-21-3450263623-690944591-812587964-500': Failed to initialize ACL: The parameter is incorrect. Error: /Stage[main]/REDACTED::Winrm/File[c:/os_config/scripts/configureWinRM.ps1]/owner: change from BUILTIN\Administrators to \Administrator failed: Failed to set owner to 'S-1-5-21-3450263623-690944591-812587964-500': Failed to initialize ACL: The parameter is incorrect. Error: Failed to set group to 'S-1-5-32-544': Failed to initialize ACL: The parameter is incorrect. Error: /Stage[main]/REDACTED::Winrm/File[c:/os_config/scripts/configureWinRM.ps1]/group: change from NT AUTHORITY\SYSTEM to BUILTIN\Administrators failed: Failed to set group to 'S-1-5-32-544': Failed to initialize ACL: The parameter is incorrect.{code} Things to note:-Initial deployments of this file work without issue, the error only appears when the permissions are being changed-Modifying the permissions with powershell or the gui works without issue-I've developed a powershell exec workaround for this, and
Jira (PUP-9479) "Failed to initialize ACL: The parameter is incorrect" errors when changing windows permissions.
Title: Message Title
Paul H created an issue
Puppet / PUP-9479
"Failed to initialize ACL: The parameter is incorrect" errors when changing windows permissions.
Issue Type:
Bug
Assignee:
Unassigned
Created:
2019/02/06 12:49 PM
Priority:
Normal
Reporter:
Paul H
Pertinent information: -I've personally confirmed that this affects the following OS versions: Windows Server 2008 SP1 Windows Server 2008 SP2 Windows Windows Server 2008 R2 SP1 Windows Server 2012 Windows Server 2012 R2 -Puppet version: 4.9.4 -Scope: This behavior has affected hundred of windows hosts throughout our environment. -Summary: After pushing an update to change the group of a powershell script from "Administrator" to "Administrators", a large number of managed hosts started to fail with "Failed to initialize ACL: The parameter is incorrect." errors. I'm speculating that this might be related to an sid conflict, as all of our hosts are joined to a domain and there is an administrators group with an sid that matches what appears for local groups. Code before issue appeared:
file { 'c:/os_config/scripts/configureWinRM.ps1':
ensure => 'file',
owner => 'Administrator',
group => 'Administrator',
Jira (PDOC-171) generate the hiera keynames to use for parameterised classes
Title: Message Title Trevor Vaughan commented on PDOC-171 Re: generate the hiera keynames to use for parameterised classes Actually, thinking about this, it might be a LOT easier than going 'full Hiera': If the hiera path has interpolation, the strings value becomes see in module data If it does not, return the value That should be it, right? 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-9478) puppet generate certificate gives linux permissions to ssldir
Title: Message Title
Nick GW updated an issue
Puppet / PUP-9478
puppet generate certificate gives linux permissions to ssldir
Change By:
Nick GW
Running `puppet certificate generate --ca-location remote $hostname`, where $hostname is the FQDN of the node, gives ssldir, as well as other files on Windows Linux-style permissions, breaking puppet. The puppet certificate command does request and deliver the correct certificate, but the puppet agent can not open and read them: {code:java} ``` // PS C:\Windows\system32> puppet agent -vError: Could not request certificate: Permission denied @ rb_sysopen - C:/ProgramData/PuppetLabs/puppet/etc/ssl/private_keys/HOSTNAME.pem ``` {code} In addition, the cache folder in vardir has broken permissions: {code:java} ``` // Error: Transaction store file C:/ProgramData/PuppetLabs/puppet/cache/state/transactionstore.yaml is corrupt (Permission denied @ rb_sysopen - C:/ProgramData/PuppetLabs/puppet/cache/state/transactionstore.yaml); replacingWrapped exception:Permission denied @ rb_sysopen - C:/ProgramData/PuppetLabs/puppet/cache/state/transactionstore.yaml``` ```Error: Could not send report: ReplaceFile(C:/ProgramData/PuppetLabs/puppet/cache/state/last_run_report.yaml, C:/ProgramData/PuppetLabs/puppet/cache/state/last_run_report.yaml20190206-3632-7u91t6): Access is denied. ``` {code}
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9478) puppet generate certificate gives linux permissions to ssldir
Title: Message Title Nick GW created an issue Puppet / PUP-9478 puppet generate certificate gives linux permissions to ssldir Issue Type: Bug Affects Versions: PUP 5.5.3 Assignee: Unassigned Components: Windows Created: 2019/02/06 11:58 AM Priority: Normal Reporter: Nick GW Running `puppet certificate generate --ca-location remote $hostname`, where $hostname is the FQDN of the node, gives ssldir, as well as other files on Windows Linux-style permissions, breaking puppet. The puppet certificate command does request and deliver the correct certificate, but the puppet agent can not open and read them: ```PS C:\Windows\system32> puppet agent -v Error: Could not request certificate: Permission denied @ rb_sysopen - C:/ProgramData/PuppetLabs/puppet/etc/ssl/private_keys/HOSTNAME.pem``` In addition, the cache folder in vardir has broken permissions: ```Error: Transaction store file C:/ProgramData/PuppetLabs/puppet/cache/state/transactionstore.yaml is corrupt (Permission denied @ rb_sysopen - C:/ProgramData/PuppetLabs/puppet/cache/state/transactionstore.yaml); replacing Wrapped exception: Permission denied @ rb_sysopen - C:/ProgramData/PuppetLabs/puppet/cache/state/transactionstore.yaml``` ```Error: Could not send report: ReplaceFile(C:/ProgramData/PuppetLabs/puppet/cache/state/last_run_report.yaml, C:/ProgramData/PuppetLabs/puppet/cache /state/last_run_report.yaml20190206-3632-7u91t6): Access is denied.```
Jira (BOLT-1114) Update homebrew-puppet (Bolt 1.11.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1114 Update homebrew-puppet (Bolt 1.11.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/02/06 11:51 AM Due Date: 2019/02/07 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-02-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-1113) Kick off release pipeline (Bolt 1.11.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1113 Kick off release pipeline (Bolt 1.11.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/02/06 11:51 AM Due Date: 2019/02/07 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-02-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-1115) Docs for bolt release (Bolt 1.11.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1115 Docs for bolt release (Bolt 1.11.0) Issue Type: Sub-task Assignee: Melissa Amos Created: 2019/02/06 11:51 AM Due Date: 2019/02/07 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-02-07) Release notes and docs changes for bolt 1.11.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1116) Send release announcements (Bolt 1.11.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1116 Send release announcements (Bolt 1.11.0) Issue Type: Sub-task Assignee: Melissa Amos Created: 2019/02/06 11:51 AM Due Date: 2019/02/07 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-02-07) Once docs have finished building (check that all links resolve appropriately) - Create an e-mail announcement with the subject "Bolt 1.11.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.11.0 is now available".
Jira (BOLT-1111) Bolt 1.11.0 2019-02-07 Release
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT- Bolt 1.11.0 2019-02-07 Release Issue Type: Task Assignee: Cas Donoghue Created: 2019/02/06 11:50 AM Priority: Normal Reporter: Cas Donoghue Bolt 1.11.0 2019-02-07 Release Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1112) Reconcile git commits, JIRA tickets, and versions (Bolt 1.11.0)
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1112 Reconcile git commits, JIRA tickets, and versions (Bolt 1.11.0) Issue Type: Sub-task Assignee: Cas Donoghue Created: 2019/02/06 11:51 AM Due Date: 2019/02/07 Priority: Normal Reporter: Cas Donoghue (Initial planned release date: 2019-02-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 (PUP-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Eric Thompson commented on PUP-9337 Re: Puppet sets permissions for Puppet files every run Keiran Haggerty this is starting to impact more and more customers. any ideas on the relative priority of this and chances to get it into the next Z? fyi Jed Gresham 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 (PDOC-171) generate the hiera keynames to use for parameterised classes
Title: Message Title Trevor Vaughan commented on PDOC-171 Re: generate the hiera keynames to use for parameterised classes Henrik Lindberg How difficult would it be to just get defaults and not follow any logical paths? This is what is blocking us right now from putting all of our defaults in module data. Also, is it actually a good idea to put all defaults in module data? This seems to be less readable and 'easy to use' for new users. 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-153) Copy files over SMB on Windows
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet Task Runner / BOLT-153 Copy files over SMB 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-153) Copy files over SMB on Windows
Title: Message Title Ethan Brown updated an issue Puppet Task Runner / BOLT-153 Copy files over SMB on Windows Change By: Ethan Brown 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-153) Copy files over SMB on Windows
Title: Message Title Ethan Brown updated an issue Puppet Task Runner / BOLT-153 Copy files over SMB on Windows Change By: Ethan Brown 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-952) Update developer docs to send files array
Title: Message Title Alex Dreyer assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-952 Update developer docs to send files array Change By: Alex Dreyer Assignee: Cas Donoghue 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 (BOLT-987) Add CLI front end to plan executor
Title: Message Title Alex Dreyer assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-987 Add CLI front end to plan executor Change By: Alex Dreyer Assignee: Nick Lewis Cas Donoghue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-146) Configure what interpreter/shell to use
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-146 Configure what interpreter/shell to use Change By: Cas Donoghue Assignee: Cas Donoghue Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-920) Bolt unable to connect with ecdsa key
Title: Message Title
Cas Donoghue updated an issue
Puppet Task Runner / BOLT-920
Bolt unable to connect with ecdsa key
Change By:
Cas Donoghue
Release Notes Summary:
Bolt can now use keys in an {{ecdsa}} key updated OpenSSH format to authenticate {{ssh}} connections.
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-4252) Turn off dujour update checking in pdbext tests
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-4252 Turn off dujour update checking in pdbext tests Change By: Austin Blatt Comment: Decent data, important and amazing structure, as offer well done with smart thoughts and ideas, bunches of incredible data and motivation, the two of which I require, on account of offer such a supportive [godaddy 99 domain|https://www.webhostingonedollar.com/godaddy-rs-99-web-hosting-domain.html] data here. 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-920) Bolt unable to connect with ecdsa key
Title: Message Title
Cas Donoghue updated an issue
Puppet Task Runner / BOLT-920
Bolt unable to connect with ecdsa key
Change By:
Cas Donoghue
Release Notes Summary:
Bolt can now use an {{ecdsa}} key to authenticate {{ssh}} connections.
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-920) Bolt unable to connect with ecdsa key
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-920 Bolt unable to connect with ecdsa key Change By: Cas Donoghue 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 (PDB-4261) Booleans can't be used as left half of comparison
Title: Message Title
Jonathan Newman created an issue
PuppetDB / PDB-4261
Booleans can't be used as left half of comparison
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2019/02/06 6:53 AM
Priority:
Normal
Reporter:
Jonathan Newman
We have some cases where queries are generated that should always be false, and not match anything. While it is possible to create rules that self conflict (an `and` clause with a comparison that both equals and doesn't equal the same thing), it would be less of a cognitive burden if booleans could be used on the left hand side of an _expression_, or if there was a way to represent something as always being false. For example:
curl -X POST -H 'Content-Type: application/json' http://localhost:8080/pdb/query/v4/inventory -d '{"query":["=", true, false]}'
Unfortunately generates the following output:
Jira (PUP-9474) Automatic parameter lookup times should show up in profiler metrics
Title: Message Title Henrik Lindberg commented on PUP-9474 Re: Automatic parameter lookup times should show up in profiler metrics I think there is one, yes. IIRC, the current way profiling is done is to make the call inside of a lambda, and the lambda is either called with or without measuring time. Thus an overhead of at least one call, plus creation of the profiling id/string, plus calling a lambda, plus generating more garbage for the gc - which does not really show up on short benchmarks. Since hiera backend functions that return an entire hash (like the json and yaml ones) are only called once per data file (or possibly multiple times if the cache needs to be evicted) the number of profiled calls will be much lower than if we measure every parameter lookup. The "by key" backend functions will get many calls and those are typically also the ones that are advanced (eyaml, or remote lookup backends). 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-9477) Unable to use call() on custom functions
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-9477 Unable to use call() on custom functions Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-9477) Unable to use call() on custom functions
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9477 Unable to use call() on custom functions Change By: Henrik Lindberg Sprint: Platform Core 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-9477) Unable to use call() on custom functions
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9477 Unable to use call() on custom functions Change By: Henrik Lindberg Sub-team: Language Release Notes Summary: The `call()` function was only able to call functions in puppet core. This is now fixed so that any function in the environment is visible and can be called. 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.go
Jira (PUP-9477) Unable to use call() on custom functions
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9477 Unable to use call() on custom functions Change By: Henrik Lindberg Fix Version/s: PUP 6.2.1 Fix Version/s: PUP 6.0.6 Fix Version/s: PUP 5.5.11 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-9477) Unable to use call() on custom functions
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9477 Unable to use call() on custom functions Change By: Henrik Lindberg Affects Version/s: PUP 5.5.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-9477) Unable to use call() on custom functions
Title: Message Title Henrik Lindberg commented on PUP-9477 Re: Unable to use call() on custom functions Note that `Deferred` cannot be used agent side with functions written in the puppet language since they are not plugin synced. 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-9477) Unable to use call() on custom functions
Title: Message Title
Henrik Lindberg commented on PUP-9477
Re: Unable to use call() on custom functions
This simple snippet replicates the problem.
function pfunction() {
"from pfunction"
}
$message = pfunction()
notify {$message: }
$message2 = call('pfunction')
notify{$message2: }
The `call` version fails with an error that it cannot find the function.
Add Comment
Jira (PUP-9437) Make it easier to set Puppets current locale
Title: Message Title David Mallon commented on PUP-9437 Re: Make it easier to set Puppets current locale Hey Josh Cooper, is there any more information you guys need from us? 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-9477) Unable to use call() on custom functions
Title: Message Title
Jan Vansteenkiste updated an issue
Puppet / PUP-9477
Unable to use call() on custom functions
Change By:
Jan Vansteenkiste
Using custom functions, I'm unable to call them using the call() function.Test case: modules/call_me/functions/pfunction.pp{code:puppet}function call_me::pfunction( Optional[String] $args = undef) { "returned from pfunction"}{code}test.pp;{code:puppet} $message = call_me::pfunction() notify {'direct function call': message => $message, } $deferred = Deferred('call_me::pfunction') $message3 = $deferred.call() notify {'deferred, function name hardcoded': message => $message3, }$function_name = 'call_me::pfunction' $deferred2 = Deferred($function_name) $message4 = $deferred2.call() notify {'deferred, function name in variable': message => $message4, }{code}output:{code} Info: Using configured environment 'production'Info: Retrieving pluginfactsInfo: Retrieving pluginInfo: Retrieving localesInfo: Caching catalog for cyberflox.irken.orgInfo: Applying configuration version '1549449374'Notice: Most basic class ever: call_meNotice: /Stage[main]/Call_me/Notify[Most basic class ever: call_me]/message: defined 'message' as 'Most basic class ever: call_me'Notice: returned from pfunctionNotice: /Stage[main]/Main/Node[default]/Notify[direct function call]/message: defined 'message' as 'returned from pfunction'Notice: returned from pfunctionNotice: /Stage[main]/Main/Node[default]/Notify[deferred, function name hardcoded]/message: defined 'message' as 'returned from pfunction'Notice: returned from pfunctionNotice: /Stage[main]/Main/Node[default]/Notify[deferred, function name in variable]/message: defined 'message' as 'returned from pfunction'Notice: Applied catalog in 0.02 seconds{code}code that fails:{code}# THIS BLOCK FAILS$message2 = call('call_me::pfunction')notify{'call(call_me::pfunction)': message => $message2, }{code}output:{code}Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Function Call, Function call(): Unknown function: 'call_me::pfunction' (file: /etc/puppetlabs/code/environments/production/manifests/site.pp, line: 9, column: 15) on node cyberflox.irken.orgWarning: Not using cache on failed catalogError: Could not retrieve catalog; skipping run{code}
Jira (PUP-9477) Unable to use call() on custom functions
Title: Message Title
Jan Vansteenkiste updated an issue
Puppet / PUP-9477
Unable to use call() on custom functions
Change By:
Jan Vansteenkiste
Using custom functions, I'm unable to call them using the call() function.Test case:modules/call_me/functions/pfunction.pp{code: java puppet } function call_me::pfunction( Optional[String] $args = undef) { "returned from pfunction"}{code}test.pp;{code: java puppet } $message = call_me::pfunction() notify {'direct function call': message => $message, } $deferred = Deferred('call_me::pfunction') $message3 = $deferred.call() notify {'deferred, function name hardcoded': message => $message3, }$function_name = 'call_me::pfunction' $deferred2 = Deferred($function_name) $message4 = $deferred2.call() notify {'deferred, function name in variable': message => $message4, }{code}output:{code :java } Info: Using configured environment 'production'Info: Retrieving pluginfactsInfo: Retrieving pluginInfo: Retrieving localesInfo: Caching catalog for cyberflox.irken.orgInfo: Applying configuration version '1549449374'Notice: Most basic class ever: call_meNotice: /Stage[main]/Call_me/Notify[Most basic class ever: call_me]/message: defined 'message' as 'Most basic class ever: call_me'Notice: returned from pfunctionNotice: /Stage[main]/Main/Node[default]/Notify[direct function call]/message: defined 'message' as 'returned from pfunction'Notice: returned from pfunctionNotice: /Stage[main]/Main/Node[default]/Notify[deferred, function name hardcoded]/message: defined 'message' as 'returned from pfunction'Notice: returned from pfunctionNotice: /Stage[main]/Main/Node[default]/Notify[deferred, function name in variable]/message: defined 'message' as 'returned from pfunction'Notice: Applied catalog in 0.02 seconds {code} { code that fails : java {code } # THIS BLOCK FAILS $message2 = call('call_me::pfunction')notify{'call(call_me::pfunction)': message => $message2, }{code} output:{code}Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Function Call, Function call(): Unknown function: 'call_me::pfunction' (file: /etc/puppetlabs/code/environments/production/manifests/site.pp, line: 9, column: 15) on node cyberflox.irken.orgWarning: Not using cache on failed catalogError: Could not retrieve catalog; skipping run{code}
Jira (PUP-9477) Unable to use call() on custom functions
Title: Message Title
Jan Vansteenkiste created an issue
Puppet / PUP-9477
Unable to use call() on custom functions
Issue Type:
Bug
Affects Versions:
PUP 6.2.0
Assignee:
Henrik Lindberg
Components:
Functions
Created:
2019/02/06 2:35 AM
Priority:
Normal
Reporter:
Jan Vansteenkiste
Using custom functions, I'm unable to call them using the call() function. Test case: modules/call_me/functions/pfunction.pp
function call_me::pfunction(
Optional[String] $args = undef
) {
"returned from pfunction"
}
Jira (PDB-4252) Turn off dujour update checking in pdbext tests
Title: Message Title josef bican commented on PDB-4252 Re: Turn off dujour update checking in pdbext tests Decent data, important and amazing structure, as offer well done with smart thoughts and ideas, bunches of incredible data and motivation, the two of which I require, on account of offer such a supportive godaddy 99 domain data here. 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.
