Jira (PUP-3238) puppet reports end of file reached if server closes HTTP connection

2014-12-24 Thread Nick Moriarty (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nick Moriarty commented on  PUP-3238 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: puppet reports end of file reached if server closes HTTP connection  
 
 
 
 
 
 
 
 
 
 
I've finally tracked down the cause of the client-initiated connection closures causing our issue. These were caused by bad file descriptor usage in a custom fact; in Ruby 1.8, IO objects seem to be very low-level, and the Open3 library can return illegal but valid-looking IO objects from a call to popen3 even if the underlying command fails to run. It looks like these objects can end up relating to other, existing IOs; in our case, this was sometimes the HTTP socket. Closing of the connection appeared to be a side-effect of these invalid IOs. I've fixed the associated fact, and the problem seems to have subsided. 
I'd still like to see a retry feature and/or a test of HTTP connections to see if they're actually still open before using them. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-137) Document use of PuppetDB with SELinux

2014-12-24 Thread Rob Nelson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Nelson commented on  PDB-137 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Document use of PuppetDB with SELinux  
 
 
 
 
 
 
 
 
 
 
PR 1191 submitted https://github.com/puppetlabs/puppetdb/pull/1191 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3318) Puppet prints warning when environment is set using classifier rather than local puppet.conf

2014-12-24 Thread Marc Seeger (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Marc Seeger commented on  PUP-3318 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Puppet prints warning when environment is set using classifier rather than local puppet.conf   
 
 
 
 
 
 
 
 
 
 
Hey Gilson Jose Montanha Junior , the ticket is marked as needs information Is there anything in addition to the description that I can provide? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3792) Remove Entry from Crontab

2014-12-24 Thread Tammy Shaikh (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tammy Shaikh created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3792 
 
 
 
  Remove Entry from Crontab  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 PUP 3.6.2 
 
 
 

Assignee:
 
 Kylo Ginsberg 
 
 
 

Components:
 

 Client 
 
 
 

Created:
 

 2014/12/24 8:54 AM 
 
 
 

Environment:
 
 
Redhat Linux 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Tammy Shaikh 
 
 
 
 
 
 
 
 
 
 
Hello, 
I'm new to Puppet and looking for option to remove an existing entry from crontab. Hoping to hear back soon from the experts. thanks 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 

Jira (HI-121) Add hiera_resources similar to hiera_include

2014-12-24 Thread Rob Nelson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Nelson commented on  HI-121 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Add hiera_resources similar to hiera_include  
 
 
 
 
 
 
 
 
 
 
Justin, I published https://forge.puppetlabs.com/rnelson0/hiera_resources (https://github.com/rnelson0/hiera_resources) based on Robin Bowes's work. I haven't had any chance to test it yet, given the holidays. I plan to try in the next few days, if you get to it first, let me know how it goes here or as a github issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-121) Add hiera_resources similar to hiera_include

2014-12-24 Thread Rob Nelson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Nelson assigned an issue to Rob Nelson 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Hiera /  HI-121 
 
 
 
  Add hiera_resources similar to hiera_include  
 
 
 
 
 
 
 
 
 

Change By:
 
 Rob Nelson 
 
 
 

Assignee:
 
 EricSorenson RobNelson 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3732) type validation should not run for `puppet resource`

2014-12-24 Thread Hunter Haugen (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hunter Haugen updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3732 
 
 
 
  type validation should not run for `puppet resource`  
 
 
 
 
 
 
 
 
 

Change By:
 
 Hunter Haugen 
 
 
 

Summary:
 
 typevalidationshould rot not runfor`puppetresource` 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-546) facter fails when on non standard nic

2014-12-24 Thread Ori Gofen (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ori Gofen commented on  FACT-546 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: facter fails when on non standard nic  
 
 
 
 
 
 
 
 
 
 
The issue here is at Facter::Util::IP ifconfig_interface. While a network name in linux is perfectly legal when wrapped in semicolons, bash Interprets the ifconfig command (ifconfig -a ;vdsmdummy; 2/dev/null) executed on puppet agent as: ifconfig -a, now there's a new line because of semicolon vdsmdummy (that's what prompts stderr), another new line and finaly 2 /dev/null which doesn't do anything of course. 
The function: def self.ifconfig_interface(interface) output = Facter::Util::IP.exec_ifconfig([interface,2/dev/null])  end should check if an interface is wrapped in semicolons and add \ before semicolons and then execute: ifconfig -a \;vdsmdummy\; 2/dev/null I tried to fix it myself but it seems that facter code encounter the new \ and then adds another \ before it so the implementation was not quite easy for me as I'm not a ruby dev . 
guys, please fix this issue when you can as it seem to bother a lot of community users (I found at least ten sites complaining about this visual error easily) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.