date:20160628

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6361 
 
 
 
  Validate and error if a class or define is given a name starting with ::  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Acceptance Criteria:
 
 That {code}class ::foo { }define ::foo { }function ::foo() { }type ::Foo = Integerapplication ::foo { }  # requires  opt in  --app_management {code}All lead to an error being raised. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6361) Validate and error if a class or define is given a name starting with ::

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6361 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Validate and error if a class or define is given a name starting with ::  
 
 
 
 
 
 
 
 
 
 
Maintenance PR merged f04567e 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6361) Validate and error if a class or define is given a name starting with ::

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6361 
 
 
 
  Validate and error if a class or define is given a name starting with ::  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Acceptance Criteria:
 
 That {code}class ::foo { }define ::foo { }function ::foo() { }type ::Foo = Integer application ::foo {  }  # requires opt in{ code}All lead to an error being raised. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6361) Validate and error if a class or define is given a name starting with ::

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6361 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Validate and error if a class or define is given a name starting with ::  
 
 
 
 
 
 
 
 
 
 
Thomas, I think the example you showed is wrong - it should have been ::foo, not just foo - right? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6378) Add failover information to the report

2016-06-28 Thread Maggie Dreyer (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Maggie Dreyer commented on  PUP-6378 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add failover information to the report  
 
 
 
 
 
 
 
 
 
 
Do we know what we want the format of this to be? What are the fields that should be created, and what type of data would we like to see in them? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6361) Validate and error if a class or define is given a name starting with ::

2016-06-28 Thread Thomas Hallgren (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-6361 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Validate and error if a class or define is given a name starting with ::  
 
 
 
 
 
 
 
 
 
 
Here's a (maint) PR that fixes the error message: PR-5071. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDOC-71) Stack Level Too Deep Exception and Spurious Errors

2016-06-28 Thread Hailee Kenney (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney commented on  PDOC-71 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Stack Level Too Deep Exception and Spurious Errors  
 
 
 
 
 
 
 
 
 
 
Noting for myself and others: to reproduce this bug using the steps described in the ticket on a CentOS 7 virtual machine, makes sure you install rpm-build and rpm-devel. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6361) Validate and error if a class or define is given a name starting with ::

2016-06-28 Thread Thomas Hallgren (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-6361 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Validate and error if a class or define is given a name starting with ::  
 
 
 
 
 
 
 
 
 
 
The following command will yield an error when this fix is applied: 
 
 
 
 
 
 
puppet apply --app_management -e "application foo {}"
 
 
 
 
 
 
 
but the error message could be clearer. It presently says: "Unacceptable name. The name '::foo' is unacceptable as the name of an Object" 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2845) allow disablement of returned rows with insert-records*

2016-06-28 Thread Wyatt Alt (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2845 
 
 
 
  allow disablement of returned rows with insert-records*  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/06/28 2:04 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
Our storage function insert-records*, as well as the underlying clojure jdbc function insert!, will always return the rows inserted. Often we just drop these on the floor, but the results are still transferred over the wire and read. We should be able to get some performance gains by modifying our function to allow the returned keys to be disabled. As best as I can tell this can't be done within clojure jdbc, but should be possible with jdbc proper. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian

Jira (FACT-1422) Facter should detect PhotonOS

2016-06-28 Thread William Hopper (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1422 
 
 
 
  Facter should detect PhotonOS  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Release Notes Summary:
 
 This commit adds PhotonOS detection to the Facter {{os}} structured facts and related legacy flat facts. The OS name is "PhotonOS", and its family is "RedHat". 
 
 
 

Release Notes:
 
 New Feature 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (FACT-1422) Facter should detect PhotonOS

2016-06-28 Thread William Hopper (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 William Hopper updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1422 
 
 
 
  Facter should detect PhotonOS  
 
 
 
 
 
 
 
 
 

Change By:
 
 William Hopper 
 
 
 

Fix Version/s:
 
 FACT 3.3.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6450) Group resource members order can break idempotence in Windows

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6450 
 
 
 
  Group resource members order can break idempotence in Windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Glenn Sarti 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 Glenn Sarti qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6450) Group resource members order can break idempotence in Windows

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti assigned an issue to Erick Banks 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6450 
 
 
 
  Group resource members order can break idempotence in Windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Glenn Sarti 
 
 
 

Assignee:
 
 qa Erick Banks 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6450) Group resource members order can break idempotence in Windows

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6450 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Group resource members order can break idempotence in Windows  
 
 
 
 
 
 
 
 
 
 
CI Completed with success https://jenkins.puppetlabs.com/view/puppet-agent/view/stable/view/puppet/job/platform_puppet_pkg-van-promote_stable/145/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6361) Validate and error if a class or define is given a name starting with ::

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6361 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Validate and error if a class or define is given a name starting with ::  
 
 
 
 
 
 
 
 
 
 
The implementation validates all NamedDefinitions including applications. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6452) Allow defaultfor to accept regex

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Souter updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6452 
 
 
 
  Allow defaultfor to accept regex  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Souter 
 
 
 

Labels:
 
 puppethack 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6452) Allow defaultfor to accept regex

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Souter updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6452 
 
 
 
  Allow defaultfor to accept regex  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Souter 
 
 
 

Summary:
 
 Allow defaultfor to accept  operators  regex 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6452) Allow defaultfor to accept regex

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Souter commented on  PUP-6452 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow defaultfor to accept regex  
 
 
 
 
 
 
 
 
 
 
Regex makes a lot more sense, will give that a go for Puppethack  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5900) Global noop true should override resource noop=>false

2016-06-28 Thread Jenny Mahmoudi (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jenny Mahmoudi updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5900 
 
 
 
  Global noop true should override resource noop=>false  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jenny Mahmoudi 
 
 
 

CS Priority:
 
 Needs Priority 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6450) Group resource members order can break idempotence in Windows

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6450 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Group resource members order can break idempotence in Windows  
 
 
 
 
 
 
 
 
 
 
CI Started https://jenkins.puppetlabs.com/view/puppet-agent/view/stable/view/puppet/job/platform_puppet_init-van-component_stable/198/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5604) Add journalctl command when service fails for systemd

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Souter assigned an issue to Peter Souter 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5604 
 
 
 
  Add journalctl command when service fails for systemd  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Souter 
 
 
 

Assignee:
 
 Peter Souter 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2826) Smoke test packages (PDB 1.0.1)

2016-06-28 Thread Andrew Roetker (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andrew Roetker commented on  PDB-2826 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Smoke test packages (PDB 1.0.1)  
 
 
 
 
 
 
 
 
 
 
Smoke tested on el7 with vagrant and everything looks good! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (FACT-1422) Facter should detect PhotonOS

2016-06-28 Thread Sean Griffin (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin commented on  FACT-1422 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter should detect PhotonOS  
 
 
 
 
 
 
 
 
 
 
With values for Fixed-In and Docs (release note, maybe "not needed"), this can be moved to done. 
Assigning to Whopper for review. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (FACT-1422) Facter should detect PhotonOS

2016-06-28 Thread Sean Griffin (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin assigned an issue to William Hopper 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1422 
 
 
 
  Facter should detect PhotonOS  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

Assignee:
 
 William Hopper 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (FACT-1422) Facter should detect PhotonOS

2016-06-28 Thread Sean Griffin (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1422 
 
 
 
  Facter should detect PhotonOS  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6445) Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6445 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor  
 
 
 
 
 
 
 
 
 
 
CI passed https://jenkins.puppetlabs.com/view/puppet-agent/view/stable/view/puppet/job/platform_puppet_pkg-van-promote_stable/143/ 
FR is probably not required on this ticket 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6445) Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6445 
 
 
 
  Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor  
 
 
 
 
 
 
 
 
 

Change By:
 
 Glenn Sarti 
 
 
 

Status:
 
 Resolved Ready for Test 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Assignee:
 
 Ethan Brown qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6445) Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti assigned an issue to Erick Banks 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6445 
 
 
 
  Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor  
 
 
 
 
 
 
 
 
 

Change By:
 
 Glenn Sarti 
 
 
 

Assignee:
 
 qa Erick Banks 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6445) Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti assigned an issue to Ethan Brown 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6445 
 
 
 
  Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor  
 
 
 
 
 
 
 
 
 

Change By:
 
 Glenn Sarti 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Assignee:
 
 qa Ethan Brown 
 
 
 

Status:
 
 Ready for Test Resolved 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6445) Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6445 
 
 
 
  Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor  
 
 
 
 
 
 
 
 
 

Change By:
 
 Glenn Sarti 
 
 
 

Status:
 
 Ready for  CI  Test 
 
 
 

Assignee:
 
 Ethan Brown qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-1498) scheduled_task won't update command

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-1498 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: scheduled_task won't update command  
 
 
 
 
 
 
 
 
 
 
Last stable CI was green https://jenkins.puppetlabs.com/view/puppet-agent/view/stable/view/puppet/job/platform_puppet_pkg-van-promote_stable/143/ 
Which was for commit d4d6734e5f858b4e3f4db24c356ea7cb9db2d991, but also included our commit (https://github.com/puppetlabs/puppet/commit/257d5b2d6ed94def50e8d6e040302d1c87135947) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6450) Group resource members order can break idempotence in Windows

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6450 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Group resource members order can break idempotence in Windows  
 
 
 
 
 
 
 
 
 
 
Merged into stable at; https://github.com/puppetlabs/puppet/commit/c56f5a9a30fb4acad635b4ae7ebc42c115a44755 
Merged up to master at; https://github.com/puppetlabs/puppet/commit/6c4a799330a68c23acfc2b6a332c2add3726b756 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (FACT-1448) facter json output converts all booleans to true

2016-06-28 Thread Allister Banks (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Allister Banks commented on  FACT-1448 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: facter json output converts all booleans to true  
 
 
 
 
 
 
 
 
 
 
Can reproduce (on 10.11.5, facter 3.2.0) in my environment 
 
 
 
 
 
 
# facter -p jsontest --custom-dir=/tmp 
 
 
 
 
{ 
 
 
 
 
  true => true, 
 
 
 
 
  false => false 
 
 
 
 
} 
 
 
 
 
bash-3.2# facter -p jsontest --custom-dir=/tmp --json 
 
 
 
 
{ 
 
 
 
 
  "jsontest": { 
 
 
 
 
"true": true, 
 
 
 
 
"false": true 
 
 
 
 
  }

Jira (PUP-6445) Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6445 
 
 
 
  Win32-Service Windows Gem 0.8.9 causing CI PR failures in AppVeyor  
 
 
 
 
 
 
 
 
 

Change By:
 
 Glenn Sarti 
 
 
 

Scope Change Category:
 
 Found 
 
 
 

Scope Change Reason:
 
 Unexpected update of 3rd party gem broke CI 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6437) directoryservice user provider crashes if no ShadowHashData is found

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6437 
 
 
 
  directoryservice user provider crashes if no ShadowHashData is found  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Sprint:
 
 Client 2016-06-29 (failover) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6437) directoryservice user provider crashes if no ShadowHashData is found

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6437 
 
 
 
  directoryservice user provider crashes if no ShadowHashData is found  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Story Points:
 
 0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6450) Group resource members order can break idempotence in Windows

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6450 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Group resource members order can break idempotence in Windows  
 
 
 
 
 
 
 
 
 
 
The redordering issue is only present for the `inclusive` group membership on users 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6244) Acceptance: fix module upgrade tests

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6244 
 
 
 
  Acceptance: fix module upgrade tests  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Assignee:
 
 John Duarte 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6094) {{puppet -h|--help}} should be equivalent to {{puppet help}}

2016-06-28 Thread Michael Smith (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6094 
 
 
 
  {{puppet -h|--help}} should be equivalent to {{puppet help}}  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Fix Version/s:
 
 PUP 4.y 
 
 
 

Fix Version/s:
 
 PUP 4.6.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6409) "integer too big to convert to `int' at" with lookupvar

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Price commented on  PUP-6409 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "integer  too big to convert to `int' at" with lookupvar  
 
 
 
 
 
 
 
 
 
 
Matthew Nicholson great, thanks for confirming. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6450) Group resource members order can break idempotence in Windows

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6450 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Group resource members order can break idempotence in Windows  
 
 
 
 
 
 
 
 
 
 
PR Review 
Test Setup; Create a bunch of groups using the following puppet manifest 
 
 
 
 
 
 
group { 'group1': 
 
 
 
 
  ensure => present, 
 
 
 
 
} 
 
 
 
 
  
 
 
 
 
group { 'group2': 
 
 
 
 
  ensure => present, 
 
 
 
 
} 
 
 
 
 
  
 
 
 
 
group { 'group3': 
 
 
 
 
  ensure => present, 
 
 
 
 
}

Jira (PUP-6094) {{puppet -h|--help}} should be equivalent to {{puppet help}}

2016-06-28 Thread Lori Landesman (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lori Landesman commented on  PUP-6094 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: {{puppet -h|--help}} should be equivalent to {{puppet help}}  
 
 
 
 
 
 
 
 
 
 
Michael Smith I definitely would have both commands do the same thing so that we support users who are used to the current way and accommodate newer ones who would benefit from the consistency across tools. I agree with you that it's too complex to have different kinds of help and force users to try to remember which help does what. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6415) static_compiler: symlinks in recursed directories don't work

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6415 
 
 
 
  static_compiler: symlinks in recursed directories don't work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Sprint:
 
 Client 2016-06-29 (failover) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6415) static_compiler: symlinks in recursed directories don't work

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6415 
 
 
 
  static_compiler: symlinks in recursed directories don't work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Scrum Team:
 
 Client Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6415) static_compiler: symlinks in recursed directories don't work

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6415 
 
 
 
  static_compiler: symlinks in recursed directories don't work  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Story Points:
 
 0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5604) Add journalctl command when service fails for systemd

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5604 
 
 
 
  Add journalctl command when service fails for systemd  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Sprint:
 
 Client 2016-06-29 (failover) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5604) Add journalctl command when service fails for systemd

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5604 
 
 
 
  Add journalctl command when service fails for systemd  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Story Points:
 
 0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-5604) Add journalctl command when service fails for systemd

2016-06-28 Thread Michael Smith (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5604 
 
 
 
  Add journalctl command when service fails for systemd  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Fix Version/s:
 
 PUP 4.6.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6450) Group resource members order can break idempotence in Windows

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6450 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Group resource members order can break idempotence in Windows  
 
 
 
 
 
 
 
 
 
 
Spec Unit tests - OK Integration tests - OK 
Note that the reordering seemed to only affect authoritative membership 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6450) Group resource members order can break idempotence in Windows

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6450 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Group resource members order can break idempotence in Windows  
 
 
 
 
 
 
 
 
 
 
PR Review 
Test Setup; Create a bunch of users using the following puppet manifest 
 
 
 
 
 
 
user { 'user1': 
 
 
 
 
  ensure => present, 
 
 
 
 
} 
 
 
 
 
  
 
 
 
 
user { 'user2': 
 
 
 
 
  ensure => present, 
 
 
 
 
} 
 
 
 
 
  
 
 
 
 
user { 'user3': 
 
 
 
 
  ensure => present, 
 
 
 
 
}

Jira (PUP-6409) "integer too big to convert to `int' at" with lookupvar

2016-06-28 Thread Matthew Nicholson (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew Nicholson commented on  PUP-6409 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "integer  too big to convert to `int' at" with lookupvar  
 
 
 
 
 
 
 
 
 
 
I actually do, yes.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6452) Allow defaultfor to accept operators

2016-06-28 Thread Michael Smith (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  PUP-6452 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow defaultfor to accept operators  
 
 
 
 
 
 
 
 
 
 
Operators would require a block. A regex might fulfill the same need, and be simpler. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6257) Add --allow-authorization-extensions to puppet cert sign

2016-06-28 Thread Nathaniel Smith (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nathaniel Smith assigned an issue to Nathaniel Smith 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6257 
 
 
 
  Add --allow-authorization-extensions to puppet cert sign  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nathaniel Smith 
 
 
 

Assignee:
 
 Nathaniel Smith 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6257) Add --allow-authorization-extensions to puppet cert sign

2016-06-28 Thread Nathaniel Smith (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nathaniel Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6257 
 
 
 
  Add --allow-authorization-extensions to puppet cert sign  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nathaniel Smith 
 
 
 

Sprint:
 
 Server Jade 2016-06-29 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6361) Validate and error if a class or define is given a name starting with ::

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6361 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Validate and error if a class or define is given a name starting with ::  
 
 
 
 
 
 
 
 
 
 
Same thing there actually. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6409) "integer too big to convert to `int' at" with lookupvar

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Price commented on  PUP-6409 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "integer  too big to convert to `int' at" with lookupvar  
 
 
 
 
 
 
 
 
 
 
Matthew Nicholson do you also have hiera lookups in your catalogs, which may be looking up undefined variables? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6409) "integer too big to convert to `int' at" with lookupvar

2016-06-28 Thread Matthew Nicholson (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew Nicholson commented on  PUP-6409 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "integer  too big to convert to `int' at" with lookupvar  
 
 
 
 
 
 
 
 
 
 
So, just for a +1, I see this in my environment as well, every now and then, all 4 of my masters start throwing this on all catalogs(well...maybe not "all" but a very high percentage of them as most of our systems have nearly identical profiles/catalogs) , and a restart fixes it right away. I've seen this 3 times in maybe the last month and a half or so.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6361) Validate and error if a class or define is given a name starting with ::

2016-06-28 Thread Peter Huene (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene commented on  PUP-6361 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Validate and error if a class or define is given a name starting with ::  
 
 
 
 
 
 
 
 
 
 
Sorry late to the party: what about applications? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6450) Group resource members order can break idempotence in Windows

2016-06-28 Thread Ethan Brown (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6450 
 
 
 
  Group resource members order can break idempotence in Windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 

Sprint:
 
 Windows 2016- 07 06 - 13 - Choco Un 29 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6452) Allow defaultfor to accept operators

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6452 
 
 
 
  Allow defaultfor to accept operators  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Scrum Team:
 
 Client Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6452) Allow defaultfor to accept operators

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6452 
 
 
 
  Allow defaultfor to accept operators  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Component/s:
 
 Types and Providers 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6361) Validate and error if a class or define is given a name starting with ::

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6361 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Validate and error if a class or define is given a name starting with ::  
 
 
 
 
 
 
 
 
 
 
Merged to master at: 926b42a 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6361) Validate and error if a class or define is given a name starting with ::

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6361 
 
 
 
  Validate and error if a class or define is given a name starting with ::  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Acceptance Criteria:
 
 That {code}class ::foo { }define ::foo { } function ::foo() {  }type ::Foo = Integer{ code} Both leads All lead  to an error being raised. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (FACT-1448) facter json output converts all booleans to true

2016-06-28 Thread Clay Caviness (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Clay Caviness created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1448 
 
 
 
  facter json output converts all booleans to true  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 FACT 3.1.4 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/06/28 8:47 AM 
 
 
 

Environment:
 
 
macOS 10.11 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Clay Caviness 
 
 
 
 
 
 
 
 
 
 
When json output is requested, any fact value that is a boolean true/false is returned as true. 
This is a pretty huge regression. 
To recreate, add a simple fact like this: 
 
 
 
 
 
 
Facter.add('jsontest') do 
 
 
 
 
  setcode do

Jira (PDB-2825) Tag the release and create packages (PDB 1.0.1)

2016-06-28 Thread Morgan Rhodes (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Morgan Rhodes assigned an issue to Morgan Rhodes 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2825 
 
 
 
  Tag the release and create packages (PDB 1.0.1)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Morgan Rhodes 
 
 
 

Assignee:
 
 Melissa Stone Morgan Rhodes 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (HI-519) Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8

2016-06-28 Thread Kenn Hussey (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kenn Hussey commented on  HI-519 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8  
 
 
 
 
 
 
 
 
 
 
Yeah Ethan Brown, so far we don't have a plan/need to bump Hiera in puppet-agent 1.5.3, so the version would be 3.2.2 unless there is something causing a 'y' version bump in puppet-agent 1.6.0. Steve Barlow or Kylo Ginsberg may have more insight here. /cc David Kramer 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2828) Push tag (PDB 1.0.1)

2016-06-28 Thread Morgan Rhodes (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Morgan Rhodes assigned an issue to Morgan Rhodes 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2828 
 
 
 
  Push tag (PDB 1.0.1)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Morgan Rhodes 
 
 
 

Assignee:
 
 Melissa Stone Morgan Rhodes 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDB-2829) Packages pushed (PDB 1.0.1)

2016-06-28 Thread Morgan Rhodes (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Morgan Rhodes assigned an issue to Morgan Rhodes 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2829 
 
 
 
  Packages pushed (PDB 1.0.1)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Morgan Rhodes 
 
 
 

Assignee:
 
 Melissa Stone Morgan Rhodes 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6409) "integer too big to convert to `int' at" with lookupvar

2016-06-28 Thread Jeremy Barlow (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jeremy Barlow commented on  PUP-6409 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "integer  too big to convert to `int' at" with lookupvar  
 
 
 
 
 
 
 
 
 
 

Jeremy Barlow can you think of any easy way to use jmap or some other tool to watch the instances of org.jruby.runtime.ThreadContext to confirm or refute the theory that the SoftReferences are being GC'd? Or, based on your recent work do you have any suggestions about how to force GC of SoftReferences in a reproducer program?
 
Chris Price For viewing when specific instances of objects are being created/freed across a set of snapshots, I've found taking repeated snapshots and viewing them via the YourKit Generations (https://www.yourkit.com/docs/java/help/generations.jsp) feature to be useful. With that, I can look at two different snapshot generation views and see whether or not specific instances of objects which are present in a generation in one view are still present in a different view at that same generation after a number of additional snapshots have been captured. 
I haven't found any methods, though, for forcing a "harder" GC that will clean up referents of SoftReferences when no other strong references to those referents exist. Supposedly - although it has seemed inconsistent for me - the referents of unused WeakReferences will be slated for clean up on any old GC whereas the references of SoftReferences will only get slated for clean up when there's sufficient memory pressure on the heap. 
Looking at the code snippets you linked, though, I wonder if we can take advantage of fact that the org.jruby.internal.runtime.ThreadService.localContext uses a ThreadLocal to more easily create a reproducer. 
For example, could we instrument Puppet Server such that every time a JRubyPuppet instance is used to send a catalog request that runs the code with the undefined variable, the call is marshaled onto a unique, bare java.lang.Thread instance that we spin up - avoiding any thread pooling that might otherwise have caused Java threads (and, via ThreadLocals, RubyThreads?) to be reused? 
Not sure since I haven't actually seen the reproducer setup but it may be that we haven't been able to locally reproduce the issue thusfar because our reproducer is largely just reusing the same Java thread (or small number of threads) in the Jetty web server's QueuedThreadPool. It could be that RubyThread objects aren't being created frequently enough to trigger the error as a result. In Jürgen Thomann's reproduction environment, though, threads in the QueuedThreadPool may be swapped out more frequently over time if there's more intermittent concurrency among the set of requests. Jetty will dispose/replace Java threads in its pool if they go idle for some period of time, scaling the number of outstanding threads up/down in order to meet demands of the incoming request load. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

Jira (PUP-6323) Support tdnf package provider for VMware PhotonOS

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6323 
 
 
 
  Support tdnf package provider for VMware PhotonOS  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Risk Assessment Reason:
 
 Not yet a supported OS 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6323) Support tdnf package provider for VMware PhotonOS

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6323 
 
 
 
  Support tdnf package provider for VMware PhotonOS  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6323) Support tdnf package provider for VMware PhotonOS

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6323 
 
 
 
  Support tdnf package provider for VMware PhotonOS  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Risk Assessment:
 
 Low 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (HI-341) Hiera should support native HOCON to match Puppet Server

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Price updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-341 
 
 
 
  Hiera should support native HOCON to match Puppet Server  
 
 
 
 
 
 
 
 
 

Change By:
 
 Chris Price 
 
 
 

Scrum Team:
 
 Language Puppet Server 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6409) "integer too big to convert to `int' at" with lookupvar

Title: Message Title

Chris Price commented on PUP-6409

Re: "integer too big to convert to `int' at" with lookupvar

I found a code path in the JRuby code that might explain it. There is a method called org.jruby.Ruby#getCurrentContext, which gets called from lots and lots of places. Its call stack ends up checking for the existence of a soft reference of a context object that would contain the current RubyThread object, and if that reference has been cleared out by GC, then it calls an adopt method to "adopt" the current Java thread, which ultimately results in the construction of a new RubyThread instance.
If you have enough load on your server, and a small enough heap size, it may be garbage collecting these SoftReferences frequently enough to trigger this code path and I think that would explain it.
Jeremy Barlow can you think of any easy way to use jmap or some other tool to watch the instances of org.jruby.runtime.ThreadContext to confirm or refute the theory that the SoftReferences are being GC'd? Or, based on your recent work do you have any suggestions about how to force GC of SoftReferences in a reproducer program?

Add Comment

This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)

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

Jira (PUP-6361) Validate and error if a class or define is given a name starting with ::

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6361 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Validate and error if a class or define is given a name starting with ::  
 
 
 
 
 
 
 
 
 
 
Same thing for those - there are no relative functions, nor any relative types (and where they are relative, it is not allowed to break out of the name space). So error for those as well in validation. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6361) Validate and error if a class or define is given a name starting with ::

2016-06-28 Thread Thomas Hallgren (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-6361 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Validate and error if a class or define is given a name starting with ::  
 
 
 
 
 
 
 
 
 
 
Should the acceptance critera also contain: 
 
 
 
 
 
 
function ::foo() {} 
 
 
 
 
type ::Foo = Any
 
 
 
 
 
 
 
? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6452) Allow defaultfor to accept operators

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Souter created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6452 
 
 
 
  Allow defaultfor to accept operators  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/06/28 5:42 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Peter Souter 
 
 
 
 
 
 
 
 
 
 
Right now the defaultfor method for providers only accepts hashes. Meaning for something that releases fairly often like Fedora, the DNF provider has to get bumped over and over. 
As Rick Sherman suggests, it makes sense to just set it to be Fedora >= 24, and then if Fedora changes to another package manager in the future  then we can add a lesser-than constraint also 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)

Jira (PUP-6452) Allow defaultfor to accept operators

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Souter updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6452 
 
 
 
  Allow defaultfor to accept operators  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Souter 
 
 
 
 
 
 
 
 
 
 Right now the defaultfor method for providers only accepts hashes. Meaning for something that releases fairly often like Fedora, the DNF provider has to get bumped over and over.As [~richard.sherman] suggests, it makes sense to just set it to be Fedora >= 24, and then if Fedora changes to another package manager in the future ( ! unlikely hopefully, but possible :D ) then we can add a lesser-than constraint also 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDOC-71) Stack Level Too Deep Exception and Spurious Errors

2016-06-28 Thread Hailee Kenney (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney assigned an issue to Hailee Kenney 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-71 
 
 
 
  Stack Level Too Deep Exception and Spurious Errors  
 
 
 
 
 
 
 
 
 

Change By:
 
 Hailee Kenney 
 
 
 

Assignee:
 
 Hailee Kenney 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-1125) Exec checks should be turned into metaparameters

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-1125 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Exec checks should be turned into metaparameters  
 
 
 
 
 
 
 
 
 
 
I think that puppet needs to be able to manage f(s(r)) rather than just s(r) - that is, a function of resource r's state as opposed to just its state. The way to do that now is to compute f(s(r)) as a fact (symbolically defining which state out of a set of possible states for r to use) and sending it to the compiler. The compiler then produces s(r). It would probably be much better if the agent could pick the state s(r) out of multiple s'(r), s''(r) etc. It would also mean that it would potentially be possible to model transitions from one s(r) to s'(r) in one and the same catalog run. 
(I say probably be better, as it could bloat the catalog with potentially a very large set of alternative states for r that would not be used (even entire trees of states for dependent resources of r) - as opposed to producing a catalog "pruned" from such alternative states via a conditional in the compilation). 
I am not very much in favor of shoehorning in conditionals as meta parameters... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6422) ensure_resource not longer working with undef parameters

2016-06-28 Thread David Schmitt (JIRA)

Title: Message Title

David Schmitt commented on PUP-6422

Re: ensure_resource not longer working with undef parameters

The error is caused by this commit:

317727dafff612cbdb489c98ed286c53c25f290d is the first bad commit commit 317727dafff612cbdb489c98ed286c53c25f290d Author: Henrik Lindberg Date: Sat Jun 4 00:43:14 2016 +0200
(

PUP-6385
) Make create_resources filter out undef relationships
This adds logic that filters out all parameters that are undef from the instruction built by create_resources.
This is done to prevent validation of relationships to flag relationships to undef as an error. This is done for all parameters since an undef parameter means that the default value should be used. (The language evaluator does the same thing).

Of course this specific surfacing of the API change can be worked around in stdlib.

Add Comment

This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)

Jira (PUP-6447) Allow UTF8 files to have a leading BOM to be more tolerant of files produced on Windows

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6447 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow UTF8 files to have a leading BOM to be more tolerant of files produced on Windows  
 
 
 
 
 
 
 
 
 
 
Language specification needs to be updated for this. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PDOC-81) @param tag help text should be in JSON

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-81 
 
 
 
  @param tag help text should be in JSON  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Story Points:
 
 2 
 
 
 

Scrum Team:
 
 Language 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6451) User resource unable to remove users from groups

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6451 
 
 
 
  User resource unable to remove users from groups  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Scrum Team:
 
 Client Platform 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6451) User resource unable to remove users from groups

2016-06-28 Thread Jesse Reynolds (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Reynolds updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6451 
 
 
 
  User resource unable to remove users from groups  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Reynolds 
 
 
 
 
 
 
 
 
 
 The type reference docs state that the default behaviour of the user resource should 'membership => minimum' however it is behaving as per 'membership => inclusive' even if minimum is specified. Therefore, it appears that there's no way to remove users from secondary groups using the user resource. Steps to reproduce:Run the following with puppet apply:{code}group {'baz':  ensure => present,}user {'foo':  ensure=> present,  groups=> ['baz'],  membership => 'minimum',}{code}Now run the following code with puppet apply:{code}group {'baz':  ensure => present,}user {'foo':  ensure=> present,  groups=> [],  membership => 'minimum',}{code}Expected result:- user 'foo' is no longer a member of group 'baz'Actual result:- user ' foof foo ' is still a member of group 'baz'The "membership" attribute seems to be doing nothing. Furthermore, removing it should default to 'minimum' but it still behaves as if it were 'inclusive'. Docs reference: https://docs.puppet.com/puppet/latest/reference/type.html#user-attribute-membership 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

Jira (PUP-6451) User resource unable to remove users from groups

2016-06-28 Thread Jesse Reynolds (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Reynolds created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6451 
 
 
 
  User resource unable to remove users from groups  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.5.2 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Components:
 

 Types and Providers 
 
 
 

Created:
 

 2016/06/28 12:33 AM 
 
 
 

Environment:
 
 
CentOS 6.7 32bit VM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Jesse Reynolds 
 
 
 
 
 
 
 
 
 
 
The type reference docs state that the default behaviour of the user resource should 'membership => minimum' however it is behaving as per 'membership => inclusive' even if minimum is specified. Therefore, it appears that there's no way to remove users from secondary groups using the user resource.  
Steps to reproduce: 
Run the following with puppet apply:

Jira (PUP-6409) "integer too big to convert to `int' at" with lookupvar

2016-06-28 Thread JIRA

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jürgen Thomann commented on  PUP-6409 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "integer  too big to convert to `int' at" with lookupvar  
 
 
 
 
 
 
 
 
 
 
Chris Price It affected all which did a look up of a undefined variable. And we use at some places a external script from ruby code to do something and if it matters I have some gems installed were maybe the thread_safe gem is interesting as that one had a dependency to thread_safe. 
 
 
 
 
 
 
jruby-openssl (0.9.7 java) 
 
 
 
 
json (1.8.0 java) 
 
 
 
 
rake (10.1.0) 
 
 
 
 
rdoc (4.1.2) 
 
 
 
 
thread_safe (0.3.5 java) 
 
 
 
 
tzinfo (1.2.2) 
 
 
 
 
tzinfo-data (1.2016.4)
 
 
 
 
 
 
 
I looked also on the number it throws and it seems like the number increases by 200.000 in less than one minute. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

Jira (PUP-6409) "integer too big to convert to `int' at" with lookupvar