Jira (PUP-4795) smf.rb provider for service - manifest does not work for S11.x
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4795 smf.rb provider for service - manifest does not work for S11.x Change By: Josh Cooper Component/s: RE 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-9005) epp template fails to translate <%= ... %> when it is followed by a left parenthesis
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9005 epp template fails to translate <%= ... %> when it is followed by a left parenthesis Change By: Josh Cooper Component/s: Epp Component/s: Language 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-7823) Invalid EPP: Syntax error at '|' when use hash in epp templates
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7823 Invalid EPP: Syntax error at '|' when use hash in epp templates Change By: Josh Cooper Component/s: Epp Component/s: Language 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-8476) Incorrect handling of white space surrounding comments in EPP
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8476 Incorrect handling of white space surrounding comments in EPP Change By: Josh Cooper Component/s: Epp Component/s: Language 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-7691) puppet epp render fails on valid templates
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7691 puppet epp render fails on valid templates Change By: Josh Cooper Component/s: Epp Component/s: CLI 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-6169) Feature Request: Deprecation Logs
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6169 Feature Request: Deprecation Logs Change By: Josh Cooper Component/s: PuppetDB 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-8901) Puppet5 server does not work with Puppet4 termini
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8901 Puppet5 server does not work with Puppet4 termini Change By: Josh Cooper Component/s: PuppetDB 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-8373) Lookup CLI should use RBAC token if available for PuppetDB
Title: Message Title Josh Cooper updated an issue Puppet / PUP-8373 Lookup CLI should use RBAC token if available for PuppetDB Change By: Josh Cooper Component/s: PuppetDB 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-5747) puppet/PuppetBoard 2.7.3 not running with puppetdb 2.3.8
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5747 puppet/PuppetBoard 2.7.3 not running with puppetdb 2.3.8 Change By: Josh Cooper Component/s: PuppetDB 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-7306) puppet generate types for environment isolation generates invalid code
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7306 puppet generate types for environment isolation generates invalid code Change By: Josh Cooper Component/s: Generate types 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-9363) puppet bigtop installation error while importing '/bigtop-home/bigtop-deploy/puppet/modules/kerberos/manifests/init.pp' in environment production
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9363 puppet bigtop installation error while importing '/bigtop-home/bigtop-deploy/puppet/modules/kerberos/manifests/init.pp' in environment production Change By: Josh Cooper Component/s: Generate types 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-6432) Puppet::Util::Execution.execute cannot handle Unicode output on Windows
Title: Message Title Josh Cooper updated an issue Puppet / PUP-6432 Puppet::Util::Execution.execute cannot handle Unicode output on Windows Change By: Josh Cooper Component/s: triaged 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-7551) deprecate 'puppet describe'
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7551 deprecate 'puppet describe' Change By: Josh Cooper Component/s: triaged 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-1886) Realize virtual resource does not recognise name var unless explicitly set in user resource
Title: Message Title Josh Cooper updated an issue Puppet / PUP-1886 Realize virtual resource does not recognise name var unless explicitly set in user resource Change By: Josh Cooper Component/s: triaged 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-7647) All Puppet components should support SCEP
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7647 All Puppet components should support SCEP Change By: Josh Cooper Component/s: AIO 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-4450) Cannot load 'provider/network_route/routes.rb'
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4450 Cannot load 'provider/network_route/routes.rb' Change By: Josh Cooper Component/s: AIO 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-7976) Puppet agent fights with RPM package over owner/group of certain directories
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7976 Puppet agent fights with RPM package over owner/group of certain directories Change By: Josh Cooper Component/s: AIO 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-9506) Tried to load unspecified class: Time
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9506 Tried to load unspecified class: Time Change By: Josh Cooper Component/s: AIO 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-3973) puppet-mode.el indentation problems with if/else blocks
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3973 puppet-mode.el indentation problems with if/else blocks Change By: Josh Cooper Component/s: Emacs 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-9604) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Title: Message Title
Halim Wijaya updated an issue
Puppet / PUP-9604
Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Change By:
Halim Wijaya
**This is spin-off ticket of PUP-7326.*Steps to reproduce:* # Setup Active Directory with Domain Functional level 2016 # Spin up a Win2012R2 machine and connect to AD # Create a test user (e.q. testadmin1) in Active Directory # Add testadmin1 user to local administrators group in Win2012R2 # Delete testadmin1 user in AD # Run{code:java}puppet apply -e "group {'Administrators': members => ['Administrator'], auth_membership => true }"{code}Or # Setup Active Directory with Domain Functional level 2012 R2 # Spin up a Win2016 machine and connect to AD # Create a test user (e.q. testadmin1) in Active Directory # Add testadmin1 user to local administrators group in Win2016 # Delete testadmin1 user in AD # Run{code:java}puppet apply -e "group {'Administrators': members => ['Administrator'], auth_membership => true }{code}Puppet apply returns error below!image- 2019-04-05-10-41- 13-985.png |thumbnail !Note the error occurs only on Windows client machine with condition its OS version is different with the AD Domain Functional level. E.q. Client OS Win2012R connected to AD Domain Functional level 2016 or Client OS Win2016 connected to AD Domain Functional level 2012R2.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-7326) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts
Title: Message Title Halim Wijaya commented on PUP-7326 Re: Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts Thanks Josh, created new issue https://tickets.puppetlabs.com/browse/PUP-9604 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-9604) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Title: Message Title
Halim Wijaya updated an issue
Puppet / PUP-9604
Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Change By:
Halim Wijaya
**This is spin-off ticket of PUP-7326.*Steps to reproduce:* # Setup Active Directory with Domain Functional level 2016 # Spin up a Win2012R2 machine and connect to AD # Create a test user (e.q. testadmin1) in Active Directory # Add testadmin1 user to local administrators group in Win2012R2 # Delete testadmin1 user in AD # Run{code:java}puppet apply -e "group {'Administrators': members => ['Administrator'], auth_membership => true }"{code}Or # Setup Active Directory with Domain Functional level 2012 R2 # Spin up a Win2016 machine and connect to AD # Create a test user (e.q. testadmin1) in Active Directory # Add testadmin1 user to local administrators group in Win2016 # Delete testadmin1 user in AD # Run{code:java}puppet apply -e "group {'Administrators': members => ['Administrator'], auth_membership => true }{code}Puppet apply returns error below!image- 2019-04-05-10-41- 13-985.png!Note the error occurs only on Windows client machine with condition its OS version is different with the AD Domain Functional level. E.q. Client OS Win2012R connected to AD Domain Functional level 2016 or Client OS Win2016 connected to AD Domain Functional level 2012R2.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9604) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Title: Message Title Halim Wijaya updated an issue Puppet / PUP-9604 Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression) Change By: Halim Wijaya Attachment: image-2019-04-05-10-41-13-985.png 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-9604) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Title: Message Title
Halim Wijaya updated an issue
Puppet / PUP-9604
Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Change By:
Halim Wijaya
**This is spin-off ticket of PUP-7326.*Steps to reproduce:* # Setup Active Directory with Domain Functional level 2016 # Spin up a Win2012R2 machine and connect to AD # Create a test user (e.q. testadmin1) in Active Directory # Add testadmin1 user to local administrators group in Win2012R2 # Delete testadmin1 user in AD # Run{code:java} puppet apply -e "group {'Administrators': members => ['Administrator'], auth_membership => true }"{code}Or # Setup Active Directory with Domain Functional level 2012 R2 # Spin up a Win2016 machine and connect to AD # Create a test user (e.q. testadmin1) in Active Directory # Add testadmin1 user to local administrators group in Win2016 # Delete testadmin1 user in AD # Run{code:java} puppet apply -e "group {'Administrators': members => ['Administrator'], auth_membership => true }{code}Puppet apply returns error below! Screen Shot image- 2019-04- 03 at 11 05-10-41-13-985 . 44.28 AM. png!Note the error occurs only on Windows client machine with condition its OS version is different with the AD Domain Functional level. E.q. Client OS Win2012R connected to AD Domain Functional level 2016 or Client OS Win2016 connected to AD Domain Functional level 2012R2.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9604) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Title: Message Title
Halim Wijaya updated an issue
Puppet / PUP-9604
Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Change By:
Halim Wijaya
* Puppet Version: * This is spin-off ticket of PUP-7326. *Puppet Server Version:* * OS Name/Version Steps to reproduce :* # Setup Active Directory with Domain Functional level 2016 Describe your issue # Spin up a Win2012R2 machine and connect to AD # Create a test user (e.q. testadmin1) in as much detail as possible… Active Directory Describe steps # Add testadmin1 user to reproduce… local administrators group in Win2012R2 # Delete testadmin1 user in AD *Desired Behavior # Run{code : * java} *Actual Behavior puppet apply -e "group {'Administrators' : * members => ['Administrator'], auth_membership => true }"{code} Please take Or # Setup Active Directory with Domain Functional level 2012 R2 # Spin up a moment Win2016 machine and attach any relevant log output and/or manifests connect to AD # Create a test user (e . This will help us immensely when troubleshooting the issue q . testadmin1) in Active Directory # Add testadmin1 user to local administrators group in Win2016 Examples: # Delete testadmin1 user in AD # Run puppet agent with --test --trace --debug {code:java} Relevant sections of puppet apply -e "group { 'Administrators': members => ['Administrator'], auth_membership => true } { /var/log/puppetlabs/puppetserver/puppetserver.log code } } or any applicable logs from the same directory Puppet apply returns error below!Screen Shot 2019-04-03 at 11 . 44.28 AM.png! For more detailed information turn up Note the server logs by upping error occurs only on Windows client machine with condition its OS version is different with the log AD Domain Functional level in the server's logback . xmlRelevant sections of configurations files (puppet E . conf, hiera q . conf, Server's conf Client OS Win2012R connected to AD Domain Functional level 2016 or Client OS Win2016 connected to AD Domain Functional level 2012R2 . d, defaults/sysconfig) For memory issues with server heap dumps are also helpful.
Add Comment
Jira (PUP-9604) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression)
Title: Message Title Halim Wijaya updated an issue Puppet / PUP-9604 Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression) Change By: Halim Wijaya Summary: Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression ) 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-9604) Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression
Title: Message Title Halim Wijaya created an issue Puppet / PUP-9604 Group resource (with auth_membership) fails if local Windows group contains not resolvable Domain accounts (possible regression Issue Type: Bug Assignee: Unassigned Created: 2019/04/04 7:29 PM Priority: Normal Reporter: Halim Wijaya Puppet Version: Puppet Server Version: OS Name/Version: Describe your issue in as much detail as possible… Describe steps to reproduce… Desired Behavior: Actual Behavior: Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue. Examples: Run puppet agent with --test --trace --debug Relevant sections of /var/log/puppetlabs/puppetserver/puppetserver.log or any applicable logs from the same directory. For more detailed information turn up the server logs by upping the log level in the server's logback.xml Relevant sections of configurations files (puppet.conf, hiera.conf, Server's conf.d, defaults/sysconfig) For memory issues with server heap dumps are also helpful. Add Comment
Jira (PUP-9577) Large numbers of facts cause slow performance
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-9577 Large numbers of facts cause slow performance Change By: Adam Bottchen Priority: Normal Major 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-9577) Large numbers of facts cause slow performance
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-9577 Large numbers of facts cause slow performance Change By: Adam Bottchen CS Priority: Reviewed Major 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-9577) Large numbers of facts cause slow performance
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-9577 Large numbers of facts cause slow performance Change By: Adam Bottchen CS Priority: Needs Priority Reviewed 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 Josh Cooper commented on PUP-9579 Re: device application is broken in 6.4 Merged to 6.4.x in https://github.com/puppetlabs/puppet/commit/cb43a63cf7423fcb9e1e61afe696b16d411cb3a9, which fixes the regression in 6.4.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1914) Expose Facter.reset under jruby
Title: Message Title Casey Williams updated an issue Facter / FACT-1914 Expose Facter.reset under jruby Change By: Casey Williams Fix Version/s: FACT 3.13.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 (FACT-1914) Expose Facter.reset under jruby
Title: Message Title Casey Williams updated an issue Facter / FACT-1914 Expose Facter.reset under jruby Change By: Casey Williams Fix Version/s: FACT 3.13.1 Fix Version/s: FACT 3.13.z Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1914) Expose Facter.reset under jruby
Title: Message Title Branan Riley updated an issue Facter / FACT-1914 Expose Facter.reset under jruby Change By: Branan Riley Sprint: Skeletor Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1914) Expose Facter.reset under jruby
Title: Message Title Casey Williams assigned an issue to Branan Riley Facter / FACT-1914 Expose Facter.reset under jruby Change By: Casey Williams Assignee: Branan Riley 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 (FACT-1914) Expose Facter.reset under jruby
Title: Message Title Casey Williams created an issue Facter / FACT-1914 Expose Facter.reset under jruby Issue Type: Task Assignee: Unassigned Created: 2019/04/04 3:33 PM Priority: Normal Reporter: Casey Williams PAL calls Facter.reset here, but Facter.reset is not available under jruby. PAL will not be useful in orchestrator until facter.jar exposes reset. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4328) Change puppet-client-tools-vanagon to build puppetdb-cli as a ruby project
Title: Message Title Molly Waggett commented on PDB-4328 Re: Change puppet-client-tools-vanagon to build puppetdb-cli as a ruby project I've created separate puppet5 and puppet6 branches in the puppet-client-tools-vanagon repo. They're currently identical, but at least https://github.com/puppetlabs/puppet-client-tools-vanagon/pull/43 will be needed to build against puppet6. When we release, we should probably take this opportunity to do a major version bump and align with puppet5/puppet6 platform versions. This could either be creating 5.x and 6.x major versions (even though the content will be mostly identical) or we could do a single 2.x version and add a release field to distinguish between streams, e.g. https://github.com/puppetlabs/puppetlabs-release/blob/master/configs/projects/puppet5-release.rb#L3 but set to like '1p5' and '1p6' or something. Feel free to reach out to RE when you get to this step if you need help. 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-6382) Add "Automatic (delayed start)" as option for Service Resource on Windows
Title: Message Title Ryan Anderson commented on PUP-6382 Re: Add "Automatic (delayed start)" as option for Service Resource on Windows Our organization is very interested in having the ability to set this startup state on Windows services. It was submitted some time ago, might some development resources be given to this? 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-9262) Remove fine grained file and environment timeouts
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9262 Remove fine grained file and environment timeouts Change By: Josh Cooper Puppet will let you set fine grained file and environment timeouts, but it doesn't really work. We are deprecating the ability to set the timeout to something other than "always cache" vs "never cache" in [https://github.com/puppetlabs/puppet/pull/7001 . ] This ticket is to disallow any values other than 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9579) device application is broken in 6.4
Title: Message Title Josh Cooper commented on PUP-9579 Re: device application is broken in 6.4 Merged to 6.0.x in https://github.com/puppetlabs/puppet/commit/2101265205c839aaf898aa4f483a55df9bb10c7e. Note this cleans up the code in 6.0.8. The merge up will fix the regression in 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-9579) device application is broken in 6.4
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9579 device application is broken in 6.4 Change By: Josh Cooper Fix Version/s: PUP 6.0.8 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 Josh Cooper updated an issue Puppet / PUP-9584 Puppet Device plugin sync slow Change By: Josh Cooper Fix Version/s: PUP 6.0.8 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 Josh Cooper commented on PUP-9047 Re: puppet device --apply fails to apply catalog to unregistered targets pt. 2 David Schmitt can you add release notes? 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 Josh Cooper commented on PUP-9584 Re: Puppet Device plugin sync slow Merged to 6.0.x in https://github.com/puppetlabs/puppet/commit/00ffde0de472c78c9804daefbba2ba5dff3541be 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 Josh Cooper commented on PUP-9584 Re: Puppet Device plugin sync slow David Schmitt can you add release notes? 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 Josh Cooper updated an issue Puppet / PUP-9047 puppet device --apply fails to apply catalog to unregistered targets pt. 2 Change By: Josh Cooper Fix Version/s: PUP 6.4.1 Fix Version/s: PUP 6.0.8 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 Josh Cooper commented on PUP-9047 Re: puppet device --apply fails to apply catalog to unregistered targets pt. 2 Merged to 6.0.x in https://github.com/puppetlabs/puppet/commit/c72f735053e7f30069188caf1544fa8eb9b02d30 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-9602) puppet 6 apply fails if puppet types have been generated
Title: Message Title Vadym Chepkov commented on PUP-9602 Re: puppet 6 apply fails if puppet types have been generated To summarize my reproducer: [root@localhost ~]# puppet module install puppetlabs-puppetdb Notice: Preparing to install into /etc/puppetlabs/code/environments/production/modules ... Notice: Downloading from https://forgeapi.puppet.com ... Notice: Installing -- do not interrupt ... /etc/puppetlabs/code/environments/production/modules └─┬ puppetlabs-puppetdb (v7.1.0) ├── puppetlabs-firewall (v1.15.2) ├─┬ puppetlabs-inifile (v2.5.0) │ └── puppetlabs-translate (v1.2.0) └─┬ puppetlabs-postgresql (v5.12.1) ├── puppetlabs-apt (v6.3.0) ├── puppetlabs-concat (v5.3.0) └── puppetlabs-stdlib (v5.2.0)
Jira (PUP-9603) Documentation and/or spec for syntax checkers in heredocs out of date
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9603 Documentation and/or spec for syntax checkers in heredocs out of date Change By: Josh Cooper Sub-team: Language 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-9603) Documentation and/or spec for syntax checkers in heredocs out of date
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9603 Documentation and/or spec for syntax checkers in heredocs out of date Change By: Josh Cooper Team: Server Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9603) Documentation and/or spec for syntax checkers in heredocs out of date
Title: Message Title Josh Cooper assigned an issue to Jean Bond Puppet / PUP-9603 Documentation and/or spec for syntax checkers in heredocs out of date Change By: Josh Cooper Assignee: Jean Bond 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-9603) Documentation and/or spec for syntax checkers in heredocs out of date
Title: Message Title Josh Cooper commented on PUP-9603 Re: Documentation and/or spec for syntax checkers in heredocs out of date /cc Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9603) Documentation and/or spec for syntax checkers in heredocs out of date
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9603 Documentation and/or spec for syntax checkers in heredocs out of date Change By: Josh Cooper Component/s: DOCS 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-9602) puppet 6 apply fails if puppet types have been generated
Title: Message Title Vadym Chepkov commented on PUP-9602 Re: puppet 6 apply fails if puppet types have been generated If I am removing modules, I do not have catalog compiled. If you check output I provided earlier, catalog compiles and then it fails during applying it. I have tried to remove files from /etc/puppetlabs/code/environments/production/.resource_types/ one by one to see which one triggers the failure and all 4 listed type files do 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. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9603) Documentation and/or spec for syntax checkers in heredocs out of date
Title: Message Title LeLutin created an issue Puppet / PUP-9603 Documentation and/or spec for syntax checkers in heredocs out of date Issue Type: Bug Assignee: Unassigned Created: 2019/04/04 1:01 PM Priority: Normal Reporter: LeLutin Puppet Version: 6.4 Puppet Server Version: OS Name/Version: The document visible on https://github.com/puppetlabs/puppet-specifications/blob/master/language/heredoc.md#additional-semantics specifies a syntax for syntax checking of the contents of a heredoc string. (e.g. `@(END:_javascript_)` ) However official documentation has no mention of this: https://puppet.com/docs/puppet/6.4/lang_data_string.html#syntax I was told on IRC that the herdoc syntax for string content syntax checker was an experimental thing. helindbe then asked me to open this ticket so that documentation can be made up to date. Add Comment
Jira (PUP-9602) puppet 6 apply fails if puppet types have been generated
Title: Message Title Henrik Lindberg commented on PUP-9602 Re: puppet 6 apply fails if puppet types have been generated Hence my question regarding what you tried and what was on the module path. So, when you say "if any of these are present (even just alone)" does that mean that they were all on the modulepath, but you only declared a resource from one of them? If so, try by adding modules one by one to the module path to try to find the one that causes the problem. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-833) JSON Output for Results is confusing for new users
Title: Message Title Alex Dreyer commented on BOLT-833 Re: JSON Output for Results is confusing for new users In general I think we should prefer breaking changes to the json format rather then the plan language. One possible path forward that will not break plans is to inject _target and _status keys into the result's value. In Bolt 2.0 we can then change the json output to be just the value rather then have the value nested in result Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1223) Type information not available in plans.
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1223 Type information not available in plans. Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1223) Type information not available in plans.
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1223
Type information not available in plans.
Change By:
Alex Dreyer
There are major inconsistencies in how views a Result output vs how one accesses it. For example, running this command The use of { code}run_command('mkdir ~/boltexamples', $nodes).each | $result | { notice($result) type } {code } Provides me with a json hash output that looks easy to navigate (after piping through | python -mjson.tool:{code:json}{"node": "puppet.c.splunk-217321.internal","object": "mkdir ~/boltexamples","result": {"exit_code": 0,"stderr": "","stdout": ""},"status": "success"," refer to the type ": "command"}{code}Now looking at this of action that created a result , I would assume I could access the node name, object , result, and status just by referring is unable to be exposed as an attribute on the hash keys, result object since that's what I'm looking at. Assuming I've not yet dove into the docs and I'm just reading existing code and want to poke around, I may go and do this: { code}run_command('mkdir ~/boltexamples', $nodes).each | $result | { notice($result['node']) type } {code } Which is frustrating because the output I get is:{code}Starting: command 'mkdir ~/boltexamples' on puppet.c.splunk-217321.internalFinished: command 'mkdir ~/boltexamples' with 0 failures used elsewhere in 2 Puppet . 28 sec Finished Possible solutions : plan firstproject::firstplan in 5.1 sec Plan completed successfully with no result{code}So I guess that's an empty hash? How do I actually access these variables? Now I have to go to the documentation to see what is what - which explains that I can access those as functions, but function names have no correllation to what I was just looking at, in fact we hide the mapping in the code here:https://github 1 . com/puppetlabs/bolt/blob/master/lib/bolt/result.rb#L93-L99Ah, now I see if I want the node name, I have Rename this key to call $result.target.name - otherwise I just get the result of { code}Target('puppet.c.splunk-217321.internal', { "user"=>"cbarker" action } ){code } Bonus surprise: I'd think I could get away and expose it with `$result a method . type` to see what type of function this was, but instead, I get the ruby definition of the object: 2. Add a { code}Object[ { name => 'Result', attributes => {'value' => Hash[String[1], Data], 'target' => Target to_data } , functions => {'error' => Callable[[0, 0], Optional[Error]], 'message' => Callable[[0, 0], Optional[String]], 'ok' => Callable[[0, 0], Boolean], '[]' => Callable[[String[1]], Data] } }]{code}Making the onscreen output of Bolt be logically consistent with methods method to call and extract the Result object that data will be essential for new users to learn how to access and work with it. If we're going to to have `notice($result)` output returns a hash , I should be able equivalent to access the subhash without having to read the
Jira (BOLT-1223) Inconsistencies in Result outputs vs access methods
Title: Message Title Alex Dreyer commented on BOLT-1223 Re: Inconsistencies in Result outputs vs access methods I appreciate the feedback advocating for new users. Please keep in mind the following constraints. 1. The plan language is constrained by the syntax of the puppet language on top of which it is built. The core syntax has been mature for years. We can add new features but we can't really change the core behavior of the language. 2. We need to balance the ease of learning the language with adding features that increase it's expressiveness for advanced users. Standardizing in such a way that advances users have to type out lots of boilerplate or run into leaky abstractions is not an option. 3. Bolt is 1.0. Changes that break existing plans are expensive for us to develop and release and a burden for the community to adopt. Most requests for breaking changes will be closed. I'm constraining this ticket to handle the type issue with the result. The rest of this is covered by BOLT-833. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1223) Type information not available in plans.
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1223 Type information not available in plans. Change By: Alex Dreyer Summary: Inconsistencies Type information not available in Result outputs vs access methods plans. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4311) Build and test pe-puppetdb for el-8
Title: Message Title Sara Meisburger updated an issue PuppetDB / PDB-4311 Build and test pe-puppetdb for el-8 Change By: Sara Meisburger pe-puppetdb & pe-puppetdb-termini need to go into enterprise-dist kearney * Update ezbake version in pe-puppetdb-extensions for el-8 * Add el 8 to [pe-puppetdb-extensions in ci-job-configs|https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/enterprise/projects/puppetdb.yaml] https://tickets.puppetlabs.com/browse/PDB-4302 seems to relate? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4311) Build and test pe-puppetdb for el-8
Title: Message Title Sara Meisburger updated an issue PuppetDB / PDB-4311 Build and test pe-puppetdb for el-8 Change By: Sara Meisburger pe-puppetdb & pe-puppetdb-termini need to go into enterprise-dist kearney * Update ezbake version in pe-puppetdb-extensions for el-8* Add el 8 to [pe-puppetdb-extensions in ci-job-configs|https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/enterprise/projects/puppetdb.yaml] Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4311) Build and test pe-puppetdb for el-8
Title: Message Title Sara Meisburger updated an issue PuppetDB / PDB-4311 Build and test pe-puppetdb for el-8 Change By: Sara Meisburger Summary: Build and test pe-puppetdb -extensions for el-8 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1223) Inconsistencies in Result outputs vs access methods
Title: Message Title Alex Dreyer commented on BOLT-1223 Re: Inconsistencies in Result outputs vs access methods All attributes of Result object itself are all available with dot notation. Those attributes return different types of objects which each have their own behavior. Some like value return a Hash object which exposes bracket indexing but not many attributes. Some return a simple objects on which attributes don't make sense for example success. Some return a more specific which has other attributes and methods Target for example has .name and .port methods. The keys inside the results value are not really "properties" of the result object in the same way .target is. $r.value['key'] turned out in our initial testing to be one of the most common interactions with a Result object. The value is the core attribute of the object therefore we decided to add the syntactic sugar of letting bracket indexing on the Result object itself index into the value. We could, if desired, add bracket indexing to the Target object to allow $target['port'] to behave the same as $target.port this makes some sense semantically because port could be part of the options hash of the Target. In the puppet language there is no way we can do all of the following: support powerful methods like $result.errorset, have meaningful errors when things are used incorrectly and support a single lookup method either dot syntax or bracket syntax. While the puppet language has some rough edges this is not one of them. It's true of pretty much every language except _javascript_ where bracket syntax can be used everywhere. It could be argued that _javascript_ doesn't provide meaningful errors when things are used incorrectly because of this design choice. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1209) Intermittent AppVeyor test failure - WSMAN ERROR CODE: 1018 / WSMAN ERROR CODE: 2147746132
Title: Message Title David Kramer assigned an issue to Ethan Brown Puppet Task Runner / BOLT-1209 Intermittent AppVeyor test failure - WSMAN ERROR CODE: 1018 / WSMAN ERROR CODE: 2147746132 Change By: David Kramer Assignee: Ethan Brown Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1223) Inconsistencies in Result outputs vs access methods
Title: Message Title JD Welch commented on BOLT-1223 Re: Inconsistencies in Result outputs vs access methods For specific cases we can enable . indexing into hashlike objects but that means those objects cannot be generic data structures like Hash. Ah, OK. Thanks for the detailed context; that helps a lot. So because target will always have a name, we can enable the more magical indexing. Gotcha. try something and see what works and what fails are the main ways to learn a programming language That's exactly how I'm finding inconsistent behaviour. Will neither syntax (dots or braces) work for all cases? I don't even care all that much about which it is, just that all the properties of $result can be accessed in a predictable way. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1223) Inconsistencies in Result outputs vs access methods
Title: Message Title Alex Dreyer commented on BOLT-1223 Re: Inconsistencies in Result outputs vs access methods JD Welch unfortunately puppet is a language in which the user has to care about that distinction. The only language that isn't that I can think of off of the top of my head is _javascript_ which is fundamentally built around the concept that all objects are the same and indexable with brace and dot notation. It's not a feature that can be tacked on to a language and even in _javascript_ users still cannot use dot indexing in every case. The nature of the puppet language is that is has DataTypes which can have methods they can also implement indexing with []. For specific cases we can enable . indexing into hashlike objects but that means those objects cannot be generic data structures like Hash. In addition to methods that live on the DataType users can write their own functions that live separately in modules and still use . indexing. When we enable magical . indexing we make that interface behave poorly. It would be feasible for us to have a special DataType for the results of run_command and run_script that exposed .stdout as a method without allowing magical .indexing into the value. Due to the fact that the puppet language does not have inheritance we would need a separate DataType for those results from the other types which would have to be reunited with a type alias. There are some rough edges with using an alias instead of a proper type and there is no way we can do this without introducing a breaking change to the plan language. Read the docs, copy/paste from stack overflow, rely on an editor plugin that exposes options and docs as you type, and try something and see what works and what fails are the main ways to learn a programming language. Learning what the core objects are and how they behave is just part of learning to use a new language or framework. We should make that as easy as possible without limiting the power of the language(for example by only using hashes for everything) or making expensive leaky abstractions(like magical . indexing). Add Comment This message was sent by Atlassian JIRA
Jira (BOLT-1223) Inconsistencies in Result outputs vs access methods
Title: Message Title JD Welch commented on BOLT-1223 Re: Inconsistencies in Result outputs vs access methods So why doesn't $result.value.stdout behave similarly? Because there's not a method stdout on value, of course. But how am I supposed to learn name is a method and stdout is a property? "Read the docs" isn't a reasonable answer. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1223) Inconsistencies in Result outputs vs access methods
Title: Message Title Alex Dreyer commented on BOLT-1223 Re: Inconsistencies in Result outputs vs access methods notice($result.target.name) puppet.c.splunk-217321.internal Is correct. The Result object has a .target method that returns a Target object. The Target object has a .name method that returns a name. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1186) Improve Bolt startup time on Windows redux
Title: Message Title Kevin Reeuwijk commented on BOLT-1186 Re: Improve Bolt startup time on Windows redux running Bolt 1.15 on my Windows server at home: bolt command run "echo hello" --nodes localhost --> 6.28 seconds bolt --> 5.07 seconds so it got a bit faster, but I’d still call it slow. For comparison on my Mac: bolt command run "echo hello" --nodes localhost --> 2.17 seconds bolt --> 2.33 seconds Basically it’s twice as slow on Windows. We could blame Windows Defender as it doubles the runtime, but the problem is that Ansible is lightning fast on Windows... Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1223) Inconsistencies in Result outputs vs access methods
Title: Message Title Alex Dreyer commented on BOLT-1223 Re: Inconsistencies in Result outputs vs access methods But do we prevent a task from returning a _*? Or are we dependent on the task author to not do that. We are dependent on the task author following documentation. The use of some special keys is documented and encouraged for example _error and _output. The only other option for ill behaved tasks would be to error or warn after running any task that uses an unexpected special key which would introduce unnecessary versioning pain. But that isn't consistent with the API calls, and unless $result['_node'] returns the value then that isn't exactly useful either. It is useful, you can pass it to get_targets or --nodes. Returning references instead of full objects in a json representation is a pretty common pattern. It also avoids issues about returning secrets with this data or it bloating with all of the facts and vars that are also conceptually part of a Target object. How is this better for someone who is trying to write their first plan? Why are we optimizing for the person who is already writing multiple plans? We work balance the needs of the new user with those of the returning user. Ideally language syntax is easily understandable, efficient, and powerful. Most of the time especially when building on top of existing syntax there are tradeoffs. As a rough heuristic the language features that a beginning user is likely to use are optimized for understandability while those targeted at more advanced users are optimized towards efficiency and power. Add Comment This message was sent by Atlassian JIRA
Jira (BOLT-1228) SPIKE Add `bolt module create` command to create skeleton module
Title: Message Title Lucy Wyman updated an issue Puppet Task Runner / BOLT-1228 SPIKE Add `bolt module create` command to create skeleton module Change By: Lucy Wyman Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1228) SPIKE Add `bolt module create` command to create skeleton module
Title: Message Title Lucy Wyman created an issue Puppet Task Runner / BOLT-1228 SPIKE Add `bolt module create` command to create skeleton module Issue Type: New Feature Assignee: Unassigned Created: 2019/04/04 8:28 AM Priority: Normal Reporter: Lucy Wyman This would be a new subcommand to create a skeleton module, per https://puppet.com/docs/bolt/latest/bolt_project_directories.html#local-project-directory. The main question here is how tightly coupled this should be with `pdk new module`. Having an entirely separate subcommand that lives in and is owned by bolt means users only have to install 1 package to generate the module, but on the other hand it feels like a duplication. Add Comment This
Jira (BOLT-1223) Inconsistencies in Result outputs vs access methods
Title: Message Title JD Welch commented on BOLT-1223 Re: Inconsistencies in Result outputs vs access methods OK, here's my real example I'm using to try and figure out the current behaviour: # works: $t = $result.target.name $v = $result.value['stdout'] # following on that, I expect these to work, but do not: $t = $result.target['name'] $v = $result.value.stdout As an end user, I simply don't understand why one works and the other doesn't. And I shouldn't have to care. Add Comment
Jira (BOLT-1223) Inconsistencies in Result outputs vs access methods
Title: Message Title
Chris Barker commented on BOLT-1223
Re: Inconsistencies in Result outputs vs access methods
Alex Dreyer which one is the right one? 1) notice($result.target.name) gives me: puppet.c.splunk-217321.internal or 2) notice($result['target']['name']) gives me:
{
"kind": "bolt/pal-error",
"msg": "Evaluation Error: Operator '[]' is not applicable to an Undef Value. (file: /Users/cbarker/src/pdx/bolt/firstproject/site-modules/firstproject/plans/firstplan.pp, line: 15, column: 12)",
"details": {
}
}
Add Comment
Jira (BOLT-1223) Inconsistencies in Result outputs vs access methods
Title: Message Title Alex Dreyer commented on BOLT-1223 Re: Inconsistencies in Result outputs vs access methods JD Welch thats valid syntax in _javascript_ but not puppet(or most other programming languages). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1223) Inconsistencies in Result outputs vs access methods
Title: Message Title JD Welch commented on BOLT-1223 Re: Inconsistencies in Result outputs vs access methods FWIW, I'm trying to sort out the current behaviour and am getting fairly lost myself. As a reasonably adept but novice end-user of Bolt, I would expect both $t = $result.target.name $t = $result['target']['name'] to return a sensible value. 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-9602) puppet 6 apply fails if puppet types have been generated
Title: Message Title Vadym Chepkov commented on PUP-9602 Re: puppet 6 apply fails if puppet types have been generated Yes, his example works, it must be combination of other types that causes it 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-9602) puppet 6 apply fails if puppet types have been generated
Title: Message Title Henrik Lindberg commented on PUP-9602 Re: puppet 6 apply fails if puppet types have been generated Vadym Chepkov That seems to contradict what Josh Cooper showed in his example using anchor - does the example he showed work for you? 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-9602) puppet 6 apply fails if puppet types have been generated
Title: Message Title Vadym Chepkov commented on PUP-9602 Re: puppet 6 apply fails if puppet types have been generated Henrik Lindberg, I have experimented with all of the generated puppet types and determined that if any of these are present (even just alone) catalog fails anchor.pp postgresql_conf.pp postgresql_conn_validator.pp postgresql_psql.pp Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) --
Jira (PUP-9602) puppet 6 apply fails if puppet types have been generated
Title: Message Title Henrik Lindberg commented on PUP-9602 Re: puppet 6 apply fails if puppet types have been generated Vadym Chepkov When you reduced the reproducer did you also take out all unused modules on the module path so it contained only exactly what was needed? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9602) puppet 6 apply fails if puppet types have been generated
Title: Message Title Henrik Lindberg commented on PUP-9602 Re: puppet 6 apply fails if puppet types have been generated When we have had issues with this in the past it has usually been because of logic using old or internal APIs. Could be that one of the modules is doing something it is not supposed to do. The last one that I remember was fixed with a PR from eric sorensson - the PR is here https://github.com/puppetlabs/puppet/pull/7162. (A lot more detective work needed). While a solution is to simply skip the generated types in an apply case, that would also mean it is not possible to debug/try-out compilation with puppet apply running with generated types, which makes testing a lot more difficult. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1223) Inconsistencies in Result outputs vs access methods
Title: Message Title
Chris Barker commented on BOLT-1223
Re: Inconsistencies in Result outputs vs access methods
What I'm trying to reconcile as an enduser and as someone whose looking at teaching these concepts to a novice user with no programming experience is: The $result.value() is important and referenced often, so we want to make less keystrokes to get to it, so $result[] should just include all the contents of it. However a task can return arbitrary values and any keyname it wants, so for internal things we want to prevent being conflicted with, we will prepend them with _*. But do we prevent a task from returning a _*? Or are we dependent on the task author to not do that. Since we're exposing keynames as _* to the user, they may assume that is a safe behavior, we make no indication as such in the code, instead relying on the user to read and learn more about the philosophy of our tool and internalize the mental model how objects and methods behave, before they can continue working on it. Going back to the original problem: I am trying to get values from a thing called $result, when I do notice($result) I get:
{
"node": "puppet.c.splunk-217321.internal",
"object": "mkdir ~/boltexamples",
"result": {
"exit_code": 0,
"stderr": "",
"stdout": ""
},
"status": "success",
"type": "command"
Jira (PUP-9601) mount resource should trigger 'systemctl daemon-reload'
Title: Message Title Adam Winberg commented on PUP-9601 Re: mount resource should trigger 'systemctl daemon-reload' Additionally you would also need to trigger a systemctl restart remote-fs.target or systemctl restart local-fs.target , depending on whether the mount is remote (for example nfs) or local. Otherwise systemd will not create the mountpoints until next reboot. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because
Jira (PUP-9139) Package provider apt fails when installing from local file
Title: Message Title Dirk Heinrichs commented on PUP-9139 Re: Package provider apt fails when installing from local file Any news on this? 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-9502) codesigning puppet executables on macOS 10.14
Title: Message Title Gheorghe Popescu assigned an issue to Gheorghe Popescu Puppet / PUP-9502 codesigning puppet executables on macOS 10.14 Change By: Gheorghe Popescu Assignee: Gheorghe Popescu Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4330) (DO NOT MERGE) trash bad state on build server
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4330 (DO NOT MERGE) trash bad state on build server Issue Type: Bug Assignee: Unassigned Created: 2019/04/03 11:40 PM Priority: Normal Reporter: gepetto-bot I don't have SSH access to the build server, so using this to run a couple quick commands Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9601) mount resource should trigger 'systemctl daemon-reload'
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9601 mount resource should trigger 'systemctl daemon-reload' Change By: Mihai Buzgau Story Points: 3 Sprint: PR - 2019-04-17 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.
