Jira (PUP-5309) Yum package provider: ensure => latest fails when kernel is updated but not current

2015-10-26 Thread Tristan Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tristan Smith commented on  PUP-5309 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Yum package provider: ensure => latest fails when kernel is updated but not current  
 
 
 
 
 
 
 
 
 
 
Went ahead and spun a PR to fix this. https://github.com/puppetlabs/puppet/pull/4377 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-5309) Yum package provider: ensure => latest fails when kernel is updated but not current

2015-10-26 Thread Tristan Smith (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tristan Smith commented on  PUP-5309 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Yum package provider: ensure => latest fails when kernel is updated but not current  
 
 
 
 
 
 
 
 
 
 
Seconded; in our case we're on CentOS and have crammed security metadata into OS by dark magics, effectively reproducing this problem. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-2700) Puppet 3.6.1 File recurse improperly handles spaces in filenames

2014-05-30 Thread Tristan Smith (JIRA)
Title: Message Title










 

 Tristan Smith commented on an issue


















  Re: Puppet 3.6.1 File recurse improperly handles spaces in filenames 










Yeah, it's a custom mount on a separate fileserver. I'll do some isolation work and get you a simplified example.












   

 Add Comment

























 Puppet /  PUP-2700



  Puppet 3.6.1 File recurse improperly handles spaces in filenames 







 This one's new on me.  We're using file{ : recurse = remote} to pull a directory structure from a remote puppet fileserver. It would appear that there's a mismatch causing it to multiply urlencode resources it's recursing over, causing it to render a space ' ' as %2520 in the file_content call.   Here's a convenient, if ugly, example:   In the Fileserv...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-2700) Puppet 3.6.1 File recurse improperly handles spaces in filenames

2014-05-29 Thread Tristan Smith (JIRA)
Title: Message Title










 

 Tristan Smith created an issue


















 Puppet /  PUP-2700



  Puppet 3.6.1 File recurse improperly handles spaces in filenames 










Issue Type:

  Bug




Affects Versions:


 3.6.1




Assignee:

 Kylo Ginsberg




Components:


 Types and Providers




Created:


 29/May/14 2:23 PM




Environment:


Puppet 3.6.1 server, Puppet 3.6.1 client. Separate puppet server for catalog and puppet fileserver for this content, using passenger for both.




Priority:

  Normal




Reporter:

 Tristan Smith










This one's new on me. We're using file{ : recurse = remote} to pull a directory structure from a remote puppet fileserver. It would appear that there's a mismatch causing it to multiply urlencode resources it's recursing over, causing it to render a space ' ' as %2520 in the file_content call.
Here's a convenient, if ugly, example:
In the Fileserver: [29/May/2014:14:15:18 -0700] GET /production/file_content/puppet/python340/lib/python3.4/site-packages/setuptools/_pycache_/script%2520template%2520(dev).cpython-34.pyc HTTP/1.1 404 147 

  

Jira (PUP-2700) Puppet 3.6.1 File recurse improperly handles spaces in filenames

2014-05-29 Thread Tristan Smith (JIRA)
Title: Message Title










 

 Tristan Smith commented on an issue


















  Re: Puppet 3.6.1 File recurse improperly handles spaces in filenames 










This appears to be server-side, as it did not manifest with puppet 3.4.3 server and does still happen with 3.4.3 clients. 












   

 Add Comment

























 Puppet /  PUP-2700



  Puppet 3.6.1 File recurse improperly handles spaces in filenames 







 This one's new on me.  We're using file{ : recurse = remote} to pull a directory structure from a remote puppet fileserver. It would appear that there's a mismatch causing it to multiply urlencode resources it's recursing over, causing it to render a space ' ' as %2520 in the file_content call.   Here's a convenient, if ugly, example:   In the Fileserv...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send 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-1892) PR (2420) Puppet remote fileserver facility for file resources.

2014-03-24 Thread Tristan Smith (JIRA)
Title: Message Title










 

 Tristan Smith commented on an issue


















  Re: PR (2420) Puppet remote fileserver facility for file resources. 










I've unscrewed travis for this pull; the code appears to behave properlike now, though I'm not sure it's properly idiomatic, per se. 












   

 Add Comment

























 Puppet /  PUP-1892



  PR (2420) Puppet remote fileserver facility for file resources. 







 As of current release, due to the use of source_or_content.full_path, the hostname is stripped from attempts to handle file_content calls in type/file.rb. Because of this, it correctly calls file_metadata from the proper server, but then calls the puppetmaster instead of the remote fileserver for content retrieval, which fails.   This resolution might st...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1892) PR (2420) Puppet remote fileserver facility for file resources.

2014-03-07 Thread Tristan Smith (JIRA)
Title: Message Title










 

 Tristan Smith created an issue


















 Puppet /  PUP-1892



  PR (2420) Puppet remote fileserver facility for file resources. 










Issue Type:

  Bug




Affects Versions:


 3.4.3




Assignee:

 Kylo Ginsberg




Components:


 Types and Providers




Created:


 07/Mar/14 1:25 PM




Priority:

  Normal




Reporter:

 Tristan Smith










As of current release, due to the use of source_or_content.full_path, the hostname is stripped from attempts to handle file_content calls in type/file.rb. Because of this, it correctly calls file_metadata from the proper server, but then calls the puppetmaster instead of the remote fileserver for content retrieval, which fails.
This resolution might still be a bit naive, but it mitigates the issue pretty neatly.












   

 Add Comment