Jira (PDB-2627) (maint) Add puppet-agent libs to load path

2016-04-14 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2627 
 
 
 
  (maint) Add puppet-agent libs to load path  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/04/14 5:45 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
When we build puppetdb, we require access to the facter library. Unfortunately, this is under the Ruby Lib path installed with puppet-agent. System ruby, which we are currently using to build, doesn't have access to this libdir. This appends the puppet-agent vendor_lib path to the search path so system ruby can find Facter. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (FACT-1392) Facter fails when locale files are missing for specified locale on CentOS 7

2016-04-14 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1392 
 
 
 
  Facter fails when locale files are missing for specified locale on CentOS 7  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Acceptance Criteria:
 
 Should be covered by acceptance test. I haven't been able to reproduce the user's case, otherwise extending the acceptance test to cover that would be nice. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1392) Facter fails when locale files are missing for specified locale on CentOS 7

2016-04-14 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1392 
 
 
 
  Facter fails when locale files are missing for specified locale on CentOS 7  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Sprint:
 
 Client 2016- 05- 04 -20 (Bigga Bugs) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1392) Facter fails when locale files are missing for specified locale on CentOS 7

2016-04-14 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1392 
 
 
 
  Facter fails when locale files are missing for specified locale on CentOS 7  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Scope Change Category:
 
 Found 
 
 
 

Scope Change Reason:
 
 Merged for Facter 3.1.6 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5727) acceptance: cached catalog should allow encodings from utf8

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson assigned an issue to Eric Thompson 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5727 
 
 
 
  acceptance: cached catalog should allow encodings from utf8  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Assignee:
 
 qa Eric Thompson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1392) Facter fails when locale files are missing for specified locale on CentOS 7

2016-04-14 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1392 
 
 
 
  Facter fails when locale files are missing for specified locale on CentOS 7  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Fix Version/s:
 
 FACT 3.1.6 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (NPUP-36) Implement the `step` function.

2016-04-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Native Puppet /  NPUP-36 
 
 
 
  Implement the `step` function.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Status:
 
 Ready for  Merge  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-6139) Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/

2016-04-14 Thread Erik Dasher (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erik Dasher updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6139 
 
 
 
  Puppet Server 1.0.2 Could not find file file_metadata and file_bucket md5/  
 
 
 
 
 
 
 
 
 

Change By:
 
 Erik Dasher 
 
 
 

QA Risk Assessment Reason:
 
 QA RA=N/A; No code change associated with this ticket. 
 
 
 

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 (NPUP-36) Implement the `step` function.

2016-04-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  NPUP-36 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Implement the `step` function.  
 
 
 
 
 
 
 
 
 
 
Merged to master: 0d566cd 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5105) Add a ci:test:aio_per_commit Rake target for reduced acceptance suite

2016-04-14 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-5105 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add a ci:test:aio_per_commit Rake target for reduced acceptance suite  
 
 
 
 
 
 
 
 
 
 
Verified that this ran through the per-commit pipeline. And the time for the Integration Tests step dropped from 90-ish minutes to 22 minutes. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5929) Allow type alias to define a mapping between puppet names and runtime types

2016-04-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5929 
 
 
 
  Allow type alias to define a mapping between puppet names and runtime types  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Acceptance Criteria:
 
 That the {{Runtime}} type in puppet now accepts parameters allowing it to define a mapping between a runtime type, and a puppet type name . , or by mapping patterns:  A one to one mapping:{code:puppet}type MyModule::ImplementationRegistry = Object[{}]type Runtime[ruby, 'Puppet::Pops::Types::ImplementationRegistry'] = MyModule::ImplementationRegistrynotice MyModule::ImplementationRegistry{code}And a pattern based mapping:{code:puppet}type MyModule::TypeMismatchDescriber = Object[{}]type Runtime[ruby, [/^Puppet::Pops::Types::(\\w+)$/, 'MyModule::\\1']] = [/^MyModule::(\\w+)$/, 'Puppet::Pops::Types::\\1']notice MyModule::TypeMismatchDescriber{code} There is no user facing functionality at this point  except being able to create an notice these mappings (  as this is a technical enabler for serialization/deserialization ), and that errors are raised if attempting to define mappings with illegal parameters / data types . 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (NPUP-39) Conform to Puppet's `assignable?` logic.

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Native Puppet /  NPUP-39 
 
 
 
  Conform to Puppet's `assignable?` logic.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

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 (FACT-1379) Facter returns incorrect MAC address for bonded interfaces

2016-04-14 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley commented on  FACT-1379 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter returns incorrect MAC address for bonded interfaces  
 
 
 
 
 
 
 
 
 
 
I'm not sure a test is practical, despite my earlier assertion. Every distro is different, and what I had thought/hoped was standard "modern systemd way to do things" on my laptop turns out to be fairly arch-specific . I'm gonna keep playing with it a bit more before I give up totally. I'd like to get a test on at least one distro 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5638) acceptance: lookup() and data-in-modules' should work in site clauses

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson assigned an issue to Eric Thompson 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5638 
 
 
 
  acceptance: lookup() and data-in-modules' should work in site clauses  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Assignee:
 
 qa Eric Thompson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5929) Allow type alias to define a mapping between puppet names and runtime types

2016-04-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5929 
 
 
 
  Allow type alias to define a mapping between puppet names and runtime types  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 Henrik Lindberg 
 
 
 

Acceptance Criteria:
 
 That the {{Runtime}} type in puppet now accepts parameters allowing it to define a mapping between a runtime type, and a puppet type name.There is no user facing functionality at this point as this is a technical enabler for serialization/deserialization. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5929) Allow type alias to define a mapping between puppet names and runtime types

2016-04-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-5929 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allow type alias to define a mapping between puppet names and runtime types  
 
 
 
 
 
 
 
 
 
 
Merged to master at: a47f670 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6176) Behavior of undef in relationships has changed in master since 4.4.x

2016-04-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6176 
 
 
 
  Behavior of undef in relationships has changed in master since 4.4.x  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Acceptance Criteria:
 
 That the following example does not cause an error:{code}puppet apply -e ' user notify  {example:  ensure  message  =>  present  yay , notify => undef}'{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6176) Behavior of undef in relationships has changed in master since 4.4.x

2016-04-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6176 
 
 
 
  Behavior of undef in relationships has changed in master since 4.4.x  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Acceptance Criteria:
 
 That the following example does not cause an error:{code}puppet apply -e 'user {example: ensure => present, notify => undef}'{code} 
 
 
 

Release Notes Summary:
 
 Regression in not yet released code. 
 
 
 

Release Notes:
 
 Not Needed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-76) Document the available YARD @tags for ruby/pp doc objects

2016-04-14 Thread Nicholas Fagerlund (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nicholas Fagerlund updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-76 
 
 
 
  Document the available YARD @tags for ruby/pp doc objects  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nicholas Fagerlund 
 
 
 
 
 
 
 
 
 
 You can use tags like {{@return}} and {{@example}} to document your classes, functions, types, etc., but as a user, I'm not sure exactly what's available or what I SHOULD be using. It'd be nice to have a list! For example: I went looking to see whether there's a way to override the default value for a parameter in a native Ruby resource type (like in cases where the default isn't cleanly introspectable). I can't tell! (If there's not, that'll be another 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-6176) Behavior of undef in relationships has changed in master since 4.4.x

2016-04-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6176 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Behavior of undef in relationships has changed in master since 4.4.x  
 
 
 
 
 
 
 
 
 
 
Merged to master at: cf44d8d 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6168) Runtime3Loader initiates load that updates loader, then tries to update again

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6168 
 
 
 
  Runtime3Loader initiates load that updates loader, then tries to update again  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

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-6168) Runtime3Loader initiates load that updates loader, then tries to update again

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6168 
 
 
 
  Runtime3Loader initiates load that updates loader, then tries to update again  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

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 (PUP-6167) Default Tuple type constructed with "max" of 0 instead of "infinity".

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6167 
 
 
 
  Default Tuple type constructed with "max" of 0 instead of "infinity".  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

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 (PUP-6167) Default Tuple type constructed with "max" of 0 instead of "infinity".

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6167 
 
 
 
  Default Tuple type constructed with "max" of 0 instead of "infinity".  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

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-6167) Default Tuple type constructed with "max" of 0 instead of "infinity".

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson commented on  PUP-6167 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Default Tuple type constructed with "max" of 0 instead of "infinity".  
 
 
 
 
 
 
 
 
 
 
validated on ubuntu1404 at puppet-agent master SHA: ef41d9d33b55c2c9474ca30e314ca47d971953c8 
 
 
 
 
 
 
root@nmqvp3nzinbknf3:~# puppet apply -e 'notice([1,2,3].reverse_each)' 
 
 
 
 
Notice: Scope(Class[main]): Iterator[Integer] value 
 
 
 
 
Notice: Compiled catalog for nmqvp3nzinbknf3.delivery.puppetlabs.net in environment production in 0.04 seconds 
 
 
 
 
Notice: Applied catalog in 0.02 seconds 
 
 
 
 
root@nmqvp3nzinbknf3:~# puppet apply -e 'notice(Tuple >= Tuple[String])' 
 
 
 
 
Notice: Scope(Class[main]): true 
 
 
 
 
Notice: Compiled catalog for nmqvp3nzinbknf3.delivery.puppetlabs.net in environment production in 0.04 seconds 
 
 
 
 
Notice: Applied catalog in 0.02 seconds 
 
 
 
 
root@nmqvp3nzinbknf3:~# puppet apply -e 'notice(Tuple > Tuple[String])' 
 
 
 
 
   

Jira (PUP-6157) Reduce inferred Variant[T] to T in inference of Array and Hash

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6157 
 
 
 
  Reduce inferred Variant[T] to T in inference of Array and Hash  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

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-6157) Reduce inferred Variant[T] to T in inference of Array and Hash

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson commented on  PUP-6157 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Reduce inferred Variant[T] to T in inference of Array and Hash  
 
 
 
 
 
 
 
 
 
 
validated on ubuntu1404 at puppet-agent master sha: ef41d9d33b55c2c9474ca30e314ca47d971953c8 
 
 
 
 
 
 
root@nmqvp3nzinbknf3:~# puppet apply -e 'notice([1,2,3].reverse_each)' 
 
 
 
 
Notice: Scope(Class[main]): Iterator[Integer] value 
 
 
 
 
Notice: Compiled catalog for nmqvp3nzinbknf3.delivery.puppetlabs.net in environment production in 0.04 seconds 
 
 
 
 
Notice: Applied catalog in 0.02 seconds
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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



Jira (PUP-6157) Reduce inferred Variant[T] to T in inference of Array and Hash

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6157 
 
 
 
  Reduce inferred Variant[T] to T in inference of Array and Hash  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

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 (PUP-6157) Reduce inferred Variant[T] to T in inference of Array and Hash

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6157 
 
 
 
  Reduce inferred Variant[T] to T in inference of Array and Hash  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Acceptance Criteria:
 
 That  the example in PUP-6151  {{notice(\[1 , 2,3\].reverse_each)}},  outputs 'Iterator \ [Integer \ ]' instead of 'Iterator \ [Variant \ [Integer \ ] \ ]' 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1392) Facter fails when locale files are missing for specified locale on CentOS 7

2016-04-14 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1392 
 
 
 
  Facter fails when locale files are missing for specified locale on CentOS 7  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 FACT 3.1.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/04/14 3:15 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Michael Smith 
 
 
 
 
 
 
 
 
 
 
I'm not completely sure of the circumstances, but this seems like a trivial thing to try to fix. 
From #puppet-dev and #puppet on April 8th, 2016 
 
1:37 PM  failed to initialize logging system due to a locale error: Invalid or unsupported charset:ANSI_X3.4-1968 1:38 PM  our locale appear to be setup correctly, and have an strace of facter if it helps 1:38 PM  http://paste.openstack.org/show/493540/ ... 2:49 PM  I've tried both en_US.utf8 and C 2:51 PM  nibalizer: this was working on our devstack-centos7 image IIRC 2:51 PM  but stopped once we migrated to centos-7 dib 2:51 PM  huh 2:51 PM  anything interesent in 'env' ? 2:52 PM  said that again? 2:52 PM  give me a sec, need to grab a node 2:53 PM  but env looked good last I remember 2:54 PM  https://confluence.atlassian.com/confkb/filesystem-encoding-is-written-as-ansi_x3-4-1968-even-though-the-server-is-set-to-utf-8-658735809.html suggests how to change the system encoding. We can look into why that locale isn't working. 2:56 PM  What does 'locale' print on that system? 2:56 PM  It could be a bug in one of the libraries Facter is using. 2:57 PM  sure, give me a min to log into a node 3:03 PM  http://paste.openstack.org/show/493545/ is current locale 3:03 PM  which is generating some errors 3:03 PM  let m

Jira (PUP-6157) Reduce inferred Variant[T] to T in inference of Array and Hash

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6157 
 
 
 
  Reduce inferred Variant[T] to T in inference of Array and Hash  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Release Notes Summary:
 
 Error messages and other output of data type information could sometimes display a Variant type having only a single variant. While correct, this verbose output is now  reduce  reduced  to that single type. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (NPUP-38) Respect `environment` scope.

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Native Puppet /  NPUP-38 
 
 
 
  Respect `environment` scope.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

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 (NPUP-38) Respect `environment` scope.

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Native Puppet /  NPUP-38 
 
 
 
  Respect `environment` scope.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

QA Risk Assessment:
 
 High 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (NPUP-38) Respect `environment` scope.

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Native Puppet /  NPUP-38 
 
 
 
  Respect `environment` scope.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Release Notes:
 
 Not Needed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6156) Access operator is not implemented for Iterator type

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson commented on  PUP-6156 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Access operator is not implemented for Iterator type  
 
 
 
 
 
 
 
 
 
 
validated on ubuntu1404 at puppet-agent master sha: ef41d9d33b55c2c9474ca30e314ca47d971953c8 
 
 
 
 
 
 
root@nmqvp3nzinbknf3:~# cat iterable.pp 
 
 
 
 
function foo(Iterable[String] $x) { 
 
 
 
 
  $x.each |$e| { 
 
 
 
 
notice $e 
 
 
 
 
  } 
 
 
 
 
} 
 
 
 
 
foo([foo, bar, baz, cake].reverse_each) 
 
 
 
 
root@nmqvp3nzinbknf3:~# puppet apply iterable.pp 
 
 
 
 
Notice: Scope(Class[main]): cake 
 
 
 
 
Notice: Scope(Class[main]): baz 
 
 
 
 
   

Jira (PUP-6156) Access operator is not implemented for Iterator type

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6156 
 
 
 
  Access operator is not implemented for Iterator type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

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-6156) Access operator is not implemented for Iterator type

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6156 
 
 
 
  Access operator is not implemented for Iterator type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

QA Risk Assessment:
 
 Medium 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6156) Access operator is not implemented for Iterator type

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson assigned an issue to Eric Thompson 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6156 
 
 
 
  Access operator is not implemented for Iterator type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Assignee:
 
 qa Eric Thompson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1168) Segfault on invalid locale settings

2016-04-14 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1168 
 
 
 
  Segfault on invalid locale settings  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Fix Version/s:
 
 FACT 3.1.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-6155) Access operator is not implemented for Iterable type

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6155 
 
 
 
  Access operator is not implemented for Iterable type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

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 (FACT-1168) Segfault on invalid locale settings

2016-04-14 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1168 
 
 
 
  Segfault on invalid locale settings  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Affects Version/s:
 
 FACT 3.0.1 
 
 
 

Affects Version/s:
 
 FACT 3.0.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-6155) Access operator is not implemented for Iterable type

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6155 
 
 
 
  Access operator is not implemented for Iterable type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

QA Risk Assessment:
 
 Medium 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6155) Access operator is not implemented for Iterable type

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson commented on  PUP-6155 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Access operator is not implemented for Iterable type  
 
 
 
 
 
 
 
 
 
 
validated on ubuntu1404 at puppet-agent master sha:  
 
 
 
 
 
 
root@nmqvp3nzinbknf3:~# puppet apply iterable.pp 
 
 
 
 
Notice: Scope(Class[main]): bar 
 
 
 
 
Notice: Scope(Class[main]): baz 
 
 
 
 
Notice: Scope(Class[main]): cake 
 
 
 
 
Notice: Compiled catalog for nmqvp3nzinbknf3.delivery.puppetlabs.net in environment production in 0.05 seconds 
 
 
 
 
Notice: Applied catalog in 0.02 seconds 
 
 
 
 
root@nmqvp3nzinbknf3:~# vi iterable.pp 
 
 
 
 
#[where we pass single string of 'failure' unquoted to foo()] 
 
 
 
 
root@nmqvp3nzinbknf3:~# puppet apply iterable.pp 
 
 
 
 
Notice: Scope(Class[main]): f 
 
 
 

Jira (FACT-1168) Segfault on invalid locale settings

2016-04-14 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1168 
 
 
 
  Segfault on invalid locale settings  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Affects Version/s:
 
 FACT 3.x 
 
 
 

Affects Version/s:
 
 FACT 3.0.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6155) Access operator is not implemented for Iterable type

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson assigned an issue to Eric Thompson 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6155 
 
 
 
  Access operator is not implemented for Iterable type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Assignee:
 
 qa Eric Thompson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6155) Access operator is not implemented for Iterable type

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6155 
 
 
 
  Access operator is not implemented for Iterable type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Acceptance Criteria:
 
 * It is possible to narrow an Iterable using access operator i.e  {{  Iterable[T] }} {code}function foo(Iterable[String] $x) {  $x.each |$e| {notice $e  }} foo([bar, baz, cake]){code}should produce:{code} Notice: Scope(Class[main]): barNotice: Scope(Class[main]): bazNotice: Scope(Class[main]): cake{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6155) Access operator is not implemented for Iterable type

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6155 
 
 
 
  Access operator is not implemented for Iterable type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Acceptance Criteria:
 
 * It is possible to narrow an Iterable using access operator i.e Iterable[T] * Above example produces the expected result {code}function foo(Iterable[String] $x) {  $x . each |$e| {notice $e  }} foo([bar, baz, cake]){code}should produce:{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6155) Access operator is not implemented for Iterable type

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6155 
 
 
 
  Access operator is not implemented for Iterable type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 
 
 
 
 
 
 
 The following code causes a compilation error:{code}function foo(Iterable[String] $x) {  $x.each |$e| {notice $e  }}foo([bar, baz, cake]){code}Resulting in:{code}Error: Evaluation Error: Operator '[]' is not applicable to an Iterable-Type.{code}Expected output:{code}Notice: Scope(Class[main]): barNotice: Scope(Class[main]): bazNotice: Scope(Class[main]): cake{code}This is because the access operator for {{Iterable}} is not implemented.  I'd expect the access operator to take a single type parameter to construct a constrained {{Iterable}} type. ACCEPTANCE CRITERIA* That it is possible to narrow the an Iterable using access operator i.e {{Iterable\[T]}}* That the above example produces the expected result. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6155) Access operator is not implemented for Iterable type

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6155 
 
 
 
  Access operator is not implemented for Iterable type  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Acceptance Criteria:
 
 * It is possible to narrow an Iterable using access operator i.e Iterable[T]* Above example produces the expected result. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (NPUP-39) Conform to Puppet's `assignable?` logic.

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Native Puppet /  NPUP-39 
 
 
 
  Conform to Puppet's `assignable?` logic.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

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 (FACT-1391) --custom-dir does not support trailing slashes on Windows

2016-04-14 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1391 
 
 
 
  --custom-dir does not support trailing slashes on Windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

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 (NPUP-39) Conform to Puppet's `assignable?` logic.

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Native Puppet /  NPUP-39 
 
 
 
  Conform to Puppet's `assignable?` logic.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Release Notes:
 
 Not Needed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (NPUP-35) Implement the `reverse_each` function.

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Native Puppet /  NPUP-35 
 
 
 
  Implement the `reverse_each` function.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

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 (NPUP-35) Implement the `reverse_each` function.

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Native Puppet /  NPUP-35 
 
 
 
  Implement the `reverse_each` function.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Release Notes:
 
 New Feature Not Needed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (NPUP-35) Implement the `reverse_each` function.

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Native Puppet /  NPUP-35 
 
 
 
  Implement the `reverse_each` function.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

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 (NPUP-35) Implement the `reverse_each` function.

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Native Puppet /  NPUP-35 
 
 
 
  Implement the `reverse_each` function.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

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 (NPUP-36) Implement the `step` function.

2016-04-14 Thread Peter Huene (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Native Puppet /  NPUP-36 
 
 
 
  Implement the `step` function.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Huene 
 
 
 

Sprint:
 
 Language  Triage  2016-04-20 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 (NPUP-36) Implement the `step` function.

2016-04-14 Thread Peter Huene (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene assigned an issue to Peter Huene 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Native Puppet /  NPUP-36 
 
 
 
  Implement the `step` function.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Huene 
 
 
 

Assignee:
 
 Peter Huene 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1391) --custom-dir does not support trailing slashes on Windows

2016-04-14 Thread Hailee Kenney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1391 
 
 
 
  --custom-dir does not support trailing slashes on Windows  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Windows 
 
 
 

Created:
 

 2016/04/14 2:19 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Hailee Kenney 
 
 
 
 
 
 
 
 
 
 
When giving facter a directory to look for custom facts, if the path is giving with a trailing slash facter will fail to find the facts in that directory. 
 
 
 
 
 
 
PS C:\Users\HAIL 9000\my_custom_facts> ls 
 
 
 
 
  
 
 
 
 
  
 
 
 
 
 

Jira (FACT-1391) --custom-dir does not support trailing slashes on Windows

2016-04-14 Thread Hailee Kenney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1391 
 
 
 
  --custom-dir does not support trailing slashes on Windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Hailee Kenney 
 
 
 
 
 
 
 
 
 
 When giving facter a directory to look for custom facts, if the path is giving with a trailing slash facter will fail to find the facts in that directory.{noformat}PS C:\Users\HAIL 9000\my_custom_facts> lsDirectory: C:\Users\HAIL 9000\my_custom_factsModeLastWriteTime Length Name- -- -a4/14/2016   1:33 PM 71 my_fact.rbPS C:\Users\HAIL 9000\my_custom_facts> cat .\my_fact.rbFacter.add('my_fact') do  setcode do'my_fact_value'  endendPS C:\Users\HAIL 9000\my_custom_facts> cd 'C:\Users\HAIL 9000\facter\release\'PS C:\Users\HAIL 9000\facter\release> .\bin\facter.exe my_fact --custom-dir 'C:\Users\HAIL 9000\my_custom_facts\'  PS C:\Users\HAIL 9000\facter\release> .\bin\facter.exe my_fact --custom-dir 'C:\Users\HAIL 9000\my_custom_facts'my_fact_value{noformat} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6122) add deprecation warning for resource_types endpoint

2016-04-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6122 
 
 
 
  add deprecation warning for resource_types endpoint  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Fix Version/s:
 
 PUP 4.5.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-6122) add deprecation warning for resource_types endpoint

2016-04-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6122 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: add deprecation warning for resource_types endpoint  
 
 
 
 
 
 
 
 
 
 
Is there a corresponding removal ticket? If so link it here and to the "5.0.0 Removals" Epic. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-76) Document the available YARD @tags for ruby/pp doc objects

2016-04-14 Thread Nicholas Fagerlund (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nicholas Fagerlund created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet Strings /  PDOC-76 
 
 
 
  Document the available YARD @tags for ruby/pp doc objects  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/04/14 2:18 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Nicholas Fagerlund 
 
 
 
 
 
 
 
 
 
 
You can use tags like @return and @example to document your classes, functions, types, etc., but as a user, I'm not sure exactly what's available or what I SHOULD be using. It'd be nice to have a list! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (NPUP-38) Respect `environment` scope.

2016-04-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Native Puppet /  NPUP-38 
 
 
 
  Respect `environment` scope.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Status:
 
 Ready for  Merge  Test 
 
 
 

Assignee:
 
 Henrik Lindberg 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 (NPUP-38) Respect `environment` scope.

2016-04-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  NPUP-38 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Respect `environment` scope.  
 
 
 
 
 
 
 
 
 
 
Merged to master: 16457b8 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5025) Package resource showing notice when ensure attribute contains Epoch tag

2016-04-14 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-5025 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Package resource showing notice when ensure attribute contains Epoch tag  
 
 
 
 
 
 
 
 
 
 
Updating fixVersion since we're grouping this with other yum/rpm/dnf providers next sprint, all targeting 4.5.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-5025) Package resource showing notice when ensure attribute contains Epoch tag

2016-04-14 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5025 
 
 
 
  Package resource showing notice when ensure attribute contains Epoch tag  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Fix Version/s:
 
 PUP 4.4.2 
 
 
 

Fix Version/s:
 
 PUP 4.5.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-6176) Behavior of undef in relationships has changed in master since 4.4.x

2016-04-14 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6176 
 
 
 
  Behavior of undef in relationships has changed in master since 4.4.x  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Scope Change Category:
 
 Found 
 
 
 

Scope Change Reason:
 
 Must be fixed right away 
 
 
 

Story Points:
 
 1 
 
 
 

Priority:
 
 Normal Blocker 
 
 
 

Sprint:
 
 Language 2016-04-20 
 
 
 

Scrum Team:
 
 Language 
 
 
 

Fix Version/s:
 
 PUP 4.5.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

   

Jira (PUP-5802) Yum provider incorrectly computes epoch for RPM package versions

2016-04-14 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-5802 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Yum provider incorrectly computes epoch for RPM package versions  
 
 
 
 
 
 
 
 
 
 
Updating fixVersion since we're grouping this with other yum/rpm/dnf providers next sprint, all targeting 4.5.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-5802) Yum provider incorrectly computes epoch for RPM package versions

2016-04-14 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5802 
 
 
 
  Yum provider incorrectly computes epoch for RPM package versions  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Fix Version/s:
 
 PUP 4.4.2 
 
 
 

Fix Version/s:
 
 PUP 4.5.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-5105) Add a ci:test:aio_per_commit Rake target for reduced acceptance suite

2016-04-14 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5105 
 
 
 
  Add a ci:test:aio_per_commit Rake target for reduced acceptance suite  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Fix Version/s:
 
 PUP 4.4.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5105) Add a ci:test:aio_per_commit Rake target for reduced acceptance suite

2016-04-14 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5105 
 
 
 
  Add a ci:test:aio_per_commit Rake target for reduced acceptance suite  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Release Notes:
 
 Not Needed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6122) add deprecation warning for resource_types endpoint

2016-04-14 Thread Preben Ingvaldsen (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Preben Ingvaldsen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6122 
 
 
 
  add deprecation warning for resource_types endpoint  
 
 
 
 
 
 
 
 
 

Change By:
 
 Preben Ingvaldsen 
 
 
 

Release Notes Summary:
 
 We need to mention in the resource_types documentation that the feature has been deprecated in favor of the environment_classes endpoint in 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-6122) add deprecation warning for resource_types endpoint

2016-04-14 Thread Preben Ingvaldsen (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Preben Ingvaldsen updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6122 
 
 
 
  add deprecation warning for resource_types endpoint  
 
 
 
 
 
 
 
 
 

Change By:
 
 Preben Ingvaldsen 
 
 
 

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 (PUP-6176) Behavior of undef in relationships has changed in master since 4.4.x

2016-04-14 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-6176 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Behavior of undef in relationships has changed in master since 4.4.x  
 
 
 
 
 
 
 
 
 
 
I'm investigating 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 (PUP-6176) Behavior of undef in relationships has changed in master since 4.4.x

2016-04-14 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren assigned an issue to Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6176 
 
 
 
  Behavior of undef in relationships has changed in master since 4.4.x  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1280) Empty 'aio_agent_version' fact on AIO agent

2016-04-14 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1280 
 
 
 
  Empty 'aio_agent_version' fact on AIO agent  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 
 
 
 
 
 
 
 I've seen a reference to the {{aio_agent_version}} fact in several modules ([one example among others|https://github.com/puppet-community/puppet-archive/blob/master/manifests/params.pp#L26]), unfortunately in the environment described above this fact is not set when installing {{puppet-agent}} from the PC1 yum repos. A solution to this going forward is to allow the {{aio_agent_version}} to be specified during compilation, so puppet-agent packaging can set the correct version. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1280) Ensure 'aio_agent_version' fact is available in an AIO agent

2016-04-14 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1280 
 
 
 
  Ensure 'aio_agent_version' fact is available in an AIO agent  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Story Points:
 
 1 
 
 
 

Summary:
 
 Empty Ensure  'aio_agent_version' fact  on  is available in an  AIO agent 
 
 
 

Sprint:
 
 Client Triage 
 
 
 

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

Jira (NPUP-38) Respect `environment` scope.

2016-04-14 Thread Peter Huene (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene assigned an issue to Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Native Puppet /  NPUP-38 
 
 
 
  Respect `environment` scope.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Huene 
 
 
 

Assignee:
 
 Peter Huene Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2362) ssh_authorized_keys temporary file Operation not permitted

2016-04-14 Thread Dan Alvizu (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Alvizu commented on  PUP-2362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ssh_authorized_keys temporary file Operation not permitted  
 
 
 
 
 
 
 
 
 
 
Some more info: we are running ruby 1.8.7 as well. 
On the VM where we run puppet agent, the /tmp/puppet* files are all ssh keys owned by different users.  
The 'operation not permitted' operation happens for a user which has not yet had their key copied. For example, the error: 
 
 
 
 
 
 
(/Stage[main]/Users::Pcadmin/Users::Add_user[user-a]/Ssh_authorized_key[user-a]) Could not evaluate: Puppet::Util::FileType::FileTypeFlat could not write /home/user-a/.ssh/authorized_keys: Operation not permitted - /tmp/puppet20160414-2438-14ibl9k-0
 
 
 
 
 
 
 
The file ' /tmp/puppet20160414-2438-14ibl9k-0' is owned by 'user-b' not 'user-a', but 'user-b' also does not have a /tmp/puppet* file  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1280) Empty 'aio_agent_version' fact on AIO agent

2016-04-14 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  FACT-1280 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Empty 'aio_agent_version' fact on AIO agent  
 
 
 
 
 
 
 
 
 
 
I've also looked at whether this could be added to the puppet-agent package, and filed PA-241. As changes would likely also be desired in Facter, this ticket could cover the Facter portion of that work. The way I see it working is: 
 

add a compile-time flag to Facter that, when set, creates an aio_agent_version fact in Facter; we can use the same name, with the assumption that the PE custom fact may override it
 

the puppet-agent build sets that compile-time flag
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2626) (maint) Update TK version

2016-04-14 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2626 
 
 
 
  (maint) Update TK version  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/04/14 11:08 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
This updates trapperkeeper and kitchensink to match the versions used in other PE projects. 
Depends on puppetlabs/puppetdb#1930. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (FACT-1379) Facter returns incorrect MAC address for bonded interfaces

2016-04-14 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  FACT-1379 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter returns incorrect MAC address for bonded interfaces  
 
 
 
 
 
 
 
 
 
 
Are you looking at adding testing still as part of 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 (PDB-2625) Update to raynes.fs 1.4.6

2016-04-14 Thread Nick Lewis (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Lewis created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 PuppetDB /  PDB-2625 
 
 
 
  Update to raynes.fs 1.4.6  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/04/14 10:55 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Nick Lewis 
 
 
 
 
 
 
 
 
 
 
In order to run with other projects in a single jvm (a la the aio), PuppetDB needs to move from raynes.fs 1.4.5 to 1.4.6. Other projects use 1.4.6, which through pedantic mode prevents using 1.4.5. 
However, fs 1.4.6 is backward incompatible with 1.4.5 in a couple of important ways. Specifically, it removes absolute-path and normalized-path. Those functions have thus been moved to kitchensink 1.3.0. Since trapperkeeper 1.2.0 (currently used by PuppetDB) itself was also using some of those functions, it also needs to be updated to at least 1.3.0. Doing so, however, will bring in support for HUP reloads; it's not clear whether PuppetDB is currently reading for that functionality or whether bringing it in early is harmful. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
  

Jira (PUP-6122) add deprecation warning for resource_types endpoint

2016-04-14 Thread Kevin Corcoran (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kevin Corcoran assigned an issue to Preben Ingvaldsen 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6122 
 
 
 
  add deprecation warning for resource_types endpoint  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kevin Corcoran 
 
 
 

Assignee:
 
 Preben Ingvaldsen 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2362) ssh_authorized_keys temporary file Operation not permitted

2016-04-14 Thread Adam Gibbins (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adam Gibbins updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-2362 
 
 
 
  ssh_authorized_keys temporary file Operation not permitted  
 
 
 
 
 
 
 
 
 

Change By:
 
 Adam Gibbins 
 
 
 

Affects Version/s:
 
 PUP 3.8.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2362) ssh_authorized_keys temporary file Operation not permitted

2016-04-14 Thread Dan Alvizu (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Alvizu commented on  PUP-2362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ssh_authorized_keys temporary file Operation not permitted  
 
 
 
 
 
 
 
 
 
 
cc Patrick Carlisle looks like you fixed this last time https://github.com/puppetlabs/puppet/pull/1898 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-2362) ssh_authorized_keys temporary file Operation not permitted

2016-04-14 Thread Dan Alvizu (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Alvizu commented on  PUP-2362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ssh_authorized_keys temporary file Operation not permitted  
 
 
 
 
 
 
 
 
 
 
Related issue on old tracker: https://projects.puppetlabs.com/issues/21203 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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

2016-04-14 Thread Steve Potter (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Steve Potter commented on  PUP-1125 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Exec checks should be turned into metaparameters  
 
 
 
 
 
 
 
 
 
 
It doesn't seem like this has request has had any action in a long time. I would like to propose a few other examples that I've run across that would be useful to have onlyif/unless act like metaparameters. 
1) I have modules that set up and manage the underlying infrastructure of applications, but not the entirety of their data and usage. For example, databases, and database filesystems. In our environment, we create /d## filesystems and as the databases grow, we add additional filesystems. Because of this, on any individual server, I could have /d01 by itself, /d01 - /d03, /d01 - /d05, or even /d01 - /d99. I would like to have my basic database manifest have 
$dbvols = [ "/d01", "/d02", "/d03"  , "/d99"] file  { $dbvols: owner => 'oracle', group => 'oinstall', mode => '0750', _onlyif_ => exists # for example, not sure how exactly syntax would work } 
so that permissions are always correct if the filesystem exists, but it doesn't create a whole bunch of empty directories if they don't already exist. 
2) In a similar vein, we create certain local service accounts with default passwords, but the service owners change those passwords once we turn the servers over to them (we have multiple teams that use the same service account name but don't actually manage other servers). It would be useful to be able to do something like: 
user  { 'oracle': password => , unless => exists } 
to create the account and set a default password, but not to change it if the account already exists and has a different password. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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+u

Jira (PUP-6176) Behavior of undef in relationships has changed in master since 4.4.x

2016-04-14 Thread Matthaus Owens (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthaus Owens created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6176 
 
 
 
  Behavior of undef in relationships has changed in master since 4.4.x  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/04/14 10:17 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Matthaus Owens 
 
 
 
 
 
 
 
 
 
 
Before (in puppet 4.4.1 and earlier), something like 
 
 
 
 
 
 
puppet apply -e "user {'matthaus': ensure => present, notify => undef}" 
 
 
 
 
 
 
Would work, but now it causes a compile error: 
 
 
 
 
 
 
puppet apply -e "user {'matthaus': ensure => present, notify => undef}" 
 
 
 
 
Error: No title provided and "" is not a valid resource reference on node wyclef-2.local 
   

Jira (PUP-2362) ssh_authorized_keys temporary file Operation not permitted

2016-04-14 Thread Dan Alvizu (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Dan Alvizu commented on  PUP-2362 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ssh_authorized_keys temporary file Operation not permitted  
 
 
 
 
 
 
 
 
 
 
Charlie Sharpsteen this looks like it could be a regression of 

PUP-288
 which you fixed in 2013. We're seeing it on puppet 3.8.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6113) `puppet resource user` on Solaris fails when LDAP users are present

2016-04-14 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley commented on  PUP-6113 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: `puppet resource user` on Solaris fails when LDAP users are present  
 
 
 
 
 
 
 
 
 
 
You just have to spin up an LDAP instance and connect Solaris to it, which I don't really know how to do. Adam Bottchen had one set up that I used for development. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6136) newparam(:downgrade) for package type

2016-04-14 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-6136 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: newparam(:downgrade) for package type  
 
 
 
 
 
 
 
 
 
 
Matt Schuchard I haven't really had a chance to engage with this ticket, but a question and a comment. 
First, can you provide some sample snippets / use-cases? I'm guessing you want to be able to disable downgrades so that something like 
 
 
 
 
 
 
pakage { 'foo': 
 
 
 
 
  ensure => '1.2.3', 
 
 
 
 
  downgrade => false 
 
 
 
 
}
 
 
 
 
 
 
 
And a node on 1.2.1 would end up on 1.2.3, whereas a node on 1.2.5 would remain at 1.2.3. Is that what the goal is? 
Second, there's some prior discussion on version matching at https://groups.google.com/forum/#!msg/puppet-dev/f2bPw9liasg/pfWFUja_-XwJ, which itself links to earlier discussions. Just mentioning that in case any of it sheds useful light on the problems you're solving. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (PUP-6175) Extension point for environment providers

2016-04-14 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-6175 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Extension point for environment providers  
 
 
 
 
 
 
 
 
 
 
The main reason for the current implementation (a file layout) is the puppet runtime relies on the layout on disk and file paths to a very high degree. While there could be an API for an environment provider, without quite extensive changes, that environment provider would have to lay down the information on disk and essentially construct a module path that consists of roots of all modules. 
I think it is well worth exploring as the knowledge about mapping names to paths is both complicated and implemented in multiple places (autoloader, 4.x loaders, module tooling, puppet server). There is one complication with an API approach as it requires that the environment providers are available in Ruby (later C++) as well as in the JVM (in an efficient way). Now, this is not required since the API is the paths in the file system (plus modulepath). (Imagine an environment provider that is served from in-memory, or from a DB. 
If the intent here is to provide "on demand file system layout for an env" then that may be completely doable without extensive changes. I don't see how such an API would have an impact on caching logic or env isolation - it would basically just automate the copying/linking into the right file system location on demand instead of a-priori. There may be a small performance penalty as the module path would grow in size. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1389) Facter.rb regression when called from MCO

2016-04-14 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith assigned an issue to Michael Smith 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1389 
 
 
 
  Facter.rb regression when called from MCO  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Assignee:
 
 Michael 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 (FACT-1389) Facter.rb regression when called from MCO

2016-04-14 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  FACT-1389 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter.rb regression when called from MCO  
 
 
 
 
 
 
 
 
 
 
Failed nightly, the test fails when running a 32-bit install on a 64-bit 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-5353) Statically-enabled systemd service is treated like SysV init scripts - enabled each run.

2016-04-14 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  PUP-5353 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Statically-enabled systemd service is treated like SysV init scripts - enabled each run.  
 
 
 
 
 
 
 
 
 
 
William Hopper https://github.com/puppetlabs/puppet/compare/master...MikaelSmith:PUP-5353 has some thoughts I had on implementation. It's a little finicky to try and cache the status check, but I'd rather not shell out more than we need to. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6113) `puppet resource user` on Solaris fails when LDAP users are present

2016-04-14 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6113 
 
 
 
  `puppet resource user` on Solaris fails when LDAP users are present  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Acceptance Criteria:
 
 {{puppet resource user}} on Solaris should succeed and filter LDAP users, when present 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6160) Triage 3.x acceptance failure

2016-04-14 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-6160 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Triage 3.x acceptance failure  
 
 
 
 
 
 
 
 
 
 
This has now passed CI, so closing. 
Joshua Partlow if you think this fix was the wrong approach, please chime in here or 

PUP-5737
 and we can re-evaluate. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6160) Triage 3.x acceptance failure

2016-04-14 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-6160 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Triage 3.x acceptance failure  
 
 
 
 
 
 
 
 
 
 
Joshua Partlow more info in the PR: https://github.com/puppetlabs/puppet/pull/4880. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.


  1   2   >