Jira (FACT-1886) Facter3 should also check for 'Virtuozzo Linux'

2019-06-12 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau assigned an issue to Gheorghe Popescu  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1886  
 
 
  Facter3 should also check for 'Virtuozzo Linux'
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.276378.1537368012000.43459.1560326700272%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1886) Facter3 should also check for 'Virtuozzo Linux'

2019-06-12 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1886  
 
 
  Facter3 should also check for 'Virtuozzo Linux'
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-04-17, PR - 2019-05-02, PR - 2019-05-15, PR - 2019-05-29, PR - 2019-06-12 , PR - 2019-06-25  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.276378.1537368012000.43485.1560327664174%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1926) ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5

2019-06-12 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1926  
 
 
  ipaddress fact changed behaviour in FreeBSD, returns incorrect result with Puppet 5   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-06-12 , PR - 2019-06-25  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309683.1558519845000.43545.1560327667837%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1910) Mountpoint fact only shows tmpfs and physical mounts

2019-06-12 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1910  
 
 
  Mountpoint fact only shows tmpfs and physical mounts   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-06-12 , PR - 2019-06-25  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.299364.1552075723000.43537.1560327667477%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9722) Regression: File mode changed on every puppet run

2019-06-12 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9722  
 
 
  Regression: File mode changed on every puppet run   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-06-12 , PR - 2019-06-25  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310253.1558976203000.43554.1560327668294%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8736) /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs

2019-06-12 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8736  
 
 
  /opt/puppetlabs contains device ssldir(s) normally in /etc/puppetlabs   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-06-12 , PR - 2019-06-25  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.251027.1526491177000.43534.1560327667333%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1888) 'os.release' values not correct for VZ7

2019-06-12 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1888  
 
 
  'os.release' values not correct for VZ7   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-04-03, PR - 2019-04-17, PR - 2019-05-02, PR - 2019-05-15, PR - 2019-05-29, PR - 2019-06-12 , PR - 2019-06-25  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.278967.1538669961000.43492.1560327664965%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9573) win32-service gem needs updating

2019-06-12 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9573  
 
 
  win32-service gem needs updating   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-05-15, PR - 2019-05-29, PR - 2019-06-12 , PR - 2019-06-25  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.301020.1553109081000.43501.1560327665492%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9691) Puppet pidlock incorrectly clears lock when running under bundler

2019-06-12 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9691  
 
 
  Puppet pidlock incorrectly clears lock when running under bundler   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-05-29, PR - 2019-06-12 , PR - 2019-06-25  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307420.1556926648000.43526.1560327666948%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9697) Solaris Crontabs -> puppet resource cron only returns root account

2019-06-12 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9697  
 
 
  Solaris Crontabs -> puppet resource cron only returns root account   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR - 2019-06-12 , PR - 2019-06-25  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308025.155742000.43523.1560327666751%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9573) win32-service gem needs updating

2019-06-12 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9573  
 
 
  win32-service gem needs updating   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR -  Triage, PR -  2019-05-15, PR - 2019-05-29, PR - 2019-06-12 , PR - 2019-06-25  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.301020.1553109081000.43564.1560327960447%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9719) Can't run puppet agent after installing the MSI using the SYSTEM account

2019-06-12 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9719  
 
 
  Can't run puppet agent after installing the MSI using the SYSTEM account   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310162.1558726819000.43571.1560328380198%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9719) Can't run puppet agent after installing the MSI using the SYSTEM account

2019-06-12 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9719  
 
 
  Can't run puppet agent after installing the MSI using the SYSTEM account   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR -  Triage  2019-06-25  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310162.1558726819000.43573.1560328740324%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9605) Type package (provider yum) fails when handling kernel packages

2019-06-12 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9605  
 
 
  Type package (provider yum) fails when handling kernel packages   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.303636.1554712703000.43584.1560328980294%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9605) Type package (provider yum) fails when handling kernel packages

2019-06-12 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9605  
 
 
  Type package (provider yum) fails when handling kernel packages   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR -  Triage  2019-06-25  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.303636.1554712703000.43586.1560328980387%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1884) Add NIM master detection

2019-06-12 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1884  
 
 
  Add NIM master detection   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 5  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.276290.1537303892000.43602.1560329580283%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1884) Add NIM master detection

2019-06-12 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1884  
 
 
  Add NIM master detection   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR -  Triage  2019-06-25  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.276290.1537303892000.43604.1560329640213%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1929) Report disks serial numbers

2019-06-12 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1929  
 
 
  Report disks serial numbers   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR -  Triage  2019-06-25  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310677.1559162327000.43613.1560329940449%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1929) Report disks serial numbers

2019-06-12 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1929  
 
 
  Report disks serial numbers   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310677.1559162327000.43610.1560329940350%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1916) facter fails to parse routing table

2019-06-12 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1916  
 
 
  facter fails to parse routing table   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Sprint: 
 PR -  Triage  2019-06-25  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307043.155680303.43624.1560330360377%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1916) facter fails to parse routing table

2019-06-12 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1916  
 
 
  facter fails to parse routing table   
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307043.155680303.43622.1560330360278%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1886) Facter3 should also check for 'Virtuozzo Linux'

2019-06-12 Thread Mihai Buzgau (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mihai Buzgau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Facter /  FACT-1886  
 
 
  Facter3 should also check for 'Virtuozzo Linux'
 

  
 
 
 
 

 
Change By: 
 Mihai Buzgau  
 
 
Story Points: 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.276378.1537368012000.43694.1560331920808%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-4399) PuppetDB Docker DNS lookup requirement may break CI

2019-06-12 Thread Rune Juhl Jacobsen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rune Juhl Jacobsen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4399  
 
 
  PuppetDB Docker DNS lookup requirement may break CI   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 PuppetDB  
 
 
Created: 
 2019/06/12 2:49 AM  
 
 
Labels: 
 docker  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Rune Juhl Jacobsen  
 

  
 
 
 
 

 
 Recent changes to the PuppetDB Docker image adds a requirement on DNS resolution for Puppetserver and Consul hosts linked to the PuppetDB. This has had the unfortunate effect of breaking our CI pipeline. In the pipeline we spin up PostgreSQL, PuppetDB and Puppetserver in Gitlab CI. Because Gitlab CI doesn't provide a local DNS server for "services" we inject a hosts file into each of the parts of the system so each container can resolve the IP of the other containers. I've added some comments on https://github.com/puppetlabs/puppetdb/commit/0319e96c4d759bb419ec6e53c711538a0d1ff405#r33804010 , and a few other users have chimed in saying that the change also broke their CI. IMO the best solution is to provide a flag set by an environment variable to select whether or not DNS name resolution should be used. Using it by default is fine, as long as it's possible to disable it easily.  
 

  
 
 
 
 

 
 
 

 
   

Jira (PUP-9554) Add ability to create regexp with all special chars escaped

2019-06-12 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9554  
 
 
  Add ability to create regexp with all special chars escaped   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Release Notes Summary: 
 It is now possible to create a Regexp that escapes all regexp special characters by adding a boolean `true` as a second argument in a call to `new`. For example `Regexp(".[/", true)` or `Regexp.new(".[/", true)`. A second value of `false` is the default.  
 
 
Release Notes: 
 New Feature  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.299501.1552318633000.43801.1560339241717%40Atlassian.JIR

Jira (PUP-9643) protection against illegal methods in legacy functions hides syntax error

2019-06-12 Thread Henrik Lindberg (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Henrik Lindberg updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9643  
 
 
  protection against illegal methods in legacy functions hides syntax error   
 

  
 
 
 
 

 
Change By: 
 Henrik Lindberg  
 
 
Release Notes Summary: 
 When loading a 3x (legacy)  ruby  Ruby  function  with  containing  Ruby syntax errors the error raised would only say "does not seem to be a Puppet 3x API function". Now the underlying syntax error is made visible.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.304723.1555336207000.43816.1560339420929%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-4397) Error while evaluating a Resource Statement, Systemd::Unit_file[puppetdb-dlo-cleanup.timer]

2019-06-12 Thread zoen (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 zoen commented on  PDB-4397  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Error while evaluating a Resource Statement, Systemd::Unit_file[puppetdb-dlo-cleanup.timer]   
 

  
 
 
 
 

 
 Austin Blatt, thanks for your quick answer. yeap disabling the automatic_dlo_cleanup it pass away. I will try to update our systemd module to 2.0. Thanks  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312001.1560267294000.43833.1560343020389%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1380) OSCON Demo

2019-06-12 Thread Lucy Wyman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucy Wyman commented on  BOLT-1380  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: OSCON Demo   
 

  
 
 
 
 

 
 https://github.com/enquirer/enquirer  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312023.1560269876000.43898.1560349080067%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1316) The plan language should have a catch_errors functions

2019-06-12 Thread Lucy Wyman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lucy Wyman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1316  
 
 
  The plan language should have a catch_errors functions   
 

  
 
 
 
 

 
Change By: 
 Lucy Wyman  
 
 
Labels: 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309066.155804176.43901.1560349140311%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1261) Common debugging and best practices documents

2019-06-12 Thread Melissa Amos (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Melissa Amos updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1261  
 
 
  Common debugging and best practices documents   
 

  
 
 
 
 

 
Change By: 
 Melissa Amos  
 
 
Labels: 
 docs_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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305719.1555863895000.44017.1560355080264%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9720) puppet agent --fingerprint is broken

2019-06-12 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9720  
 
 
  puppet agent --fingerprint is broken   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Sprint: 
 Coremunity Hopper Platform Core KANBAN  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310230.1558735767000.44020.1560355209683%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9720) puppet agent --fingerprint is broken

2019-06-12 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9720  
 
 
  puppet agent --fingerprint is broken   
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Fix Version/s: 
 PUP 6.5.0  
 
 
Fix Version/s: 
 PUP 6.6.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310230.1558735767000.44021.1560355260268%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9717) Puppet 6 client exits on start when it cannot connect to puppetserver

2019-06-12 Thread Josh Cooper (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh Cooper updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9717  
 
 
  Puppet 6 client exits on start when it cannot connect to puppetserver
 

  
 
 
 
 

 
Change By: 
 Josh Cooper  
 
 
Fix Version/s: 
 PUP 6.5.0  
 
 
Fix Version/s: 
 PUP 6.6.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309697.1558538932000.44023.1560355260371%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9749) puppet generate types should be run when the puppetserver is upgraded

2019-06-12 Thread Trevor Vaughan (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Trevor Vaughan created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9749  
 
 
  puppet generate types should be run when the puppetserver is upgraded   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/06/12 9:01 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Trevor Vaughan  
 

  
 
 
 
 

 
 When the puppetserver is upgraded, existing artifacts generated by puppet generate types may no longer work and so it needs to be re-run automatically on upgrade.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   

Jira (PUP-9717) Puppet 6 client exits on start when it cannot connect to puppetserver

2019-06-12 Thread Siebrand Mazeland (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Siebrand Mazeland updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9717  
 
 
  Puppet 6 client exits on start when it cannot connect to puppetserver
 

  
 
 
 
 

 
Change By: 
 Siebrand Mazeland  
 

  
 
 
 
 

 
 *Puppet Version: 6.4.2* *Puppet Server Version: 6.3.0* *OS Name/Version: CentOS 7.6*In previous versions of puppet, I would spin up instances in AWS, regardless of the puppetservere being available, and have runinterval at 20 seconds. Whenever the base packages were installed, I'd update the puppet configuration to a runinterval of every 30 minutes.Since I've started version 6 clients, this "trick" no longer works. The puppet client will try to connect to the puppetserver when it starts, and if it doesn't it will exit. That's quite disastrous for my deployment strategy.Steps to reproduce:Pre-requisites: Have the above puppet server and client versions on a single machine. Have puppetserver and client stopped.1. Start puppet client.*Desired Behavior:*A. puppet client starts, regardless of a connection is possible with the puppetserver. It will re-try each runinterval.*Actual Behavior:*  - puppet client exits with below message in /var/log/ message messages :{noformat}  May 22 15:08:05 bas-t-1 systemd: Started Puppet agent.May 22 15:08:07 bas-t-1 puppet-agent[12580]: Could not run: Failed to open TCP connection to bas-t-1.t.dam.loc:8140 (Connection refused - connect(2) for "bas-t-1.t.dam.loc" port 8140)May 22 15:08:07 bas-t-1 systemd: puppet.service: main process exited, code=exited, status=1/FAILUREMay 22 15:08:07 bas-t-1 systemd: Unit puppet.service entered failed state.May 22 15:08:07 bas-t-1 systemd: puppet.service failed.{noformat}puppet.conf:{noformat}  [main]server = bas-t-1.t.dam.locenvironment = productionruninterval = 20shiera_config = /etc/puppetlabs/puppet/hiera.yaml[master]dns_alt_names = bas-t-1.t.dam.loc{noformat}   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 

Jira (BOLT-1379) Document that "upload file" is able to handle directories as well as files

2019-06-12 Thread Melissa Amos (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Melissa Amos updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1379  
 
 
  Document that "upload file" is able to handle directories as well as files   
 

  
 
 
 
 

 
Change By: 
 Melissa Amos  
 
 
Labels: 
 docs  docs_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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311900.1560188799000.44208.1560357120582%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9570) Catalog failure on first run due to pluginsync and environment switch

2019-06-12 Thread Jorie Tappa (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jorie Tappa updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9570  
 
 
  Catalog failure on first run due to pluginsync and environment switch   
 

  
 
 
 
 

 
Change By: 
 Jorie Tappa  
 
 
Fix Version/s: 
 PUP 6.6.0  
 
 
Fix Version/s: 
 PUP 6.y  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300842.1553021716000.44213.1560357180862%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1376) Support puppetfile -> forge -> baseurl setting in bolt.yaml

2019-06-12 Thread Nick Lewis (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Lewis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1376  
 
 
  Support puppetfile -> forge -> baseurl setting in bolt.yaml   
 

  
 
 
 
 

 
Change By: 
 Nick Lewis  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311712.1559939792000.44227.1560357300205%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1376) Support puppetfile -> forge -> baseurl setting in bolt.yaml

2019-06-12 Thread Nick Lewis (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Lewis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1376  
 
 
  Support puppetfile -> forge -> baseurl setting in bolt.yaml   
 

  
 
 
 
 

 
Change By: 
 Nick Lewis  
 
 
Release Notes: 
 New Feature  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311712.1559939792000.44229.1560357362162%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1376) Support puppetfile -> forge -> baseurl setting in bolt.yaml

2019-06-12 Thread Nick Lewis (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Lewis updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1376  
 
 
  Support puppetfile -> forge -> baseurl setting in bolt.yaml   
 

  
 
 
 
 

 
Change By: 
 Nick Lewis  
 
 
Release Notes Summary: 
 The "puppetfile" config section now supports a "forge" sub-section which can be used to set an alternate Puppet Forge location from which to download modules.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311712.1559939792000.44233.1560357420576%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1382) wait_until_available() incorrect results using Orchestrator

2019-06-12 Thread David Kramer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Kramer assigned an issue to Lucy Wyman  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1382  
 
 
  wait_until_available() incorrect results using Orchestrator   
 

  
 
 
 
 

 
Change By: 
 David Kramer  
 
 
Assignee: 
 Lucy Wyman  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312114.1560285784000.44266.1560357960902%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1382) wait_until_available() incorrect results using Orchestrator

2019-06-12 Thread David Kramer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 David Kramer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1382  
 
 
  wait_until_available() incorrect results using Orchestrator   
 

  
 
 
 
 

 
Change By: 
 David Kramer  
 
 
Sprint: 
 Bolt Kanban  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312114.1560285784000.44260.1560357960609%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9570) Catalog failure on first run due to pluginsync and environment switch

2019-06-12 Thread Jorie Tappa (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jorie Tappa updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9570  
 
 
  Catalog failure on first run due to pluginsync and environment switch   
 

  
 
 
 
 

 
Change By: 
 Jorie Tappa  
 
 
Fix Version/s: 
 PUP 6.y  
 
 
Fix Version/s: 
 PUP 6.6.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300842.1553021716000.44438.1560360361014%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1222) Support an "apply" step.

2019-06-12 Thread Nick Lewis (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Lewis assigned an issue to Nick Lewis  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1222  
 
 
  Support an "apply" step.   
 

  
 
 
 
 

 
Change By: 
 Nick Lewis  
 
 
Assignee: 
 Nick Lewis  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.302484.1554141988000.44454.1560360421699%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9554) Add ability to create regexp with all special chars escaped

2019-06-12 Thread Heston Hoffman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Heston Hoffman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9554  
 
 
  Add ability to create regexp with all special chars escaped   
 

  
 
 
 
 

 
Change By: 
 Heston Hoffman  
 
 
Labels: 
 resolved-issue-added  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.299501.1552318633000.44553.1560362220547%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8664) rpm package provider is too specific

2019-06-12 Thread Heston Hoffman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Heston Hoffman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8664  
 
 
  rpm package provider is too specific   
 

  
 
 
 
 

 
Change By: 
 Heston Hoffman  
 
 
Labels: 
 cs_pr_review  resolved-issue-added  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.246189.1524007177000.44597.1560363120401%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1385) Update device integration tests

2019-06-12 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1385  
 
 
  Update device integration tests   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/06/12 11:43 AM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Alex Dreyer  
 

  
 
 
 
 

 
 Once puppet 6.5.0 is released with a fixed version of the resource_api we should update the device integration tests to: 1. Not update the rsapi gem that is installed on the puppet_6 agent target 2. Use the latest release of resource_api gem release in bolts gemfile 3. Run the device integration tests agasint the default run_on: localhost. Make sure the localhost case is using the latest release of the resource_api from bolt's gemfile.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian J

Jira (BOLT-1385) Update device integration tests

2019-06-12 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer commented on  BOLT-1385  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Update device integration tests   
 

  
 
 
 
 

 
 David Schmitt This is the bolt side ticket if you want to link it to the resource_api testing ticket.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312249.156036499.44721.1560365100394%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8215) Tag filtering for skip_tag incorrectly expanded

2019-06-12 Thread Heston Hoffman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Heston Hoffman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8215  
 
 
  Tag filtering for skip_tag incorrectly expanded   
 

  
 
 
 
 

 
Change By: 
 Heston Hoffman  
 
 
Labels: 
 resolved-issue-added  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.224644.1511979864000.44729.1560365220563%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1303) Provide a Bolt Docker Image

2019-06-12 Thread Cas Donoghue (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cas Donoghue updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1303  
 
 
  Provide a Bolt Docker Image   
 

  
 
 
 
 

 
Change By: 
 Cas Donoghue  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308633.1557866171000.44750.1560366000374%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-4400) Consider upgrading clj-parent across active branches

2019-06-12 Thread Rob Browning (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4400  
 
 
  Consider upgrading clj-parent across active branches   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/06/12 12:00 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Rob Browning  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at h

Jira (PDB-4400) Consider upgrading clj-parent across active branches (2019-6)

2019-06-12 Thread Rob Browning (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rob Browning updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4400  
 
 
  Consider upgrading clj-parent across active branches (2019-6)   
 

  
 
 
 
 

 
Change By: 
 Rob Browning  
 
 
Summary: 
 Consider upgrading clj-parent across active branches  (2019-6)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312255.1560366028000.44757.1560366120343%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9750) optionally add pe_version to server_facts

2019-06-12 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9750  
 
 
  optionally add pe_version to server_facts   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/06/12 12:17 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Thomas Kishel  
 

  
 
 
 
 

 
 Members of the Puppet Community have requested a standardized best practice to determine if a Puppet Agent is a PE or FOSS Puppet Agent. Since Puppet 4.x, there is no concept of a PE or FOSS Puppet Agent, but a Puppet Agent can be served a catalog by a PE or FOSS Puppet Server. A non-empty pe_version fact would both differentiate between PE or FOSS, but would allow for conditional code depending upon the specific version of PE. The pe_version fact is available in Puppet / PE 3.x. The pe_compiling_server_version function (which calls pe_server_version) is available on a PE Puppet Server after PE 3.x, but is not available on a FOSS Puppet Server, requiring the use of the is_function_available} function to avoid generating an error when calling {{pe_compiling_server_version function on a FOSS Puppet Server. The is_function_available function is itself now deprecated.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
  

Jira (PUP-9750) optionally add pe_version to server_facts

2019-06-12 Thread Thomas Kishel (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kishel commented on  PUP-9750  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: optionally add pe_version to server_facts   
 

  
 
 
 
 

 
 If this PR is approved (and added to Puppet 7) then we could add this function to puppetlabs-stdlib ...  
 
 
 
 
 # This needs to be a function rather than updating the 3.x `pe_version` fact.  
 
 
 #  
 
 
 # In Puppet 3.x, PE is a property of the agent.  
 
 
 # In Puppet 4.x and newer, PE is a property of the compiling master.  
 
 
 # In Puppet 4.x to 6.x, inspect the `pe_version` file on the compiling master.  
 
 
 # In Puppet 7.x and newer, inspect server_facts['pe_version'].  
 
 
    
 
 
 Puppet::Functions.create_function(:get_pe_version) do  
 
 
   def get_pe_version  
 
 
 scope = closure_scope  
 
 
 facts = scope['facts']  
 
 
    
 
 
 if Puppet::Util::Package.versioncmp(facts['puppetversion'], '3.9.9') < 0  
   

Jira (PUP-6488) Gem provider should allow alternative gem command; should not rely on $PATH

2019-06-12 Thread Heston Hoffman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Heston Hoffman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-6488  
 
 
  Gem provider should allow alternative gem command; should not rely on $PATH   
 

  
 
 
 
 

 
Change By: 
 Heston Hoffman  
 
 
Labels: 
 gem package  resolved-issue-added  type_and_provider  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.140954.1468271833000.44832.1560369060456%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9644) Improve documentation around sensitive data in puppet

2019-06-12 Thread Jorie Tappa (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jorie Tappa updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9644  
 
 
  Improve documentation around sensitive data in puppet   
 

  
 
 
 
 

 
Change By: 
 Jorie Tappa  
 

  
 
 
 
 

 
 Currently, the docs don't accurately reflect the behavior of sensitive data in puppet catalogs. We should update the docs to reduce customer surprise. Not every provider is supported, so we should be clear which those are and under which circumstances data can be leaked.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.304741.1555347266000.44855.1560370560296%40Atlassian.JIRA.
For more options, visit 

Jira (PUP-8969) Sensitive parameters are not redacted from reports / agent output when used in templates

2019-06-12 Thread Jorie Tappa (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jorie Tappa updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8969  
 
 
  Sensitive parameters are not redacted from reports / agent output when used in templates   
 

  
 
 
 
 

 
Change By: 
 Jorie Tappa  
 
 
Fix Version/s: 
 PUP 7.0.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.262922.1530114614000.44880.1560370920966%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9751) Sensitive processing is fundamentally surprising to customers, so we need some fundamental rework

2019-06-12 Thread Kris Bosland (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kris Bosland created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9751  
 
 
  Sensitive processing is fundamentally surprising to customers, so we need some fundamental rework   
 

  
 
 
 
 

 
Issue Type: 
  Epic  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/06/12 1:22 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Kris Bosland  
 

  
 
 
 
 

 
 Sensitive processing is fundamentally surprising to customers, so we need some fundamental rework.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   

Jira (PUP-9751) Sensitive Fundamental Rework

2019-06-12 Thread Kris Bosland (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kris Bosland updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9751  
 
 
  Sensitive Fundamental Rework   
 

  
 
 
 
 

 
Change By: 
 Kris Bosland  
 
 
Summary: 
 Sensitive  processing is fundamentally surprising to customers, so we need some fundamental rework  Fundamental Rework  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312262.156037095.44894.1560371040089%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-4930) Provide helpful error message when provider does not have instances defined

2019-06-12 Thread Heston Hoffman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Heston Hoffman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-4930  
 
 
  Provide helpful error message when provider does not have instances defined   
 

  
 
 
 
 

 
Change By: 
 Heston Hoffman  
 
 
Labels: 
 resolved-issue-added  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.90662.1438016947000.44902.1560371161107%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9751) Sensitive Fundamental Rework

2019-06-12 Thread Kris Bosland (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Kris Bosland updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9751  
 
 
  Sensitive Fundamental Rework   
 

  
 
 
 
 

 
Change By: 
 Kris Bosland  
 
 
Team/s: 
 Coremunity  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.312262.156037095.44907.1560371280329%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9295) Notify resource exposes Sensitive data when message is a Sensitive data

2019-06-12 Thread Jorie Tappa (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jorie Tappa updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9295  
 
 
  Notify resource exposes Sensitive data when message is a Sensitive data   
 

  
 
 
 
 

 
Change By: 
 Jorie Tappa  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.283215.1540998541000.44915.1560371340806%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9295) Notify resource exposes Sensitive data when message is a Sensitive data

2019-06-12 Thread Jorie Tappa (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jorie Tappa commented on  PUP-9295  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Notify resource exposes Sensitive data when message is a Sensitive data   
 

  
 
 
 
 

 
 If it's an intended behavior, we should be explicit about it in the docs. If it's not, we can prioritize this for future Sensitive improvements. If it's an intended behavior that we now want to change, we need approval/priority from Products or a PM.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.283215.1540998541000.44927.1560371400976%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8399) Exec onlyif and unless should support sensitive data

2019-06-12 Thread Jorie Tappa (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jorie Tappa updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8399  
 
 
  Exec onlyif and unless should support sensitive data   
 

  
 
 
 
 

 
Change By: 
 Jorie Tappa  
 
 
Comment: 
 A comment with security level 'Developers' was removed.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.233091.1516914842000.44974.1560371940519%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9249) Backport sensitive DSL method PUP-8514

2019-06-12 Thread Jorie Tappa (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jorie Tappa updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9249  
 
 
  Backport sensitive DSL method PUP-8514   
 

  
 
 
 
 

 
Change By: 
 Jorie Tappa  
 
 
Acceptance Criteria: 
 Should have the same behavior as the 6.0.0+ versions.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.281329.1539907632000.44978.1560372120233%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9730) Connections with multiple addresses for a host should try ALL addresses for that host

2019-06-12 Thread Jorie Tappa (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jorie Tappa updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9730  
 
 
  Connections with multiple addresses for a host should try ALL addresses for that host   
 

  
 
 
 
 

 
Change By: 
 Jorie Tappa  
 

  
 
 
 
 

 
 A lot of considerations here Until a successful connection is made ,  and  it should try all addresses in the host list.Current behavior: looks like Puppet already does  this  ticket may spawn more tickets ,  like strategies for attempting connections with multiple addresses at once  but we haven't confirmed IPv6 ,  etc  and we haven't confirmed failover from one to another .See this doc here also: [https://tools.ietf.org/html/rfc6555]  
 

  
 
 
 
 

 
 
 

 
 
 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.googl

Jira (PUP-9730) Connections with multiple addresses for a host should try ALL addresses for that host

2019-06-12 Thread Jorie Tappa (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jorie Tappa updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9730  
 
 
  Connections with multiple addresses for a host should try ALL addresses for that host   
 

  
 
 
 
 

 
Change By: 
 Jorie Tappa  
 
 
Acceptance Criteria: 
 Until a successful connection is made, it should try all addresses that a dns entry resolves to, regardless of IPv4 or IPv6.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311671.1559920061000.45009.1560372600220%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9731) Prefer IPv6 addresses over IPv4 in dual-stack

2019-06-12 Thread Jorie Tappa (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jorie Tappa updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9731  
 
 
  Prefer IPv6 addresses over IPv4 in dual-stack   
 

  
 
 
 
 

 
Change By: 
 Jorie Tappa  
 

  
 
 
 
 

 
 Based on this standards doc:[https://tools.ietf.org/html/rfc6555]We should prefer IPv6 addresses over IPv4, however we should be mindful of PUP-9730, and come up with a strategy to prefer IPv6 addresses while still ensuring we try to connect with all addresses available regardless of their IP family. This _should_ be how the OS already behaves, but we should confirm that's the case.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/

Jira (PUP-9731) Prefer IPv6 addresses over IPv4 in dual-stack

2019-06-12 Thread Jorie Tappa (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jorie Tappa updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9731  
 
 
  Prefer IPv6 addresses over IPv4 in dual-stack   
 

  
 
 
 
 

 
Change By: 
 Jorie Tappa  
 
 
Acceptance Criteria: 
 Confirm behavior, if not confirmed, there's not much we can do about it, so it should be made known in the documentation.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311675.1559920431000.45016.1560372780102%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-2958) Rapid-fire puppet runs cause race condition with SSL data

2019-06-12 Thread Heston Hoffman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Heston Hoffman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-2958  
 
 
  Rapid-fire puppet runs cause race condition with SSL data   
 

  
 
 
 
 

 
Change By: 
 Heston Hoffman  
 
 
Labels: 
 customer  resolved-issue-added  support  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.42950.1405977404000.45019.1560372841719%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9732) Client should cache successful host address for at least the length of a Puppet run

2019-06-12 Thread Jorie Tappa (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jorie Tappa updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9732  
 
 
  Client should cache successful host address for at least the length of a Puppet run   
 

  
 
 
 
 

 
Change By: 
 Jorie Tappa  
 

  
 
 
 
 

 
 Instead of trying all addresses of a host every single time, we should cache the successful address from our initial connection for reuse for at least the length of a single puppet run. What can be done besides monkey patching ruby or submitting a patch to ruby? Net::Http in ruby controls this so we're unsure if there's anything on our side that can be done to resolve 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.
To view this discussion on the web visit

Jira (PUP-9732) Client should cache successful host address for at least the length of a Puppet run

2019-06-12 Thread Jorie Tappa (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jorie Tappa updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9732  
 
 
  Client should cache successful host address for at least the length of a Puppet run   
 

  
 
 
 
 

 
Change By: 
 Jorie Tappa  
 

  
 
 
 
 

 
 Instead of trying all addresses of a host every single time, we should cache the successful address from our initial connection for reuse for at least the length of a single puppet run.What can be done besides monkey patching ruby or submitting a patch to ruby? Net::Http in ruby controls this so we're unsure if there's anything on our side that can be done to resolve this. An alternative if we can't come up with a solution is to tune timeouts to minimize impact.  
 

  
 
 
 
 

 
 
 

 
 
 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 grou

Jira (PUP-5109) Puppet::Resource::Catalog::Compiler#set_server_facts always produces a warning on ipv6 only systems

2019-06-12 Thread Jorie Tappa (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jorie Tappa updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-5109  
 
 
  Puppet::Resource::Catalog::Compiler#set_server_facts always produces a warning on ipv6 only systems   
 

  
 
 
 
 

 
Change By: 
 Jorie Tappa  
 
 
Acceptance Criteria: 
 Should not throw warning on IPv6/behavior should be identical to IPv4.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.95553.144084808.45097.1560373321109%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-2606) Support ECC keys

2019-06-12 Thread Heston Hoffman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Heston Hoffman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-2606  
 
 
  Support ECC keys   
 

  
 
 
 
 

 
Change By: 
 Heston Hoffman  
 
 
Labels: 
 redmine  resolved-issue-added  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.35927.1400268884000.45108.1560373501099%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-3237) waitforcert should have timeout setting

2019-06-12 Thread Heston Hoffman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Heston Hoffman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-3237  
 
 
  waitforcert should have timeout setting   
 

  
 
 
 
 

 
Change By: 
 Heston Hoffman  
 
 
Labels: 
 Customer Support  resolved-issue-added  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.51001.1410479779000.45125.1560373560762%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9480) puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts

2019-06-12 Thread Jorie Tappa (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jorie Tappa updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9480  
 
 
  puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts   
 

  
 
 
 
 

 
Change By: 
 Jorie Tappa  
 
 
Acceptance Criteria: 
 Because this type was part of the T&P extraction in Puppet 6, it needs to both be updated in the code in 5.5.x, as well as the extracted module.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.295251.154953565.45134.1560373680476%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1339) Build pe-bolt-server for redhatfips-7-x86_64

2019-06-12 Thread Sara Meisburger (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sara Meisburger commented on  BOLT-1339  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Build pe-bolt-server for redhatfips-7-x86_64   
 

  
 
 
 
 

 
 Cas Donoghue assigning to you but feel free to delegate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309966.155865044.45140.1560373860363%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1339) Build pe-bolt-server for redhatfips-7-x86_64

2019-06-12 Thread Sara Meisburger (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sara Meisburger assigned an issue to Cas Donoghue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1339  
 
 
  Build pe-bolt-server for redhatfips-7-x86_64   
 

  
 
 
 
 

 
Change By: 
 Sara Meisburger  
 
 
Assignee: 
 Cas Donoghue  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309966.155865044.45142.1560373920433%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-2310) Puppet client does not update and does consult the crl during authentication

2019-06-12 Thread Heston Hoffman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Heston Hoffman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-2310  
 
 
  Puppet client does not update and does consult the crl during authentication   
 

  
 
 
 
 

 
Change By: 
 Heston Hoffman  
 
 
Labels: 
 redmine  resolved-issue-added  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.32446.1398099201000.45215.1560375301118%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-57) Download a file

2019-06-12 Thread Joshua Partlow (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Joshua Partlow commented on  BOLT-57  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Download a file   
 

  
 
 
 
 

 
 Ran into this ticket as well; need to synchronizing /etc/puppetlabs/enterprise between infrastructure nodes in a bolt plan run from a separate controller node.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.208527.1504138043000.45302.1560376801103%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1082) pip provider should handle multiple pips/pythons

2019-06-12 Thread Heston Hoffman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Heston Hoffman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-1082  
 
 
  pip provider should handle multiple pips/pythons   
 

  
 
 
 
 

 
Change By: 
 Heston Hoffman  
 
 
Labels: 
 package pip redmine  resolved-issue-added  type_and_provider  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.21416.1387220789000.45349.1560377282425%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-2310) Puppet client does not update and does consult the crl during authentication

2019-06-12 Thread Heston Hoffman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Heston Hoffman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-2310  
 
 
  Puppet client does not update and does consult the crl during authentication   
 

  
 
 
 
 

 
Change By: 
 Heston Hoffman  
 
 
Labels: 
 redmine resolved-issue-added  resolved_issue_added  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.32446.1398099201000.45372.1560377283398%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8984) Add JSON output option to `puppet parser validate`

2019-06-12 Thread Jesse Scott (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Scott updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-8984  
 
 
  Add JSON output option to `puppet parser validate`   
 

  
 
 
 
 

 
Change By: 
 Jesse Scott  
 
 
Release Notes Summary: 
 The `puppet parser validate` subcommand now supports a `--render-as=json` option to output validate errors in a machine readable JSON format.Additionally, when passed multiple target files, `puppet parser validate` will now continue validating additional files after a parse error instead of halting immediately on the first error encountered. (Note: It will still only return a maximum of one parse error per file.)  
 
 
Release Notes: 
 Enhancement  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To 

Jira (PUP-9706) Removing user on Solaris 11 with altered managehome

2019-06-12 Thread Heston Hoffman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Heston Hoffman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9706  
 
 
  Removing user on Solaris 11 with altered managehome   
 

  
 
 
 
 

 
Change By: 
 Heston Hoffman  
 
 
Labels: 
 resolved-issue-added  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.308724.155793208.45408.1560378360355%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (BOLT-1118) Add a command that lists available modules and their versions

2019-06-12 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1118  
 
 
  Add a command that lists available modules and their versions   
 

  
 
 
 
 

 
Change By: 
 Alex Dreyer  
 

  
 
 
 
 

 
 As a bolt user, I need the ability to call up a list of the modules available in my  workspace  project . This will allow me to determine the names and versions of available modules along with their order of precedence.h2. Desired OutcomeA command similar to {{puppet module list}} that displays each module available in the Bolt environment.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-b

Jira (BOLT-1386) I need a workspace for files during the duration of a plan

2019-06-12 Thread Alex Dreyer (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Dreyer created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet Task Runner /  BOLT-1386  
 
 
  I need a workspace for files during the duration of a plan   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Created: 
 2019/06/12 3:31 PM  
 
 
Priority: 
  Normal  
 
 
Reporter: 
 Alex Dreyer  
 

  
 
 
 
 

 
 Some plans build and distribute artifacts. These plans are hard to write because bolt does not have a `file_download` function or any natural space to store such artifacts. The project dir should provide a workspace that allows plans a central location to write and read data from. questions: 1. Should this workspace persist between plans run in the same project? 2. How can we ensure that files in the workspace are addressable in a way that doesn't conflict with modules.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 

Jira (PUP-9693) Hiera Lookup Fails when convert_to is used

2019-06-12 Thread Heston Hoffman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Heston Hoffman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9693  
 
 
  Hiera Lookup Fails when convert_to is used   
 

  
 
 
 
 

 
Change By: 
 Heston Hoffman  
 
 
Labels: 
 resolved-issue-added  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307503.1557191729000.45451.1560379020244%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9689) String to integer conversion fails

2019-06-12 Thread Heston Hoffman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Heston Hoffman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9689  
 
 
  String to integer conversion fails   
 

  
 
 
 
 

 
Change By: 
 Heston Hoffman  
 
 
Labels: 
 resolved-issue-added  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.306573.1556527664000.45534.1560380760742%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9642) puppet device permissions preventing reading dirs

2019-06-12 Thread Heston Hoffman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Heston Hoffman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9642  
 
 
  puppet device permissions preventing reading dirs   
 

  
 
 
 
 

 
Change By: 
 Heston Hoffman  
 
 
Labels: 
 dtt  resolved-issue-added  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.262030.152958581.45574.1560381600459%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-4390) Don't produce duplicate certname entries for certnames with special characters

2019-06-12 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4390  
 
 
  Don't produce duplicate certname entries for certnames with special characters   
 

  
 
 
 
 

 
Change By: 
 Austin Blatt  
 
 
Fix Version/s: 
 PDB 6.3.3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311094.1559593774000.45593.1560381721408%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-8984) Add JSON output option to `puppet parser validate`

2019-06-12 Thread Jesse Scott (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Scott commented on  PUP-8984  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add JSON output option to `puppet parser validate`   
 

  
 
 
 
 

 
 Josh Cooper I added release notes this afternoon so this is ready to resolve as far as I know.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.189813.149427962.45610.1560381781978%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-4362) Fix upgrade_oldest

2019-06-12 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4362  
 
 
  Fix upgrade_oldest   
 

  
 
 
 
 

 
Change By: 
 Austin Blatt  
 
 
Fix Version/s: 
 PDB 6.3.3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.306703.1556573725000.45621.1560381960988%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-4308) Check whether pdb is unkillable when db is unavailable at startup

2019-06-12 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4308  
 
 
  Check whether pdb is unkillable when db is unavailable at startup   
 

  
 
 
 
 

 
Change By: 
 Austin Blatt  
 
 
Fix Version/s: 
 PDB 6.3.2  
 
 
Fix Version/s: 
 PDB 6.3.3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.300218.1552580118000.45615.1560381960702%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-3592) HA - Failure syncing to replica - file not found - after promotion

2019-06-12 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-3592  
 
 
  HA - Failure syncing to replica - file not found - after promotion   
 

  
 
 
 
 

 
Change By: 
 Austin Blatt  
 
 
Fix Version/s: 
 PDB 6.3.2  
 
 
Fix Version/s: 
 PDB 6.3.3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.197433.1498155934000.45635.1560382141869%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-4364) Fix databind CVE-2018-5968 CVE-2018-19360 CVE-2018-19361 CVE-2018-19362 in 5.1

2019-06-12 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4364  
 
 
  Fix databind CVE-2018-5968 CVE-2018-19360 CVE-2018-19361 CVE-2018-19362 in 5.1   
 

  
 
 
 
 

 
Change By: 
 Austin Blatt  
 
 
Fix Version/s: 
 PDB n/a  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307473.155716600.45640.1560382260611%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-4346) Update sync deduplication to account for configure-expiration commands

2019-06-12 Thread Austin Blatt (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Austin Blatt updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4346  
 
 
  Update sync deduplication to account for configure-expiration commands   
 

  
 
 
 
 

 
Change By: 
 Austin Blatt  
 
 
Fix Version/s: 
 PDB 6.3.3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305159.117556000.45642.1560382260705%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-9639) Windows package resource does not remove trailing whitespace

2019-06-12 Thread Heston Hoffman (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Heston Hoffman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Puppet /  PUP-9639  
 
 
  Windows package resource does not remove trailing whitespace   
 

  
 
 
 
 

 
Change By: 
 Heston Hoffman  
 
 
Labels: 
 cstop10 jira_escalated maintenance  resolved-issue-added  triage  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.304376.1554933412000.45650.1560382320621%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-4346) Update sync deduplication to account for configure-expiration commands

2019-06-12 Thread Zachary Kent (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zachary Kent updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4346  
 
 
  Update sync deduplication to account for configure-expiration commands   
 

  
 
 
 
 

 
Change By: 
 Zachary Kent  
 
 
Release Notes: 
 Not Needed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.305159.117556000.45662.1560382500488%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-4374) Remove testing workaround for PDB-4373

2019-06-12 Thread Zachary Kent (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zachary Kent commented on  PDB-4374  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Remove testing workaround for PDB-4373   
 

  
 
 
 
 

 
 Austin Blatt I reopened this ticket even though we've already merged a commit with the ticket number. I want to make sure I don't forget to remove this workaround once the other issue mentioned in PDB-4373 is resolved.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309645.1558477521000.45720.1560383340164%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-4393) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.3)

2019-06-12 Thread Zachary Kent (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zachary Kent assigned an issue to Austin Blatt  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4393  
 
 
  Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.3)   
 

  
 
 
 
 

 
Change By: 
 Zachary Kent  
 
 
Assignee: 
 Zachary Kent Austin Blatt  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311754.1559946766000.45731.1560383400811%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


Jira (PDB-4392) Merge-up, branch, and create pipelines (PuppetDB 6.3.3)

2019-06-12 Thread Zachary Kent (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Zachary Kent assigned an issue to Austin Blatt  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 PuppetDB /  PDB-4392  
 
 
  Merge-up, branch, and create pipelines (PuppetDB 6.3.3)   
 

  
 
 
 
 

 
Change By: 
 Zachary Kent  
 
 
Assignee: 
 Zachary Kent Austin Blatt  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311753.155994676.45724.1560383400478%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


  1   2   >