Jira (PUP-9794) Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9794 Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given) Change By: Josh Cooper 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313648.1561146763000.58999.1561424880910%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9794) Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9794 Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given) Change By: Josh Cooper Team: 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313648.1561146763000.58997.1561424880818%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9790) undefined method `pip_version' with pip3 provider
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9790 undefined method `pip_version' with pip3 provider Change By: Josh Cooper Team: Coremunity 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313529.1561106191000.58988.1561424820582%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9790) undefined method `pip_version' with pip3 provider
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9790 undefined method `pip_version' with pip3 provider Change By: Josh Cooper 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313529.1561106191000.58992.1561424820780%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9790) undefined method `pip_version' with pip3 provider
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9790 undefined method `pip_version' with pip3 provider Change By: Josh Cooper Fix Version/s: PUP 6.y 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313529.1561106191000.58968.1561422660357%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9790) undefined method `pip_version' with pip3 provider
Title: Message Title Josh Cooper commented on PUP-9790 Re: undefined method `pip_version' with pip3 provider The change had to be made in 5.5.x since that's where the original change was made. However, the regression was only released in 6.5.0, so that's the only fix version 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313529.1561106191000.58964.1561422601469%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1425) Document orchestrator client config options relevant to bolt
Title: Message Title
Cas Donoghue created an issue
Puppet Task Runner / BOLT-1425
Document orchestrator client config options relevant to bolt
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2019/06/24 5:29 PM
Priority:
Normal
Reporter:
Cas Donoghue
Creating this ticket as a result of trying to debug why long running tasks are timing out. Root cause was the default job-poll-timeout in https://github.com/puppetlabs/orchestrator_client-ruby/blob/master/lib/orchestrator_client/config.rb#L40 . The issue was solved by configuring that option in /etc/puppetlabs/client-tools/orchestrator.conf on the bolt controller with something like
{
"options": {
"job-poll-timeout": 2000
}
}
It is difficult (impossible?) to figure that out without looking at
Jira (PUP-9794) Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9794 Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given) Change By: Josh Cooper 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313648.1561146763000.58957.1561422601114%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9794) Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)
Title: Message Title Josh Cooper commented on PUP-9794 Re: Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given) The change had to be made in 5.5.x since that's where the original change was made. However, the regression was only released in 6.5.0, so that's the only fix version 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313648.1561146763000.58953.1561422600911%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9794) Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9794 Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given) Change By: Josh Cooper Fix Version/s: PUP 6.4.3 Fix Version/s: PUP 6.0.10 Fix Version/s: PUP 5.5.15 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. To view this discussion on the web visit
Jira (PUP-9794) Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)
Title: Message Title Josh Cooper commented on PUP-9794 Re: Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given) Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/ec423edeeb9757c275d7c1e8c611989fc95d1dc0 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313648.1561146763000.58944.1561422541364%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9790) undefined method `pip_version' with pip3 provider
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9790 undefined method `pip_version' with pip3 provider Change By: Josh Cooper 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313529.1561106191000.58934.1561422480357%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9790) undefined method `pip_version' with pip3 provider
Title: Message Title Josh Cooper commented on PUP-9790 Re: undefined method `pip_version' with pip3 provider Merged to 5.5.x in https://github.com/puppetlabs/puppet/commit/db96da38e45126e8eeae0a0d68e12479412c0015 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313529.1561106191000.58927.1561422420621%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9794) Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)
Title: Message Title Thomas Kishel commented on PUP-9794 Re: Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given) The AMI used to test is: ami-1ee65166 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313648.1561146763000.58897.1561420620557%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9790) undefined method `pip_version' with pip3 provider
Title: Message Title
Thomas Kishel commented on PUP-9790
Re: undefined method `pip_version' with pip3 provider
Found, fixed, and spec updated: https://github.com/puppetlabs/puppet/pull/7593 Even when I added a receive count to the older/incorrect stub, the test passes?
allow(@provider).to receive(:pip_version).with("/fake/bin/pip").and_return('1.0.1').exactly(99).times
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313529.1561106191000.58879.1561419060328%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9790) undefined method `pip_version' with pip3 provider
Title: Message Title Josh Cooper commented on PUP-9790 Re: undefined method `pip_version' with pip3 provider diff --git a/lib/puppet/provider/package/pip.rb b/lib/puppet/provider/package/pip.rb index ad4af1f532..a5cce507a2 100644 --- a/lib/puppet/provider/package/pip.rb +++ b/lib/puppet/provider/package/pip.rb @@ -106,7 +106,7 @@ Puppet::Type.type(:package).provide :pip, :parent => ::Puppet::Provider::Package command = resource_or_provider_command self.class.validate_command(command) -command_version = self.pip_version(command) +command_version = self.class.pip_version(command) if Puppet::Util::Package.versioncmp(command_version, '1.5.4') == -1 latest_with_old_pip else
Jira (PUP-9790) undefined method `pip_version' with pip3 provider
Title: Message Title Josh Cooper commented on PUP-9790 Re: undefined method `pip_version' with pip3 provider git bisect: 12d6bd592be53ed3916e5b90491e07a71ea81169 is the first bad commit commit 12d6bd592be53ed3916e5b90491e07a71ea81169 Author: tkishel Date: Wed Apr 3 15:05:03 2019 -0700 (PUP-1082) targetable package command With this commit, the pip package provider implements a targetable `command`. :04 04 4cdce046cae40caf8a5af2141642a5dcf399821a 1a086aa517c99ab41b50d7304352246884b68a51 M lib :04 04 5a6a79c342317db8156f7491b628424efd0df938 80a3fd706224a9290bc0305c5b925e7ee61e5e48 M spec
Jira (PUP-9790) undefined method `pip_version' with pip3 provider
Title: Message Title Josh Cooper commented on PUP-9790 Re: undefined method `pip_version' with pip3 provider This is reproducible in 5.5.x also: root@geptbdpg2wqx9ro:~/puppet# bundle exec puppet --version 5.5.15 root@geptbdpg2wqx9ro:~/puppet# bundle exec puppet apply manifest.pp Notice: Compiled catalog for geptbdpg2wqx9ro.delivery.puppetlabs.net in environment production in 0.44 seconds Notice: /Stage[main]/Main/Package[python3-pip]/ensure: created Notice: /Stage[main]/Main/Package[checkdmarc]/ensure: created Notice: Applied catalog in 23.79 seconds root@geptbdpg2wqx9ro:~/puppet# bundle exec puppet apply manifest.pp Notice: Compiled catalog for geptbdpg2wqx9ro.delivery.puppetlabs.net in environment production in 0.45 seconds Error: Could not get latest version: undefined method `pip_version' for Package[checkdmarc](provider=pip3)(command=default):Puppet::Type::Package::ProviderPip3 Error: /Stage[main]/Main/Package[checkdmarc]/ensure: change from '4.1.10' to 'latest' failed: Could not get latest version: undefined method `pip_version' for Package[checkdmarc](provider=pip3)(command=default):Puppet::Type::Package::ProviderPip3
Jira (PUP-9789) Constants assigned twice emit warning during Litmus use on Windows.
Title: Message Title Josh Cooper commented on PUP-9789 Re: Constants assigned twice emit warning during Litmus use on Windows. Thanks Jesse Scott. Along the same lines, it'd be great to no longer define methods in the FFI namespace like https://github.com/puppetlabs/pdk/blob/4b02f0c500275b2ef9ae07c36db553de4a5ed5a3/lib/pdk/util/windows/api_types.rb#L6-L32, especially if we start fixing bugs in the puppet version. Longer term, I'd like to extract the win32 specific code from puppet and into a gem that other ruby projects can use. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313352.1561054057000.58772.1561414800235%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9794) Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given)
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9794 Could not autoload puppet/provider/package/gem: superclass must be a Class (Module given) Change By: Josh Cooper Fix Version/s: PUP 6.y Fix Version/s: PUP 6.4.3 Fix Version/s: PUP 6.0.10 Fix Version/s: PUP 5.5.15 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PUP-9789) Constants assigned twice emit warning during Litmus use on Windows.
Title: Message Title Jesse Scott commented on PUP-9789 Re: Constants assigned twice emit warning during Litmus use on Windows. We have already removed the monkey patching of those constants in pdk/master and that will be going out in the next PDK release: https://github.com/puppetlabs/pdk/commit/4b02f0c500275b2ef9ae07c36db553de4a5ed5a3 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313352.1561054057000.58764.1561414560478%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9789) Constants assigned twice emit warning during Litmus use on Windows.
Title: Message Title Josh Cooper commented on PUP-9789 Re: Constants assigned twice emit warning during Litmus use on Windows. Conditionally defining a constant is asking for trouble, since some other gem could define them to different values before puppet is required, and this PR would make puppet silently ignore that problem. We should fix litmus so it doesn't reload puppet or require multiple copies of puppet. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313352.1561054057000.58736.1561413840321%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9787) Unintentional secret reveal while installing modules
Title: Message Title Jorie Tappa updated an issue Puppet / PUP-9787 Unintentional secret reveal while installing modules Change By: Jorie Tappa Team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313276.1560984349000.58596.1561408860182%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9790) undefined method `pip_version' with pip3 provider
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9790 undefined method `pip_version' with pip3 provider Change By: Josh Cooper Team: Coremunity Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313529.1561106191000.58568.1561407180786%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9790) undefined method `pip_version' with pip3 provider
Title: Message Title
Josh Cooper commented on PUP-9790
Re: undefined method `pip_version' with pip3 provider
root@azd3qyugalnzusl:~# puppet --version
6.5.0
root@azd3qyugalnzusl:~# cat manifest.pp
package { 'checkdmarc':
ensure => 'latest'
, provider => 'pip3'
, require => Package['python3-pip']
}
package { 'python3-pip':
ensure => latest
}
root@azd3qyugalnzusl:~# puppet apply manifest.pp
Notice: Compiled catalog for azd3qyugalnzusl.delivery.puppetlabs.net in environment production in 0.38 seconds
Jira (BOLT-1424) Vault plugin
Title: Message Title Lindsey Smith commented on BOLT-1424 Re: Vault plugin In case you hadn't seen this: https://github.com/voxpupuli/puppet-vault_lookup/ 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313814.1561405465000.58560.1561407120168%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1424) Vault plugin
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1424 Vault plugin Issue Type: New Feature Assignee: Unassigned Created: 2019/06/24 12:44 PM Priority: Normal Reporter: Alex Dreyer Users should be able to lookup passwords or other credential information for targets from Vault. We should document loading ssh private keys from vault in addition to a password example. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1403) Prepare bolt-server for bolt_shim removal
Title: Message Title Casey Williams commented on BOLT-1403 Re: Prepare bolt-server for bolt_shim removal https://github.com/puppetlabs/bolt/pull/1053 is up to address the second bullet point here. Once that's merged, Jonathan Morris let's sync up on the spec test part. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312897.1560810439000.58498.1561405200159%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1300) Update install docs to point to puppet-enterprise-tools repo
Title: Message Title Alex Dreyer commented on BOLT-1300 Re: Update install docs to point to puppet-enterprise-tools repo Rob Braden We really don't want users to remain on older versions of bolt. I don't want to loudly broadcast direct rpm installs since that will make it harder for less sophisticated users to upgrade. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308071.1557427938000.58481.1561405020583%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1847) Implement "cloud" fact Azure identification for Windows platform
Title: Message Title Casey Williams assigned an issue to Unassigned Facter / FACT-1847 Implement "cloud" fact Azure identification for Windows platform Change By: Casey Williams Assignee: Casey Williams 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.247441.1524674206000.58448.1561404481430%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1779) Windows 2016 container not detected as virtual=docker by facter
Title: Message Title Casey Williams assigned an issue to Unassigned Facter / FACT-1779 Windows 2016 container not detected as virtual=docker by facter Change By: Casey Williams Assignee: Casey Williams 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.216080.1507889554000.58455.1561404481770%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1409) Remove 'lookups' from 'target_lookups'
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1409
Remove 'lookups' from 'target_lookups'
Change By:
Alex Dreyer
Release Notes Summary:
This deprecates the {{target-lookups}} key in the experimental inventory file v2. Users should migrate any {{target-lookups}} entries to {{targets}} and move the {{plugin}} key in each entry to {{_plugin}}. d
Release Notes:
Deprecation
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313045.1560895034000.58404.1561403040296%40Atlassian.JIRA.
For more options, visit
Jira (BOLT-1318) Modulepath unable to handle folder names in uppercase characters on Windows
Title: Message Title Cas Donoghue commented on BOLT-1318 Re: Modulepath unable to handle folder names in uppercase characters on Windows yeah, 1.24.0 installed from MSI 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309321.1558130157000.58218.1561398601042%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1318) Modulepath unable to handle folder names in uppercase characters on Windows
Title: Message Title Kevin Reeuwijk commented on BOLT-1318 Re: Modulepath unable to handle folder names in uppercase characters on Windows Cas Donoghue is that with the latest Bolt version? Because it seems this issue is then fixed in the latest version... This output is encouraging, as it was shown in all lower case in an older Bolt version: MODULEPATH: C:/DATA/modules:C:/DATA/site-modules:C:/DATA/site 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309321.1558130157000.58172.1561397820600%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1300) Update install docs to point to puppet-enterprise-tools repo
Title: Message Title Rob Braden commented on BOLT-1300 Re: Update install docs to point to puppet-enterprise-tools repo We could, similar to PDK, have a page on the web site that links directly to the packages? Would that solve these issues? https://puppet.com/download-puppet-development-kit I'm happy to rethink our repos/download infrastructure but I think we should take a wider view. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308071.1557427938000.58135.1561397340636%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1318) Modulepath unable to handle folder names in uppercase characters on Windows
Title: Message Title Cas Donoghue commented on BOLT-1318 Re: Modulepath unable to handle folder names in uppercase characters on Windows Kevin Reeuwijk I'm having trouble reproducing the case you mention (vmpooler win-10-pro) PS C:\DATA> New-Item -Type File -Path bolt.yaml -Force Directory: C:\DATA ModeLastWriteTime Length Name - -- -a6/24/2019 5:03 PM 0 bolt.yaml PS C:\DATA> ls
Jira (PUP-9719) Cannot run Puppet Agent as Administrator if first PA run is done as System
Title: Message Title John O'Connor commented on PUP-9719 Re: Cannot run Puppet Agent as Administrator if first PA run is done as System The issue is the first Puppet Agent run regardless of whether System or Administrator was used to install, so again - it looks to be a Puppet Agent issue and not an MSI installer issue. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310162.1558726819000.57800.1561388340271%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9719) Cannot run Puppet Agent as Administrator if first PA run is done as System
Title: Message Title John O'Connor updated an issue Puppet / PUP-9719 Cannot run Puppet Agent as Administrator if first PA run is done as System Change By: John O'Connor Summary: Can't Cannot run puppet agent after installing the MSI using the SYSTEM account Puppet Agent as Administrator if first PA run is done as System 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310162.1558726819000.57791.1561388281177%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9719) Cannot run Puppet Agent as Administrator if first PA run is done as System
Title: Message Title
John O'Connor updated an issue
Puppet / PUP-9719
Cannot run Puppet Agent as Administrator if first PA run is done as System
Change By:
John O'Connor
*Puppet Version:* 6.4.2 *Puppet Server Version:* N/A *OS Name/Version:* Windows Server 2016 x64When installing Puppet Agent (6.4.2/PE 2019.1.0) on Server 2016 using a Powershell script running as the SYSTEM account, Administrator users can't run Puppet. Daemon/service runs are performed as expected. Direct Puppet runs appear to occur but no report is sent to the master. *UPDATE* - It the first Run as SYSTEM that is the problem - so have changed ticket title. PUP-8939 had reportedly solved this issue.*Desired Behavior:**note* - you need to use {{psexec -s}} to repro this on {{vmpooler}} nodes to ensure the SYSTEM account is used:1. Install: {{psexec -s -i "msiexec.exe" /qn /norestart /l*v C:\windows\temp\puppetinstall.log /i C:\Users\Administrator\Downloads\puppet-agent-6.4.2-x64.msi PUPPET_AGENT_STARTUP_MODE=Manual}}2. Run PA {{psexec -s "C:\Program Files\Puppet Labs\Puppet\bin\puppet.bat" agent -t}} 1. Download the Agent 6.4.2 x64 MSI to a temp path (in this example, {{C:\temp\puppet\puppet-agent-x64.msi}}). 2. Install Puppet Agent on a Server 2016 node as the SYSTEM user by running {{start-process -filepath "msiexec.exe" -arg "/qn /norestart /l*v C:\windows\temp\puppetinstall.log /i c:\temp\puppet\puppet-agent-x64.msi PUPPET_AGENT_STARTUP_MODE=Manual" -Wait}} 3. Populate csr_attributes.yml and {{server}} in the agent config as necessary. 4. As an Administrator, run {{puppet agent --test}} on the newly installed agent.*Actual Behavior:*Catalog retrieval fails; log has been redacted:{code}2019-05-21 17:20:36 -0400 Puppet (debug): HTTP POST https://compiler.example.net:8140/puppet/v3/catalog/examplenode.example.net returned 200 OK2019-05-21 17:20:36 -0400 Puppet (debug): Caching connection for https://compiler.example.net:81402019-05-21 17:20:36 -0400 Puppet (info): Caching catalog for examplenode.example.net2019-05-21 17:20:38 -0400 Puppet (err): ReplaceFile(C:/ProgramData/PuppetLabs/puppet/cache/client_data/catalog/examplenode.example.net.json, C:/ProgramData/PuppetLabs/puppet/cache/client_data/catalog/examplenode.example.net.json20190521-6580-blokpv): Access is denied. c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/file.rb:89:in `replace_file'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util.rb:636:in `replace_file'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/indirector/json.rb:17:in `save'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/indirector/indirection.rb:200:in `find'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:466:in `block in retrieve_new_catalog'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util.rb:518:in `block in thinmark'c:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/2.5.0/benchmark.rb:308:in `realtime'c:/Program Files/Puppet
Jira (BOLT-1423) Bolt actions hang over ssh transport when ProxyCommand is set in openssh config
Title: Message Title Cas Donoghue created an issue Puppet Task Runner / BOLT-1423 Bolt actions hang over ssh transport when ProxyCommand is set in openssh config Issue Type: Bug Assignee: Unassigned Created: 2019/06/24 7:40 AM Priority: Normal Reporter: Cas Donoghue When trying to run a task on Server A the output stop after printing Started on $HOSTNAME..., no output is printed and bolt does not return to the shell. The same command works on Server B, it prints Finished on $HOSTNAME, the stdout of the task and the final report. The only difference between Server A and B is the fact, that Server A uses the follwoing SSH config ProxyCommand ssh $PROXY netcat -w 120 %h %p User root As reported in https://github.com/puppetlabs/bolt/issues/666 The net-ssh ruby library will read the https://github.com/net-ssh/net-ssh/blob/master/lib/net/ssh/config.rb#L32 perhaps there are other settings we need in order for that to work as expected.
Jira (PUP-9719) Can't run puppet agent after installing the MSI using the SYSTEM account
Title: Message Title John O'Connor commented on PUP-9719 Re: Can't run puppet agent after installing the MSI using the SYSTEM account So - Summarising - the following files are missing Administrator permissions: C:\ProgramData\PuppetLabs\puppet\cache\client_data\catalog\umtzu5243z6go5b.delivery.puppetlabs.net.json NT AUTHORITY\SYSTEM:(F) Everyone:(Rc,S,RA) C:\ProgramData\PuppetLabs\puppet\cache\state\last_run_report.yaml NT AUTHORITY\SYSTEM:(F) Everyone:(Rc,S,RA) C:\ProgramData\PuppetLabs\puppet\cache\state\last_run_summary.yaml NT AUTHORITY\SYSTEM:(F) Everyone:(R) C:\ProgramData\PuppetLabs\puppet\cache\state\state.yaml NT AUTHORITY\SYSTEM:(F) Everyone:(Rc,S,RA)
Jira (PUP-9719) Can't run puppet agent after installing the MSI using the SYSTEM account
Title: Message Title John O'Connor commented on PUP-9719 Re: Can't run puppet agent after installing the MSI using the SYSTEM account I have done an icacls dump of the puppet directory once the first puppet run is over - it comes to 2000+ lines so have saved this in a GIST at: https://gist.github.com/jcoconnor/6078f7898d1eb91e57155d2cdef4ab55 Excluding the directory tree C:\ProgramData\PuppetLabs\puppet\cache\lib, the pruned output is below: C:\ProgramData\PuppetLabs\puppet NT AUTHORITY\SYSTEM:(OI)(CI)(F) BUILTIN\Administrators:(OI)(CI)(F) C:\ProgramData\PuppetLabs\puppet\cache NT AUTHORITY\SYSTEM:(OI)(CI)(F) BUILTIN\Administrators:(OI)(CI)(F) C:\ProgramData\PuppetLabs\puppet\etc NT AUTHORITY\SYSTEM:(I)(OI)(CI)(F) BUILTIN\Administrators:(I)(OI)(CI)(F) C:\ProgramData\PuppetLabs\puppet\var NT AUTHORITY\SYSTEM:(I)(OI)(CI)(F) BUILTIN\Administrators:(I)(OI)(CI)(F)
Jira (PUP-9719) Can't run puppet agent after installing the MSI using the SYSTEM account
Title: Message Title John O'Connor commented on PUP-9719 Re: Can't run puppet agent after installing the MSI using the SYSTEM account Some further data - icacls of puppet data directory immediately following Puppet Installation: PS C:\ProgramData\PuppetLabs> icacls puppet /t puppet NT AUTHORITY\SYSTEM:(OI)(CI)(F) BUILTIN\Administrators:(OI)(CI)(F) puppet\etc NT AUTHORITY\SYSTEM:(I)(OI)(CI)(F) BUILTIN\Administrators:(I)(OI)(CI)(F) puppet\var NT AUTHORITY\SYSTEM:(I)(OI)(CI)(F) BUILTIN\Administrators:(I)(OI)(CI)(F) puppet\etc\csr_attributes.yaml NT AUTHORITY\SYSTEM:(I)(F) BUILTIN\Administrators:(I)(F)
Jira (BOLT-1318) Modulepath unable to handle folder names in uppercase characters on Windows
Title: Message Title Kevin Reeuwijk commented on BOLT-1318 Re: Modulepath unable to handle folder names in uppercase characters on Windows except that the auto-generated modulepath is all lowercase, see the original ticket info: ```User has this Bolt project folder: `C:\DATA\workshop` with a bolt.yaml in it and subsequently the modulepath becomes c:/data/workshop/modules``` Notice that the modulepath didn't become `c:/DATA/workshop/modules`, but `c:/data/workshop/modules` So a quick fix could be to correctly auto-generate the modulepath so that it honors the source case of characters. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309321.1558130157000.57633.1561381380911%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9748) Puppet Device doesn't honor ENC-set Environment in 5.5.10 or later
Title: Message Title David Mallon commented on PUP-9748 Re: Puppet Device doesn't honor ENC-set Environment in 5.5.10 or later David Schmitt - I might need some help from you on this one to 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312177.1560307583000.57530.1561375020162%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
