Jira (PUP-10950) unless should support sensitive data for any type
Title: Message Title David Schmitt commented on PUP-10950 Re: unless should support sensitive data for any type This issue is affecting customers deploying the recent security-related postgresql release (see https://github.com/puppetlabs/puppetlabs-postgresql/pull/1249 for details). Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.389976.1614881718000.158343.1614951480079%40Atlassian.JIRA.
Jira (PUP-10954) .gemspec doesn't fulfill its stated goal
Title: Message Title David Schmitt created an issue Puppet / PUP-10954 .gemspec doesn't fulfill its stated goal Issue Type: Bug Affects Versions: PUP 6.21.1, PUP 7.4.0 Assignee: Unassigned Created: 2021/03/05 5:19 AM Priority: Normal Reporter: David Schmitt Puppet Version: git repo, main and 6.x branch The .gemspec file claims it is "intended for use with bundler when Puppet is a dependency of another project", but is not reflecting the correct gem dependencies as uploaded to rubygems. Desired Behavior: Referencing the puppet repository in a Gemfile pulls all gems required by puppet and packaged in the agent. Actual Behavior: Referencing the puppet repository in a Gemfile doesn't pull in the win32-* dependencies that https://rubygems.org/gems/puppet/versions/6.21.1-x64-mingw32 has. Context: This was found during the analysis of MODULES-10963. Add Comment
Jira (PUP-10924) `module install` can't unpack modules with long paths because of minitar bug
Title: Message Title David Schmitt created an issue Puppet / PUP-10924 `module install` can't unpack modules with long paths because of minitar bug Issue Type: Bug Affects Versions: PUP 7.3.0, PUP 6.21.1 Assignee: Unassigned Created: 2021/02/18 1:00 AM Priority: Normal Reporter: David Schmitt Puppet Version: 6.21.1 but because of minitar 0.9 origins, likely also relevant to all other recent releases. OS Name/Version: xenial Trying to install modules with puppet module install when the module contains deeply nested paths fails with a minitar error. See https://github.com/puppetlabs/puppet-modulebuilder/pull/37 for the puppet-modulebuilder code changes to trigger this; See https://travis-ci.com/github/puppetlabs/puppet-modulebuilder/jobs/484161960#L423-L430 for the test results. Desired Behavior: Puppet should be able to install all valid modules. Actual Behavior: puppet module install fails with Failed to install the module using Puppet. Exit code 1: Notice: Preparing to install into /tmp/d20210218-7106-kfle20 ... Error: "/1234567890" is not a valid octal string Error: Try 'puppet help module install' for usage
Jira (PUP-10885) Race-condition in service resource
Title: Message Title David Schmitt created an issue Puppet / PUP-10885 Race-condition in service resource Issue Type: Bug Assignee: Unassigned Attachments: wsusclient-service-errors.json Components: Types and Providers Created: 2021/02/03 2:21 AM Priority: Normal Reporter: David Schmitt Puppet Version: latest puppet5; puppet6 nightlies Puppet Server Version: n/a OS Name/Version: windows during wsus_client acceptance testing, approximately 10% of all tries to manage the wuauserv service fail with the service resource being confused about the state transitions of the service: Error: /Stage[main]/Wsus_client/Service[wuauserv]: Failed to call refresh: Failed to transition the wuauserv service to the SERVICE_STOPPED state. Detail: Unexpected transition to the SERVICE_RUNNING state while waiting for the pending transition from SERVICE_STOP_PENDING to SERVICE_STOPPED to finish. Error: /Stage[main]/Wsus_client/Service[wuauserv]: Failed to transition the wuauserv service to the SERVICE_STOPPED state. Detail: Unexpected transition to the SERVICE_RUNNING state while waiting for the pending transition from SERVICE_STOP_PENDING to SERVICE_STOPPED to finish. C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/service.rb:940:in `block (2 levels) in wait_on_pending_state' C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/service.rb:735:in `block (2 levels) in query_status' C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/service.rb:723:in `initialize' C:/Program Files/Puppet Labs/Puppet/puppet/lib/ruby/vendor_ruby/puppet/util/windows/service.rb:723:in `new'
Jira (FACT-2880) facter 4 differing output from facter 3 for service_provider fact
Title: Message Title David Schmitt commented on FACT-2880 Re: facter 4 differing output from facter 3 for service_provider fact we have precedence of writing rubocop plugins for important issues. Theoretically this should be quite easy to detect. cc Ben Ford for prioritisation. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.379364.1606744776000.92192.1607336820039%40Atlassian.JIRA.
Jira (FACT-2682) facter -p returns NUL character on stdout when called from nested ruby on windows
Title: Message Title David Schmitt created an issue Facter / FACT-2682 facter -p returns NUL character on stdout when called from nested ruby on windows Issue Type: Bug Assignee: Unassigned Components: Windows Created: 2020/06/24 12:15 PM Environment: Personally reproduced with puppet 6.16.0, facter 3.14.11 (commit ed6c9052b125bee55f21f43d55f790c08ec75c1c), windows server 2019 (gusztavvargadr/windows-server) as well as the hydra demo environment. See the linked tickets for more tangential reproduction environments going back to 2019.2.1. Priority: Normal Reporter: David Schmitt As result of the investigation into MODULES-10602 and FM-8887, it was found that facter misbehaves on windows when being called from another ruby process while at the same time also executing other processes: When deploying the following fact to C:\ProgramData\PuppetLabs\puppet\cache\lib\facter\debugg.rb Facter.add(:debugg) do setcode do puts `cmd /c echo bar`.inspect
Jira (PUP-7197) make type aliases from modules available on the agent
Title: Message Title
David Schmitt commented on PUP-7197
Re: make type aliases from modules available on the agent
Josh Cooper your comment about the stdlib types not being in the "correct" directory seems to raise another issue: as the stdlib types are laid out currently works with puppet apply:
david@zion:~/git/puppetlabs-stdlib (master)$ ls spec/fixtures/modules/stdlib/types/
absolutepath.pp compat filesource.pp httpsurl.pp mac.pp port unixpath.pp
base32.ppensure fqdn.pphttpurl.pp objectstore port.ppwindowspath.pp
base64.ppfilemode.pp host.ppip objectstore.pp syslogfacility.pp yes_no.pp
david@zion:~/git/puppetlabs-stdlib (master)$ pdk bundle exec puppet apply --modulepath spec/fixtures/modules --verbose -e 'notice("https://foo" =~ Stdlib::HTTPSUrl)'
pdk (INFO): Using Ruby 2.5.7
pdk (INFO): Using Puppet 6.13.0
Info: Loading facts
Info: Loading facts
Notice: Scope(Class[main]): true
Notice: Compiled catalog for zion in environment production in 0.05 seconds
Jira (FACT-2565) Debian development versions cause fatal error when resolving os.release
Title: Message Title David Schmitt commented on FACT-2565 Re: Debian development versions cause fatal error when resolving os.release works for me: operatingsystem => Debian operatingsystemmajrelease => bullseye/sid operatingsystemrelease => bullseye/sid osfamily => Debian Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups
Jira (PUP-10428) Puppet parser only consider first element of array for properties in custom provider
Title: Message Title David Schmitt commented on PUP-10428 Re: Puppet parser only consider first element of array for properties in custom provider To answer the question for the Resource API side, I've enhanced the tests in https://github.com/puppetlabs/puppet-resource_api/pull/269 to show that even with an Any-typed attribute, the handling of array-valued arguments works. Given the complexity of interactions between Resource API and the low-level APIs, I can't say that the behaviour shown in the tests gives any indication for what should or would be happening in a manual implementation of the low-level API. Dan33l as I already said on slack yesterday, I'm happy to answer specific questions there, and if they're recurring question I'll also make sure the answers get integrated into the existing docs, and that's all I can currently promise given staffing levels and company priorities. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356064.1587390623000.42793.1587479580140%40Atlassian.JIRA.
Jira (FACT-2565) Debian development versions cause fatal error when resolving os.release
Title: Message Title David Schmitt updated an issue Facter / FACT-2565 Debian development versions cause fatal error when resolving os.release Change By: David Schmitt Affects Version/s: FACT 4.0.14 Affects Version/s: FACT 4.0.15 Affects Version/s: FACT 4.0.16 Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.356068.158739506.41727.1587395220026%40Atlassian.JIRA.
Jira (FACT-2565) Debian development versions cause fatal error when resolving os.release
Title: Message Title David Schmitt created an issue Facter / FACT-2565 Debian development versions cause fatal error when resolving os.release Issue Type: Bug Assignee: Unassigned Created: 2020/04/20 8:04 AM Environment: Debian bullseye/sid Priority: Normal Reporter: David Schmitt When running facter on Debian bullseye/sid, the code in https://github.com/puppetlabs/facter-ng/blob/b4917e6244b044bbb1cfa646f4e2fa85f3b12b4e/lib/facts/debian/os/release.rb#L16-L20 fails, because while - in contrast to FACT-2475 - determine_release_for_os does return a value, it does not match facter's expectations. To illustrate, here's the key values from the linked function: fact_value: "bullseye/sid" versions: ["bullseye/sid"] without versions[1] having a value, the gsub fails with the following exception: david@zion:~/git/puppetlabs-motd (master)$ ruby2.5 /usr/bin/bundle
Jira (FACT-2478) Unit tests on puppetlabs_apache modules fails with facter 4
Title: Message Title David Schmitt updated an issue Facter / FACT-2478 Unit tests on puppetlabs_apache modules fails with facter 4 Change By: David Schmitt Comment: does that mean we can revert https://github.com/puppetlabs/puppetlabs-apache/pull/2013 ? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.350533.1584608952000.17163.1584717420043%40Atlassian.JIRA.
Jira (FACT-2478) Unit tests on puppetlabs_apache modules fails with facter 4
Title: Message Title David Schmitt commented on FACT-2478 Re: Unit tests on puppetlabs_apache modules fails with facter 4 does that mean we can revert https://github.com/puppetlabs/puppetlabs-apache/pull/2013 ? Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.350533.1584608952000.17160.1584717300054%40Atlassian.JIRA.
Jira (PUP-3630) The compiler does not process metaparameter inheritance for resources declared outside of Class[main]
Title: Message Title David Schmitt updated an issue Puppet / PUP-3630 The compiler does not process metaparameter inheritance for resources declared outside of Class[main] Change By: David Schmitt Affects Version/s: PUP 5.5.12 Affects Version/s: PUP 6.12.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.57919.1415306898000.32363.1582145883925%40Atlassian.JIRA.
Jira (PUP-3630) The compiler does not process metaparameter inheritance for resources declared outside of Class[main]
Title: Message Title David Schmitt commented on PUP-3630 Re: The compiler does not process metaparameter inheritance for resources declared outside of Class[main] A community member on slack and I just rediscovered this problem in PUP-10301. It's still alive and kicking in both puppet 5 and 6. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.57919.1415306898000.32346.1582145821008%40Atlassian.JIRA.
Jira (PUP-10301) noop metaparam on defined ignored inside of classes
Title: Message Title David Schmitt updated an issue Puppet / PUP-10301 noop metaparam on defined ignored inside of classes Change By: David Schmitt Affects Version/s: PUP 5.5.12 Affects Version/s: PUP 6.12.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.346687.1582115895000.31156.1582118103580%40Atlassian.JIRA.
Jira (PUP-10301) noop metaparam on defined ignored inside of classes
Title: Message Title
David Schmitt created an issue
Puppet / PUP-10301
noop metaparam on defined ignored inside of classes
Issue Type:
Bug
Assignee:
Unassigned
Components:
Catalog Application
Created:
2020/02/19 4:38 AM
Priority:
Normal
Reporter:
David Schmitt
Puppet Version: 5.5.12 and 6.12.0 Puppet Server Version: n/a OS Name/Version: n/a In specific situations the noop metaparameter is ignored.
define testop {
notify{$name: }
}
class test {
testop { 'foo':
Jira (PUP-7197) make type aliases from modules available on the agent
Title: Message Title David Schmitt commented on PUP-7197 Re: make type aliases from modules available on the agent Josh Cooper how much effort would it be to add the types module directory to pluginsync and how much more load would it put on the puppetserver? I've done a quick survey of supported and voxpupuli modules: accounts, apache, apt, ntp and stdlib have 62 type aliases together (more than half of that in stdlib) voxpupuli has 32 (out of 134) modules with aggregate 209 aliases looking over the results, I've also noticed that the files are not properly namespaced (i.e. Stdlib::Base64 is in puppetlabs-stdlib/types/base64.pp (instead of puppetlabs-stdlib/types/stdlib/base64.pp) so a naive pluginsync would lead to potential problems, if another module also has a base64.pp type alias. Maybe a stupid idea, but would it be possible/feasible to generate a PCore representation of all those aliases in a single file that gets sent to the agent instead? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.174775.1486632721000.30923.1582106520324%40Atlassian.JIRA.
Jira (BOLT-1535) Error with bolt when running Concat module against windows machines
Title: Message Title David Schmitt updated an issue Puppet Task Runner / BOLT-1535 Error with bolt when running Concat module against windows machines Change By: David Schmitt Labels: impacts_content 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.344205.1580376983000.6229.1580379180127%40Atlassian.JIRA.
Jira (PUP-10220) puppet device runs do not currently show errors when performed without --debug option
Title: Message Title David Schmitt commented on PUP-10220 Re: puppet device runs do not currently show errors when performed without --debug option Moved it to the public tracker, as this is affecting OSP 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.304466.1554994063000.14364.1578412020583%40Atlassian.JIRA.
Jira (PUP-10220) puppet device runs do not currently show errors when performed without --debug option
Title: Message Title David Schmitt moved an issue Puppet / PUP-10220 puppet device runs do not currently show errors when performed without --debug option Change By: David Schmitt Key: FM PUP - 7956 10220 Project: Modules [Internal] 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.304466.1554994063000.14360.1578412020407%40Atlassian.JIRA.
Jira (PDOC-183) Puppet Strings 2.0.0
Title: Message Title David Schmitt updated an issue Puppet Strings / PDOC-183 Puppet Strings 2.0.0 Change By: David Schmitt Labels: iac_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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.220059.1509641082000.10797.1577971680403%40Atlassian.JIRA.
Jira (PUP-7435) Add support for snap packages
Title: Message Title David Schmitt commented on PUP-7435 Re: Add support for snap packages FTR I'd like to emphasise that Igor Galić and my discussion was specifically about the difficulties putting snap support into the package type as a provider. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.184760.1491554952000.9782.1577697840171%40Atlassian.JIRA.
Jira (PUP-10025) puppet describe does not show top-level docs
Title: Message Title David Schmitt updated an issue Puppet / PUP-10025 puppet describe does not show top-level docs Change By: David Schmitt 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.246931.1524479943000.41631.1574344200163%40Atlassian.JIRA.
Jira (PUP-10025) puppet describe does not show top-level docs
Title: Message Title David Schmitt commented on PUP-10025 Re: puppet describe does not show top-level docs fix was merged in https://github.com/puppetlabs/puppet-resource_api/pull/247 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.246931.1524479943000.38367.1574181540616%40Atlassian.JIRA.
Jira (PUP-10025) puppet describe does not show top-level docs
Title: Message Title David Schmitt commented on PUP-10025 Re: puppet describe does not show top-level docs PUP-2641 does not happen in 6.10.1 anymore (I've manually removed the last "." from the java_ks type to test): david@davids:~/git/puppetlabs-java_ks$ bundle exec puppet describe --libdir ./lib java_ks | head java_ks === Manages the entries in a java keystore, and uses composite namevars to accomplish the same alias spread across multiple target keystores Parameters -- david@davids:~/git/puppetlabs-java_ks$ puppet --version 6.10.1
Jira (FACT-2059) premature loading of module-provided facts under `-p`
Title: Message Title David Schmitt updated an issue Facter / FACT-2059 premature loading of module-provided facts under `-p` Change By: David Schmitt Affects Version/s: FACT 3.13.2 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.328315.1570469412000.131936.1570469580071%40Atlassian.JIRA.
Jira (FACT-2059) premature loading of module-provided facts under `-p`
Title: Message Title David Schmitt created an issue Facter / FACT-2059 premature loading of module-provided facts under `-p` Issue Type: Bug Assignee: Unassigned Attachments: 2019-10-07_18MS+0100_2069x1151.png Created: 2019/10/07 10:30 AM Environment: ciscopuppet module, facter 3.13.2 (commit a34181878), windows 2016 x64 (gnocchi.platform9.puppet.net) Priority: Normal Reporter: David Schmitt When running facter -p on windows with the puppetlabs/ciscopuppet module pluginsynced to the agent, facter is loading facter/cisco.rb from C:/ProgramData/PuppetLabs/puppet/cache/lib before setting up the $LOAD_PATH to load that file's dependencies from there. Please see the attached screenshot for the debug modifications I did and the results on the machine showing the issue. To make sure there is nothing wonky with the facter/cisco_nexus file itself, a require within a setcode worked fine. Regular agent runs work fine and do not show any errors. Desired Behaviour facter -p loads files from puppet's cache only once, after $LOAD_PATH has been properly initialised.
Jira (PDOC-291) Build reference doc for transport schemas
Title: Message Title
David Schmitt updated an issue
Puppet Strings / PDOC-291
Build reference doc for transport schemas
Change By:
David Schmitt
To make use of the new Resource API transport schema information, puppet-strings should read and render the information from {{ register_transport }} to the REFERENCE.md.The existing code for parsing {{ register_type }} can be used as a template.
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.296968.1550757016000.110953.1569321840110%40Atlassian.JIRA.
Jira (PDOC-291) Build reference doc for transport schemas
Title: Message Title David Schmitt moved an issue Puppet Strings / PDOC-291 Build reference doc for transport schemas Change By: David Schmitt Key: FM PDOC - 7816 291 Project: Modules [Internal] Puppet Strings 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.296968.1550757016000.110952.1569321780136%40Atlassian.JIRA.
Jira (PUP-2968) Make it possible to namespace ruby-defined custom types
Title: Message Title David Schmitt assigned an issue to Unassigned Puppet / PUP-2968 Make it possible to namespace ruby-defined custom types Change By: David Schmitt Team: Network Automation Coremunity Assignee: David Schmitt 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.43382.1406157609000.110932.1569320460303%40Atlassian.JIRA.
Jira (PUP-10025) puppet describe does not show top-level docs
Title: Message Title David Schmitt updated an issue Puppet / PUP-10025 puppet describe does not show top-level docs Change By: David Schmitt Team: Network Automation 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.246931.1524479943000.105529.1568893200131%40Atlassian.JIRA.
Jira (PUP-10025) puppet describe does not show top-level docs
Title: Message Title David Schmitt commented on PUP-10025 Re: puppet describe does not show top-level docs this is also tracked in https://github.com/puppetlabs/puppet-resource_api/issues/208 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.246931.1524479943000.105527.1568893140117%40Atlassian.JIRA.
Jira (PUP-10025) puppet describe does not show top-level docs
Title: Message Title David Schmitt updated an issue Puppet / PUP-10025 puppet describe does not show top-level docs Change By: David Schmitt Affects Version/s: PUP 6.9.0 Affects Version/s: PUP 5.5.16 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.246931.1524479943000.105525.1568893080238%40Atlassian.JIRA.
Jira (PUP-10025) puppet describe does not show top-level docs
Title: Message Title David Schmitt moved an issue Puppet / PUP-10025 puppet describe does not show top-level docs Change By: David Schmitt Key: PDK PUP - 945 10025 Project: Puppet Development Kit 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.246931.1524479943000.105510.1568890380158%40Atlassian.JIRA.
Jira (PUP-9994) External/Extended trusted data
Title: Message Title David Schmitt assigned an issue to David Schmitt Puppet / PUP-9994 External/Extended trusted data Change By: David Schmitt Assignee: David Schmitt 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.323248.1567522563000.82757.1567526412323%40Atlassian.JIRA.
Jira (PUP-9994) External/Extended trusted data
Title: Message Title David Schmitt created an issue Puppet / PUP-9994 External/Extended trusted data Issue Type: Improvement Assignee: Unassigned Created: 2019/09/03 7:56 AM Priority: Normal Reporter: David Schmitt To facilitate enhancing catalog compilation with dynamic trusted data from third parties (i.e. not the ENC or the agent), this change adds $trusted_ext. The data gets loaded from the indirector (currently only through calling a script that needs to return JSON). This is an experimental feature. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1377) Include networking gem in bolt dependencies.
Title: Message Title David Schmitt commented on BOLT-1377 Re: Include networking gem in bolt dependencies. re-opened as https://github.com/puppetlabs/bolt-vanagon/issues/115 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311783.1560160088000.73573.1566898680201%40Atlassian.JIRA.
Jira (PUP-8736) /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs
Title: Message Title David Schmitt updated an issue Puppet / PUP-8736 /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs Change By: David Schmitt Release Notes Summary: Prior to this change, Puppet device certificates were stored under the cache directory. When the proxy Puppet agent for a device is the master, and the user executes a backup and restore (manually, or as automated in OpsWorks), the certificate and keys are lost, requiring certificate regeneration for those devices.This fix moves the device certificate directory to a persistent path, leaving the old path as a symbolic link for compatibility purposes. If you are using the `device_manager` module to manage your devices, please make sure to upgrade to 3.0.1 or later to avoid a bug deleting certificates from their new location. 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 view this discussion on the web visit
Jira (PUP-9926) "Failed to apply catalog: undefined method `each' for #"
Title: Message Title
David Schmitt updated an issue
Puppet / PUP-9926
"Failed to apply catalog: undefined method `each' for #"
Change By:
David Schmitt
*Puppet Version:* 6.7.0*Puppet Server Version:* n/a*OS Name/Version:* n/aThe ciscopuppet acceptance tests fail on trivial catalogs with "Error: Failed to apply catalog: undefined method `each' for #", due to https://github.com/puppetlabs/puppet/commit/6c257fc7827989c2af2901f974666f0f23611153#diff-7f00f7dbc0f9bfecbaadfec966d0b8b1L2149 . Specifically, the change from {{[list]}} to {{Array(list)}} in the chunk linked.Observe the following pry example to show the issue:{code}[10] pry(main)> class Foo[10] pry(main)* include Enumerable[10] pry(main)* end => Foo[11] pry(main)> Foo.new.to_aNoMethodError: undefined method `each' for #from (pry):13:in `to_a'[12] pry(main)> Array(Foo.new)NoMethodError: undefined method `each' for #from (pry):14:in `to_a'[13] pry(main)> [Foo.new]=> [#][14] pry(main)> class Foo2[14] pry(main)* end => nil[15] pry(main)> Array(Foo2.new)=> [#][16] pry(main)> {code}This can be traced back to https://github.com/puppetlabs/puppet/blob/0c34993f87f100f3bbbccfbb5b000a51094fce5e/lib/puppet/type.rb#L2276 without having a `each` method. This bug was introduced in 2005 (see my previous unrelated analysis of this in https://twitter.com/dev_el_ops/status/1141814653653311489?s=19).*Desired Behavior:*Puppet not failing on a ruby error.*Actual Behavior:*Puppet failing on a ruby error. Full stacktrace from https://jenkins-master-prod-1.delivery.puppetlabs.net/view/modules/view/networking/view/ciscopuppet/job/forge-netdev_cisco-ciscopuppet_intn-sys_smoke-develop/lastFailedBuild/PLATFORM=cisconx-64default.%257Bssh%253D%257Buser%253Dadmin%252Cpassword%253Dadmin%257D%257D,WORKER_LABEL=beaker/consoleFull : {code}00:06:07.170 * TestStep :: 1.1 Apply default manifest with 'default' as a string in attributes [ensure => present] :: MANIFEST00:06:07.170 test_manifest :: manifest:00:06:07.171 000:06:07.171 test_manifest :: check puppet apply cmd (code: [0, 2])00:06:07.171 00:06:16.260 cisco_tacacs_server { 'default': ensure => present }00:06:16.260 00:06:16.260 cisco_aaa_authorization_login_cfg_svc { 'default':00:06:16.260 00:06:16.260 ensure => 'present',00:06:16.260 groups => 'default',00:06:16.260 method => 'default',00:06:16.260 00:06:16.260 }00:06:16.260 Notice: Compiled catalog for sut in environment production in 0.12 seconds00:06:16.271 Info: Applying configuration version '1564016874'00:06:16.271 Error: Failed to apply catalog: undefined method `each' for #00:06:16.271 /tmp/jenkins/workspace/forge-netdev_cisco-ciscopuppet_intn-sys_smoke-develop/PLATFORM/cisconx-64default.%7Bssh%3D%7Buser%3Dadmin%2Cpassword%3Dadmin%7D%7D/WORKER_LABEL/beaker/.bundle/gems/gems/puppet-6.7.0/lib/puppet/type.rb:2190:in `to_a'00:06:16.271
Jira (PUP-8564) resource api transports - add support for custom remote facts
Title: Message Title
David Schmitt updated an issue
Puppet / PUP-8564
resource api transports - add support for custom remote facts
Change By:
David Schmitt
Since none of the remote content goes through facter - and the local execution model of facter also doesn't lend itself to extension, `puppet device` directly delegates facts collection to the {{Device}} class. In the course of this, the possibility for customers to inject custom facts has been lost.With the advent of Resource API Transports, we now have a architectural fault line where we can re-insert that capability.-Specifically customers want to be able to get the IP address of their IOS devices as a fact.- moved to MODULES-9459* custom remote facts go to {{lib/puppet/remote_facts/TRANSPORT/NAME.rb}}, and can be deployed through any module* custom remote facts never get loaded on the server* puppet device and friends load all custom remote facts for the current transport* custom remote facts directly interact with the transport and can modify the facts hash at will (add/delete/modify)* custom remote facts need to ensure they do not interfere with each other{code:ruby}# lib/puppet/remote_facts/cisco_ios/ifspeeds.rbrequire 'puppet/resource_api/transport'require 'puppet_x/customer/site/cisco_ios_utility'Puppet::ResourceApi::Transport.register_fact(:cisco_ios) do |context, facts| facts[:ifspeeds] = PuppetX::Customer::Site::CiscoIosUtility.parse_ifspeeds(context.transport.run_command('show interfaces'))end{code}The example adds a custom fact for {{cisco_ios}} devices that parses out some information from the {{show interfaces}} command using a helper method from {{puppet_x/customer/site/cisco_ios_utility}}.Note how the transport name and fact implementation is passed into {{Puppet::ResourceApi::Transport.register_fact}} to be stored and used when required.Similar to https://github.com/puppetlabs/puppet-resource_api/blob/55e464bcd591345ed5e12166f5416b44bafd10d8/lib/puppet/resource_api/transport.rb#L43-L50 when collecting facts for a remote target, the Resource API needs to load all remote_facts files for that transport and remember the discovered fact blocks. Once that is done, the transport wrapper (https://github.com/puppetlabs/puppet-resource_api/blob/55e464bcd591345ed5e12166f5416b44bafd10d8/lib/puppet/resource_api/transport/wrapper.rb#L31-L35) can retrieve the actual facts from the device, and apply all the collected custom remote facts to the facts hash before returning the result: {code:ruby} def factscontext = Puppet::ResourceApi::PuppetContext.new(@schema)facts = @transport.facts(context)Puppet::ResourceApi::Transport.custom_facts(@schema.name).each do |custom_fact_block| custom_fact_block.call(context, facts)endfacts end{code}
Jira (PUP-8564) resource api transports - add support for custom remote facts
Title: Message Title
David Schmitt updated an issue
Puppet / PUP-8564
resource api transports - add support for custom remote facts
Change By:
David Schmitt
Since none of the remote content goes through facter - and the local execution model of facter also doesn't lend itself to extension, `puppet device` directly delegates facts collection to the {{Device}} class. In the course of this, the possibility for customers to inject custom facts has been lost.With the advent of Resource API Transports, we now have a architectural fault line where we can re-insert that capability.-Specifically customers want to be able to get the IP address of their IOS devices as a fact.- moved to MODULES-9459* custom remote facts go to {{lib/puppet/remote_facts/TRANSPORT/NAME.rb}}, and can be deployed through any module* custom remote facts never get loaded on the server* puppet device and friends load all custom remote facts for the current transport* custom remote facts directly interact with the transport and can modify the facts hash at will (add/delete/modify)* custom remote facts need to ensure they do not interfere with each other{code:ruby}# lib/puppet/remote_facts/cisco_ios/ifspeeds.rbrequire 'puppet/resource_api/transport'require 'puppet_x/customer/site/cisco_ios_utility'Puppet::ResourceApi::Transport.register_fact(:cisco_ios) do |context, facts| facts[:ifspeeds] = PuppetX::Customer::Site::CiscoIosUtility.parse_ifspeeds(context.transport.run_command('show interfaces'))end{code} The example adds a custom fact for {{cisco_ios}} devices that parses out some information from the {{show interfaces}} command using a helper method from {{puppet_x/customer/site/cisco_ios_utility}}.Note how the transport name and fact implementation is passed into {{Puppet::ResourceApi::Transport.register_fact}} to be stored and used when required.Similar to https://github.com/puppetlabs/puppet-resource_api/blob/55e464bcd591345ed5e12166f5416b44bafd10d8/lib/puppet/resource_api/transport.rb#L43-L50 when collecting facts for a remote target, the Resource API needs to load all remote_facts files for that transport and remember the discovered fact blocks. Once that is done, the transport wrapper (https://github.com/puppetlabs/puppet-resource_api/blob/55e464bcd591345ed5e12166f5416b44bafd10d8/lib/puppet/resource_api/transport/wrapper.rb#L31-L35) can retrieve the actual facts from the device, and apply all the collected custom remote facts to the facts hash before returning the result:{code:ruby} def factscontext = Puppet::ResourceApi::PuppetContext.new(@schema)facts = @transport.facts(context)Puppet::ResourceApi::Transport.custom_facts(@schema.name).each do |custom_fact_block| custom_fact_block.call(context, facts)endfacts end{code}
Jira (PUP-8564) resource api transports - add support for custom remote facts
Title: Message Title
David Schmitt updated an issue
Puppet / PUP-8564
resource api transports - add support for custom remote facts
Change By:
David Schmitt
Since none of the remote content goes through facter - and the local execution model of facter also doesn't lend itself to extension, `puppet device` directly delegates facts collection to the {{Device}} class. In the course of this, the possibility for customers to inject custom facts has been lost.With the advent of Resource API Transports, we now have a architectural fault line where we can re-insert that capability.-Specifically customers want to be able to get the IP address of their IOS devices as a fact.- moved to MODULES-9459 * custom remote facts go to {{lib/puppet/remote_facts/TRANSPORT/NAME.rb}}, and can be deployed through any module* custom remote facts never get loaded on the server* puppet device and friends load all custom remote facts for the current transport* custom remote facts directly interact with the transport and can modify the facts hash at will (add/delete/modify)* custom remote facts need to ensure they do not interfere with each other{code:ruby}# lib/puppet/remote_facts/cisco_ios/ifspeeds.rbrequire 'puppet/resource_api/transport'require 'puppet_x/customer/site/cisco_ios_utility'Puppet::ResourceApi::Transport.register_fact(:cisco_ios) do |context, facts| facts[:ifspeeds] = PuppetX::Customer::Site::CiscoIosUtility.parse_ifspeeds(context.transport.run_command('show interfaces'))end{code}
Add Comment
This message was sent by
Jira (PUP-8564) resource api transports - add support for custom remote facts
Title: Message Title
David Schmitt updated an issue
Puppet / PUP-8564
resource api transports - add support for custom remote facts
Change By:
David Schmitt
Currently Since none of the remote content goes through facter - and the local execution model of facter also doesn't lend itself to extension, `puppet device` directly delegates the collection of facts collection to the module being used {{Device}} class . This prevents In the course of this, the possibility for customers to inject custom facts from being used has been lost . Investigate if it is possible to integrate custom facts into `puppet device` With the advent of Resource API Transports, we now have a architectural fault line where we can re-insert that capability. - Specifically customers want to be able to get the IP address of their IOS devices as a fact. - moved -to MODULES-9459-
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
Jira (PUP-8564) resource api transports - add support for custom remote facts
Title: Message Title
David Schmitt updated an issue
Puppet / PUP-8564
resource api transports - add support for custom remote facts
Change By:
David Schmitt
Since none of the remote content goes through facter - and the local execution model of facter also doesn't lend itself to extension, `puppet device` directly delegates facts collection to the {{Device}} class. In the course of this, the possibility for customers to inject custom facts has been lost.With the advent of Resource API Transports, we now have a architectural fault line where we can re-insert that capability.-Specifically customers want to be able to get the IP address of their IOS devices as a fact.- moved - to MODULES-9459 -
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this
Jira (PUP-8564) resource api transports - add support for custom remote facts
Title: Message Title David Schmitt commented on PUP-8564 Re: resource api transports - add support for custom remote facts Moved the work for adding default implementations for default networking facts for IOS to MODULES-9459. Remodelling this ticket for the work to add custom facts capabilities to Resource API. 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.242221.1521582486000.61490.1561551840791%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8564) resource api transports - add support for custom remote facts
Title: Message Title David Schmitt updated an issue Puppet / PUP-8564 resource api transports - add support for custom remote facts Change By: David Schmitt Summary: puppet device resource api transports - add support for custom remote facts 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.242221.1521582486000.61482.1561551120364%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-259) relax ruby requirement to 2.1.0 from 2.1.9
Title: Message Title David Schmitt commented on PDOC-259 Re: relax ruby requirement to 2.1.0 from 2.1.9 Jesse Scott I believe (without proof) that we're far enough down the line that everybody who is running puppet-strings should do so on the ruby supplied by the PDK. 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.261734.1529500595000.54916.1561019400289%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9744) Create acceptance test for PUP-9047
Title: Message Title David Schmitt commented on PUP-9744 Re: Create acceptance test for PUP-9047 David Mallon since I don't know who else (w|c|sh)ould be picking it up, I assigned it to our team. 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.311833.1560175214000.49139.1560771060223%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9747) Bolt provides too many attributes to remote transports
Title: Message Title David Schmitt updated an issue Puppet / PUP-9747 Bolt provides too many attributes to remote transports Change By: David Schmitt From https://groups.google.com/a/puppet.com/forum/#!topic/team-network-automation/bEiFEudGyrc and private slack convo with [~alex]Bolt provides a lot of attributes to remote transports that the Resource API is not prepared to handle. Change the resource api transport layer to silently discard any attributes from the list of "default" attributes bolt provides passed in as connection_info if they do not match up the transport is not prepared to receive them 's schema .* For each discarded attribute that matches the list in https://github.com/puppetlabs/puppet-resource_api#usable-within-the-schema emit a info message. * For each discarded attribute that matches the list in https://github.com/puppetlabs/puppet-resource_api#non-usable-within-the-schema emit a debug message.* For every other discarded attribute emit a warning message. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9747) Bolt provides too many attributes to remote transports
Title: Message Title David Schmitt created an issue Puppet / PUP-9747 Bolt provides too many attributes to remote transports Issue Type: Bug Affects Versions: PUP 6.4.2 Assignee: David Schmitt Created: 2019/06/11 8:25 AM Priority: Critical Reporter: David Schmitt From https://groups.google.com/a/puppet.com/forum/#!topic/team-network-automation/bEiFEudGyrc and private slack convo with Alex Dreyer Bolt provides a lot of attributes to remote transports that the Resource API is not prepared to handle. Change the resource api transport layer to silently discard any attributes from the list of "default" attributes bolt provides if the transport is not prepared to receive them. Add Comment
Jira (PUP-9744) Create acceptance test for PUP-9047
Title: Message Title David Schmitt commented on PUP-9744 Re: Create acceptance test for PUP-9047 good point. 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.311833.1560175214000.41876.1560261060350%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9745) resource api 'Attempt to redefine entity' generation issue
Title: Message Title David Schmitt moved an issue Puppet / PUP-9745 resource api 'Attempt to redefine entity' generation issue Change By: David Schmitt Method Found: Needs Assessment Issue Type: Improvement Bug Key: PDK PUP - 1382 9745 Project: Puppet Development Kit 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-9744) Create acceptance test for PUP-9047
Title: Message Title David Schmitt created an issue Puppet / PUP-9744 Create acceptance test for PUP-9047 Issue Type: Improvement Assignee: Unassigned Created: 2019/06/10 7:00 AM Priority: Normal Reporter: David Schmitt https://github.com/puppetlabs/puppet/pull/7550 showed that the current acceptance test in https://github.com/puppetlabs/puppet/blob/d9523b596c5c09ac3858029ecd628174f752552b/acceptance/tests/puppet_device_test.rb is not sufficient to catch issues like PUP-9047. To make sure this does not regress again, modify the existing test to also check for the condition described in PUP-9047 - the ticket has a simple repro step. Add Comment This message was sent by Atlassian JIRA
Jira (PUP-9642) puppet device permissions preventing reading dirs
Title: Message Title David Schmitt commented on PUP-9642 Re: puppet device permissions preventing reading dirs Hi David Schmitt this was merged into master and will be part of the 6.5.0 release. Can you please let us know if this is resolved by closing the ticket ? The commit has acceptance tests. If those pass, the problem won't be seen by customers any more. 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.262030.152958581.39657.1560175080512%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9642) puppet device permissions preventing reading dirs
Title: Message Title David Schmitt updated an issue Puppet / PUP-9642 puppet device permissions preventing reading dirs Change By: David Schmitt Fix Version/s: PUP 6.0.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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.262030.152958581.18681.1558627140623%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9642) puppet device permissions preventing reading dirs
Title: Message Title David Schmitt commented on PUP-9642 Re: puppet device permissions preventing reading dirs Checked against 6.0.10 from puppet-enterprise-2019.0.4-rc1-47-gb975b36-ubuntu-18.04-amd64 and the problem exists there too. I could not reproduce it with 6.4.3 from puppet-enterprise-2019.1.1-rc1-77-g4687836-ubuntu-18.04-amd64. 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.262030.152958581.18450.1558606980156%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9642) puppet device permissions preventing reading dirs
Title: Message Title David Schmitt updated an issue Puppet / PUP-9642 puppet device permissions preventing reading dirs Change By: David Schmitt Affects Version/s: PUP 6.0.10 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.262030.152958581.18447.1558606860295%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9642) puppet device permissions preventing reading dirs
Title: Message Title David Schmitt updated an issue Puppet / PUP-9642 puppet device permissions preventing reading dirs Change By: David Schmitt Fix Version/s: PUP 6.4.z Fix Version/s: PUP 5.5.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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.262030.152958581.18442.1558605420419%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9642) puppet device permissions preventing reading dirs
Title: Message Title David Schmitt commented on PUP-9642 Re: puppet device permissions preventing reading dirs https://puppet.slack.com/archives/CF466J67L/p1558546760042800 Hey, there's a really nasty looking merge conflict in `lib/puppet/application/device.rb` trying to merge 5.5.x up into 6.0.x, and it looks like it's from commits you had a hand in. Could you take a crack at resolving that? There's also some conflicts in `pip` related files that aren't 100% straight-forward, but feel free to ping @jorie or myself on that. 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.262030.152958581.18425.1558603320285%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9642) puppet device permissions preventing reading dirs
Title: Message Title David Schmitt updated an issue Puppet / PUP-9642 puppet device permissions preventing reading dirs Change By: David Schmitt Release Notes Summary: Under certain circumstances `puppet device` would get confused with directory permissions when initialising new device certificates. This fixes `puppet device` to always initialise the ssl directories with the correct permissions. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.262030.152958581.16270.1558521780232%40Atlassian.JIRA. For more options, visit
Jira (PUP-4930) Provide helpful error message when provider does not have instances defined
Title: Message Title David Schmitt assigned an issue to Rob Braden A really simple change. I've put up https://github.com/puppetlabs/puppet/pull/7522 to address this. Assigning to Rob Braden for hand-holding through the process. Puppet / PUP-4930 Provide helpful error message when provider does not have instances defined Change By: David Schmitt Assignee: Rob Braden Release Notes Summary: Improved a developer error on `provider.instances`. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9642) puppet device permissions preventing reading dirs
Title: Message Title David Schmitt commented on PUP-9642 Re: puppet device permissions preventing reading dirs Dimitri Tischenko The long-term solution is to not run puppet device as root. I'd love to hear your opinion about that. Meanwhile I've got some code changes in https://github.com/puppetlabs/puppet/pull/7483 which will likely fix the initialisation problem. I'm a bit concerned that it went away with 6.4, because that means that there is sometihng else going on that I do not fully understand yet (or I have messed up my testing). 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-9642) puppet device permissions preventing reading dirs
Title: Message Title David Schmitt updated an issue Puppet / PUP-9642 puppet device permissions preventing reading dirs While I was able to reproduce this on 5.5, the effect is not reproducible on 6.4.1. Change By: David Schmitt Affects Version/s: PUP 5.5.13 Affects Version/s: PUP 5.5.1 Fix Version/s: PUP 6.4.1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You
Jira (PUP-9642) puppet device permissions preventing reading dirs
Title: Message Title David Schmitt moved an issue Puppet / PUP-9642 puppet device permissions preventing reading dirs Change By: David Schmitt Key: FM PUP - 7133 9642 Project: Modules [Internal] 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9047) puppet device --apply fails to apply catalog to unregistered targets pt. 2
Title: Message Title David Schmitt updated an issue Puppet / PUP-9047 puppet device --apply fails to apply catalog to unregistered targets pt. 2 Change By: David Schmitt Release Notes Summary: With these changes `puppet device` properly initialises private directories required for compiling and running catalogs. 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 (PUP-9584) Puppet Device plugin sync slow
Title: Message Title David Schmitt updated an issue Puppet / PUP-9584 Puppet Device plugin sync slow Change By: David Schmitt Release Notes Summary: This release improves performance of `puppet device` by removing redundant work during initialisation. 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 (PUP-9579) device application is broken in 6.4
Title: Message Title David Schmitt commented on PUP-9579 Re: device application is broken in 6.4 assigning this to me to sweep it up in the current puppet device cleanup 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-9579) device application is broken in 6.4
Title: Message Title David Schmitt assigned an issue to David Schmitt Puppet / PUP-9579 device application is broken in 6.4 Change By: David Schmitt Assignee: Josh Cooper David Schmitt 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-9584) Puppet Device plugin sync slow
Title: Message Title David Schmitt assigned an issue to David Schmitt Puppet / PUP-9584 Puppet Device plugin sync slow Change By: David Schmitt Assignee: David Schmitt 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-9587) Serial execution with puppet device and ciscopuppet fails
Title: Message Title David Schmitt moved an issue Puppet / PUP-9587 Serial execution with puppet device and ciscopuppet fails Change By: David Schmitt Key: FM PUP - 7876 9587 Project: Modules [Internal] 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9047) puppet device --apply fails to apply catalog to unregistered targets pt. 2
Title: Message Title David Schmitt assigned an issue to David Schmitt Puppet / PUP-9047 puppet device --apply fails to apply catalog to unregistered targets pt. 2 Change By: David Schmitt Assignee: Thomas Honey David Schmitt 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-9584) Puppet Device plugin sync slow
Title: Message Title David Schmitt updated an issue Puppet / PUP-9584 Puppet Device plugin sync slow David Mallon pulling this in, as the perf loss on puppet device is quite dire. Puppet 6.4.1 is scheduled for release April 16th, just in time to roll into kearney. 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-9584) Puppet Device plugin sync slow
Title: Message Title David Schmitt updated an issue Puppet / PUP-9584 Puppet Device plugin sync slow Change By: David Schmitt Fix Version/s: PUP 6.4.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-9047) puppet device --apply fails to apply catalog to unregistered targets pt. 2
Title: Message Title David Schmitt commented on PUP-9047 Re: puppet device --apply fails to apply catalog to unregistered targets pt. 2 In https://github.com/puppetlabs/puppet-resource_api/pull/145 I've removed the workaround in the Resource API tests for this issue, and in the travis run only 5.5.3 failed, so maybe this has been fixed in 5.5.4? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9356) `puppet device` does not load local plugins for --apply --facts and --resource
Title: Message Title David Schmitt updated an issue Puppet / PUP-9356 `puppet device` does not load local plugins for --apply --facts and --resource Change By: David Schmitt The changes in PUP-8766 (https://github.com/puppetlabs/puppet/pull/7242) removed plugin loading from a local environment for `puppet device`, even in the cases where local content is supposed to be used. The issue was detected in Resource API acceptance testing yesterday after the merge-up from 5.5.x to 6.0.x. The fix should be trivially mergeable to 6.0.x and beyond. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-9356) {brief summary of issue}
Title: Message Title
David Schmitt created an issue
Puppet / PUP-9356
{brief summary of issue}
Issue Type:
Bug
Affects Versions:
PUP 5.5.9, PUP 6.0.5
Assignee:
David Schmitt
Created:
2018/12/11 3:22 AM
Priority:
Blocker
Reporter:
David Schmitt
The changes in PUP-8766 (https://github.com/puppetlabs/puppet/pull/7242) removed plugin loading from a local environment for `puppet device`, even in the cases where local content is supposed to be used.
Add Comment
This message was sent by Atlassian
Jira (PUP-9356) `puppet device` does not load local plugins for --apply --facts and --resource
Title: Message Title David Schmitt updated an issue Puppet / PUP-9356 `puppet device` does not load local plugins for --apply --facts and --resource Change By: David Schmitt Team: Network Automation Method Found: Needs Assessment Automated Test 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-9322) implement tests
Title: Message Title David Schmitt updated an issue Puppet / PUP-9322 implement tests Change By: David Schmitt Team: Network Automation 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-9322) implement tests
Title: Message Title David Schmitt created an issue Puppet / PUP-9322 implement tests Issue Type: Sub-task Assignee: Unassigned Created: 2018/11/19 1:52 AM Priority: Normal Reporter: David Schmitt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-8766) puppet device fails with undefined method `loaders' for nil:NilClass when env is not production
Title: Message Title David Schmitt commented on PUP-8766 Re: puppet device fails with undefined method `loaders' for nil:NilClass when env is not production Published draft code changes at https://github.com/puppetlabs/puppet/pull/7242 - waiting for review from Josh Cooper 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-9319) fix --environment handling
Title: Message Title David Schmitt updated an issue Puppet / PUP-9319 fix --environment handling Change By: David Schmitt Team: Network Automation 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-9318) Fixup puppet device to correctly pluginsync and only put pluginsyncdest on the LOAD_PATH
Title: Message Title David Schmitt assigned an issue to David Schmitt Puppet / PUP-9318 Fixup puppet device to correctly pluginsync and only put pluginsyncdest on the LOAD_PATH Change By: David Schmitt Assignee: David Schmitt 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-9319) fix --environment handling
Title: Message Title David Schmitt created an issue Puppet / PUP-9319 fix --environment handling Issue Type: Sub-task Assignee: Unassigned Created: 2018/11/16 6:02 AM Priority: Normal Reporter: David Schmitt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-9318) Fixup puppet device to correctly pluginsync and only put pluginsyncdest on the LOAD_PATH
Title: Message Title David Schmitt created an issue Puppet / PUP-9318 Fixup puppet device to correctly pluginsync and only put pluginsyncdest on the LOAD_PATH Issue Type: Sub-task Assignee: Unassigned Created: 2018/11/16 6:01 AM Priority: Normal Reporter: David Schmitt 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-9248) add support for devices to puppet ssl
Title: Message Title David Schmitt updated an issue Puppet / PUP-9248 add support for devices to puppet ssl Change By: David Schmitt Release Notes Summary: The `puppet ssl clean` now takes a `--target CERTNAME` parameter to clean certificates for remote nodes configured through `device.conf`. Release Notes: Enhancement 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-8766) puppet device fails with undefined method `loaders' for nil:NilClass when env is not production
Title: Message Title David Schmitt updated an issue Puppet / PUP-8766 puppet device fails with undefined method `loaders' for nil:NilClass when env is not production I could reproduce this in a local & clean 5.3 environment. Exploring this functionality raised two concerning issues: puppet device is loading plugin code from the proxy agent's cache. puppet device is using the plugin code before it is downloading the plugins required to do so On the one hand this makes it actually work, on the other hand it completely evades environment isolation and will cause confusion when used. Charlie' fix above avoids the issue of the loaders failure, but does not help with the loadpath issue. Some background loading from the agent's libdir The device.rb#L253 changes the vardir setting, but this does not update the $LOAD_PATH. I've instrumented the code for some debug output: david@zion:~/git/puppet$ bundle exec puppet device --verbose --trace libdir: replacing '' with '/home/david/.puppetlabs/opt/puppet/cache/lib' libdir: replacing '/home/david/.puppetlabs/opt/puppet/cache/lib' with '/home/david/.puppetlabs/opt/puppet/cache/lib' vardir before configuring: /home/david/.puppetlabs/opt/puppet/cache libdir before configuring: /home/david/.puppetlabs/opt/puppet/cache/lib $LOAD_PATH.last before configuring: /home/david/.puppetlabs/opt/puppet/cache/lib vardir after configuring: /home/david/.puppetlabs/opt/puppet/cache/devices/panos libdir after
Jira (PUP-8766) puppet device fails with undefined method `loaders' for nil:NilClass when env is not production
Title: Message Title David Schmitt assigned an issue to David Schmitt Puppet / PUP-8766 puppet device fails with undefined method `loaders' for nil:NilClass when env is not production Change By: David Schmitt Assignee: David Schmitt 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-8736) /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs
Title: Message Title David Schmitt commented on PUP-8736 Re: /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs The specific location currently used is a hold-over from 9 years ago when that was implemented by a community contributor. Today we can do better. Someone (preferably with in-depth knowledge of the agent packaging) needs to figure out where the various files should go someone needs to implement that the implementation needs to also encompass a migration process so that existing files get moved to the right locations when upgrading docs, up-/downgrade testing, etc. None of this will be relevant in the next PE, as the new integration will run devices in a completely different context. For FOSS, Davin Hanlon and who-ever feels responsible for this particular bit on the platerprise product side need to hash out priorities. 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
Jira (PUP-2368) using booleans result in unmanaged property
Title: Message Title David Schmitt commented on PUP-2368 Re: using booleans result in unmanaged property Mykhailo Danylenko to avoid this (and many other issues) please use the Resource API: https://puppet.com/docs/puppet/6.0/custom_resources.html The Resource API is available to install on puppet 4 and 5 as a gem (there is also a module for that), and it is shipped fully supported with puppet 6. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9143) Puppet device raises `undefined method` error
Title: Message Title David Schmitt commented on PUP-9143 Re: Puppet device raises `undefined method` error Maggie Dreyer I can confirm that using this change the Resource API tests that originally flagged that issue pass now: https://travis-ci.org/puppetlabs/puppet-resource_api/jobs/429743241 Finished in 2 minutes 48.7 seconds (files took 2.45 seconds to load) 1272 examples, 0 failures, 1 pending Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PDOC-266) Getting "unexpected construct regexp_literal" when using resource API title_patterns
Title: Message Title David Schmitt commented on PDOC-266 Re: Getting "unexpected construct regexp_literal" when using resource API title_patterns That looks like a sensible approach to solve this. Anything speaking against getting that merged right now? 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-266) Getting "unexpected construct regexp_literal" when using resource API title_patterns
Title: Message Title David Schmitt commented on PDOC-266 Re: Getting "unexpected construct regexp_literal" when using resource API title_patterns I'm glad it's not a "everything on fire" situation. That said, it should definitely not swallow the docs for types using title_patterns. Can you post the patch somewhere, even if we don't think it'll be the right solution. It's at least a pointer to the offending code 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-266) Getting "unexpected construct regexp_literal" when using resource API title_patterns
Title: Message Title David Schmitt updated an issue Puppet Strings / PDOC-266 Getting "unexpected construct regexp_literal" when using resource API title_patterns Change By: David Schmitt Method Found: Needs Assessment Customer Feedback 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-266) Getting "unexpected construct regexp_literal" when using resource API title_patterns
Title: Message Title David Schmitt updated an issue Puppet Strings / PDOC-266 Getting "unexpected construct regexp_literal" when using resource API title_patterns Sean Millichamp, how big is the impact here? Is this only annoying, or does it break doc generation? If the latter, how hard? 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-8987) add resource_api gem to puppet gemspec
Title: Message Title David Schmitt commented on PUP-8987 Re: add resource_api gem to puppet gemspec If it is any help to you deciding whether to get this done or not, the PDK already walks folks through adding the gem dependency manually because otherwise nobody would get it yet. 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-9104) YAML safe_load too strict
Title: Message Title
David Schmitt updated an issue
Puppet / PUP-9104
YAML safe_load too strict
Change By:
David Schmitt
*Puppet Version:* current master, e.g. ddd5610aa9ffb5eb9da13521f1fc68e562a2e0b3*Puppet Server Version:* n/a*OS Name/Version:* n/a*Actual Behavior:*In some cases puppet creates a {{transactionstore.yaml}} that are not able to be read back, causing {code}Error: Transaction store file /home/david/.puppetlabs/opt/puppet/cache/devices/pavm/state/transactionstore.yaml is corrupt (Unknown alias: 1); replacing{code}*Desired Behavior:*No errors or stacktraces on regular puppet use.*Reproduction:*[~thomas.franklin] has put together a detailed description and a potential fix in https://github.com/Thomas-Franklin/puppet/commit/49b8e023c6c9bb551bd0ce21648a604042c490ff The issue is also visible in the panos acceptance pipelines: https://jenkins-master-prod-1.delivery.puppetlabs.net/view/modules/view/networking/view/panos/view/master/job/forge-module_puppetlabs-panos_intn-sys_full-pe-future-master/8/
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9104) YAML safe_load too strict
Title: Message Title
David Schmitt updated an issue
Puppet / PUP-9104
YAML safe_load too strict
Change By:
David Schmitt
*Puppet Version:* current master , e.g. ddd5610aa9ffb5eb9da13521f1fc68e562a2e0b3 *Puppet Server Version:* n/a*OS Name/Version:* n/a*Actual Behavior:*In some cases puppet creates a {{transactionstore.yaml}} s that are not able to be read back, causing {code}Error: Transaction store file /home/david/.puppetlabs/opt/puppet/cache/devices/pavm/state/transactionstore.yaml is corrupt (Unknown alias: 1); replacing{code}*Desired Behavior:*No errors or stacktraces on regular puppet use.*Reproduction:*[~thomas.franklin] has put together a detailed description and a potential fix in https://github.com/Thomas-Franklin/puppet/commit/49b8e023c6c9bb551bd0ce21648a604042c490ff
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
Jira (PUP-9104) YAML safe_load too strict
Title: Message Title
David Schmitt created an issue
Puppet / PUP-9104
YAML safe_load too strict
Issue Type:
Bug
Affects Versions:
PUP 6.0.0
Assignee:
Unassigned
Created:
2018/09/05 5:35 AM
Priority:
Normal
Reporter:
David Schmitt
Puppet Version: current master Puppet Server Version: n/a OS Name/Version: n/a Actual Behavior: In some cases puppet creates {{transactionstore.yaml}}s that are not able to be read back, causing
Error: Transaction store file /home/david/.puppetlabs/opt/puppet/cache/devices/pavm/state/transactionstore.yaml is corrupt (Unknown alias: 1); replacing
Desired Behavior: No errors or stacktraces on regular puppet use. Reproduction: Thomas Franklin has put together a detailed description and a potential fix in https://github.com/Thomas-Franklin/puppet/commit/49b8e023c6c9bb551bd0ce21648a604042c490ff
Jira (BOLT-791) Support running a task on a proxy node targeting a device or API with run-on
Title: Message Title David Schmitt commented on BOLT-791 Re: Support running a task on a proxy node targeting a device or API with run-on This sounds very much like what devices would need from bolt. I'd love to see an end-to-end example of how this will look like to the user to get a better understanding of the proposed UX. Open questions: would the _target metaparam contain the device's credentials (or credential reference) similar to the device.conf of puppet device? how does bolt connect to the run-on proxy node? Is that "just" a reference to another target in the inventory? 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.
