Jira (PUP-7980) Add a run_script() function to enable this bolt feature from the language
Title: Message Title John Duarte commented on PUP-7980 Re: Add a run_script() function to enable this bolt feature from the language Using bolt at SHA 18e5d843f61f9bec0e1b4e2f9eb1776abd7a3de8 containing puppet at SHA 57a470e74a00ec114cfeb34358c08747c1499ee0 this now passes functional review. Using the same plan as defined in the comment above, the plan compiles and executes on the given node as expected. bundle exec bolt plan run test::my_plan nodes=jhmms7tr7kvo1qz.delivery.puppetlabs.net --modules /tmp/modules jhmms7tr7kvo1qz.delivery.puppetlabs.net Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7979) Add a run_command() function
Title: Message Title John Duarte commented on PUP-7979 Re: Add a run_command() function Using bolt at SHA 18e5d843f61f9bec0e1b4e2f9eb1776abd7a3de8 containing puppet at SHA 57a470e74a00ec114cfeb34358c08747c1499ee0 this now passes functional review. Using the same plan as defined in the comment above, the plan compiles and executes on the given node as expected. bundle exec bolt plan run test::my_plan nodes=jhmms7tr7kvo1qz.delivery.puppetlabs.net --modules /tmp/modules jhmms7tr7kvo1qz.delivery.puppetlabs.net Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1757) Update libwhereami's readme, changelog, and reported version
Title: Message Title Casey Williams assigned an issue to Branan Riley Facter / FACT-1757 Update libwhereami's readme, changelog, and reported version Change By: Casey Williams Assignee: Casey Williams Branan Riley Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7979) Add a run_command() function
Title: Message Title Patrick Carlisle commented on PUP-7979 Re: Add a run_command() function I've changed the bolt executor methods to return a normal ruby Hash for results instead of Concurrent::Map. This should fix problems in consuming it. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7511) Test puppet-agent against FIPS-compliant system openssl library
Title: Message Title Jayant Sane commented on PUP-7511 Re: Test puppet-agent against FIPS-compliant system openssl library Thanks. That is good news as well as interesting. I have stumbled upon some strange failures when attempting to use PA on RHEL 7 which was built on Centos 7 (against system openssl). This was w/o even enabling FIPS mode. I looked at some plausible reasons but nothing obvious turns up. Both centos7 and rhel7 have 1.0.1e version of system openssl libs. Based on the failures the behavior appears to originate from ruby (openssl.so) and libcurl.so. I wrote a test C application using openssl to do somethings on SSL context, including generating rsa keys etc. Followed same sequence as above - compiled on centos7 and executed on rhel7. It works fine and so does vice versa - compiled on rhel7 and executed on centos7. Even if I figure out the exact cause in the above suspect components, I would be concerned if we might see any such or unexpected behaviors down the line across different versions of openssl and/or platforms. Not to mention the maintenance overhead it might introduce as we may need to maintain 'fixed' versions of ruby and/or curl. One obvious/logical workaround for the above issue seemed like - compile PA on RHEL when targeting RHEL. I tried that but it actually gets worse. Installing openssl development package on RHEL bumps the versions of system openssl libraries. It moved from 1.0.1e to 1.0.2k. Since only only minor version changed, thought it might not been that bad - all relevant PA, including ruby, curl etc., binaries link against libssl.so.10 & libcrypto.so.10 (SONAMEs). But despite that openssl.so (ruby) and libcurl.so.xxx latch to version 1.0.2 of openssl libs. So now if you attempt to use the PA compiled on RHEL7 on another RHEL 7 system w/o openssl development package installed, it would not work since the openssl libs version would be still at 1.0.1e. All said, though, since it seems to work for you (PA compiled on Centos runs on RHEL), I wonder if there is any difference across the RHEL images you use compared to what we use. I think I just answered myself: I tried using Centos7 compiled PA on a RHEL7 that was provisioned on different infrastructure (openstack). That seems to work fine - at least the specific failure seen above is not seen. Encouraging it sounds but also worrisome as it just could be one of those waiting to fail type of issues depending on what our customers might have. I would also like to request you to test Puppet agent 5.x to see if it still works in case there is anything different from PA 4.x that you have (though it just might be a data point w/o necessarily providing anything helpful to triage it). This is not urgent now that I may be able to do some testing using the 'right kind' of RHEL systems Add Comment
Jira (PDB-558) Design: PuppetDB should support granular access control for queries
Title: Message Title Owen Rodabaugh updated an issue PuppetDB / PDB-558 Design: PuppetDB should support granular access control for queries Change By: Owen Rodabaugh CS Priority: Major CS Impact: The all-or-nothing nature of the PDB API makes it difficult to allow others to integrate with it for security conscious customers. The PDB CLI lowers the bar for this to be found by customers. Even getting read/write access control would be a good start rather than aiming for deeply detailed query controls.RBAC allows customers to delegate, because there isn't any actual control other than can you access it or not it makes it more difficult for them to delegate as they often can't trust others to not abuse the full access. CS Severity: 3 - Serious CS Business Value: 5 - $$ CS Frequency: 4 - 50-90% of Customers Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (FACT-1642) facter should understand cpu model on Power for the processors.model fact
Title: Message Title Geoff Nichols assigned an issue to Sean McDonald Facter / FACT-1642 facter should understand cpu model on Power for the processors.model fact Change By: Geoff Nichols Assignee: Branan Riley Sean McDonald Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1766) Man page is not installed when rdoc gem is not prsent
Title: Message Title Lucien Weller commented on FACT-1766 Re: Man page is not installed when rdoc gem is not prsent Opened pull request for this issue https://github.com/puppetlabs/facter/pull/1654 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1764) Error message with zpool_vesion fact when zfs service is installed bt not running
Title: Message Title Lucien Weller updated an issue Facter / FACT-1764 Error message with zpool_vesion fact when zfs service is installed bt not running Change By: Lucien Weller Fix Version/s: FACT 2.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1764) Error message with zpool_vesion fact when zfs service is installed bt not running
Title: Message Title Lucien Weller updated an issue Facter / FACT-1764 Error message with zpool_vesion fact when zfs service is installed bt not running Change By: Lucien Weller Fix Version/s: FACT 2.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7999) Puppet Lookup should be easily used as a library in other applications
Title: Message Title
Henrik Lindberg commented on PUP-7999
Re: Puppet Lookup should be easily used as a library in other applications
We have been working on the Puppet::Pal API ("Puppet as-a Library) for the purpose of making it easy to do "puppety" things with a degree of separation between the caller and "puppet". We could add "lookup" to that API as well. The API already has various ways to define the environment and node to operate on.
With lookup in general, there is the question if such an API should return the exact same values as would be looked up during compilation, or/and if it should be possible to also give it a separate hierarchy for other purposes than "compiling for a node".
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-3263) Architecture Parameter for Package Resource
Title: Message Title Casey Williams updated an issue Puppet / PUP-3263 Architecture Parameter for Package Resource Change By: Casey Williams Sprint: Platform OS Hold Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1766) Man page is not installed when rdoc gem is not prsent
Title: Message Title Lucien Weller created an issue Facter / FACT-1766 Man page is not installed when rdoc gem is not prsent Issue Type: Bug Affects Versions: FACT 2.4.6 Assignee: Lucien Weller Created: 2017/09/28 1:38 PM Priority: Normal Reporter: Lucien Weller install.rb prevents installation of man page when rdoc gem is not present. This make no sense any more, because facter includes a static man page for over 4 years now. This issue breaks rpm build in Fedora, as rdoc gem is not a required dependency (what is correct) but requires man page to be included. Add Comment
Jira (PUP-8002) "Attempt to redefine entity" caused by using a resource collector
Title: Message Title Thomas Hallgren commented on PUP-8002 Re: "Attempt to redefine entity" caused by using a resource collector Ben Ford, please run the puppetserver with log-level trace and then extract the stack trace from servers puppetserver.log after the error occurs and paste it into this ticket. Without that, or clear steps to reproduce, there's not much I can do. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8003) Update and test rubocop performance complaints Performance/Caller and Performance/CompareWithBlock
Title: Message Title Eric Delaney created an issue Puppet / PUP-8003 Update and test rubocop performance complaints Performance/Caller and Performance/CompareWithBlock Issue Type: Task Affects Versions: PUP 5.3.z Assignee: Unassigned Created: 2017/09/28 11:52 AM Priority: Normal Reporter: Eric Delaney While updating the rubocop version, I found 2 new rubocop checks that fail on the puppet code base that we should look at doing performance tests against to see if making the suggested change would have any performance improvements. Performance/Caller: rake aborted! RuboCop detected offenses /Users/eric.delaney/work/my_repos/puppet/Rakefile:75:in
Jira (PUP-7988) resources/group/should_create test fails on fedora-26-64a
Title: Message Title Enis Inan assigned an issue to Enis Inan Puppet / PUP-7988 resources/group/should_create test fails on fedora-26-64a Change By: Enis Inan Assignee: Enis Inan Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3693) Prepare PupppetDB 5.1.1 release for Platform 5.3.1 (2017-09-29)
Title: Message Title Jeff Yarnell commented on PDB-3693 Re: Prepare PupppetDB 5.1.1 release for Platform 5.3.1 (2017-09-29) Molly Waggett I don't have Winston installed and have a messed bundler install, so I created RE-9423. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1765) Facter should not output a warning for a missing dmidecode component on Power Linux machines
Title: Message Title John Duarte commented on FACT-1765 Re: Facter should not output a warning for a missing dmidecode component on Power Linux machines Using a pre-release version of puppet-agent at SHA 445a971 containing facter at SHA 09e7cfe, the dmidecode warning is no longer output tested on RedHat 7.3 on POWER8. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7974) puppet master compile command with language in japanese doesn't print solution in japanese
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7974 puppet master compile command with language in japanese doesn't print solution in japanese Change By: Craig Gomes Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7975) "LANG=ja_JP puppet enterprise support" produces non-printable error
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7975 "LANG=ja_JP puppet enterprise support" produces non-printable error Change By: Craig Gomes Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7984) `puppet cert revoke` doesn't verify the loaded CRL
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7984 `puppet cert revoke` doesn't verify the loaded CRL Change By: Craig Gomes Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7985) `puppet cert generate` uses the wrong CA certificate
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7985 `puppet cert generate` uses the wrong CA certificate Change By: Craig Gomes Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7988) resources/group/should_create test fails on fedora-26-64a
Title: Message Title Craig Gomes updated an issue Puppet / PUP-7988 resources/group/should_create test fails on fedora-26-64a Change By: Craig Gomes Team: Platform OS Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1763) Facter acceptance tests fail on POWER Linux machines
Title: Message Title John Duarte updated an issue Facter / FACT-1763 Facter acceptance tests fail on POWER Linux machines Change By: John Duarte QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1752) Add support for AIX LPAR and WPAR detection
Title: Message Title John Duarte updated an issue Facter / FACT-1752 Add support for AIX LPAR and WPAR detection Change By: John Duarte QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8002) "Attempt to redefine entity" caused by using a resource collector
Title: Message Title Geoff Nichols commented on PUP-8002 Re: "Attempt to redefine entity" caused by using a resource collector Thomas Hallgren, when you have a chance, could you please take a look? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1765) Facter should not output a warning for a missing dmidecode component on Power Linux machines
Title: Message Title John Duarte updated an issue Facter / FACT-1765 Facter should not output a warning for a missing dmidecode component on Power Linux machines Change By: John Duarte QA Risk Assessment: Needs Assessment Manual Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8002) "Attempt to redefine entity" caused by using a resource collector
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-8002 "Attempt to redefine entity" caused by using a resource collector Change By: Geoff Nichols Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7899) acceptance: Update aix package test to validate 'ensure => latest'
Title: Message Title John Duarte updated an issue Puppet / PUP-7899 acceptance: Update aix package test to validate 'ensure => latest' Change By: John Duarte Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8000) Puppet lookup should be aware of node classification class parameters
Title: Message Title Past Haus commented on PUP-8000 Re: Puppet lookup should be aware of node classification class parameters Henrik Lindberg I'm not sure if an actual compile is required, but the class parameters from the ENC will trump anything from hiera, so whenever the parameters are available they need to be merged over the hiera params. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8000) Puppet lookup should be aware of node classification class parameters
Title: Message Title Past Haus commented on PUP-8000 Re: Puppet lookup should be aware of node classification class parameters Thomas Hallgren Classifying class parameters in the console has been a feature since PE 3.7 (https://docs.puppet.com/pe/3.7/release_notes.html#new-features-in-370). This is not a new requirement, however this is something that seems desirable in a lookup. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-2169 Not possible to manage SELinux file contexts via puppet in a sane way Change By: Owen Rodabaugh CS Priority: Normal Needs Priority Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8002) "Attempt to redefine entity" caused by using a resource collector
Title: Message Title Ben Ford created an issue Puppet / PUP-8002 "Attempt to redefine entity" caused by using a resource collector Issue Type: Bug Affects Versions: PUP 4.10.4 Assignee: Unassigned Created: 2017/09/28 9:59 AM Priority: Major Reporter: Ben Ford See PUP-7650 for the root cause of the issue. This behaviour is also sometimes (indeterminately) cause by using a resource collector, and that does not seem to be corrected by the patch linked in PUP-7650 . The error thrown is: Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Virtual Query, Could not autoload puppet/type/pe_ini_setting: Attempt to redefine entity 'http://puppet.com/2016.1/runtime/type/pe_ini_setting'. Set at unknown location at /etc/puppetlabs/code/modules/classroom/manifests/master/student_environment.pp:51:3 on node superdog.puppetlabs.vm
Jira (PUP-8001) "Attempt to redefine entity" caused by using a resource collector
Title: Message Title Ben Ford updated an issue Puppet / PUP-8001 "Attempt to redefine entity" caused by using a resource collector Change By: Ben Ford Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8001) "Attempt to redefine entity" caused by using a resource collector
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-8001 "Attempt to redefine entity" caused by using a resource collector Issue Type: Bug Affects Versions: PUP 4.10.1 Assignee: Unassigned Created: 2017/09/28 9:54 AM Fix Versions: PUP 4.10.3, PUP 5.0.0 Priority: Critical Reporter: Thomas Hallgren A load of a resource type will sometimes create a Puppet::Pops::Loader::TypedName that starts with an uppercase letter. When this name is used in order to find a type generated with puppet generate types, it isn't found. Since it's not found, a load of the Ruby type is performed instead, which results in an "Attempt to redefine entity" error when that a successful load of the generated type has been performed earlier (with a TypedName that didn't start with an uppercase letter).
Jira (PDB-3692) PDB migration error due to facts deduplication and null values
Title: Message Title Kenn Hussey updated an issue PuppetDB / PDB-3692 PDB migration error due to facts deduplication and null values Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3692) PDB migration error due to facts deduplication and null values
Title: Message Title Kenn Hussey commented on PDB-3692 Re: PDB migration error due to facts deduplication and null values Russell Mull please provide release notes for this issue. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7308) classes do not honor refresh events when running with tags
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7308 classes do not honor refresh events when running with tags Change By: Kenn Hussey Fix Version/s: PUP 5.3.2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1732) Facter core dump on large integers
Title: Message Title Trevor Vaughan commented on FACT-1732 Re: Facter core dump on large integers Branan Riley I just realized that what I said previously is simply untenable since it would break a lot of existing code. I guess auto-Stringification of big numbers is all that can be done for right now with a warning that things that get big might mysteriously break until Bignum support is added across the stack. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1732) Facter core dump on large integers
Title: Message Title Trevor Vaughan commented on FACT-1732 Re: Facter core dump on large integers Branan Riley I can work on getting tickets in when I have time. We're trying to get a release out so it might be after PuppetConf. 1) Technically, that's everything that's an Integer. We can't dynamically Stringify things that are big because it will destroy logic in the underlying Puppet manifests. With strong typing, either something is an Integer or a String, it won't auto-cast (I think). And, of course, you can't have things be Strings sometimes and Integers other times because users just won't know what to do with the data and manifests will mysteriously break when things get too big (for whatever reason). I would definitely send out an announcement for people to be starting to watch for this and there's going to need to be some sort of purge script for PuppetDB to get bad data converted internally. 2) Yeah, this is the correct solution really but that's going to cover at least 3 languages. They're all solved problems but implementation and testing takes time. 3) Makes sense, but I still think you're going to have to Stringify all Numbers for the short term. You might be able to make this a Stringification of only custom facts and not core facts, but the disk sizes still pose a problem. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3693) Prepare PupppetDB 5.1.1 release for Platform 5.3.1 (2017-09-29)
Title: Message Title Molly Waggett commented on PDB-3693 Re: Prepare PupppetDB 5.1.1 release for Platform 5.3.1 (2017-09-29) Jeff Yarnell winston (https://github.com/puppetlabs/winston) is RE's ticket generator. It will make tickets for each step in the release process, mainly for the team releasing, it also makes an associated RE ticket so that we know a release is coming up. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-2709) Puppet Agent: fails to run on non english Windows
Title: Message Title Luiz Henrique Pareschi de Oliveira commented on PUP-2709 Re: Puppet Agent: fails to run on non english Windows It didn't have solution. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8000) Puppet lookup should be aware of node classification class parameters
Title: Message Title Henrik Lindberg commented on PUP-8000 Re: Puppet lookup should be aware of node classification class parameters Isn't this a case of requiring an actual compilation based on a node, thus making sure that an ENC has had impact on the state of compilation before attempting a lookup? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7998) Add an Error data type to puppet
Title: Message Title Henrik Lindberg commented on PUP-7998 Re: Add an Error data type to puppet Changed in the description - undef default is ok. Is however more complex to then match kind == undef if the kind type parameter in Error is restricted to String. It then needs to accept an explicit match on Undef as well. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7998) Add an Error data type to puppet
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-7998
Add an Error data type to puppet
Change By:
Henrik Lindberg
It is of value to describe a value as being an {{Error\[kind, issue_code]}} - a kind of exceptional result that can be returned from functions and passed around.An error type is parameterised with a "kind" discriminator - a missing parameter means "all kinds". A "kind" is a string that should follow certain conventions, but is not required to. It is typically a string on the form {{authority/name}} where authority is something like "puppetlabs" or "puppet", or the loose notion of "author" (the authority that controls what is valid as a kind-name). The type parameter can be given as {{Variant\[String, Regexp, Type\[Enum], Type\[Pattern], Type\[Any] ]}}, where a given {{String}} is the same as an Enum with that single value, and {{Regexp }}is the same as {{Pattern}} with that single regexp). An {{Error\[Any]}} is the same as {{Error}}.The issue code type parameter is of the same type as kind, but here it is expected that than an issue code (without structure) is used.As an example, the type {{Error\[Any, "SYNTAX_ERROR"]}} would match all error objects from any authority using an issue code of "SYNTAX_ERROR". An {{Error\[/^puppet/]}} would match all errors with "puppet..." as the authority.An error instance is described by:{code:puppet}type Error = Object[ attributes => {message => String,kind => { type => Optional[ String ] , default_value => "unspecified" undef },issue_code => { type => String, default_value => "ERROR" },details => { type => Optional[DataHash], default_value = undef } }}{code}Type algebra: An Error {{Error\[K, I] op Error\[K2, I2]}} is true if {{K op K2}} and {{I op I2}} are both true. Error < Object.The "detail" hash is an encoding of additional information such as "exitcode", "stacktrace", "exception", etc. These are included for the purpose of being able to give a user more debugging information. The exact content and details of "details" is left open ended to be flexible for different kinds of error information.
Add Comment
Jira (PUP-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Martin Ewings updated an issue Puppet / PUP-2169 Not possible to manage SELinux file contexts via puppet in a sane way customer notes that is an annoyance if you have e.g. a forge module and files on some non-default paths for which you need to add fcontext rules. Forge modules normally don't explicitly set selcontext on file resources (or allow to pass the value to use). Either you fixup the module code locally or restart the agent-daemon to complete the "automated" installation. Having setting selinux_ignore_defaults results in getting the selinux fcontext from the parent directory which is also not the correct behaviour. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Martin Ewings updated an issue Puppet / PUP-2169 Not possible to manage SELinux file contexts via puppet in a sane way Change By: Martin Ewings CS Priority: Normal CS Severity: 2 - Annoyance CS Business Value: 1 - ? CS Frequency: 1 - 1-5% of Customers Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7998) Add an Error data type to puppet
Title: Message Title Thomas Hallgren commented on PUP-7998 Re: Add an Error data type to puppet I'd rather like kind to be undef when it's not given. Or do we really want to match against the "unspecified" string? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7998) Add an Error data type to puppet
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-7998 Add an Error data type to puppet Change By: Henrik Lindberg Assignee: Henrik Lindberg Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7998) Add an Error data type to puppet
Title: Message Title Henrik Lindberg commented on PUP-7998 Re: Add an Error data type to puppet Thomas Hallgren Ok to use an ErrorObj (or similar) as the runtime object. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7998) Add an Error data type to puppet
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-7998
Add an Error data type to puppet
Change By:
Henrik Lindberg
It is of value to describe a value as being an {{Error\[kind, issue_code]}} - a kind of exceptional result that can be returned from functions and passed around.An error type is parameterised with a "kind" discriminator - a missing parameter means "all kinds". A "kind" is a string that should follow certain conventions, but is not required to. It is typically a string on the form {{authority/name}} where authority is something like "puppetlabs" or "puppet", or the loose notion of "author" (the authority that controls what is valid as a kind-name). The type parameter can be given as {{Variant\[String, Regexp, Type\[Enum], Type\[Pattern], Type\[Any] ]}}, where a given {{String}} is the same as an Enum with that single value, and {{Regexp }}is the same as {{Pattern}} with that single regexp). An {{Error\[Any]}} is the same as {{Error}}.The issue code type parameter is of the same type as kind, but here it is expected that than an issue code (without structure) is used.As an example, the type {{Error\[Any, "SYNTAX_ERROR"]}} would match all error objects from any authority using an issue code of "SYNTAX_ERROR". An {{Error\[/^puppet/]}} would match all errors with "puppet..." as the authority.An error instance is described by:{code:puppet}type Error = Object[ attributes => {message => String, kind => { type => String, default_value => "unspecified" }, issue_code => { type => String, default_value => "ERROR" },details => { type => Optional[DataHash], default_value = undef } }}{code}Type algebra: An Error {{Error\[K, I] op Error\[K2, I2]}} is true if {{K op K2}} and {{I op I2}} are both true. Error < Object.The "detail" hash is an encoding of additional information such as "exitcode", "stacktrace", "exception", etc. These are included for the purpose of being able to give a user more debugging information. The exact content and details of "details" is left open ended to be flexible for different kinds of error information.
Add Comment
Jira (PUP-7998) Add an Error data type to puppet
Title: Message Title Henrik Lindberg commented on PUP-7998 Re: Add an Error data type to puppet 1. Meh, "kind" was missing in the description. Updating Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7998) Add an Error data type to puppet
Title: Message Title Thomas Hallgren commented on PUP-7998 Re: Add an Error data type to puppet The description suggest that the object representing error instances should be described as: type Error = Object[...] That won't fly since the Error here collides with the new parameterized Error[K,I] type. Ideally, this would be the same type but we haven't yet decided to create parameterized Object types. I suggest naming the Object type that describes an instance of an error ErrorObj or similar. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7998) Add an Error data type to puppet
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-7998
Add an Error data type to puppet
Change By:
Thomas Hallgren
Comment:
The description suggest that the object representing error instances should be described as:{code:puppet}type Error = Object[...]{code}That won't fly since the {{Error}} here collides with the new {{Error}} type. I suggest naming the actual instance type to {{ErrorImpl}} or similar.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-7998) Add an Error data type to puppet
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-7998 Add an Error data type to puppet Change By: Kenn Hussey Sprint: Tasks EUP (PuppetConf) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7998) Add an Error data type to puppet
Title: Message Title Thomas Hallgren commented on PUP-7998 Re: Add an Error data type to puppet The description suggest that the object representing error instances should be described as: type Error = Object[...] That won't fly since the Error here collides with the new Error type. I suggest naming the actual instance type to ErrorImpl or similar. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7998) Add an Error data type to puppet
Title: Message Title Thomas Hallgren commented on PUP-7998 Re: Add an Error data type to puppet 1. No, not as opposed to anything. The object describes message, issue_code, and details. No authority or kind. So how can I compare an instance with respect to kind (or authority)? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7998) Add an Error data type to puppet
Title: Message Title Henrik Lindberg commented on PUP-7998 Re: Add an Error data type to puppet 1. As opposed to "kind" that is both authority and some additional detail? (If so, because we have not formalized "kind" beyond being a string at this point). 2. Enough to be a string 3. Yes, intentional - if wanted we need a third parameter to the type. I may be wrong in wanting ISSUE_CODE and that we should skip that in favor of matching on the issue itself - this because the current API does not really have issue-code. You could view an actual message as a kind of issue-code I guess. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3693) Prepare PupppetDB 5.1.1 release for Platform 5.3.1 (2017-09-29)
Title: Message Title Jeff Yarnell commented on PDB-3693 Re: Prepare PupppetDB 5.1.1 release for Platform 5.3.1 (2017-09-29) Molly Waggett Sorry, but what is 'winston?' Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7997) add loading tasks and plans from an "init" named element to name it after containing module
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-7997 add loading tasks and plans from an "init" named element to name it after containing module Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7996) Avoid loading manifests, puppet types and providers when running tasks.
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7996 Avoid loading manifests, puppet types and providers when running tasks. Change By: Eric Delaney QA Risk Assessment: Needs Assessment No Action Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7994) run_task crashes with bad message when passed a string that doesn't represent a task
Title: Message Title Eric Delaney updated an issue Puppet / PUP-7994 run_task crashes with bad message when passed a string that doesn't represent a task Change By: Eric Delaney QA Risk Assessment Reason: test added with fix QA Risk Assessment: Needs Assessment No Action Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7997) add loading tasks and plans from an "init" named element to name it after containing module
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-7997 add loading tasks and plans from an "init" named element to name it after containing module Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Martin Ewings updated an issue Puppet / PUP-2169 Not possible to manage SELinux file contexts via puppet in a sane way Change By: Martin Ewings Affects Version/s: PUP 4.10.5 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Martin Ewings updated an issue Puppet / PUP-2169 Not possible to manage SELinux file contexts via puppet in a sane way Change By: Martin Ewings Environment: CentOS 7 with Puppet 4.8.2 (puppet-agent 1.8.3)Fedora 25 with Puppet 4.8.2 (puppet-agent 1.8.3)CentOS 6.5 x86_64 Puppet 3.4.3 from Puppetlabs repositoryCentOS 6 with Puppet 3.8.7 from Pupptlabs Repo Rhel 7.3 PE 2016.4.7 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Martin Ewings updated an issue Puppet / PUP-2169 Not possible to manage SELinux file contexts via puppet in a sane way Change By: Martin Ewings Method Found: Customer Feedback Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7988) resources/group/should_create test fails on fedora-26-64a
Title: Message Title Enis Inan commented on PUP-7988 Re: resources/group/should_create test fails on fedora-26-64a Failed after being re-kicked: https://jenkins-master-prod-1.delivery.puppetlabs.net/view/puppet-agent/view/5.3.x/view/Suite/job/platform_puppet-agent_intn-van-sys_suite-daily-puppet-5.3.x/SLAVE_LABEL=beaker,TEST_TARGET=fedora26-64a/23/console Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7998) Add an Error data type to puppet
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-7998 Add an Error data type to puppet Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7998) Add an Error data type to puppet
Title: Message Title Thomas Hallgren commented on PUP-7998 Re: Add an Error data type to puppet Henrik Lindberg, some questions the description: It seems like you describe two types here. One Error type whose instances will contain error information and one ErrorMatch whose instances are capable of matching Error (as with String and Pattern). Why isn't there an authority attribute in the Error definition? What is the motivation for allowing the kind to be a Type[Any]? Isn't it enough to be able to match strings? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7979) Add a run_command() function
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-7979 Add a run_command() function Change By: Thomas Hallgren Assignee: John Duarte Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7988) resources/group/should_create test fails on fedora-26-64a
Title: Message Title Enis Inan commented on PUP-7988 Re: resources/group/should_create test fails on fedora-26-64a Failed again during 5.3.x puppet-agent pipeline: https://jenkins-master-prod-1.delivery.puppetlabs.net/job/platform_puppet-agent_intn-van-sys_suite-daily-puppet-5.3.x/SLAVE_LABEL=beaker,TEST_TARGET=fedora26-64a/22/ Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7998) Add an Error data type to puppet
Title: Message Title Thomas Hallgren commented on PUP-7998 Re: Add an Error data type to puppet Adding this as a blocker for all tickets concerning Puppet calling Bolt, since all of them will need to have their handling of the returned value redesigned and several of them are broken due to the fact that Bolt returns a Concurrent#Map that doesn't respond to #map. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7967) Add a file_upload() function
Title: Message Title Thomas Hallgren commented on PUP-7967 Re: Add a file_upload() function All Bolt commands returns an instance of Concurrent::Map. The several calling Puppet functions expect the returned value to respond to #map bu that's not the case with the Concurrent::Map. I'm creating a new ticket for this since it affects file_upload, run_command, and run_script. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7979) Add a run_command() function
Title: Message Title Thomas Hallgren assigned an issue to John Duarte Puppet / PUP-7979 Add a run_command() function Change By: Thomas Hallgren Assignee: John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7979) Add a run_command() function
Title: Message Title Thomas Hallgren commented on PUP-7979 Re: Add a run_command() function The problem here is that the name of the Bolt#execute method was changed to Bolt#run_command in (maint) Add verbose debug and logging. I pushed a corresponding commit to the feature_puppet-tasks branch. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8000) Puppet lookup should be aware of node classification class parameters
Title: Message Title Thomas Hallgren assigned an issue to Past Haus Puppet / PUP-8000 Puppet lookup should be aware of node classification class parameters Change By: Thomas Hallgren Assignee: Thomas Hallgren Past Haus Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-8000) Puppet lookup should be aware of node classification class parameters
Title: Message Title Thomas Hallgren commented on PUP-8000 Re: Puppet lookup should be aware of node classification class parameters Is this a completely new requirement or has there been some other way of setting class parameters using a node classifier in the past? I find it odd that PE should fall short unless a new design is added. If it's a new design, is there a specification for this somewhere? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
