Jira (HI-14) Allow access to structured data

2015-01-26 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Hiera /  HI-14 
 
 
 
  Allow access to structured data  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Sprint:
 
 Language2015-02-04 
 
 
 

Scrum Team:
 
 Language 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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 (HI-294) Traverse hiera with a fact that returns an array

2015-01-26 Thread Jon Shanks (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jon Shanks commented on  HI-294 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Traverse hiera with a fact that returns an array  
 
 
 
 
 
 
 
 
 
 
This woudl mean i wouldn't have to use my custom wrapper function around hiera to achieve this:  
https://github.com/jon-shanks/customlib 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-2689) A node can't always collect its own exported resources

2015-01-26 Thread Iain Buclaw (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Iain Buclaw commented on  PUP-2689 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: A node can't always collect its own exported resources  
 
 
 
 
 
 
 
 
 
 
This seems to have caused a regression in my environment when upgrading from 3.5.1 to 3.6.2. 
 
 
 
 
 
 
node arthur { 
 
 
 
 
@notify { I feel very depressed: 
 
 
 
 
tag = 'marvin' 
 
 
 
 
} 
 
 
 
 
Notify | tag == 'arthur' | 
 
 
 
 
}
 
 
 
 
 
 
 
Before upgrade, Arthur never saw the notification, now Arthur does. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

Jira (HI-328) Hiera does not detect interpolation recursion

2015-01-26 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren assigned an issue to Thomas Hallgren 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Hiera /  HI-328 
 
 
 
  Hiera does not detect interpolation recursion  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Assignee:
 
 ThomasHallgren 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3911) Ignored included dependencies due to interpretation order

2015-01-26 Thread David Barbion (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Barbion created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3911 
 
 
 
  Ignored included dependencies due to interpretation order   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.6.2 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Language 
 
 
 

Created:
 

 2015/01/26 5:41 AM 
 
 
 

Environment:
 
 
RHEL6, 7 MacOs X 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 David Barbion 
 
 
 
 
 
 
 
 
 
 
Hello, 
We are massively using tags to provision servers (production and development) to restrict catalog to a sub-part. 
We found a strange behaviour when mixing the use of tags, include directive and definitions: 
 
 
 
 
 
 
  class do_not_ignore_me { 

Jira (PUP-2689) A node can't always collect its own exported resources

2015-01-26 Thread Iain Buclaw (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Iain Buclaw commented on  PUP-2689 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: A node can't always collect its own exported resources  
 
 
 
 
 
 
 
 
 
 
Henrik Lindberg So not having a specification has justified a means for changing how collecting virtual resources work with tags? Given that the ramifications are pretty hefty here, I'm surprised this didn't get deterred to the next major version. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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 (HI-294) Traverse hiera with a fact that returns an array

2015-01-26 Thread Jon Shanks (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jon Shanks commented on  HI-294 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Traverse hiera with a fact that returns an array  
 
 
 
 
 
 
 
 
 
 
Also, it would allow you to potentially utilise the list of classes assigned to a machine hence traversing data relevant to what is applied to a box i.e. if classes contained an array list of classes assigned to a machine, then modules could find other data for other modules within it: 
— :backends: 
 

yaml :hierarchy:
 

defaults
 

modules/% {module_name} 
/%{::classes}
 

global
 
 
So if you had a box which had jenkins + sudo modules assigned, you could drop have modules/sudo/jenkins.yaml on the machine with specific jenkins sudo rules and sudo, when it went to compile data for the module, would read the jenkins.yaml and apply the sudo rules for jenkins on the box. If you removed jenkins module, it wouldn't find it anymore. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3911) Ignored included dependencies due to interpretation order

2015-01-26 Thread Mathieu BONIFACE (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mathieu BONIFACE updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3911 
 
 
 
  Ignored included dependencies due to interpretation order   
 
 
 
 
 
 
 
 
 

Change By:
 
 Mathieu BONIFACE 
 
 
 
 
 
 
 
 
 
 Hello,Wearemassivelyusingtagstoprovisionservers(productionanddevelopment)torestrictcatalogtoasub-part.Wefoundastrangebehaviourwhenmixingtheuseoftags,includedirectiveanddefinitions:{code :puppet }classdo_not_ignore_me{notify{'Thismessageshouldalwaysbedisplayed':}}definefoobar($message=''){notify{$message:}includedo_not_ignore_me}classfoo{foobar{'from_foo':message=$name}}classbar{foobar{'from_bar':message=$name}}includefooincludebar{code}Whenwetrytoapplythiscatalog,usingthefollowingcommand:{code}puppetapplyfoobar.pp--tagsfoo{code}wegetthisoutput:{code}Notice:Compiledcatalogformy-wksinenvironmentproductionin0.03secondsNotice:fooNotice:/Stage[main]/Foo/Foobar[from_foo]/Notify[foo]/message:defined'message'as'foo'Notice:ThismessageshouldalwaysbedisplayedNotice:/Stage[main]/Do_not_ignore_me/Notify[Thismessageshouldalwaysbedisplayed]/message:defined'message'as'Thismessageshouldalwaysbedisplayed'Notice:Finishedcatalogrunin0.05seconds{code}Andwhenweswitchthelast2lines,wegetadifferentresult,stillwiththesamecommand:{code}Notice:Compiledcatalogformy-wksinenvironmentproductionin0.03secondsNotice:fooNotice:/Stage[main]/Foo/Foobar[from_foo]/Notify[foo]/message:defined'message'as'foo'Notice:Finishedcatalogrunin0.05seconds{code}Thisbugisembarassingasonlyalittlepartofthelargecatalogisapplied.Regards. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed 

Jira (PUP-3911) Ignored included dependencies due to interpretation order

2015-01-26 Thread Mathieu BONIFACE (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mathieu BONIFACE updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3911 
 
 
 
  Ignored included dependencies due to interpretation order   
 
 
 
 
 
 
 
 
 

Change By:
 
 Mathieu BONIFACE 
 
 
 
 
 
 
 
 
 
 Hello,Wearemassivelyusingtagstoprovisionservers(productionanddevelopment)torestrictcatalogtoasub-part.Wefoundastrangebehaviourwhenmixingtheuseoftags,includedirectiveanddefinitions:{code:puppet}classdo_not_ignore_me{notify{'Thismessageshouldalwaysbedisplayed':}}definefoobar($message=''){notify{$message:}includedo_not_ignore_me}classfoo{foobar{'from_foo':message=$name}}classbar{foobar{'from_bar':message=$name}}includefooincludebar{code}Whenwetrytoapplythiscatalog,usingthefollowingcommand:{code :shell }puppetapplyfoobar.pp--tagsfoo{code}wegetthisoutput:{code}Notice:Compiledcatalogformy-wksinenvironmentproductionin0.03secondsNotice:fooNotice:/Stage[main]/Foo/Foobar[from_foo]/Notify[foo]/message:defined'message'as'foo'Notice:ThismessageshouldalwaysbedisplayedNotice:/Stage[main]/Do_not_ignore_me/Notify[Thismessageshouldalwaysbedisplayed]/message:defined'message'as'Thismessageshouldalwaysbedisplayed'Notice:Finishedcatalogrunin0.05seconds{code}Andwhenweswitchthelast2lines,wegetadifferentresult,stillwiththesamecommand:{code}Notice:Compiledcatalogformy-wksinenvironmentproductionin0.03secondsNotice:fooNotice:/Stage[main]/Foo/Foobar[from_foo]/Notify[foo]/message:defined'message'as'foo'Notice:Finishedcatalogrunin0.05seconds{code}Thisbugisembarassingasonlyalittlepartofthelargecatalogisapplied.Regards. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are 

Jira (PUP-2689) A node can't always collect its own exported resources

2015-01-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-2689 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: A node can't always collect its own exported resources  
 
 
 
 
 
 
 
 
 
 
Iain Buclaw Since we do not have a complete specification of how tags should work in all cases I am not sure if this is a regression, or if you are seeing the effect of a corrected bug. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3910) puppet agent: RUNTIME_ERROR during certificate creation

2015-01-26 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-3910 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: puppet agent: RUNTIME_ERROR during certificate creation  
 
 
 
 
 
 
 
 
 
 
Wolfgang Hotwagner it looks like this is some kind of Rack permissions or config issue based on Server Error: No such file or directory - /tmp/RackRewindableInput20150126-14275-kc4s7z.lock. Can you narrow this down to a configuration that can be reproduced independently? 
Btw, you might ask on the #puppet channel or the puppet-users group as well to see if anyone else has run into this one before. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3484) Cron hour/minute format 0-6,13-23 is not allowed

2015-01-26 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-3484 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Cron hour/minute format 0-6,13-23 is not allowed  
 
 
 
 
 
 
 
 
 
 
This is what the docs indicate as well: https://docs.puppetlabs.com/references/latest/type.html#cron 
Note that all periodic attributes can be specified as an array of values. 
I think we can close this unless there's a remaining issue. Maksym Polshcha thoughts? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-949) Retrieving facts that have had 'trusted' facts injected into them causes a 400 Attempt to assign to a reserved variable name: 'trusted' on node failure during Puppet catalog compilati

2015-01-26 Thread Ben Ford (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ben Ford commented on  PDB-949 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Retrieving facts that have had 'trusted' facts injected into them causes a 400 Attempt to assign to a reserved variable name: 'trusted' on node failure during Puppet catalog compilation.  
 
 
 
 
 
 
 
 
 
 
Joshua Partlow is there any chance that the time value you mention that the master uses to set fact expiration does not include the time zone? IE, just the raw time of day? 
We are running into this problem in the classroom with completely synced clocks, but with the possibility that some agents are on different time zones. 
Ping Gabe Schuyler  Peter Souter. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3910) puppet agent: RUNTIME_ERROR during certificate creation

2015-01-26 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg assigned an issue to Wolfgang Hotwagner 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3910 
 
 
 
  puppet agent: RUNTIME_ERROR during certificate creation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Assignee:
 
 KyloGinsberg WolfgangHotwagner 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3909) Error: /Service[servicename]: Provider upstart is not functional on this host

2015-01-26 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg assigned an issue to Maksym Polshcha 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3909 
 
 
 
  Error: /Service[servicename]: Provider upstart is not functional on this host  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Assignee:
 
 KyloGinsberg MaksymPolshcha 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3909) Error: /Service[servicename]: Provider upstart is not functional on this host

2015-01-26 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg commented on  PUP-3909 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Error: /Service[servicename]: Provider upstart is not functional on this host  
 
 
 
 
 
 
 
 
 
 
Maksym Polshcha there have been some changes in puppet/master for the upstart provider. If you're able to test from source, can you try to repro this with puppet/master? (If not, we should be releasing puppet 4.0 off of puppet/master in the next week or so, so you could try then.) 
Also where do you see initctl --test being invoked? 
/cc Scott Garman 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3911) Ignored included dependencies due to interpretation order

2015-01-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3911 
 
 
 
  Ignored included dependencies due to interpretation order   
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Scrum Team:
 
 Language 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3911) Ignored included dependencies due to interpretation order

2015-01-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3911 
 
 
 
  Ignored included dependencies due to interpretation order   
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Fix Version/s:
 
 PUP3.7.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3910) puppet agent: RUNTIME_ERROR during certificate creation

2015-01-26 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3910 
 
 
 
  puppet agent: RUNTIME_ERROR during certificate creation  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 
 
 
 
 
 
 
 Ifitrytocreateacertificateusingpuppetagent--serverpuppet-server--waitforcert60-t,thenthefollowingerroroccurs: {code} 

Jira (HI-294) Traverse hiera with a fact that returns an array

2015-01-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  HI-294 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Traverse hiera with a fact that returns an array  
 
 
 
 
 
 
 
 
 
 
In PUP-1640 we have defined a new mechanism that allows a provider of data to be specified per module and per environment in a way that does not force a user to use one particular technology for supplying the data. That mechanism will cater to the need of being able to associate the data for a module with a module and not having to update the global hierarchy. I believe that R.I.Pienaar is working on an implementation for PUP-1640 for hiera. 
As for expanding the hierarchy based on the contents of an array I see no harm in adding such a feature even if it may be a bit difficult since it means that different requests will end up with a different hierarchy (i.e. different number of levels) - something I am not sure the current implementation can deal with in a straight forward way. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-1135) PR (1227): (maint) eastwood linting - wkalt

2015-01-26 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1135 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (1227): (maint) eastwood linting - 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/462/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-2689) A node can't always collect its own exported resources

2015-01-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-2689 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: A node can't always collect its own exported resources  
 
 
 
 
 
 
 
 
 
 
Iain Buclaw I was trying to say that I am sorry this bit you. The consequences of fixing what seemed like a bug to us were not understood. That was in turned caused by lack of specification. Had we understood that fixing the problem would mean that collection in general would find additional objects and that it could lead to bad results we should have deferred the fix to the next major release (4.0.0). Again, I am sorry about that. 
Now, what should we do about this? The fix (this ticket) was released in 3.6.2 (june 10, 2014), and we are about to release 3.7.4 (any day now) and there has been a number of releases in between. I am afraid that reverting the change will cause more pain (albeit other people's pain) than keeping it since there has been more complaints about tagging not doing what was expected (and that this ticket fixed) than there has been complaints about the consequences of fixing this problem. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-1135) PR (1227): (maint) eastwood linting - wkalt

2015-01-26 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1135 
 
 
 
  PR (1227): (maint) eastwood linting - wkalt  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/01/26 7:28 AM 
 
 
 

Labels:
 

 github 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 gepetto-bot 
 
 
 
 
 
 
 
 
 
 
(maint) eastwood linting 
 

Author: Wyatt Alt 
 

Company:
 

Github ID: wkalt
 

Pull Request 1227 Discussion
 

Pull Request 1227 File Diff
 
 
Pull Request Description 
 
I ran lein eastwood on the repo and these are the things that jumped out at me. A few docstrings after function arguments, a few places where tests weren't running as expected. 
 
(webhooks-id: 275fed14c6a462224f854587bdfc0e6e) 

Jira (PUP-3911) Ignored included dependencies due to interpretation order

2015-01-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3911 
 
 
 
  Ignored included dependencies due to interpretation order   
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Affects Version/s:
 
 PUP3.7.3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3911) Ignored included dependencies due to interpretation order

2015-01-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-3911 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Ignored included dependencies due to interpretation order   
 
 
 
 
 
 
 
 
 
 
Verified that problem is still present in 3.7.3 and in 4.0.0 (in the making). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-1136) communicate v4 API changes to stakeholders ahead of release

2015-01-26 Thread Wyatt Alt (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wyatt Alt created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1136 
 
 
 
  communicate v4 API changes to stakeholders ahead of release  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Task 
 
 
 

Affects Versions:
 

 PDB 2.2.2 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/01/26 7:54 AM 
 
 
 

Fix Versions:
 

 PDB 3.0.0 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Wyatt Alt 
 
 
 
 
 
 
 
 
 
 
Since we're dropping v2 and v3 for the next release, and v4 is undergoing some changes, there is no API version in PDB 2.2.2 that matches reality in 3.0. We need to make sure other teams using PDB are aware of the changes occurring to v4 in the next release, before the release occurs. We should send out an email once we have a complete list of changes. 
An incomplete list is: 
 

dashes in command and API endpoint fieldnames converted to underscores
 

reports endpoint now supplies resource events
 

top level extract
 
 

Jira (PUP-3484) Cron hour/minute format 0-6,13-23 is not allowed

2015-01-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3484 
 
 
 
  Cron hour/minute format 0-6,13-23 is not allowed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Scrum Team:
 
 Language 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3484) Cron hour/minute format 0-6,13-23 is not allowed

2015-01-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Kylo Ginsberg 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3484 
 
 
 
  Cron hour/minute format 0-6,13-23 is not allowed  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 MaksymPolshcha KyloGinsberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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 (HI-294) Traverse hiera with a fact that returns an array

2015-01-26 Thread R.I.Pienaar (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 R.I.Pienaar commented on  HI-294 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Traverse hiera with a fact that returns an array  
 
 
 
 
 
 
 
 
 
 
This feature has been requested many times: 
https://github.com/puppetlabs/hiera/pull/193 https://github.com/puppetlabs/hiera/pull/48 
I'd like to see it implemented, but lots of to and fro in those 2 PRs 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3910) puppet agent: RUNTIME_ERROR during certificate creation

2015-01-26 Thread Wolfgang Hotwagner (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Wolfgang Hotwagner commented on  PUP-3910 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: puppet agent: RUNTIME_ERROR during certificate creation  
 
 
 
 
 
 
 
 
 
 
My fault, I thought it is a bug of the puppet version with the actual debian package, since i have a lot of puppet-agents working. But it was actually a full disk on my puppet-server.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3897) add acceptance to ensure newly assigned node environments are picked up by agents on first run

2015-01-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-3897 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: add acceptance to ensure newly assigned node environments are picked up by agents on first run  
 
 
 
 
 
 
 
 
 
 
Merged to master in c4343d4 
Henrik Lindberg do you want to backport this change to stable for 3.7.5? or change the fix version for this ticket to 4.0? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3809) Separate code (content?) and configuration directories for AIO packaging

2015-01-26 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson commented on  PUP-3809 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Separate code (content?) and configuration directories for AIO packaging  
 
 
 
 
 
 
 
 
 
 
i commented on 

HI-289
, but for completeness sake the hiera.yaml should live alongside puppet's config files, and its datadir should default to the root of the 'code' directory. Typical deployments have it either in the control repo root (which would man /etc/puppet/code/hieradata) or use a per-environment datadir. The latter relies on variable interpolation on the master, and would land it in /etc/puppet/code/environments/$environment/hieradata, but that is not usable for a default.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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 (HI-298) Update FS layout for hiera

2015-01-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  HI-298 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Update FS layout for hiera  
 
 
 
 
 
 
 
 
 
 
What is then really missing is the ability to override the default datadir from puppet (and that we add a setting for that in puppet). With those changes the hiera release can remain at 1.4 if I understand things correctly. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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 (HI-328) Hiera does not detect interpolation recursion

2015-01-26 Thread Thomas Hallgren (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Thomas Hallgren updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Hiera /  HI-328 
 
 
 
  Hiera does not detect interpolation recursion  
 
 
 
 
 
 
 
 
 

Change By:
 
 Thomas Hallgren 
 
 
 

Sprint:
 
 Language2015-02-04 
 
 
 

Scrum Team:
 
 Language 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3168) Fix all file permissions on puppet module install

2015-01-26 Thread Anderson Mills (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anderson Mills updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3168 
 
 
 
  Fix all file permissions on puppet module install  
 
 
 
 
 
 
 
 
 

Change By:
 
 Anderson Mills 
 
 
 

Fix Version/s:
 
 PUP4.0.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3894) Default license for module metadata does not match an identifier provided by SPDX

2015-01-26 Thread Adrien Thebo (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrien Thebo assigned an issue to Adrien Thebo 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3894 
 
 
 
  Default license for module metadata does not match an identifier provided by SPDX  
 
 
 
 
 
 
 
 
 

Change By:
 
 Adrien Thebo 
 
 
 

Assignee:
 
 AdrienThebo 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3912) Update specs to rspec 3

2015-01-26 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3912 
 
 
 
  Update specs to rspec 3  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/01/26 11:39 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Kylo Ginsberg 
 
 
 
 
 
 
 
 
 
 
Rspec 3 has been out for 6 months and includes some nice new features that would be useful to leverage in puppet specs. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 

Jira (PUP-3912) Update specs to rspec 3

2015-01-26 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3912 
 
 
 
  Update specs to rspec 3  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Scrum Team:
 
 ClientPlatform 
 
 
 

Story Points:
 
 3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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 (HI-298) Update FS layout for hiera

2015-01-26 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson commented on  HI-298 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Update FS layout for hiera  
 
 
 
 
 
 
 
 
 
 
does that Unblock it? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3912) Update specs to rspec 3

2015-01-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3912 
 
 
 
  Update specs to rspec 3  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Sprint:
 
 PlatformClient2015-02-04 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-1515) Invalid parameter provider for custom types/providers

2015-01-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-1515 
 
 
 
  Invalid parameter provider for custom types/providers  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Fix Version/s:
 
 PUP3.7.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3168) Fix all file permissions on puppet module install

2015-01-26 Thread Anderson Mills (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anderson Mills commented on  PUP-3168 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Fix all file permissions on puppet module install  
 
 
 
 
 
 
 
 
 
 
A new PR is up for this problem (PR 3520). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3168) Fix all file permissions on puppet module install

2015-01-26 Thread Anderson Mills (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anderson Mills assigned an issue to Adrien Thebo 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3168 
 
 
 
  Fix all file permissions on puppet module install  
 
 
 
 
 
 
 
 
 

Change By:
 
 Anderson Mills 
 
 
 

Assignee:
 
 AdrienThebo 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3901) Host type has unexpected behavior and is not idempotent

2015-01-26 Thread Eli Young (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eli Young commented on  PUP-3901 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Host type has unexpected behavior and is not idempotent  
 
 
 
 
 
 
 
 
 
 
After doing some research, I have determined that the format of lines in a hostfile is as follows: 
 
 
 
 
 
 
IPcanonical-hostname[alias-hostnames]
 
 
 
 
 
 
 
This is evidenced by the fact that, when a hostname is resolved by either gethostbyname() or getaddrinfo(), the canonical name returned by those functions is canonical-hostname. See also the Windows documentation for gethostbyname() and getaddrinfo(). 
Incidentally, Augeas has the same assessment. Given a hostfile of: 
 
 
 
 
 
 
1.1.1.1 host alias1 alias2
 
 
 
 
 
 
 
Augeas parses it into this: 
 
 
 
 
 
 
augtool print /files/etc/hosts 
 
 
 
 
/files/etc/hosts 
 
 
 
 
/files/etc/hosts/1 
 
 
 
 
/files/etc/hosts/1/ipaddr = 1.1.1.1 
 
 
 
 

Jira (PUP-3912) Update specs to rspec 3

2015-01-26 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg assigned an issue to Kylo Ginsberg 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3912 
 
 
 
  Update specs to rspec 3  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Assignee:
 
 KyloGinsberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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 (HI-298) Update FS layout for hiera

2015-01-26 Thread Eric Sorenson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Sorenson commented on  HI-298 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Update FS layout for hiera  
 
 
 
 
 
 
 
 
 
 
We bashed this out in a room and I have run it by a few people for validation; consensus is the hiera config file (hiera.yaml) should live alongside puppet's config, and the data directory should default to the root of the 'code' directory described in PUP-3809 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3912) Update specs to rspec 3

2015-01-26 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3912 
 
 
 
  Update specs to rspec 3  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Fix Version/s:
 
 PUP4.0.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3897) add acceptance to ensure newly assigned node environments are picked up by agents on first run

2015-01-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-3897 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: add acceptance to ensure newly assigned node environments are picked up by agents on first run  
 
 
 
 
 
 
 
 
 
 
Backport to 3.7.5 please (but wait for stable to be tagged first). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-1515) Invalid parameter provider for custom types/providers

2015-01-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-1515 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Invalid parameter provider for custom types/providers  
 
 
 
 
 
 
 
 
 
 
Reopened as a backport is wanted to 3.7.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3868) Is the code ready for release?

2015-01-26 Thread Hailee Kenney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney commented on  PUP-3868 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Is the code ready for release?  
 
 
 
 
 
 
 
 
 
 
I confirmed that the commit we're tagging for the release (3e8e84200) has been through CI and everything is green. All the tickets that have their fix version tagged as PUP 3.7.4 have been resolved. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3869) Is there a JIRA ticket targeted at the release for every commit?

2015-01-26 Thread Hailee Kenney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney assigned an issue to Hailee Kenney 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3869 
 
 
 
  Is there a JIRA ticket targeted at the release for every commit?  
 
 
 
 
 
 
 
 
 

Change By:
 
 Hailee Kenney 
 
 
 

Assignee:
 
 HenrikLindberg HaileeKenney 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-1137) Dujour - Simplify deployment/packaging of dujour

2015-01-26 Thread AJ Roetker (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 AJ Roetker created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 PuppetDB /  PDB-1137 
 
 
 
  Dujour - Simplify deployment/packaging of dujour  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2015/01/26 12:06 PM 
 
 
 

Labels:
 

 dujour 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 AJ Roetker 
 
 
 
 
 
 
 
 
 
 
Currently Dujour packaging has fallen out of sync with the rest of the packaging for our other Clojure projects. Also OPs interaction with Dujour has traditionally been confusing. It may just be easier to deploy a jar with an init script from the github repo and have some simple monitoring cron job, but it would probably be worthwhile to simplify the deploy process to minimize upkeep. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 

Jira (PUP-3912) Update specs to rspec 3

2015-01-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-3912 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Update specs to rspec 3  
 
 
 
 
 
 
 
 
 
 
Merged in 75561067. When this passes, it can be moved directly to resolved. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3446) CertificateError when running tests with OpenSSL = 1.0.1i

2015-01-26 Thread Hailee Kenney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3446 
 
 
 
  CertificateError when running tests with OpenSSL = 1.0.1i  
 
 
 
 
 
 
 
 
 

Change By:
 
 Hailee Kenney 
 
 
 

Fix Version/s:
 
 PUP4.0.0 
 
 
 

Fix Version/s:
 
 PUP3.7.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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 (HI-298) Update FS layout for hiera

2015-01-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  HI-298 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Update FS layout for hiera  
 
 
 
 
 
 
 
 
 
 
Eric Sorenson yes, if we do this for puppet's use of hiera only; all change is on the puppet side, and the free-standing hiera is unchanged as the AIO is all about changing settings in Puppet. Is this correct? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3894) Default license for module metadata does not match an identifier provided by SPDX

2015-01-26 Thread Anderson Mills (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anderson Mills commented on  PUP-3894 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Default license for module metadata does not match an identifier provided by SPDX  
 
 
 
 
 
 
 
 
 
 
This looks good. I also need to add a small PR to change the example in face/module/generate.rb, too. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3894) Default license for module metadata does not match an identifier provided by SPDX

2015-01-26 Thread Anderson Mills (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anderson Mills updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3894 
 
 
 
  Default license for module metadata does not match an identifier provided by SPDX  
 
 
 
 
 
 
 
 
 

Change By:
 
 Anderson Mills 
 
 
 

Story Points:
 
 1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3082) Error in puppet module skeleton

2015-01-26 Thread Ryan Gard (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Gard commented on  PUP-3082 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Error in puppet module skeleton  
 
 
 
 
 
 
 
 
 
 
The issue was verified by visual inspection of the Gemfile. Console output of commands below: 
 
 
 
 
 
 
[root@centos7 ~]# cd /tmp/ 
 
 
 
 
[root@centos7 tmp]# puppet module generate ryan-test 
 
 
 
 
We need to create a metadata.json file for this module.  Please answer the 
 
 
 
 
following questions; if the question is not applicable to this module, feel free 
 
 
 
 
to leave it blank. 
 
 
 
 
 
 
 
 
 
Puppet uses Semantic Versioning (semver.org) to version modules. 
 
 
 
 
What version is this module?  [0.1.0] 
 
 
 
 
-- 
 
 
 
 
 
 
 
 
  

Jira (PUP-3867) puppet 3.7.4 2014-01-27 Release

2015-01-26 Thread Kylo Ginsberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kylo Ginsberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3867 
 
 
 
  puppet 3.7.4 2014-01-27 Release  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kylo Ginsberg 
 
 
 

Story Points:
 
 3 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3868) Is the code ready for release?

2015-01-26 Thread Hailee Kenney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney assigned an issue to Hailee Kenney 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3868 
 
 
 
  Is the code ready for release?  
 
 
 
 
 
 
 
 
 

Change By:
 
 Hailee Kenney 
 
 
 

Assignee:
 
 HenrikLindberg HaileeKenney 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3867) puppet 3.7.4 2014-01-27 Release

2015-01-26 Thread Hailee Kenney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney assigned an issue to Hailee Kenney 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3867 
 
 
 
  puppet 3.7.4 2014-01-27 Release  
 
 
 
 
 
 
 
 
 

Change By:
 
 Hailee Kenney 
 
 
 

Assignee:
 
 ReleaseEngineering HaileeKenney 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3082) Error in puppet module skeleton

2015-01-26 Thread Ryan Gard (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Gard commented on  PUP-3082 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Error in puppet module skeleton  
 
 
 
 
 
 
 
 
 
 
Verified as fixed against Puppet at SHA 0bf24a7d58f08e8b9b67665af5c21d6f015bfa3d on master branch. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3894) Default license for module metadata does not match an identifier provided by SPDX

2015-01-26 Thread Heidi Pio (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Heidi Pio updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3894 
 
 
 
  Default license for module metadata does not match an identifier provided by SPDX  
 
 
 
 
 
 
 
 
 

Change By:
 
 Heidi Pio 
 
 
 

Sprint:
 
 CODEMGMT2015-01-28 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3082) Error in puppet module skeleton

2015-01-26 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson commented on  PUP-3082 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Error in puppet module skeleton  
 
 
 
 
 
 
 
 
 
 
Ryan Gard sorry to be pedantic here, but how was this verified? we typically put terminal output of our manual FR in here, to enable future automation, and for general posterity. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3894) Default license for module metadata does not match an identifier provided by SPDX

2015-01-26 Thread Anderson Mills (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anderson Mills commented on  PUP-3894 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Default license for module metadata does not match an identifier provided by SPDX  
 
 
 
 
 
 
 
 
 
 
Another PR is currently on the way, and both PRs should be included to close this ticket. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-2689) A node can't always collect its own exported resources

2015-01-26 Thread Iain Buclaw (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Iain Buclaw commented on  PUP-2689 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: A node can't always collect its own exported resources  
 
 
 
 
 
 
 
 
 
 
I'm not sure - I've been trying to understand the nature of the change through printing debug messages from util/tagging.rb 
I can see that it now recursively goes through every parent resource for a match. 
 
 
 
 
 
 
self.tags = ['marvin', 'notify'] 
 
 
 
 
tags = ['arthur'] 
 
 
 
 
caller = /usr/lib/ruby/vendor_ruby/puppet/parser/resource.rb:200:in `tagged?', ... 
 
 
 
 
return = false 
 
 
 
 
 
 
 
 
 
self.tags = ['node', 'arthur', 'class'] 
 
 
 
 
tags = ['arthur'] 
 
 
 
 
caller = /usr/lib/ruby/vendor_ruby/puppet/parser/resource.rb:200:in `tagged?', /usr/lib/ruby/vendor_ruby/puppet/parser/resource.rb:200:in `tagged?', ... 
 
 
 
 
return = true
 
 
 
 
 
 
 
  

Jira (PUP-3082) Error in puppet module skeleton

2015-01-26 Thread Ryan Gard (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ryan Gard updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3082 
 
 
 
  Error in puppet module skeleton  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ryan Gard 
 
 
 

QA Status:
 
 Reviewed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3894) Default license for module metadata does not match an identifier provided by SPDX

2015-01-26 Thread Anderson Mills (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anderson Mills updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3894 
 
 
 
  Default license for module metadata does not match an identifier provided by SPDX  
 
 
 
 
 
 
 
 
 

Change By:
 
 Anderson Mills 
 
 
 

Fix Version/s:
 
 PUP4.0.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3901) Host type has unexpected behavior and is not idempotent

2015-01-26 Thread Eli Young (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eli Young commented on  PUP-3901 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Host type has unexpected behavior and is not idempotent  
 
 
 
 
 
 
 
 
 
 
Further complications: on Windows, you can only put 9 domains per line: 
 
 
 
 
 
 
C:\ type \windows\system32\drivers\etc\hosts 
 
 
 
 
1.1.1.1 host alias1 alias2 alias3 alias4 alias5 alias6 alias7 alias8 alias9 
 
 
 
 
C:\ping host 
 
 
 
 
 
 
 
 
 
Pinging host [1.1.1.1] with 32 bytes of data: 
 
 
 
 
Control-C 
 
 
 
 
^C 
 
 
 
 
C:\ping alias8 
 
 
 
 
 
 
 
 
 
Pinging host [1.1.1.1] with 32 bytes of data: 
 
 
 
 
Control-C 
  

Jira (PUP-3168) Fix all file permissions on puppet module install

2015-01-26 Thread Anderson Mills (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anderson Mills commented on  PUP-3168 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Fix all file permissions on puppet module install  
 
 
 
 
 
 
 
 
 
 
Currently creating a new PR to address problem with user's PR, which failed review as-is and has not been changed in months. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3867) puppet 3.7.4 2014-01-27 Release

2015-01-26 Thread Hailee Kenney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3867 
 
 
 
  puppet 3.7.4 2014-01-27 Release  
 
 
 
 
 
 
 
 
 

Change By:
 
 Hailee Kenney 
 
 
 

Sprint:
 
 Language2015-02-04 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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 (HI-298) Update FS layout for hiera

2015-01-26 Thread Justin Stoller (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Justin Stoller commented on  HI-298 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Update FS layout for hiera  
 
 
 
 
 
 
 
 
 
 

yes, if we do this for puppet's use of hiera only
 
Can we please get rid of the distinction between hiera-as-used-by-puppet and hiera-used-from-the-command-line. A major bump would be a great time to merge those configs. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3894) Default license for module metadata does not match an identifier provided by SPDX

2015-01-26 Thread Anderson Mills (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Anderson Mills commented on  PUP-3894 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Default license for module metadata does not match an identifier provided by SPDX  
 
 
 
 
 
 
 
 
 
 
 Second PR is waiting for merge. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3872) Merge master into stable

2015-01-26 Thread Hailee Kenney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney assigned an issue to Hailee Kenney 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3872 
 
 
 
  Merge master into stable  
 
 
 
 
 
 
 
 
 

Change By:
 
 Hailee Kenney 
 
 
 

Assignee:
 
 HenrikLindberg HaileeKenney 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3872) Merge master into stable

2015-01-26 Thread Hailee Kenney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney commented on  PUP-3872 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Merge master into stable  
 
 
 
 
 
 
 
 
 
 
Melissa Stone, I think you're right! I will go ahead and close this, thanks for pointing that out. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3870) Is there a commit for every JIRA ticket targeted at the release?

2015-01-26 Thread Hailee Kenney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney assigned an issue to Hailee Kenney 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3870 
 
 
 
  Is there a commit for every JIRA ticket targeted at the release?  
 
 
 
 
 
 
 
 
 

Change By:
 
 Hailee Kenney 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Assignee:
 
 HenrikLindberg HaileeKenney 
 
 
 

Status:
 
 Open Resolved 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3870) Is there a commit for every JIRA ticket targeted at the release?

2015-01-26 Thread Hailee Kenney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney commented on  PUP-3870 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Is there a commit for every JIRA ticket targeted at the release?  
 
 
 
 
 
 
 
 
 
 
Upon running the release-inquisition script, it appears that there is a JIRA ticket with a PUP 3.7.4 fix version that not have a corresponding commit: 
 
 
 
 
 
 
++ Issues in Jira not found in Git 
 
 
 
 
PUP-3737: (Fixed) Can't Install Puppet Gem on Windows64 Bit Ruby 1.9.3 and 2.0 
 
 
 
 
 
 
This issue was actually fixed in commit b9a50e5c, but since that commit covered two tickets (

PUP-3479
 and 

PUP-3737
), the script did not pick it up as a fix for 

PUP-3737
. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google 

Jira (PUP-3911) Ignored included dependencies due to interpretation order

2015-01-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to David Barbion 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3911 
 
 
 
  Ignored included dependencies due to interpretation order   
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 HenrikLindberg DavidBarbion 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3872) Merge master into stable

2015-01-26 Thread Melissa Stone (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Melissa Stone commented on  PUP-3872 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Merge master into stable  
 
 
 
 
 
 
 
 
 
 
This shouldn't need to happen, since this release is a patch/bugfix of the current stable release (3.7.x). Hailee Kenney feel free to correct me, but I think this should be closed. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3526) re-structure CA REST API

2015-01-26 Thread Ruth Linehan (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ruth Linehan commented on  PUP-3526 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: re-structure CA REST API  
 
 
 
 
 
 
 
 
 
 
This was merged in as 6438c7215c73e6eaffe34828fb764d672b517c32 and seems to have passed CI: https://jenkins.puppetlabs.com/job/Puppet-Packaging-Callback-master/364/. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3911) Ignored included dependencies due to interpretation order

2015-01-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3911 
 
 
 
  Ignored included dependencies due to interpretation order   
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Fix Version/s:
 
 PUP3.7.5 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3911) Ignored included dependencies due to interpretation order

2015-01-26 Thread David Barbion (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Barbion commented on  PUP-3911 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Ignored included dependencies due to interpretation order   
 
 
 
 
 
 
 
 
 
 
AFAIK, the older release which produces such result is 3.6.1. I will test with older release tomorrow. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3479) Windows ffi dependency fails for Ruby 2.1.3

2015-01-26 Thread Hailee Kenney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3479 
 
 
 
  Windows ffi dependency fails for Ruby 2.1.3  
 
 
 
 
 
 
 
 
 

Change By:
 
 Hailee Kenney 
 
 
 

Fix Version/s:
 
 PUP4.0.0 
 
 
 

Fix Version/s:
 
 PUP3.7.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3591) Puppet does not plugin sync with the proper environment after agent attempts to resolve environment

2015-01-26 Thread Hailee Kenney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney commented on  PUP-3591 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Puppet does not plugin sync with the proper environment after agent attempts to resolve environment  
 
 
 
 
 
 
 
 
 
 
It's worth noting for those who may find themselves here in the future that one of the commits for this ticket contained a small typo in the ticket number.  
Commit 7958aa034 lists the ticket as PUP-3391 rather that 

PUP-3591
, but is part of a fix for this ticket. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3911) Ignored included dependencies due to interpretation order

2015-01-26 Thread David Barbion (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 David Barbion updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3911 
 
 
 
  Ignored included dependencies due to interpretation order   
 
 
 
 
 
 
 
 
 

Change By:
 
 David Barbion 
 
 
 

Affects Version/s:
 
 PUP3.6.1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-799) operatingsystemmajrelease has excessive detail on AIX

2015-01-26 Thread Chris Roddy (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Chris Roddy created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-799 
 
 
 
  operatingsystemmajrelease has excessive detail on AIX  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 FACT 2.2.0 
 
 
 

Assignee:
 
 Eric Sorenson 
 
 
 

Created:
 

 2015/01/26 1:40 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Chris Roddy 
 
 
 
 
 
 
 
 
 
 
On AIX, 'operatingsystemmajrelease' shows full release information down to the patchlevel. It appears to contain just the same information as 'operatingsystemrelease'. Josh Preston at DSW says this was returning the correct (shorter) info in his proof-of-concept installations on earlier versions of PE 3.x. 
On PE 3.7 (Facter 2.2.0) we get these results: 
 

facter operatingsystemmajrelease operatingsystemrelease operatingsystemmajrelease = 6100-07-06-1241 operatingsystemrelease = 6100-07-06-1241
 
 
 

facter operatingsystemmajrelease operatingsystemrelease operatingsystemmajrelease = 5300-12-04-1119 operatingsystemrelease = 5300-12-04-1119
 
 
 
 
 
 
 
 
 
 
 
  

Jira (PUP-3479) Windows ffi dependency fails for Ruby 2.1.3

2015-01-26 Thread Hailee Kenney (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hailee Kenney updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3479 
 
 
 
  Windows ffi dependency fails for Ruby 2.1.3  
 
 
 
 
 
 
 
 
 

Change By:
 
 Hailee Kenney 
 
 
 

Fix Version/s:
 
 PUP3.7.4 
 
 
 

Fix Version/s:
 
 PUP4.0.0 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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 (HI-328) Hiera does not detect interpolation recursion

2015-01-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Hiera /  HI-328 
 
 
 
  Hiera does not detect interpolation recursion  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Story Points:
 
 1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3863) hiera('some::key', undef) returns empty string

2015-01-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3863 
 
 
 
  hiera('some::key', undef) returns empty string  
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Story Points:
 
 2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3911) Ignored included dependencies due to interpretation order

2015-01-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  PUP-3911 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Ignored included dependencies due to interpretation order   
 
 
 
 
 
 
 
 
 
 
Actually, this is not so strange... 
When foo and bar change places, the include of do_not_ignore_me happens within the context of bar. When it is again being included this is simply ignored. This may be an effect of dynamic scoping going away (which caused a lot of other mysterious side effects). 
Do you see this as a regression in 3.6, from some earlier release? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3911) Ignored included dependencies due to interpretation order

2015-01-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg assigned an issue to Henrik Lindberg 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3911 
 
 
 
  Ignored included dependencies due to interpretation order   
 
 
 
 
 
 
 
 
 

Change By:
 
 Henrik Lindberg 
 
 
 

Assignee:
 
 HenrikLindberg 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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 (HI-298) Update FS layout for hiera

2015-01-26 Thread Henrik Lindberg (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Henrik Lindberg commented on  HI-298 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Update FS layout for hiera  
 
 
 
 
 
 
 
 
 
 
So - decisions have been made: 
 

The next hiera release is HI 2.0.0 since we are changing the paths in a non compatible way (i.e. there will be no 

HI-1
.4.0 release)
 

hiera's lib/hiera/util.rb should be changed so that: 
 

hiera's config_dir should be /etc/puppetlabs/agent/code where hiera will load a hiera.yaml if it exists. (Notably, the hiera.yaml should not be under .../agent/config)
 

hiera's var_dir (a.k.a the default datadir) should be a directory named hieradata under the code directory in the AIO packaging i.e. /etc/puppetlabs/agent/code/hieradata. (The data itself cannot be directly in code as the other content in that directory then accidentaly may look like a data directory to hiera).
 
 
 

Since the hiera datadir can be modified in hiera.yaml, there is no need to also have an override in puppet (there is no such setting in puppet now).
 

The current puppet setting hiera_config remains as is (reference to $confdir/hiera.yaml which after the fix in PUP-3809 will refer to the AIO config directory).
 

Ensure that hiera's defaults and fallback when hiera.yaml is missing ends up using the paths as documented here
 
 
If during the cause of implementing this we find we need to prioritize between options, we should optimize on a solution that: 
 

makes hiera tooling operate with the same settings as when using puppet
 

prioritize use cases involving combined use of puppet and hiera over those that may install hiera outside of the AIO packaging
 
 
 
 
 
 
 
 
 
 
 
 
 
 
   

Jira (PUP-3901) Host type has unexpected behavior and is not idempotent

2015-01-26 Thread Eli Young (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eli Young commented on  PUP-3901 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Host type has unexpected behavior and is not idempotent  
 
 
 
 
 
 
 
 
 
 
I have opened a topic about this on the puppet-dev Google Group. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3539) add additional spec tests to cover globbing ACL matches in fileserver.conf

2015-01-26 Thread Eric Thompson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Eric Thompson updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3539 
 
 
 
  add additional spec tests to cover globbing ACL matches in fileserver.conf  
 
 
 
 
 
 
 
 
 

Change By:
 
 Eric Thompson 
 
 
 

Scrum Team:
 
 Language 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-1135) PR (1227): (maint) eastwood linting - wkalt

2015-01-26 Thread gepetto-bot (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 gepetto-bot commented on  PDB-1135 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: PR (1227): (maint) eastwood linting - 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/465/ 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3901) Host type has unexpected behavior and is not idempotent

2015-01-26 Thread Rob Nelson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Nelson commented on  PUP-3901 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Host type has unexpected behavior and is not idempotent  
 
 
 
 
 
 
 
 
 
 
Nigel Kersten brings up a valid point about how various Linux distributions set the hostname (https://twitter.com/nigelkersten/status/559915243741016064). How would the proposed changes possibly affect the ability of Debian and Enterprise Linux families to set and maintain the managed node's hostname? Debian relies on /etc/hosts whereas EL relies on /etc/sysconfig/hostname with optional modifications to /etc/hosts. I see fqdn and hostname as facts which include the hostname. I am unsure if there are other puppet variables outside of fact that may rely on, interpret, or define the node's hostname, but it seems likely (where does clientcert come from?). These concerns will have to be enumerated and addressed as well. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-713) `facter -p` should be the default behavior

2015-01-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper assigned an issue to garrett honeycutt 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-713 
 
 
 
  `facter -p` should be the default behavior  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Assignee:
 
 EricSorenson garretthoneycutt 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3143) server host name didn't match the server certificate

2015-01-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper commented on  PUP-3143 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: server host name didn't match the server certificate   
 
 
 
 
 
 
 
 
 
 
Palaniappan P this is a pretty common error for new puppet users. You probably want to update puppet.conf on your agent and make sure the server property references the fqdn of the server, e.g. 
 
 
 
 
 
 
[agent] 
 
 
 
 
server= puppetmaster.work.org
 
 
 
 
 
 
 
Also, please review https://docs.puppetlabs.com/guides/troubleshooting.html#agents-are-failing-with-a-hostname-was-not-match-with-the-server-certificate-error-whats-wrong. I'm going to close this issue, if you need additional help, checkout ask.puppetlabs.com and the puppet-users google group. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-3837) Work around Ruby string encoding behavior exercised during registry calls in win32/registry

2015-01-26 Thread Ethan Brown (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ethan Brown assigned an issue to Ethan Brown 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3837 
 
 
 
  Work around Ruby string encoding behavior exercised during registry calls in win32/registry  
 
 
 
 
 
 
 
 
 

Change By:
 
 Ethan Brown 
 
 
 

Assignee:
 
 EthanBrown 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-798) Error on Windows: cannot load such file -- util/sssd

2015-01-26 Thread Josh Cooper (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Josh Cooper assigned an issue to GeneBean 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Facter /  FACT-798 
 
 
 
  Error on Windows: cannot load such file -- util/sssd  
 
 
 
 
 
 
 
 
 

Change By:
 
 Josh Cooper 
 
 
 

Assignee:
 
 EricSorenson GeneBean 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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.


  1   2   >