Jira (PDB-2896) after upgrading PDB from 3.2.4 to 4.1.2 duplicate-key-value-violates in reports_hash_expr_idx

2016-08-03 Thread Andreas Unterkircher (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Unterkircher commented on  PDB-2896 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: after upgrading PDB from 3.2.4 to 4.1.2 duplicate-key-value-violates in reports_hash_expr_idx  
 
 
 
 
 
 
 
 
 
 
Since I have opened this bug the duplicate-key-value-violates error message have becomes less and lesser. And for some days the exceptions can no longer being found in the log. 
I can only suppose that this has something to do with the upgrade from 3.2.4 to 4.1.2 and some legacy data somewhere in pgsql or activemq that was not fitting and has now vanished. 
Anyway - I think this is resolved.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-6558) Regression: Puppet unable to load PE Trapperkeeper::Orchestrator type, breaking PE installation

2016-08-03 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren commented on  PUP-6558 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Regression: Puppet unable to load PE Trapperkeeper::Orchestrator type, breaking PE installation  
 
 
 
 
 
 
 
 
 
 
The env_path lookup is in pops/loaders.rb, line 188 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6576) What's the deal with data_binding_terminus? Deprecate?

2016-08-03 Thread Nicholas Fagerlund (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nicholas Fagerlund commented on  PUP-6576 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: What's the deal with data_binding_terminus? Deprecate?  
 
 
 
 
 
 
 
 
 
 
My take is, axe it.  
 

Puppet lookup is how Puppet does lookup.
 

If you need to substitute some other lookup system at the environment level, lookup.conf should have you 100% covered. 
 

Likewise if we decide to expand lookup.conf to the global level.
 
 
 

That doesn't give you a good way to completely disable lookup in modules, but AFAICT there's no reason to do so, so that's fine.
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6576) What's the deal with data_binding_terminus? Deprecate?

2016-08-03 Thread Nicholas Fagerlund (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nicholas Fagerlund created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6576 
 
 
 
  What's the deal with data_binding_terminus? Deprecate?  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/08/03 6:26 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Nicholas Fagerlund 
 
 
 
 
 
 
 
 
 
 
https://docs.puppet.com/puppet/latest/reference/configuration.html#databindingterminus 
This setting ostensibly controls how Puppet does automatic class parameter lookup.  
I don't think it quite works that way anymore. AFAIK, everything goes through Puppet lookup, which delegates to Hiera for the first (global) layer of lookups.  
Should we remove this setting? Should we replace it with something else? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 
 

Jira (PUP-6475) Agent should use first entry of server_list in cases where failover has not occured

2016-08-03 Thread Sean Griffin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6475 
 
 
 
  Agent should use first entry of server_list in cases where failover has not occured  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

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-5381) Evaluating instance match with Optional[T] and NotUndef[T] fails when T is a string value

2016-08-03 Thread Sean Griffin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5381 
 
 
 
  Evaluating instance match with Optional[T] and NotUndef[T] fails when T is a string value  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

QA Risk Assessment:
 
 Medium 
 
 
 

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-2575) OS X group resource triggers spurious notice of a change

2016-08-03 Thread Sean Griffin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-2575 
 
 
 
  OS X group resource triggers spurious notice of a change  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

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-5887) Interpolation in interpolation nested string does not work.

2016-08-03 Thread Sean Griffin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5887 
 
 
 
  Interpolation in interpolation nested string does not work.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

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-6042) `puppet agent --test` does not override cached catalog behavior

2016-08-03 Thread Sean Griffin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6042 
 
 
 
  `puppet agent --test` does not override cached catalog behavior   
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

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-6437) directoryservice user provider crashes if no ShadowHashData is found

2016-08-03 Thread Sean Griffin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin updated an issue 
 
 
 
 
 
 
 
 
 
 

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

Change By:
 
 Sean Griffin 
 
 
 

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-6441) Redact events with sensitive data

2016-08-03 Thread Sean Griffin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6441 
 
 
 
  Redact events with sensitive data  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

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-6434) Define data type for marking certain information as sensitive

2016-08-03 Thread Sean Griffin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6434 
 
 
 
  Define data type for marking certain information as sensitive  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

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-6083) Use --strict option to deprecate Class[] where begins with a capital letter.

2016-08-03 Thread Sean Griffin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6083 
 
 
 
  Use --strict option to deprecate Class[] where  begins with a capital letter.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

QA Risk Assessment:
 
 Medium 
 
 
 

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-1429) Facter returns an exit code 0 if you look up an non-existent fact

2016-08-03 Thread Sean Griffin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1429 
 
 
 
  Facter returns an exit code 0 if you look up an non-existent fact  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

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 (HI-505) Hiera 3.1.0 with Puppet 4.3.2 is causing an error during spec testing.

2016-08-03 Thread Sean Griffin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-505 
 
 
 
  Hiera 3.1.0 with Puppet 4.3.2 is causing an error during spec testing.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

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 (HI-505) Hiera 3.1.0 with Puppet 4.3.2 is causing an error during spec testing.

2016-08-03 Thread Sean Griffin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-505 
 
 
 
  Hiera 3.1.0 with Puppet 4.3.2 is causing an error during spec testing.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

Assignee:
 
 Trevor Vaughan 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6483) "puppet resource user", when run in Windows creates a login attempt.

2016-08-03 Thread Rob Reynolds (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Reynolds commented on  PUP-6483 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "puppet resource user", when run in Windows creates a login attempt.   
 
 
 
 
 
 
 
 
 
 
Builds kicked off for puppet at https://jenkins.puppetlabs.com/view/puppet-agent/view/stable/view/puppet/job/platform_puppet_init-van-component_stable/224/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6545) Ruby 2.3 fails spec tests on Appveyor in Windows

2016-08-03 Thread Erick Banks (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Erick Banks commented on  PUP-6545 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Ruby 2.3 fails spec tests on Appveyor in Windows  
 
 
 
 
 
 
 
 
 
 
Latest commit passes on Appveyor for Ruby 2.3 https://ci.appveyor.com/project/puppetlabs/puppet/build/4.1.0.3152/job/phm3719au7crdc7d 
And Ruby 2.1 https://ci.appveyor.com/project/puppetlabs/puppet/build/4.1.0.3152/job/bf049asnpxahd8nm 
Closing the 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-6483) "puppet resource user", when run in Windows creates a login attempt.

2016-08-03 Thread Rob Reynolds (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Reynolds commented on  PUP-6483 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "puppet resource user", when run in Windows creates a login attempt.   
 
 
 
 
 
 
 
 
 
 
Merged into stable at https://github.com/puppetlabs/puppet/commit/70426ea1effce8aaa545db911c3f340c09c25f56 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (HI-528) Remove json_pure dependency

2016-08-03 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-528 
 
 
 
  Remove json_pure dependency  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Story Points:
 
 1 
 
 
 

Release Notes Summary:
 
 Hiera 3.2.x does not support Rubies < 1.9.3. The dependencies on 'json' and 'json_pure' has therefore been dropped from hiera's gemspec to make it easier to consume hiera as a gem. 
 
 
 

Sprint:
 
 Language 2016-08-10 (3rd 1.6.0 
 
 
 

Scrum Team:
 
 Language 
 
 
 

Release Notes:
 
 Bug Fix 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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



Jira (HI-528) Remove json_pure dependency

2016-08-03 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  HI-528 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Remove json_pure dependency  
 
 
 
 
 
 
 
 
 
 
merged to stable at: 98a0d54 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (HI-528) Remove json_pure dependency

2016-08-03 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-528 
 
 
 
  Remove json_pure dependency  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Fix Version/s:
 
 HI 3.2.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-6570) pe_acceptance tests fail in Non-English Windows

2016-08-03 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6570 
 
 
 
  pe_acceptance tests fail in Non-English Windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 

Fix Version/s:
 
 PUP 4.6.x 
 
 
 

Fix Version/s:
 
 PUP 4.6.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-5984) Add ticket for 5.0.0 resolution (never match Big Num/Decimal)

2016-08-03 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-5984 
 
 
 
  Add ticket for 5.0.0 resolution (never match Big Num/Decimal)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Fix Version/s:
 
 PUP 4.6.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-6435) Replace sensitive data marker type with resource metadata after catalog compilation

2016-08-03 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6435 
 
 
 
  Replace sensitive data marker type with resource metadata after catalog compilation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Fix Version/s:
 
 PUP 4.6.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (FACT-1342) Update Facter Acceptance tests for cisco-7

2016-08-03 Thread Stan Duffy (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stan Duffy assigned an issue to Stan Duffy 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1342 
 
 
 
  Update Facter Acceptance tests for cisco-7  
 
 
 
 
 
 
 
 
 

Change By:
 
 Stan Duffy 
 
 
 

Assignee:
 
 Stan Duffy 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (HI-529) literal interpolation function can appear only once

2016-08-03 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  HI-529 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: literal interpolation function can appear only once  
 
 
 
 
 
 
 
 
 
 
See 

PUP-501
 (which PUP-513 is a dup of) for the longer explanation why this is still a problem. Short answer, use %%{::} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6483) "puppet resource user", when run in Windows creates a login attempt.

2016-08-03 Thread Rob Reynolds (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Reynolds assigned an issue to Rob Reynolds 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6483 
 
 
 
  "puppet resource user", when run in Windows creates a login attempt.   
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Reynolds 
 
 
 

Assignee:
 
 Ethan Brown Rob Reynolds 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6182) Application declarations don't properly validate component mappings

2016-08-03 Thread Nick Lewis (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Lewis assigned an issue to Nick Lewis 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6182 
 
 
 
  Application declarations don't properly validate component mappings  
 
 
 
 
 
 
 
 
 

Change By:
 
 Nick Lewis 
 
 
 

Assignee:
 
 Nick Lewis 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (HI-529) literal interpolation function can appear only once

2016-08-03 Thread Remi Ferrand (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Remi Ferrand commented on  HI-529 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: literal interpolation function can appear only once  
 
 
 
 
 
 
 
 
 
 
Of course ... the last possibility I hadn't check seems to be a solution for my very problem: 
 
 
 
 
 
 
/home/puppet/common.yaml 
 
 
 
 
 
 
--- 
 
 
 
 
content: "%%{::}{secret} %%{::}{secret2}"
 
 
 
 
 
 
 
 
 
 
 
 
 
hiera_cli 
 
 
 
 
 
 
$ /opt/puppetlabs/bin/hiera --config /etc/hiera.yaml content 
 
 
 
 
%{secret} %{secret2}
 
 
 
 
 
 
 
works like a charm. 
Question now: is this form just a workaround or the recommended way of doing this ? 
 
 
 
 
 
 
 
 
 
 
 
 

 

Jira (HI-529) literal interpolation function can appear only once

2016-08-03 Thread Remi Ferrand (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Remi Ferrand updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-529 
 
 
 
  literal interpolation function can appear only once  
 
 
 
 
 
 
 
 
 

Change By:
 
 Remi Ferrand 
 
 
 
 
 
 
 
 
 
 Like described in [HI-501|https://tickets.puppetlabs.com/browse/HI-501] or [HI-513|https://tickets.puppetlabs.com/browse/HI-513], we just can't resolve hiera data that is using multiple {{literal('%')}}.Exact same issue that in [HI-513|https://tickets.puppetlabs.com/browse/HI-513]:{code:title=/etc/hiera.yaml}---:backends:  - yaml:hierarchy:  - common:yaml:  :datadir: /home/puppet{code}{code:title=/home/puppet/common.yaml}---content: "%{literal('%')}{secret} %{literal('%')}{secret2}"{code}{code:title=hiera_cli}$ /opt/puppetlabs/bin/hiera --config /etc/hiera.yaml content/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/recursive_guard.rb:13:in `check': Lookup recursion detected in [literal('%')] (Hiera::InterpolationLoop)from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/interpolate.rb:68:in `do_interpolation'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/interpolate.rb:47:in `block in interpolate'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/interpolate.rb:46:in `gsub'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/interpolate.rb:46:in `interpolate'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend.rb:142:in `parse_string'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend.rb:153:in `parse_answer'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend/yaml_backend.rb:37:in `block in lookup'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend.rb:120:in `block in datasourcefiles'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend.rb:92:in `block in datasources'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend.rb:90:in `map'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend.rb:90:in `datasources'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend.rb:115:in `datasourcefiles'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend/yaml_backend.rb:17:in `lookup'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend.rb:270:in `block (2 levels) in lookup'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend.rb:268:in `catch'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend.rb:268:in `block in lookup'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend.rb:263:in `each'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend.rb:263:in `lookup'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera.rb:116:in `lookup'from /opt/puppetlabs/bin/hiera:246:in `'{code}I obtain the exact same error as in the quoted ticket with the latest available version of hiera.I can see that [HI-513|https://tickets.puppetlabs.com/browse/HI-513] as been closed but can't figure out how to solve my problem.This is currently a problem for me as I'm curently retrieving  some  something like  { { code} %{REMOTE_USER} {code } } for my  Apache  things  configuration stored  in Hiera.   If there is a quick workaround, please let me know. 
 
 
   

Jira (PUP-6570) pe_acceptance tests fail in Non-English Windows

2016-08-03 Thread Moses Mendoza (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza commented on  PUP-6570 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: pe_acceptance tests fail in Non-English Windows  
 
 
 
 
 
 
 
 
 
 
merged to puppet/master at https://github.com/puppetlabs/puppet/commit/3e60ca0b9c4dce51ac56d824b9706f9898735c88 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (HI-529) literal interpolation function can appear only once

2016-08-03 Thread Remi Ferrand (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Remi Ferrand updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-529 
 
 
 
  literal interpolation function can appear only once  
 
 
 
 
 
 
 
 
 

Change By:
 
 Remi Ferrand 
 
 
 
 
 
 
 
 
 
 Like described in [HI-501|https://tickets.puppetlabs.com/browse/HI-501] or [HI-513|https://tickets.puppetlabs.com/browse/HI-513], we just can't resolve hiera data that is using multiple {{ literal('%') }}.Exact same issue that in [HI-513|https://tickets.puppetlabs.com/browse/HI-513]:{code:title=/etc/hiera.yaml}---:backends:  - yaml:hierarchy:  - common:yaml:  :datadir: /home/puppet{code}{code:title=/home/puppet/common.yaml}---content: "%{literal('%')}{secret} %{literal('%')}{secret2}"{code}{code:title=hiera_cli}$ /opt/puppetlabs/bin/hiera --config /etc/hiera.yaml content/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/recursive_guard.rb:13:in `check': Lookup recursion detected in [literal('%')] (Hiera::InterpolationLoop)from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/interpolate.rb:68:in `do_interpolation'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/interpolate.rb:47:in `block in interpolate'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/interpolate.rb:46:in `gsub'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/interpolate.rb:46:in `interpolate'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend.rb:142:in `parse_string'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend.rb:153:in `parse_answer'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend/yaml_backend.rb:37:in `block in lookup'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend.rb:120:in `block in datasourcefiles'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend.rb:92:in `block in datasources'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend.rb:90:in `map'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend.rb:90:in `datasources'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend.rb:115:in `datasourcefiles'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend/yaml_backend.rb:17:in `lookup'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend.rb:270:in `block (2 levels) in lookup'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend.rb:268:in `catch'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend.rb:268:in `block in lookup'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend.rb:263:in `each'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera/backend.rb:263:in `lookup'from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/hiera.rb:116:in `lookup'from /opt/puppetlabs/bin/hiera:246:in `'{code}I obtain the exact same error as in the quoted ticket with the latest available version of hiera.I can see that [HI-513|https://tickets.puppetlabs.com/browse/HI-513] as been closed but can't figure out how to solve my problem.This is currently a problem for me as I'm curently retrieving some {{ %{REMOTE_USER} }} Apache things in Hiera. If there is a quick workaround, please let me know. 
 
 
 
 
   

Jira (HI-529) literal interpolation function can appear only once

2016-08-03 Thread Remi Ferrand (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Remi Ferrand created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-529 
 
 
 
  literal interpolation function can appear only once  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 HI 3.2.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Community 
 
 
 

Created:
 

 2016/08/03 1:13 PM 
 
 
 

Environment:
 
 
Fresh new install of PuppetServer on freshly installed CentOS 7.2 server: 
 

puppetserver-2.4.0-1.el7.noarch
 

puppetdb-termini-4.1.2-1.el7.noarch
 

puppet-agent-1.5.3-1.el7.x86_64
 
 
Hiera version: 3.2.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Remi Ferrand 
 
 
 
 
 
 
 
 
 
 
   

Jira (PUP-5938) windows, user to groupassign to local administrators failed

2016-08-03 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-5938 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: windows, user to groupassign to local administrators failed  
 
 
 
 
 
 
 
 
 
 
Merged up to master 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-5938) windows, user to groupassign to local administrators failed

2016-08-03 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-5938 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: windows, user to groupassign to local administrators failed  
 
 
 
 
 
 
 
 
 
 
Additional PR merged into stable at; https://github.com/puppetlabs/puppet/commit/6935e9c78ba4e7ee2b307914d8154b646c3ee5e9 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6397) File autorequire in Mount causes dependency loops

2016-08-03 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley commented on  PUP-6397 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: File autorequire in Mount causes dependency loops  
 
 
 
 
 
 
 
 
 
 
That sounds perfect. 
Thanks for understanding, and especially thank you for being willing to take on the work.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6575) Disambiguate puppet agent -t and puppet apply -t with quick feedback

2016-08-03 Thread Jeremy Adams (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jeremy Adams commented on  PUP-6575 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Disambiguate puppet agent -t and puppet apply -t with quick feedback  
 
 
 
 
 
 
 
 
 
 
+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-6397) File autorequire in Mount causes dependency loops

2016-08-03 Thread Matt Schuchard (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matt Schuchard commented on  PUP-6397 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: File autorequire in Mount causes dependency loops  
 
 
 
 
 
 
 
 
 
 
Thank you for the background info Branan. 
The autorequire part is not necessary for us and the autobefore is. That issue Mikhail brought up is, to me, much more alarming than the issues raised by Paul and Thomas. Part 3 of the proposal deals with it and can be considered a bugfix. While what Mikhail raised is not affecting myself or my company personally, I want to fix that because it bothers me out of personal responsibility and integrity. 
So I agree completely that 1 is the most palatable. What if we made changes 1 and 3 in my proposal for 4.6.1 (they are bugfixes), and then changes 2 and possibly 4 (depending upon feedback) for 4.7.0 (they are a new feature and improvement respectively)? 
I can start on 1 and 3 for 4.6.1 tomorrow morning. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6483) "puppet resource user", when run in Windows creates a login attempt.

2016-08-03 Thread Moses Mendoza (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza commented on  PUP-6483 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "puppet resource user", when run in Windows creates a login attempt.   
 
 
 
 
 
 
 
 
 
 
hi Kenn Hussey - yes, that is the current plan  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6575) Disambiguate puppet agent -t and puppet apply -t with quick feedback

2016-08-03 Thread Paul Anderson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Anderson commented on  PUP-6575 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Disambiguate puppet agent -t and puppet apply -t with quick feedback  
 
 
 
 
 
 
 
 
 
 
And of course, the classic fundamentals use of puppet apply -t should work, too: 
root@solaris11:/shared# /usr/local/bin/puppet apply -t hello.pp Info: Loading facts Info: Loading facts Info: Loading facts Notice: Compiled catalog for solaris11.puppetlabs.vm in environment production in 0.04 seconds Info: Applying configuration version '1470249265' Notice: hello Notice: /Stage[main]/Main/Notify[hello]/message: defined 'message' as 'hello' Notice: Applied catalog in 0.05 seconds 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6575) Disambiguate puppet agent -t and puppet apply -t with quick feedback

2016-08-03 Thread Paul Anderson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Anderson commented on  PUP-6575 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Disambiguate puppet agent -t and puppet apply -t with quick feedback  
 
 
 
 
 
 
 
 
 
 
This is another valid use case that shouldn't be broken by this new feature: 
root@solaris11:/shared# /usr/local/bin/puppet apply -t notify  { "hello": } 
 Info: Loading facts Info: Loading facts Info: Loading facts Notice: Compiled catalog for solaris11.puppetlabs.vm in environment production in 0.04 seconds Info: Applying configuration version '1470249167' Notice: hello Notice: /Stage[main]/Main/Notify[hello]/message: defined 'message' as 'hello' Notice: Applied catalog in 0.05 seconds 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6575) Disambiguate puppet agent -t and puppet apply -t with quick feedback

2016-08-03 Thread Paul Anderson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Anderson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6575 
 
 
 
  Disambiguate puppet agent -t and puppet apply -t with quick feedback  
 
 
 
 
 
 
 
 
 

Change By:
 
 Paul Anderson 
 
 
 
 
 
 
 
 
 
 Both new and experienced users alike will accidentally type "puppet apply -t" when they mean to do a puppet run (puppet agent -t)puppet apply -t is a valid use case, and should not be changed as it could affect those using masterless puppet. If the client were to detect that puppet apply -t was run, no file argument was given, no input has been fed on standard in and that it was waiting for input, it could print an informational message, such as:" INFO Info :  puppet  Puppet  apply ready for input on stdin"Then it would prevent confusion as people wait 2.. 5... 10... seconds (or going for coffee) before thinking that puppet has hung, hitting CTRL-C to break, running "puppet agent -t" like they meant to and kicking themselves for making this mistake AGAIN... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6575) Disambiguate puppet agent -t and puppet apply -t with quick feedback

2016-08-03 Thread Paul Anderson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Anderson commented on  PUP-6575 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Disambiguate puppet agent -t and puppet apply -t with quick feedback  
 
 
 
 
 
 
 
 
 
 
This use case is valid and shouldn't be broken by this new feature. 
root@solaris11:/shared# /usr/local/bin/puppet apply -t < hello.pp Info: Loading facts Info: Loading facts Info: Loading facts Notice: Compiled catalog for solaris11.puppetlabs.vm in environment production in 0.05 seconds Info: Applying configuration version '1470249024' Notice: hello Notice: /Stage[main]/Main/Notify[hello]/message: defined 'message' as 'hello' Notice: Applied catalog in 0.04 seconds 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6575) Disambiguate puppet agent -t and puppet apply -t with quick feedback

2016-08-03 Thread Paul Anderson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Anderson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6575 
 
 
 
  Disambiguate puppet agent -t and puppet apply -t with quick feedback  
 
 
 
 
 
 
 
 
 

Change By:
 
 Paul Anderson 
 
 
 
 
 
 
 
 
 
 Both new and experienced users alike will accidentally type "puppet apply -t" when they mean to do a puppet run (puppet agent -t)puppet apply -t is a valid use case, and should not be  removed, but if  changed as it could affect those using masterless puppet. If  the client were to detect that puppet apply -t was run, no  file argument was given, no  input has been fed on standard in and that it was waiting for input, it could print an informational message, such as:"INFO: puppet apply ready for input on stdin"Then it would prevent confusion as people wait 2.. 5... 10... seconds  (or going for coffee) before  thinking that puppet has hung  before realizing the issue ,  hitting CTRL-C to break , running "puppet agent -t" like they meant to and kicking themselves for making this mistake AGAIN . .. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6397) File autorequire in Mount causes dependency loops

2016-08-03 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley commented on  PUP-6397 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: File autorequire in Mount causes dependency loops  
 
 
 
 
 
 
 
 
 
 
Matt Schuchard David is taking over managerial responsibilities for our team from Kylo. I was in the room when we decided to revert this, as was Eric Sorenson 
To be clear, I think we only need to revert the autorequire portion of 

PUP-6099
. The autobefore portion can stay as-is. 
For some context, we've frozen Puppet 4.6.0 at this point. I would call your proposal a Y-release new feature, rather than a Z-release bugfix. That means it would have to wait for 4.7, which is probably about a quarter out if our release cadence doesn't change. 
That leaves us with a few super shitty options: 
1) Remove the autorequire as a bugfix in 4.6.1, since it broke users, and get the new plan out in 4.7.0 2) Push your changes in 4.6.1, as a "bugfix" to this feature 3) Let it all sit until 4.7.0 
None of these are great. Number 2 is playing games with semver, which I don't like. 3 is pretty obviously the worst overall 
Of these, 1 is the most palatable to me. /somebody/ is going to suffer no matter what we do here, and I tend to err on the side of "Pull out something that broke users, and get the correct solution in ASAP after that". In this case "ASAP" is likely 4.7.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-6575) Disambiguate puppet agent -t and puppet apply -t with quick feedback

2016-08-03 Thread Paul Anderson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Anderson updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6575 
 
 
 
  Disambiguate puppet agent -t and puppet apply -t with quick feedback  
 
 
 
 
 
 
 
 
 

Change By:
 
 Paul Anderson 
 
 
 

Summary:
 
 Disambiguate puppet agent -t and puppet apply -t  with quick feedback 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6575) Disambiguate puppet agent -t and puppet apply -t

2016-08-03 Thread Paul Anderson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Anderson created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6575 
 
 
 
  Disambiguate puppet agent -t and puppet apply -t  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Affects Versions:
 

 PUP 4.5.3 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Components:
 

 Client 
 
 
 

Created:
 

 2016/08/03 11:25 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Paul Anderson 
 
 
 
 
 
 
 
 
 
 
Both new and experienced users alike will accidentally type "puppet apply -t" when they mean to do a puppet run (puppet agent -t) 
puppet apply -t is a valid use case, and should not be removed, but if the client were to detect that puppet apply -t was run, no input has been fed on standard in and that it was waiting for input, it could print an informational message, such as: 
"INFO: puppet apply ready for input on stdin" 
Then it would prevent confusion as people wait 2.. 5... 10... seconds thinking that puppet has hung before realizing the issue hitting CTRL-C to break. 
 
 
 
 
 
 
 
 
 
 
 
   

Jira (PUP-6397) File autorequire in Mount causes dependency loops

2016-08-03 Thread Matt Schuchard (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matt Schuchard commented on  PUP-6397 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: File autorequire in Mount causes dependency loops  
 
 
 
 
 
 
 
 
 
 
I appreciate it David. Sorry if I seem testy about this, and I am trying not to be, but this is a major need for us and something I had to spend a while working on because I was ambitious by trying to forge into new Puppet territory with auto-require/before spec tests. 
I don't understand the internal process you guys use, so maybe my 'why can't someone just look over my proposal and make suggestions as necessary before I work it' is overly simplified. 
As soon as someone provides feedback I can go after this and it should just be quick to bang out. What might take longer is constructing the spec test for what Mikhail mentioned. 
Also, I need to go update the proposal a little based on something Paul Anderson said. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6397) File autorequire in Mount causes dependency loops

2016-08-03 Thread David Kramer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Kramer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6397 
 
 
 
  File autorequire in Mount causes dependency loops  
 
 
 
 
 
 
 
 
 

Change By:
 
 David Kramer 
 
 
 

Story Points:
 
 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-6397) File autorequire in Mount causes dependency loops

2016-08-03 Thread David Kramer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Kramer commented on  PUP-6397 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: File autorequire in Mount causes dependency loops  
 
 
 
 
 
 
 
 
 
 
Thanks for the feedback, Matt. I'm going to pull this back into the Client Triage sprint until the team has a chance to discuss this further. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6397) File autorequire in Mount causes dependency loops

2016-08-03 Thread David Kramer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Kramer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6397 
 
 
 
  File autorequire in Mount causes dependency loops  
 
 
 
 
 
 
 
 
 

Change By:
 
 David Kramer 
 
 
 

Sprint:
 
 Client  2016-08-24  Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6570) pe_acceptance tests fail in Non-English Windows

2016-08-03 Thread Glenn Sarti (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Glenn Sarti commented on  PUP-6570 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: pe_acceptance tests fail in Non-English Windows  
 
 
 
 
 
 
 
 
 
 
CI started https://jenkins.puppetlabs.com/job/platform_puppet_init-van-component_master/388/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6411) Puppet 3.x fails acceptance on Ubuntu precise

2016-08-03 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith commented on  PUP-6411 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet 3.x fails acceptance on Ubuntu precise  
 
 
 
 
 
 
 
 
 
 
This appears to have been fixed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6549) Acceptance: systemd_enabling_masked_service test failing for Fedora 23 i386

2016-08-03 Thread Geoff Nichols (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Geoff Nichols updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6549 
 
 
 
  Acceptance: systemd_enabling_masked_service test failing for Fedora 23 i386  
 
 
 
 
 
 
 
 
 

Change By:
 
 Geoff Nichols 
 
 
 

Sprint:
 
 RE Platforms 2016-07-27, RE Platforms 2016-08-03 , RE Platforms 2016-08-10 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (HI-528) Remove json_pure dependency

2016-08-03 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-528 
 
 
 
  Remove json_pure dependency  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/08/03 9:59 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Kylo Ginsberg 
 
 
 
 
 
 
 
 
 
 
json_pure was added as a dependency to hiera to enable easier development with ruby 1.8.7 (which doesn't include a json implementation). With hiera now supporting only ruby 1.9.3+, the dependency is no longer needed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

Jira (PUP-6552) Regression: Redhat / Debian / Ubuntu can't specify 'init' provider

2016-08-03 Thread David Kramer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Kramer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6552 
 
 
 
  Regression: Redhat / Debian / Ubuntu can't specify 'init' provider  
 
 
 
 
 
 
 
 
 

Change By:
 
 David Kramer 
 
 
 

Sprint:
 
 Client  Triage  2016-08-24 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6552) Regression: Redhat / Debian / Ubuntu can't specify 'init' provider

2016-08-03 Thread David Kramer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Kramer commented on  PUP-6552 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Regression: Redhat / Debian / Ubuntu can't specify 'init' provider  
 
 
 
 
 
 
 
 
 
 
This needs to be fixed properly. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6552) Regression: Redhat / Debian / Ubuntu can't specify 'init' provider

2016-08-03 Thread David Kramer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Kramer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6552 
 
 
 
  Regression: Redhat / Debian / Ubuntu can't specify 'init' provider  
 
 
 
 
 
 
 
 
 

Change By:
 
 David Kramer 
 
 
 

Story Points:
 
 3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6397) File autorequire in Mount causes dependency loops

2016-08-03 Thread Matt Schuchard (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matt Schuchard commented on  PUP-6397 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: File autorequire in Mount causes dependency loops  
 
 
 
 
 
 
 
 
 
 
No David, 

PUP-6099
 cannot be rolled back. Please get with our TAM (Elizabeth) on the business need for it if you need to. Please consider taking the proper route on this, especially because I am really going to be the one putting in the effort. It would be good for the quality of Puppet as a software product if we put in the effort to improve it instead of just ignoring issues. Please get someone (Kylo, Josh, Branan, etc.) to review the proposal so we can do the right thing here. Thanks. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6478) "Unable to set ownership" error with logdest on agents

2016-08-03 Thread David Kramer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Kramer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6478 
 
 
 
  "Unable to set ownership" error with logdest on agents  
 
 
 
 
 
 
 
 
 

Change By:
 
 David Kramer 
 
 
 

Sprint:
 
 Client  Triage  2016-08-24 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6478) "Unable to set ownership" error with logdest on agents

2016-08-03 Thread David Kramer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Kramer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6478 
 
 
 
  "Unable to set ownership" error with logdest on agents  
 
 
 
 
 
 
 
 
 

Change By:
 
 David Kramer 
 
 
 

Story Points:
 
 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-6478) "Unable to set ownership" error with logdest on agents

2016-08-03 Thread David Kramer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Kramer commented on  PUP-6478 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "Unable to set ownership" error with logdest on agents  
 
 
 
 
 
 
 
 
 
 
We should check to make sure the user exists before attempting to set the ownership. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6413) Pip provider fails when using ensure => latest

2016-08-03 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6413 
 
 
 
  Pip provider fails when using ensure => latest  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Sprint:
 
 Client 2016-06-29 , Client 2016-08-10 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6397) File autorequire in Mount causes dependency loops

2016-08-03 Thread David Kramer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Kramer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6397 
 
 
 
  File autorequire in Mount causes dependency loops  
 
 
 
 
 
 
 
 
 

Change By:
 
 David Kramer 
 
 
 

Sprint:
 
 Client  Triage  2016-08-24 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6397) File autorequire in Mount causes dependency loops

2016-08-03 Thread David Kramer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Kramer commented on  PUP-6397 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: File autorequire in Mount causes dependency loops  
 
 
 
 
 
 
 
 
 
 
We're going to rollback 

PUP-6099
 as a short term solution, and add documentation to the mount type about this issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6397) File autorequire in Mount causes dependency loops

2016-08-03 Thread David Kramer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Kramer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6397 
 
 
 
  File autorequire in Mount causes dependency loops  
 
 
 
 
 
 
 
 
 

Change By:
 
 David Kramer 
 
 
 

Story Points:
 
 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-6216) Puppet agent run is not clearing USER environment variable on VIO AIX

2016-08-03 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley commented on  PUP-6216 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet agent run is not clearing USER environment variable on VIO AIX  
 
 
 
 
 
 
 
 
 
 
This might be a wontfix. 
We intentionally don't clear USER when we sanitize environment variables, as a user might set that intending for it to affect Puppet's behavior. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6381) Cumulus Linux 3.0 default service provider should be systemd

2016-08-03 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6381 
 
 
 
  Cumulus Linux 3.0 default service provider should be systemd  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Risk Assessment:
 
 Low 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (FACT-1432) Fixup OpenBSD networking facts

2016-08-03 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley assigned an issue to Branan Riley 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1432 
 
 
 
  Fixup OpenBSD networking facts  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Assignee:
 
 Branan Riley 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6357) Puppet resource runs appear to be getting slower over time

2016-08-03 Thread David Kramer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Kramer commented on  PUP-6357 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Puppet resource runs appear to be getting slower over time  
 
 
 
 
 
 
 
 
 
 
Adam Bottchen Can you provide us with more details about this use case and the impact it is having on the user? Thanks. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6381) Cumulus Linux 3.0 default service provider should be systemd

2016-08-03 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6381 
 
 
 
  Cumulus Linux 3.0 default service provider should be systemd  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-6381) Cumulus Linux 3.0 default service provider should be systemd

2016-08-03 Thread David Kramer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Kramer assigned an issue to Stan Duffy 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
No further action is needed on this ticket. 
 
 
 
 
 
 
 
 
 
 Puppet /  PUP-6381 
 
 
 
  Cumulus Linux 3.0 default service provider should be systemd  
 
 
 
 
 
 
 
 
 

Change By:
 
 David Kramer 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Assignee:
 
 Stan Duffy 
 
 
 

Status:
 
 Ready for Test Resolved 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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

Jira (PUP-6381) Cumulus Linux 3.0 default service provider should be systemd

2016-08-03 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6381 
 
 
 
  Cumulus Linux 3.0 default service provider should be systemd  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Assignee:
 
 Stan Duffy 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6381) Cumulus Linux 3.0 default service provider should be systemd

2016-08-03 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6381 
 
 
 
  Cumulus Linux 3.0 default service provider should be systemd  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Fix Version/s:
 
 PUP 4.6.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-6381) Cumulus Linux 3.0 default service provider should be systemd

2016-08-03 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley assigned an issue to Stan Duffy 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6381 
 
 
 
  Cumulus Linux 3.0 default service provider should be systemd  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Assignee:
 
 qa Stan Duffy 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6369) Add new noop_status field to puppet report

2016-08-03 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6369 
 
 
 
  Add new noop_status field to puppet report  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-6369) Add new noop_status field to puppet report

2016-08-03 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6369 
 
 
 
  Add new noop_status field to puppet report  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Risk Assessment:
 
 Low 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-6369) Add new noop_status field to puppet report

2016-08-03 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6369 
 
 
 
  Add new noop_status field to puppet report  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Fix Version/s:
 
 PUP 4.6.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (FACT-1434) Recognize "wxallowed" as mount option

2016-08-03 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley assigned an issue to Branan Riley 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1434 
 
 
 
  Recognize "wxallowed" as mount option  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Assignee:
 
 Branan Riley 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6357) Puppet resource runs appear to be getting slower over time

2016-08-03 Thread David Kramer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Kramer assigned an issue to Adam Bottchen 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6357 
 
 
 
  Puppet resource runs appear to be getting slower over time  
 
 
 
 
 
 
 
 
 

Change By:
 
 David Kramer 
 
 
 

Assignee:
 
 David Kramer Adam Bottchen 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6357) Puppet resource runs appear to be getting slower over time

2016-08-03 Thread David Kramer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Kramer assigned an issue to David Kramer 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6357 
 
 
 
  Puppet resource runs appear to be getting slower over time  
 
 
 
 
 
 
 
 
 

Change By:
 
 David Kramer 
 
 
 

Assignee:
 
 David Kramer 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (FACT-1428) FreeBSD facts are missing from Facter 3.X onwards

2016-08-03 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley assigned an issue to Branan Riley 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1428 
 
 
 
  FreeBSD facts are missing from Facter 3.X onwards  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Assignee:
 
 Branan Riley 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1339) swap fact on OpenBSD

2016-08-03 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley assigned an issue to Branan Riley 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1339 
 
 
 
  swap fact on OpenBSD  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Assignee:
 
 Branan Riley 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1367) Facter2 detects VirtuozzoLinux as RedHat

2016-08-03 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley assigned an issue to Branan Riley 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1367 
 
 
 
  Facter2 detects VirtuozzoLinux as RedHat  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Assignee:
 
 Branan Riley 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3182) puppet catalog download fails

2016-08-03 Thread David Kramer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Kramer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-3182 
 
 
 
  puppet catalog download fails  
 
 
 
 
 
 
 
 
 

Change By:
 
 David Kramer 
 
 
 

Sprint:
 
 Client  Triage  2016-08-24 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6381) Cumulus Linux 3.0 default service provider should be systemd

2016-08-03 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6381 
 
 
 
  Cumulus Linux 3.0 default service provider should be systemd  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Sprint:
 
 Client Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1356) External facts should be able to return structured data

2016-08-03 Thread David Kramer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Kramer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1356 
 
 
 
  External facts should be able to return structured data  
 
 
 
 
 
 
 
 
 

Change By:
 
 David Kramer 
 
 
 

Sprint:
 
 Client  Triage  2016-08-24 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1432) Fixup OpenBSD networking facts

2016-08-03 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1432 
 
 
 
  Fixup OpenBSD networking facts  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Sprint:
 
 Client Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1356) External facts should be able to return structured data

2016-08-03 Thread David Kramer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Kramer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1356 
 
 
 
  External facts should be able to return structured data  
 
 
 
 
 
 
 
 
 

Change By:
 
 David Kramer 
 
 
 

Story Points:
 
 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 (FACT-1356) External facts should be able to return structured data

2016-08-03 Thread David Kramer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Kramer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1356 
 
 
 
  External facts should be able to return structured data  
 
 
 
 
 
 
 
 
 

Change By:
 
 David Kramer 
 
 
 

Fix Version/s:
 
 FACT 3.y 
 
 
 

Fix Version/s:
 
 FACT 3.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 (FACT-1434) Recognize "wxallowed" as mount option

2016-08-03 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1434 
 
 
 
  Recognize "wxallowed" as mount option  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (FACT-1434) Recognize "wxallowed" as mount option

2016-08-03 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1434 
 
 
 
  Recognize "wxallowed" as mount option  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Risk Assessment:
 
 Low 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


Jira (PUP-6369) Add new noop_status field to puppet report

2016-08-03 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6369 
 
 
 
  Add new noop_status field to puppet report  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Sprint:
 
 Client Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1434) Recognize "wxallowed" as mount option

2016-08-03 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1434 
 
 
 
  Recognize "wxallowed" as mount option  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Sprint:
 
 Client Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-6570) pe_acceptance tests fail in Non-English Windows

2016-08-03 Thread Moses Mendoza (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Moses Mendoza updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-6570 
 
 
 
  pe_acceptance tests fail in Non-English Windows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Moses Mendoza 
 
 
 

Fix Version/s:
 
 PUP 4.6.0 
 
 
 

Fix Version/s:
 
 PUP 4.6.x 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-348) Facter should provide a convenient way to cache values

2016-08-03 Thread David Kramer (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Kramer updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-348 
 
 
 
  Facter should provide a convenient way to cache values  
 
 
 
 
 
 
 
 
 

Change By:
 
 David Kramer 
 
 
 

Story Points:
 
 3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-1428) FreeBSD facts are missing from Facter 3.X onwards

2016-08-03 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1428 
 
 
 
  FreeBSD facts are missing from Facter 3.X onwards  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

Sprint:
 
 Client Triage 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-718) Allow for disabling certain facts within Facter

2016-08-03 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-718 
 
 
 
  Allow for disabling certain facts within Facter  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Fix Version/s:
 
 FACT 3.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 (FACT-1428) FreeBSD facts are missing from Facter 3.X onwards

2016-08-03 Thread John Duarte (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 John Duarte updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1428 
 
 
 
  FreeBSD facts are missing from Facter 3.X onwards  
 
 
 
 
 
 
 
 
 

Change By:
 
 John Duarte 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





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


  1   2   >