Jira (BOLT-1104) Linux implementation of the package task returns incorrect status output
Title: Message Title
Adrian Parreiras Horta created an issue
Puppet Task Runner / BOLT-1104
Linux implementation of the package task returns incorrect status output
Issue Type:
Bug
Assignee:
Adrian Parreiras Horta
Created:
2019/01/25 4:38 PM
Priority:
Normal
Reporter:
Adrian Parreiras Horta
Currently, this implementation returns “$name $action” as the status output, instead of the status of the actual command.
adrian@Riven:~/repos/puppet/puppetlabs-service$ bolt task run package action="" name=vim --nodes pe-201901-agent --run-as root
Started on pe-201901-agent...
Finished on pe-201901-agent:
{
"status": "vim install"
}
Jira (PUP-9372) Add collection operations to Puppet core
Title: Message Title Michael Smith updated an issue Puppet / PUP-9372 Add collection operations to Puppet core 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 (PUP-9372) Add collection operations to Puppet core
Title: Message Title Michael Smith updated an issue Puppet / PUP-9372 Add collection operations to Puppet core Change By: Michael Smith Fix Version/s: PUP 6.3.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-1099) Bolt docs suggest you can pass params as key=value when they need to be json.
Title: Message Title Michael Smith assigned an issue to Melissa Amos Puppet Task Runner / BOLT-1099 Bolt docs suggest you can pass params as key=value when they need to be json. Change By: Michael Smith Assignee: Michael Smith Melissa Amos 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-1099) Bolt docs suggest you can pass params as key=value when they need to be json.
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-1099 Bolt docs suggest you can pass params as key=value when they need to be json. Change By: Michael Smith Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1099) Bolt docs suggest you can pass params as key=value when they need to be json.
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-1099 Bolt docs suggest you can pass params as key=value when they need to be json. 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-1103) Linux implementation of the service task returns incorrect status output
Title: Message Title
Adrian Parreiras Horta created an issue
Puppet Task Runner / BOLT-1103
Linux implementation of the service task returns incorrect status output
Issue Type:
Bug
Assignee:
Adrian Parreiras Horta
Created:
2019/01/25 1:05 PM
Priority:
Normal
Reporter:
Adrian Parreiras Horta
Currently, this implementation returns “$name $action” as the status output, instead of the status of the actual command.
$ bolt task run service --nodes pe-2019 action="" name=sshd
Started on pe-201901-master...
Started on pe-201901-agent...
Started on pe-201901-compile...
Finished on pe-201901-agent:
{
Jira (PUP-9324) Puppet agent run output to differentiate between corrective and intentional change
Title: Message Title Melissa Stone updated an issue Puppet / PUP-9324 Puppet agent run output to differentiate between corrective and intentional change Change By: Melissa Stone Fix Version/s: PUP 6.1.z 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-9324) Puppet agent run output to differentiate between corrective and intentional change
Title: Message Title Melissa Stone commented on PUP-9324 Re: Puppet agent run output to differentiate between corrective and intentional change And this has passed ci for the 6.0.x branch with puppet-agent 6.0.5.93.geeb6eb5 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-6571) An invalid path to the --logdest option is silently ignored
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6571 An invalid path to the --logdest option is silently ignored Change By: Josh Cooper Fix Version/s: PUP 5.5.z 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 thi
Jira (PUP-6571) An invalid path to the --logdest option is silently ignored
Title: Message Title Josh Cooper commented on PUP-6571 Re: An invalid path to the --logdest option is silently ignored Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/a62d30ea395278358ec92b1ac0014ef8af808e6f 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-1102) Move `unwrap_sensitive_args` to common location
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-1102 Move `unwrap_sensitive_args` to common location Issue Type: Task Assignee: Unassigned Created: 2019/01/25 11:11 AM Priority: Normal Reporter: Lucy Wyman We currently define unwrap_sensitive_args in 2 locations (lib/bolt/transport/base.rb and lib/plan_executor/orch_client.rb). We should move this function to lib/bolt/pal.rb or another common location to avoid having mismatching functions. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4258) PQL : Order By Value returns Unrecognized column 'value'
Title: Message Title
Jason Grammenos created an issue
PuppetDB / PDB-4258
PQL : Order By Value returns Unrecognized column 'value'
Issue Type:
Bug
Affects Versions:
PDB 5.2.6
Assignee:
Unassigned
Components:
PuppetDB
Created:
2019/01/25 10:59 AM
Environment:
ubuntu 16.04 puppetserver version: 5.3.6 postgresql-10 10.6-1.pgdg16.04+1
Priority:
Normal
Reporter:
Jason Grammenos
When attempting to order a puppetdb query by the fact value an error is returned saying that the column is unrecognized.
curl -X GET http://localhost:8080/pdb/query/v4 --data-urlencode 'query=fact_contents[certname,name,path,value ] { path ~> ["apt_installed","whois","version"] and !(value = "undefined") order by value}'
Unrecognized column 'value' specified in :order_by; Supported columns are 'certname', 'environment', 'path', 'name'
Jira (PDB-4257) PuppetDB skips message files with LONGNAME_HASH
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-4257 PuppetDB skips message files with LONGNAME_HASH Change By: Rob Browning Assignee: Rob Browning 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-4255) Fix deprecation warnings from clojure 1.10 upgrade
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-4255 Fix deprecation warnings from clojure 1.10 upgrade Change By: Rob Browning Assignee: Rob Browning 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-4257) PuppetDB skips message files with LONGNAME_HASH
Title: Message Title Thomas Kishel updated an issue PuppetDB / PDB-4257 PuppetDB skips message files with LONGNAME_HASH Change By: Thomas Kishel Attachment: log.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 (PDB-4257) PuppetDB skips message files with LONGNAME_HASH
Title: Message Title Thomas Kishel commented on PDB-4257 Re: PuppetDB skips message files with LONGNAME_HASH These are the commands associated with the attached log file. cd /opt/puppetlabs/server/data/puppetdb/stockpile service pe-puppetdb stop cp /tmp/78342822-1548132638857_report_8_sensu-server-i-03f0ac940c00b0a97.redactedxx.xxx.xxx.xxx_711bfaa65d298e501ef503231bc4e54b0739c167.json cmd/q/ service pe-puppetdb start service pe-puppetdb stop mv cmd/q/78342822-1548132638857_report_8_sensu-server-i-03f0ac940c00b0a97.redactedxx.xxx.xxx.xxx_711bfaa65d298e501ef503231bc4e54b0739c167.json cmd/q/78342822-1548132638857_report_8_sensu-server-i-03f0ac940c00b0a97.redactedxx.xxx.xxx.xxx.json service pe-puppetdb start
Jira (PDB-4257) PuppetDB skips message files with LONGNAME_HASH
Title: Message Title
Thomas Kishel created an issue
PuppetDB / PDB-4257
PuppetDB skips message files with LONGNAME_HASH
Issue Type:
Bug
Affects Versions:
PDB 5.2.6
Assignee:
Unassigned
Components:
PuppetDB
Created:
2019/01/25 10:11 AM
Environment:
PE 2018.1.5
Priority:
Normal
Reporter:
Thomas Kishel
Given: https://puppet.com/docs/puppetdb/5.2/pdb_support_guide.html#message-queue > Note that the certname may be altered to accommodate filesystem restrictions. Currently that means replacing the characters “/”, “:”, “", and 0 with “-“, and truncating the certname so that it’s UTF-8 encoding never exceeds about 255 characters. A truncated certname will be followed by an underscore and a hash of the full certname. PuppetDB is failing to process messages with a hashed certname in the filename with a Command has disappeared error. For example:
2019-01-25T17:48:41.687Z ERROR [p.p.queue] Command has disappeared: #puppetlabs.stockpile.queue.MetaEntry{:id 78342822, :metadata "1548132638857_report_8_sensu-server-i-03f0ac940c00b0a97.redactedxx.xxx.xxx.xxx-711bfaa65d298e501ef503231bc4e54b0739c167_1958dee5369fb75326e4b32d8876ceaf51c25d22.json"}
Jira (PUP-9364) puppet module install is really slow
Title: Message Title Josh Cooper commented on PUP-9364 Re: puppet module install is really slow Matthias Baur thanks for investigating. I suspect you have a large number or expensive facts being collected. To baseline that, how long does time puppet facts find take? 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-1101) Document potential issues with powershell module
Title: Message Title Michael Smith created an issue Puppet Task Runner / BOLT-1101 Document potential issues with powershell module Issue Type: Improvement Assignee: Unassigned Created: 2019/01/25 9:48 AM Labels: docs Priority: Normal Reporter: Michael Smith https://puppet.com/docs/pdk/1.x/install_pdk_windows.html#task-3944 has several explanations of issues you can run into on Windows: manually loading powershell modules in PSv2 and v3, execution policy restrictions. We should incorporate those into Bolt's install docs. Add Comment
Jira (BOLT-1099) Bolt docs suggest you can pass params as key=value when they need to be json.
Title: Message Title David Kramer assigned an issue to Michael Smith Puppet Task Runner / BOLT-1099 Bolt docs suggest you can pass params as key=value when they need to be json. Change By: David Kramer 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 (PUP-9336) Ensure provider suitability is always lazily evaluated
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9336 Ensure provider suitability is always lazily evaluated Change By: Josh Cooper Fix Version/s: PUP 6.2.1 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-9336) Ensure provider suitability is always lazily evaluated
Title: Message Title Josh Cooper commented on PUP-9336 Re: Ensure provider suitability is always lazily evaluated These changes were reverted in 6.0.x in f785859681 and re-reverted in 6.0.x in a6f7ff57c9. 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-864) Always upload code from bolt when running a task via Orchestrator
Title: Message Title Alex Dreyer commented on BOLT-864 Re: Always upload code from bolt when running a task via Orchestrator Sean Millichamp Is there a reason to prefer bolt for that over the puppet task cli? Are they run as part of plans? Do they run over ssh and pcp in the same commands? 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-9364) puppet module install is really slow
Title: Message Title Matthias Baur commented on PUP-9364 Re: puppet module install is really slow So I just compare Puppet 6.1 with 6.2: Puppet 6.1: mbaur(2019-01-25 09:57:39) ~ $ ls -la modules/ total 0 drwxr-xr-x 2 mbaur staff 64 Jan 25 09:57 . drwxr-xr-x+ 65 mbaur staff 2080 Jan 25 09:57 .. mbaur(2019-01-25 09:57:41) ~ $ puppet --version 6.1.0 mbaur(2019-01-25 09:57:54) ~ $ time puppet module install puppetlabs-firewall -v 1.14.0 --modulepath $HOME/modules/ Notice: Preparing to install into /Users/mbaur/modules ... Notice: Downloading from https://forgeapi.puppet.com ... Notice: Installing -- do not interrupt ...
