Jira (PUP-4811) Filebucket tries to backup in local environment when set for remote

2015-07-20 Thread Benjamin Merot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Benjamin Merot commented on  PUP-4811 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Filebucket tries to backup in local environment when set for remote  
 
 
 
 
 
 
 
 
 
 
My setup of Filebucket and Main is similar in each of my environments' 'site.pp' which also contains node classification and resources created correctly.. However to try en reproduce the case you need to use environments and try to replace a file resource for a node assigned in another environment than production. In my case that will clearly show that the Puppet agent will attempt to backup to a local folder. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-112) Provide means to request events from latest report in timeframe

2015-07-20 Thread Scott Walker (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Scott Walker commented on  PDB-112 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Provide means to request events from latest report in timeframe  
 
 
 
 
 
 
 
 
 
 
Joseph Wagner Beth Cornils Verne Lindner Wyatt Alt Pinging half the world here just to make sure our expectations are aligned. This ticket directly affects how Events works in config management. 
I'd figured that filtering by latest report gives us better usability for the reasons discussed about and as a side effect reduces the usefulness of filtering by time. It makes sense to do both: first filter to get only events from a latest report, then filter by a time period. That works a lot better for a 5 min interval than a really long one. You'd also expect to see fairly minimal differences between 1 hour and 12 hours in most systems though, as you'd expect nearly all nodes to have reported within the last hour. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4901) puppet-splunk doesn't update spunk

2015-07-20 Thread Kyle Decot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kyle Decot created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4901 
 
 
 
  puppet-splunk doesn't update spunk  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/07/20 6:08 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Kyle Decot 
 
 
 
 
 
 
 
 
 
 
When using the official splunk module it installs perfectly the first time. However when updating the version numbers and rerunning puppet the package doesn't actually get updated. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 

Jira (PUP-4819) Add service for obtaining class information per environment

2015-07-20 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-4819 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Add service for obtaining class information per environment  
 
 
 
 
 
 
 
 
 
 
For Functional Review: This can not be tested manually from the command line since it is only an API. It should be possible to manually test via IRB if desired (see spec tests for required set up). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4896) puppet parser validate ruby errors

2015-07-20 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Anirudh Srinivasan 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4896 
 
 
 
  puppet parser validate ruby errors  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 AnirudhSrinivasan 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4896) puppet parser validate ruby errors

2015-07-20 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-4896 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: puppet parser validate ruby errors  
 
 
 
 
 
 
 
 
 
 
Is this a regressions? Did that module work with 3.8.0? (Or an earlier version in the 3.x series?). Is there a difference if future parser is used or not? Does the module author claim it works with 3.x? etc.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1815) PuppetDB DDL not supported when using PostgreSQL with BDR

2015-07-20 Thread Taylan Develioglu (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Taylan Develioglu created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1815 
 
 
 
  PuppetDB DDL not supported when using PostgreSQL with BDR  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 PDB 2.3.6 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/07/20 7:37 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Taylan Develioglu 
 
 
 
 
 
 
 
 
 
 
When using PostgreSQL with bi-directional replication, some of the ddl statements PuppetDB uses to bring its schema up to date are not supported. 
Trying to bring the schema up to date from scratch results in the following error from PostgreSQL (bdr 0.9.1 on postgresql 9.4.2): 
ERROR: ALTER TABLE ... ALTER COLUMN TYPE may only affect UNLOGGED or TEMPORARY tables when BDR is active; reports is a regular table_ 
There are probably more, but this is the first one that we hit. 
According to the bdr documentation 'alter table .. alter column type' is prohibited, see http://bdr-project.org/docs/0.9/ddl-replication-statements.html 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add 

Jira (FACT-1127) Too many environment vars on the command line causes overflow

2015-07-20 Thread Rob Reynolds (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Reynolds updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1127 
 
 
 
  Too many environment vars on the command line causes overflow  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Reynolds 
 
 
 

Summary:
 
 Possiblepathtoolongissue Toomanyenvironmentvars on Windows thecommandlinecausesoverflow 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4902) routes.yaml should allow an alias for terminus, with the rename to termini

2015-07-20 Thread Matthew Thode (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Matthew Thode created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4902 
 
 
 
  routes.yaml should allow an alias for terminus, with the rename to termini  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.2.0 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Puppet Server 
 
 
 

Created:
 

 2015/07/20 6:49 AM 
 
 
 

Labels:
 

 puppet 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Matthew Thode 
 
 
 
 
 
 
 
 
 
 
the default routes.yaml for connecting to puppetdb has the following, I believe that terminus should be allowed to be termini, as that package seems to have been renamed for puppetdb-3. — master: facts: terminus: puppetdb cache: yaml 
 
 
 
 
 
 
 
 
 
 
 
 
   

Jira (PUP-4896) puppet parser validate ruby errors

2015-07-20 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-4896 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: puppet parser validate ruby errors  
 
 
 
 
 
 
 
 
 
 
This looks like a problem in drwahl/puppet-git-hooks - suggest starting by reporting the problem to the author of that module. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-3673) type validation ignores tags when catalog is being converted to RAL format (on Windows)

2015-07-20 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3673 
 
 
 
  type validation ignores tags when catalog is being converted to RAL format (on Windows)  
 
 
 
 
 
 
 
 
 
 
The problem seems specific to Windows (see support ticket). 
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Scrum Team:
 
 Windows 
 
 
 

Summary:
 
 typevalidationignorestagswhencatalogisbeingconvertedtoRALformat (onWindows) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4887) Reserved words as hash keys?

2015-07-20 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-4887 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Reserved words as hash keys?  
 
 
 
 
 
 
 
 
 
 
It is not a bug. You cannot use bare word keywords as hash-keys since they can be any _expression_. If you want a keyword use a quoted string. 
 
 
 
 
 
 
$hsh = { 'if' = 'the pope has a funny hat' }
 
 
 
 
 
 
 
This because you can write: 
 
 
 
 
 
 
$funny_hat_people = [pope, santa, 'steve martin', 'the grinch'] 
 
 
 
 
$person = 'pope' 
 
 
 
 
$hsh = { if $person in $funny_hat_people { 'funny' } else {'not funny'} = true } 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
  

Jira (PUP-4904) puppet describe -s ssh_authorized_key output is really bad

2015-07-20 Thread Ben Ford (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ben Ford created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4904 
 
 
 
  puppet describe -s ssh_authorized_key output is really bad  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 4.2.0, PUP 3.8.1 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/07/20 10:00 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Ben Ford 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
root@master:~ # puppet describe -s ssh_authorized_key 
 
 
 
 
 
 
 
 
 
ssh_authorized_key 
 
 
 
 
== 
 
  

Jira (PUP-4622) Add a diff command in Puppet filebucket

2015-07-20 Thread Peter Huene (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4622 
 
 
 
  Add a diff command in Puppet filebucket  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Huene 
 
 
 

Fix Version/s:
 
 PUP4.3.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4622) Add a diff command in Puppet filebucket

2015-07-20 Thread Peter Huene (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4622 
 
 
 
  Add a diff command in Puppet filebucket  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Huene 
 
 
 

Affects Version/s:
 
 PUP4.2.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4622) Add a diff command in Puppet filebucket

2015-07-20 Thread Peter Huene (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene commented on  PUP-4622 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Add a diff command in Puppet filebucket  
 
 
 
 
 
 
 
 
 
 
Note for functional review: 
This adds a new puppet filebucket diff command that takes two arguments, either one can be a file on disk or a filebucket hash. The output of the command is a diff of the two together. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1816) PR (68): (maint) Update sync tests for export refactors in FOSS - ajroetker

2015-07-20 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1816 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (68): (maint) Update sync tests for export refactors in FOSS - ajroetker  
 
 
 
 
 
 
 
 
 
 
rbrw commented: 
Looks pretty good to me, though I might be tempted to wrap some of the long lines that are being changed. And (very minor), wondered about using ns/query instead of just query (since it's pretty generic), but not sure either way. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1816) PR (68): (maint) Update sync tests for export refactors in FOSS - ajroetker

2015-07-20 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1816 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (68): (maint) Update sync tests for export refactors in FOSS - ajroetker  
 
 
 
 
 
 
 
 
 
 
mullr commented: 
small note, looks good otherwise 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1816) PR (68): (maint) Update sync tests for export refactors in FOSS - ajroetker

2015-07-20 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1816 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (68): (maint) Update sync tests for export refactors in FOSS - ajroetker  
 
 
 
 
 
 
 
 
 
 
ajroetker commented: 
not sure about the wrapping, I'm tempted to leave that in this patch. I did change query to be namespaced @rbrw I agree it's much better  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1816) PR (68): (maint) Update sync tests for export refactors in FOSS - ajroetker

2015-07-20 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1816 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (68): (maint) Update sync tests for export refactors in FOSS - ajroetker  
 
 
 
 
 
 
 
 
 
 
mullr commented: 
yeah, for small patches it seems better to leave line wrapping alone 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4622) Add a diff command in Puppet filebucket

2015-07-20 Thread Peter Huene (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4622 
 
 
 
  Add a diff command in Puppet filebucket  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Huene 
 
 
 

Sprint:
 
 Client2015-08-05 
 
 
 

Scrum Team:
 
 ClientPlatform 
 
 
 

Story Points:
 
 1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-2301) puppet module list --tree output shows dependencies incorrectly

2015-07-20 Thread Anderson Mills (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anderson Mills commented on  PUP-2301 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: puppet module list --tree output shows dependencies incorrectly  
 
 
 
 
 
 
 
 
 
 
John, this has been lower priority than many other PMT issues that have come up. It's still on the active list, but not at the top. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1816) PR (68): (maint) Update sync tests for export refactors in FOSS - ajroetker

2015-07-20 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1816 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (68): (maint) Update sync tests for export refactors in FOSS - ajroetker  
 
 
 
 
 
 
 
 
 
 
ajroetker commented: 
@rbrw @mullr addressed your comments 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1816) PR (68): (maint) Update sync tests for export refactors in FOSS - ajroetker

2015-07-20 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1816 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (68): (maint) Update sync tests for export refactors in FOSS - ajroetker  
 
 
 
 
 
 
 
 
 
 
mullr commented: 
sweet lgtm 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-3328) tidy should follow symlinks

2015-07-20 Thread Hailee Kenney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney assigned an issue to Michael Smith 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3328 
 
 
 
  tidy should follow symlinks  
 
 
 
 
 
 
 
 
 

Change By:
 
 Hailee Kenney 
 
 
 

Assignee:
 
 CosminLehene MichaelSmith 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-3905) Evaluate impact of ruby 2.1.5 automatically retrying idempotent http methods

2015-07-20 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3905 
 
 
 
  Evaluate impact of ruby 2.1.5 automatically retrying idempotent http methods  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Sprint:
 
 Client2015-08-19 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1812) Some tables (value_types at least) are never analyzed

2015-07-20 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1812 
 
 
 
  Some tables (value_types at least) are never analyzed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Browning 
 
 
 

Priority:
 
 Major Normal 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1812) Some tables (value_types at least) are never analyzed

2015-07-20 Thread Rob Browning (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Browning updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1812 
 
 
 
  Some tables (value_types at least) are never analyzed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Browning 
 
 
 

Priority:
 
 Normal Major 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-112) Provide means to request events from latest report in timeframe

2015-07-20 Thread Reid Vandewiele (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Reid Vandewiele commented on  PDB-112 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Provide means to request events from latest report in timeframe  
 
 
 
 
 
 
 
 
 
 
Wyatt Alt Scott Walker as Wyatt said, the ability to specify an endpoint other than the current time is kind of the point. 
The specific Event Inspector (EI) desired use case that originally drove this ticket was trying to achieve a kind of freeze-frame picture of events from the latest report. 
The problem with the existing [=, latest-report?, true] query is that if in EI users pull up a view of events from classes based on that query, spend two or three minutes looking at it and then try to drill in to a specific class, it's possible that relevant nodes will have submitted an updated report in the intervening time and there are no longer any events for that class that match [=, latest-report?, true]. 
The desired user experience is that when users first load EI they are presented with a view of the world as it looked at the time of page load. They should be able to muse over it, navigate around inside it, and expect consistency inside of it, at least until they refresh the browser. 
Right now because EI makes multiple queries back to PuppetDB as the user is navigating around inside of it, to present that consistent freeze-frame of current events it seems like we would need some kind of [=, latest-report-before, 2013-10-30T14:55:00-07:00]'. 
That's the use case that originally drove the ask in the ticket. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1816) PR (68): (maint) Update sync tests for export refactors in FOSS - ajroetker

2015-07-20 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1816 
 
 
 
  PR (68): (maint) Update sync tests for export refactors in FOSS - ajroetker  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/07/20 10:01 AM 
 
 
 

Labels:
 

 github 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
(maint) Update sync tests for export refactors in FOSS 
 

Author: Andrew Roetker 
 

Company: Puppet Labs
 

Github ID: ajroetker
 

Pull Request 68 Discussion
 

Pull Request 68 File Diff
 
 
Pull Request Description 
 
This commit fixes up the sync tests which were broke due to refactors to the export utility functions in FOSS. 
 
(webhooks-id: 

Jira (FACT-1116) Unbreak network facts resolver on BSD

2015-07-20 Thread Peter Huene (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1116 
 
 
 
  Unbreak network facts resolver on BSD  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Huene 
 
 
 

Fix Version/s:
 
 FACT3.1.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-1085) Facter should not redirect stderr to stdout

2015-07-20 Thread Sean Griffin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1085 
 
 
 
  Facter should not redirect stderr to stdout  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

Assignee:
 
 SeanGriffin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1809) Slow response times to aggregate-event-counts endpoint queries

2015-07-20 Thread Rajasree Talla (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rajasree Talla updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1809 
 
 
 
  Slow response times to aggregate-event-counts endpoint queries  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rajasree Talla 
 
 
 

Scrum Team:
 
 PuppetDB 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-112) Provide means to request events from latest report in timeframe

2015-07-20 Thread Beth Cornils (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Beth Cornils commented on  PDB-112 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Provide means to request events from latest report in timeframe  
 
 
 
 
 
 
 
 
 
 
Hi Scott Walker and Deepak Giridharagopal 
In talking with Jeremy Adams and Chris Barker I think the way we handle EI is correct. The reason the counts for SO and SI do not match is because we had an issue where failed events during a 24 hour time period were obfuscated. This was viewed as a miss.  
Given that, I think making this requested change as an additional option might make more sense. I'm not sure we want to remove visibility to the events that happen in the time frame selected. 
Verne Lindner  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-3088) Debug logging messages can't be used by providers with a path method

2015-07-20 Thread Sean Griffin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3088 
 
 
 
  Debug logging messages can't be used by providers with a path method  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

Assignee:
 
 SeanGriffin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-867) Port xendomains fact to Facter 3

2015-07-20 Thread Sean Griffin (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sean Griffin assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-867 
 
 
 
  Port xendomains fact to Facter 3  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sean Griffin 
 
 
 

Assignee:
 
 SeanGriffin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4886) puppet_agent module doesn't touch puppet.conf settings outside an INI section

2015-07-20 Thread Branan Riley (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Branan Riley assigned an issue to Unassigned 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4886 
 
 
 
  puppet_agent module doesn't touch puppet.conf settings outside an INI section  
 
 
 
 
 
 
 
 
 

Change By:
 
 Branan Riley 
 
 
 

Assignee:
 
 BrananRiley 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1816) PR (68): (maint) Update sync tests for export refactors in FOSS - ajroetker

2015-07-20 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1816 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (68): (maint) Update sync tests for export refactors in FOSS - ajroetker  
 
 
 
 
 
 
 
 
 
 
ajroetker commented: 
@mullr @rbrw this will fix master ^ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4887) Reserved words as hash keys?

2015-07-20 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-4887 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Reserved words as hash keys?  
 
 
 
 
 
 
 
 
 
 
Note that keywords are allowed as attribute names in classes and defines as well as in variable names: 
 
 
 
 
 
 
class why_oh_why($if = 'reason') { 
 
 
 
 
 # ... 
 
 
 
 
} 
 
 
 
 
class { why_oh_why: 
 
 
 
 
  if = 'just because' 
 
 
 
 
}
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
  

Jira (FACT-1116) Unbreak network facts resolver on BSD

2015-07-20 Thread Peter Huene (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Peter Huene updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-1116 
 
 
 
  Unbreak network facts resolver on BSD  
 
 
 
 
 
 
 
 
 

Change By:
 
 Peter Huene 
 
 
 

Sprint:
 
 Client2015-08-05 
 
 
 

Scrum Team:
 
 ClientPlatform 
 
 
 

Story Points:
 
 1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1817) PR (1552): (maint) rollup 2.3.x to stable - mullr

2015-07-20 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1817 
 
 
 
  PR (1552): (maint) rollup 2.3.x to stable - mullr  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/07/20 2:01 PM 
 
 
 

Labels:
 

 github 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
(maint) rollup 2.3.x to stable 
 

Author: Russell Mull 
 

Company:
 

Github ID: mullr
 

Pull Request 1552 Discussion
 

Pull Request 1552 File Diff
 
 
Pull Request Description 
 
 
(webhooks-id: db58de806f9230598c6ecd08c9a6e68b) 
 
 
 
 
 
 
   

Jira (PDB-112) Provide means to request events from latest report in timeframe

2015-07-20 Thread Joseph Wagner (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joseph Wagner commented on  PDB-112 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Provide means to request events from latest report in timeframe  
 
 
 
 
 
 
 
 
 
 
My understanding (please correct me anyone if I'm wrong) is If we leave things as they are, we're shipping a brutal performance at large scale. This isn't a regression, we apparently already had these performance issues, but in SG we're explicitly optimizing for a larger scale so this is a much greater concern now. Im fine with the functionality not changing for SG, but doesn't that mean it is unusable at target scale? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1818) PR (1553): Ticket/stable/pdb 1809 slow aec performance - wkalt

2015-07-20 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1818 
 
 
 
  PR (1553): Ticket/stable/pdb 1809 slow aec performance - wkalt  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/07/20 2:34 PM 
 
 
 

Labels:
 

 github 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
Ticket/stable/pdb 1809 slow aec performance 
 

Author: Wyatt Alt 
 

Company:
 

Github ID: wkalt
 

Pull Request 1553 Discussion
 

Pull Request 1553 File Diff
 
 
Pull Request Description 
 
 
(webhooks-id: 4a33c07d6e79b23ccb73ecb5d4f663a3) 
 
 
 
 
 
  

Jira (PDB-1818) PR (1553): Ticket/stable/pdb 1809 slow aec performance - wkalt

2015-07-20 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1818 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (1553): Ticket/stable/pdb 1809 slow aec performance - wkalt  
 
 
 
 
 
 
 
 
 
 
wkalt commented: 
I need to write a few tests to verify that the query param is no longer needed, but this is ready for some functional review. I'll fix up the commits when we're happy. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4780) enhance versioncmp() error checking as it only accepts strings

2015-07-20 Thread Hailee Kenney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4780 
 
 
 
  enhance versioncmp() error checking as it only accepts strings  
 
 
 
 
 
 
 
 
 

Change By:
 
 Hailee Kenney 
 
 
 

Sprint:
 
 Language2015-08-05 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-3501) upstart provider fails with non-ASCII characters in job conf file with a non-UTF8 locale

2015-07-20 Thread Yama (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Yama commented on  PUP-3501 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: upstart provider fails with non-ASCII characters in job conf file with a non-UTF8 locale  
 
 
 
 
 
 
 
 
 
 
I'm facing the same issue on Ubuntu 14.04 
LANG=en_US.UTF-8 via /etc/environment doesn't fix this for me. 
I have tried all found solutions on google, none works. 
Any idea where this goes wrong ? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-112) Provide means to request events from latest report in timeframe

2015-07-20 Thread Beth Cornils (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Beth Cornils commented on  PDB-112 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Provide means to request events from latest report in timeframe  
 
 
 
 
 
 
 
 
 
 
Joseph Wagner and Reid Vandewiele I think for the moment my concern is, we'd change the user experience from what they have today. While the API end point could remain for the current configuration, the UI would need adjustments to allow both views. 2 days doesn't feel like enough time to meet that objective safely. 
With that said, are we comfortable with making this noticeable shift in Ankeny? I think that seems fine. I could be missing something though. 
So confirm if you think we are comfortable leaving things as they are for SG. 
Wyatt Alt, Deepak Giridharagopal 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1817) PR (1552): (maint) rollup 2.3.x to stable - mullr

2015-07-20 Thread Russell Mull (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Mull updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1817 
 
 
 
  PR (1552): (maint) rollup 2.3.x to stable - mullr  
 
 
 
 
 
 
 
 
 

Change By:
 
 Russell Mull 
 
 
 

Sprint:
 
 PuppetDB2015-07-29 
 
 
 

Story Points:
 
 1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1817) PR (1552): (maint) rollup 2.3.x to stable - mullr

2015-07-20 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1817 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (1552): (maint) rollup 2.3.x to stable - mullr  
 
 
 
 
 
 
 
 
 
 
pljenkinsro commented: 
Test FAILed. Refer to this link for build results (access rights to CI server needed):  https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1676/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-112) Provide means to request events from latest report in timeframe

2015-07-20 Thread Reid Vandewiele (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Reid Vandewiele commented on  PDB-112 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Provide means to request events from latest report in timeframe  
 
 
 
 
 
 
 
 
 
 
I'll volunteer as a point of interest that if necessary for performance reasons, I wouldn't be overly opposed to a latest-report-based view that did not necessarily have the idealized consistency characteristics. That is, I'd more or less accept an events right now view wherein events could possibly disappear, so long as I could switch back to e.g. the 5-minute or 30-minute view if I needed to to keep pursuing a specific event. I think latest-report-before is ideal, but as a practitioner I'd still be thumbs-up on using latest-report as a useful MVP. 
I 100% defer to Joe with regards to whether or not that would be acceptable product-level UX though, or if shipping that kind of thing would prevent us from achieving the ideal later. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-3070) Include indent file in vim-puppet

2015-07-20 Thread Brandon Rochon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Brandon Rochon commented on  PUP-3070 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Include indent file in vim-puppet  
 
 
 
 
 
 
 
 
 
 
Exactly which package contains these fixes? I'm looking in wheezy at the latest vim-puppet package I can find ( http://apt.puppetlabs.com/pool/wheezy/main/p/puppet/vim-puppet_3.8.1-1puppetlabs1_all.deb ) and I also check the newest AIO (http://apt.puppetlabs.com/pool/wheezy/PC1/p/puppet-agent/puppet-agent_1.2.1-1wheezy_amd64.deb ) in case that's where it is now: 
 
 
 
 
 
 
$ dpkg -c vim-puppet_3.8.1-1puppetlabs1_all.deb 
 
 
 
 
drwxr-xr-x root/root 0 2015-05-21 13:59 ./ 
 
 
 
 
drwxr-xr-x root/root 0 2015-05-21 13:59 ./usr/ 
 
 
 
 
drwxr-xr-x root/root 0 2015-05-21 13:59 ./usr/share/ 
 
 
 
 
drwxr-xr-x root/root 0 2015-05-21 13:59 ./usr/share/vim/ 
 
 
 
 
drwxr-xr-x root/root 0 2015-05-21 13:59 ./usr/share/vim/addons/ 
 
 
 
 
drwxr-xr-x root/root 0 2015-05-21 13:59 ./usr/share/vim/addons/ftdetect/ 
 
 
 
 
-rw-r--r-- root/root85 2015-05-21 13:54 ./usr/share/vim/addons/ftdetect/puppet.vim 
 
 
 
 
drwxr-xr-x root/root 0 2015-05-21 13:59 ./usr/share/vim/addons/syntax/ 
   

Jira (PDB-1816) PR (68): (maint) Update sync tests for export refactors in FOSS - ajroetker

2015-07-20 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1816 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (68): (maint) Update sync tests for export refactors in FOSS - ajroetker  
 
 
 
 
 
 
 
 
 
 
Pull request (maint) Update sync tests for export refactors in FOSS has been closed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1818) PR (1553): Ticket/stable/pdb 1809 slow aec performance - wkalt

2015-07-20 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1818 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (1553): Ticket/stable/pdb 1809 slow aec performance - wkalt  
 
 
 
 
 
 
 
 
 
 
wkalt commented: 
this will need a couple docs updates as well 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-3905) Evaluate impact of ruby 2.1.5 automatically retrying idempotent http methods

2015-07-20 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-3905 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Evaluate impact of ruby 2.1.5 automatically retrying idempotent http methods  
 
 
 
 
 
 
 
 
 
 
Any thoughts on fixing this and contribute it to MRI 2.1.5 ? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1818) PR (1553): Ticket/stable/pdb 1809 slow aec performance - wkalt

2015-07-20 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1818 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (1553): Ticket/stable/pdb 1809 slow aec performance - wkalt  
 
 
 
 
 
 
 
 
 
 
wkalt commented: 
I found a bug around using aggregate-event-counts with no query parameter and distinct_resources=false. Working through that now. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-3070) Include indent file in vim-puppet

2015-07-20 Thread Melissa Stone (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Melissa Stone commented on  PUP-3070 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Include indent file in vim-puppet  
 
 
 
 
 
 
 
 
 
 
Hmm, that's strange. They should be in the vim-puppet package you're looking at. I found them in the puppet-common package: 
 
 
 
 
 
 
dpkg -L puppet-common | grep vim 
 
 
 
 
/usr/share/puppet/ext/vim 
 
 
 
 
/usr/share/puppet/ext/vim/ftdetect 
 
 
 
 
/usr/share/puppet/ext/vim/ftdetect/puppet.vim 
 
 
 
 
/usr/share/puppet/ext/vim/README 
 
 
 
 
/usr/share/puppet/ext/vim/indent 
 
 
 
 
/usr/share/puppet/ext/vim/indent/puppet.vim 
 
 
 
 
/usr/share/puppet/ext/vim/ftplugin 
 
 
 
 
/usr/share/puppet/ext/vim/ftplugin/puppet.vim 
 
 
 
 
/usr/share/puppet/ext/vim/syntax 
 
 
 
 

Jira (PDB-112) Provide means to request events from latest report in timeframe

2015-07-20 Thread Joseph Wagner (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Joseph Wagner commented on  PDB-112 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Provide means to request events from latest report in timeframe  
 
 
 
 
 
 
 
 
 
 
+1 to everything Reid Vandewiele states. It is ideal to look at the latest run reports when State Inspector loads, but the endpoint needs to remain the time of loading as users browse the interface, otherwise there will be confusing instances where the ground shifts from under them while they're trying to investigate something because Puppet has run again and the data changes. Do we currently query PuppetDB every time a user navigates between panes in State Inspector or do we just query when a user first arrives at State Inspector? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-700) java.io.IOException: Frame size larger than max allowed 100 MB

2015-07-20 Thread Russell Mull (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Russell Mull assigned an issue to Russell Mull 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-700 
 
 
 
  java.io.IOException: Frame size larger than max allowed 100 MB  
 
 
 
 
 
 
 
 
 

Change By:
 
 Russell Mull 
 
 
 

Assignee:
 
 RussellMull 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4886) puppet_agent module doesn't touch puppet.conf settings outside an INI section

2015-07-20 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon assigned an issue to Shaigy Nixon 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4886 
 
 
 
  puppet_agent module doesn't touch puppet.conf settings outside an INI section  
 
 
 
 
 
 
 
 
 

Change By:
 
 Shaigy Nixon 
 
 
 

Assignee:
 
 qa ShaigyNixon 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4848) Global parser = future with environment.conf parser = current gives an error

2015-07-20 Thread Shaigy Nixon (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Shaigy Nixon commented on  PUP-4848 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Global parser = future with environment.conf parser = current gives an error  
 
 
 
 
 
 
 
 
 
 
Validated on redhat-7-x86_64 with the PE package http://enterprise.delivery.puppetlabs.net/3.8/ci-ready/puppet-enterprise-3.8.2-rc0-el-7-x86_64.tar 
Steps used to reproduce: 1) Install PE 2) Set 'parser = future' in the 'main' section of /etc/puppetlabs/puppet/puppet.conf 3) Create /etc/puppetlabs/puppet/environments/production/environment.conf and add line 'parser = current' 4) Modify the default node definition in /etc/puppetlabs/puppet/environments/production/manifests/site.pp 5) Restart pe-puppetserver service 6) Run puppet agent -t 
 
 
 
 
 
 
 
 
 
 
 
[root@fdo6062k8k4lxdg manifests]# cat /etc/puppetlabs/puppet/puppet.conf | grep parser 
 
 
 
 
parser = future 
 
 
 
 
[root@fdo6062k8k4lxdg manifests]# cat /etc/puppetlabs/puppet/environments/production/environment.conf 
 
 
 
 
#env.conf 
 
 
 
 
  parser = current 
 
 
 
 
 
 
 
 
 
[root@fdo6062k8k4lxdg manifests]# tail -13 /etc/puppetlabs/puppet/environments/production/manifests/site.pp 
 
 
 
 

Jira (PDB-1816) PR (68): (maint) Update sync tests for export refactors in FOSS - ajroetker

2015-07-20 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1816 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (68): (maint) Update sync tests for export refactors in FOSS - ajroetker  
 
 
 
 
 
 
 
 
 
 
rbrw commented: 
Looks good. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1809) Slow response times to aggregate-event-counts endpoint queries

2015-07-20 Thread Rajasree Talla (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rajasree Talla updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1809 
 
 
 
  Slow response times to aggregate-event-counts endpoint queries  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rajasree Talla 
 
 
 

Flagged:
 
 Impediment 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4886) puppet_agent module doesn't touch puppet.conf settings outside an INI section

2015-07-20 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith assigned an issue to Branan Riley 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4886 
 
 
 
  puppet_agent module doesn't touch puppet.conf settings outside an INI section  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Assignee:
 
 BrananRiley 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4886) puppet_agent module doesn't touch puppet.conf settings outside an INI section

2015-07-20 Thread Michael Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Michael Smith assigned an issue to qa 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4886 
 
 
 
  puppet_agent module doesn't touch puppet.conf settings outside an INI section  
 
 
 
 
 
 
 
 
 

Change By:
 
 Michael Smith 
 
 
 

Status:
 
 Readyfor CI Test 
 
 
 

Assignee:
 
 qa 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1809) Slow response times to aggregate-event-counts endpoint queries

2015-07-20 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1809 
 
 
 
  Slow response times to aggregate-event-counts endpoint queries  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Story Points:
 
 3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1809) Slow response times to aggregate-event-counts endpoint queries

2015-07-20 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1809 
 
 
 
  Slow response times to aggregate-event-counts endpoint queries  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Sprint:
 
 PuppetDB2015- 07 08 - 29 12 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1809) Slow response times to aggregate-event-counts endpoint queries

2015-07-20 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1809 
 
 
 
  Slow response times to aggregate-event-counts endpoint queries  
 
 
 
 
 
 
 
 
 

Change By:
 
 Wyatt Alt 
 
 
 

Sprint:
 
 PuppetDB2015- 08 07 - 12 29 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1809) Slow response times to aggregate-event-counts endpoint queries

2015-07-20 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-1809 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Slow response times to aggregate-event-counts endpoint queries  
 
 
 
 
 
 
 
 
 
 
There's a patch up for this here: https://github.com/puppetlabs/puppetdb/pull/1553 
Scott Walker Karel Brezina Michal RuzickaNicholas Smyth 
This will require the CM team to change the SI query to align with this: https://gist.github.com/wkalt/6b1da80b4d06104f84ee 
or, if you're uncomfortable dropping the not-null: https://gist.github.com/wkalt/9f9f4b2c9cfb12dde795 
I would recommend dropping the check on receive_time since it seems redundant with start_time and I was seeing a perf hit due to it yesterday, but currently on my PC I'm not seeing a perf difference, so if we want to be conservative even this would be much better than the status quo: https://gist.github.com/wkalt/39e7e263422008f3a237 
If we go with that last query, that means the only required change will be to use the combined summarize_by param. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1818) PR (1553): Ticket/stable/pdb 1809 slow aec performance - wkalt

2015-07-20 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1818 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (1553): Ticket/stable/pdb 1809 slow aec performance - wkalt  
 
 
 
 
 
 
 
 
 
 
pljenkinsro commented: 
Test FAILed. Refer to this link for build results (access rights to CI server needed):  https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1681/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-112) Provide means to request events from latest report in timeframe

2015-07-20 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt commented on  PDB-112 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Provide means to request events from latest report in timeframe  
 
 
 
 
 
 
 
 
 
 
To give an update on this, for the moment we've gone ahead with retaining present behavior for aggregate-event-counts, rather than shifting to a latest-report based view. In light of that, there's no immediate performance-based reason to limit this to latest report only. Since the pressing perf question is settled, I don't see a reason not to target the full functionality described in the ticket. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1818) PR (1553): Ticket/stable/pdb 1809 slow aec performance - wkalt

2015-07-20 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1818 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (1553): Ticket/stable/pdb 1809 slow aec performance - wkalt  
 
 
 
 
 
 
 
 
 
 
wkalt commented: 
@pljenkinsro retest this please 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1818) PR (1553): Ticket/stable/pdb 1809 slow aec performance - wkalt

2015-07-20 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1818 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (1553): Ticket/stable/pdb 1809 slow aec performance - wkalt  
 
 
 
 
 
 
 
 
 
 
pljenkinsro commented: 
Test FAILed. Refer to this link for build results (access rights to CI server needed):  https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1678/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1818) PR (1553): Ticket/stable/pdb 1809 slow aec performance - wkalt

2015-07-20 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1818 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (1553): Ticket/stable/pdb 1809 slow aec performance - wkalt  
 
 
 
 
 
 
 
 
 
 
pljenkinsro commented: 
Test PASSed. Refer to this link for build results (access rights to CI server needed):  https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1677/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1818) PR (1553): Ticket/stable/pdb 1809 slow aec performance - wkalt

2015-07-20 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1818 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (1553): Ticket/stable/pdb 1809 slow aec performance - wkalt  
 
 
 
 
 
 
 
 
 
 
pljenkinsro commented: 
Test FAILed. Refer to this link for build results (access rights to CI server needed):  https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1680/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1817) PR (1552): (maint) rollup 2.3.x to stable - mullr

2015-07-20 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1817 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (1552): (maint) rollup 2.3.x to stable - mullr  
 
 
 
 
 
 
 
 
 
 
mullr commented: 
↑↑↑ not a real failure ↑↑↑ Just a spurious failure on one platform; I don't think we should worry about it.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1817) PR (1552): (maint) rollup 2.3.x to stable - mullr

2015-07-20 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1817 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (1552): (maint) rollup 2.3.x to stable - mullr  
 
 
 
 
 
 
 
 
 
 
pljenkinsro commented: 
Test FAILed. Refer to this link for build results (access rights to CI server needed):  https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1675/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1818) PR (1553): Ticket/stable/pdb 1809 slow aec performance - wkalt

2015-07-20 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1818 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (1553): Ticket/stable/pdb 1809 slow aec performance - wkalt  
 
 
 
 
 
 
 
 
 
 
pljenkinsro commented: 
Test FAILed. Refer to this link for build results (access rights to CI server needed):  https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1679/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (FACT-1096) Is the code ready for release?

2015-07-20 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  FACT-1096 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Is the code ready for release?  
 
 
 
 
 
 
 
 
 
 
Yes! CI is green and we got a green light from PE QA. Woot! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4830) Is the code ready for release?

2015-07-20 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-4830 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Is the code ready for release?  
 
 
 
 
 
 
 
 
 
 
Yes! CI is green and we got a green light from PE QA. Woot! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PUP-4654) Create acceptance for custom facts using puppet facts face

2015-07-20 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-4654 
 
 
 
  Create acceptance for custom facts using puppet facts face  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Fix Version/s:
 
 PUP4.2.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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


Jira (PDB-1818) PR (1553): Ticket/stable/pdb 1809 slow aec performance - wkalt

2015-07-20 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1818 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (1553): Ticket/stable/pdb 1809 slow aec performance - wkalt  
 
 
 
 
 
 
 
 
 
 
pljenkinsro commented: 
Test PASSed. Refer to this link for build results (access rights to CI server needed):  https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1682/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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