Jira (PDB-703) Include hostname on the PuppetDB Dashboard page

2014-06-06 Thread Kenneth Barber (JIRA)
Title: Message Title










 

 Kenneth Barber commented on an issue


















  Re: Include hostname on the PuppetDB Dashboard page 










Russell Harrison You mean like the output of a 'hostname -f' (or clojure equivalent - obviously I wouldn't fork out and do this) presented on the dashboard from the server where the clojure service is running? I think thats possible, I wouldn't want to go beyond that level of complexity however.
Today the index.html is static so we'd have to probably template that or something, or alternatively keep it in _javascript_ and make an API call for it, but that seems like overkill for something so trivial. Point being its possible to do, but not exactly a 1 liner.












   

 Add Comment

























 PuppetDB /  PDB-703



  Include hostname on the PuppetDB Dashboard page 







 I have more than one PuppetDB in my environment and I look at the dashboard frequently by using ssh port forwarding and browsing to http://localhost:8080/dashboard/index.html   Frequently I find I'm ssh'd into both my production and testing PuppetDB instances. My ssh config forwards the same port for puppetdb* so first man wins. It would be very helpfu...















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




 







Jira (PDB-699) Ability to have different puppetdb servers for agent vs master

2014-06-06 Thread Kenneth Barber (JIRA)
Title: Message Title










 

 Kenneth Barber commented on an issue


















  Re: Ability to have different puppetdb servers for agent vs master 










@dalen why would this be useful? What is the use-case?












   

 Add Comment

























 PuppetDB /  PDB-699



  Ability to have different puppetdb servers for agent vs master 







 It should be possible to specify different puppetdb config files for the agent, apply and master applications. Atm all of them will read puppetdb.conf from the confdir, and the confdir is tricky to configure in the puppet config file.















 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 (PDB-702) Research ltrees for Structured Facts versus our own solution

2014-06-06 Thread Kenneth Barber (JIRA)
Title: Message Title










 

 Kenneth Barber updated an issue


















 PuppetDB /  PDB-702



  Research ltrees for Structured Facts versus our own solution 










Change By:

 Kenneth Barber









 Thistasktrackstheworkrequiredtoresearchusingltree'stoprovideabasisforqueryingstructuredfacts-versususingsomethingofourowndevising.












   

 Add Comment






















 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 (PDB-672) resource from puppetmaster deleted immediately after insertion

2014-06-06 Thread Kenneth Barber (JIRA)
Title: Message Title










 

 Kenneth Barber commented on an issue


















  Re: resource from puppetmaster deleted immediately after insertion 










Chris Love its always worth upgrading, but its not certain this will shift your problem.
Can you please supply the rest of the information I asked for:


Your routes.yaml file on your puppet master


Your puppet.conf on your puppet master (and probably agents, if they are consistent)


The contents of your /etc/puppetdb/conf.d directory.


The log you provided above for puppetdb.log doesn't actually contain the SQL delete you mentioned, can you include that - in particular include the failing example with the notify above if it is replicable.














   

 Add Comment

























 PuppetDB /  PDB-672



  resource from puppetmaster deleted immediately after insertion 







 I am using the backuppc module that has the following code for the client:  {code}  @@file { ${backuppc::params::config_directory}/pc/${::fqdn}.pl:  ensure = $ensure,  content = template(${module_name}/host.pl.erb),  owner = 'backuppc',  group = $backuppc::params::group_apache,  mode = '0640',  tag = backuppc...





  

Jira (PDB-565) Support trusted facts in PuppetDB fact storage

2014-06-06 Thread Kenneth Barber (JIRA)
Title: Message Title










 

 Kenneth Barber updated an issue


















 PuppetDB /  PDB-565



  Support trusted facts in PuppetDB fact storage 










This needs a bit more scoping and breaking up potentially, setting story points to 8 for now.










Change By:

 Kenneth Barber




Story Points:

 8












   

 Add Comment






















 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 (PDB-699) Ability to have different puppetdb servers for agent vs master

2014-06-06 Thread Kenneth Barber (JIRA)
Title: Message Title










 

 Kenneth Barber commented on an issue


















  Re: Ability to have different puppetdb servers for agent vs master 










Erik Daln (sorry I pinged you incorrectly before).
If I was honest with myself, I'm looking for a use-case because I don't see a simple solution here (at least its not obvious).
So whats in my brain, is that I would love the configuration directory to just be configurable in puppet.conf ... as an extra item, but to the best of my knowledge injecting new configuration items outside of core might not be possible/easily supported. Now if we could support configuration item injection into puppet.conf, I'd probably just consider moving all our configuration into puppet.conf ... but alas I've never seen anyone do this before, perhaps it can be done . I guess this is the primary reason why puppetdb.conf exists ... because we couldn't just use puppet.conf (at least I could be wrong we'd need to ask Nick Lewis or Deepak Giridharagopal probably ... but it wouldn't surprise me if this was the truth of it.












   

 Add Comment

























 PuppetDB /  PDB-699



  Ability to have different puppetdb servers for agent vs master 







 It should be possible to specify different puppetdb config files for the agent, apply and master applications. Atm all of them will read puppetdb.conf from the confdir, and the confdir is tricky to configure in the puppet config file.















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



Jira (PDB-699) Ability to have different puppetdb servers for agent vs master

2014-06-06 Thread Kenneth Barber (JIRA)
Title: Message Title










 

 Kenneth Barber commented on an issue


















  Re: Ability to have different puppetdb servers for agent vs master 










Come to think of it, this is a duplicate of PDB-175.












   

 Add Comment

























 PuppetDB /  PDB-699



  Ability to have different puppetdb servers for agent vs master 







 It should be possible to specify different puppetdb config files for the agent, apply and master applications. Atm all of them will read puppetdb.conf from the confdir, and the confdir is tricky to configure in the puppet config file.















 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-2735) unexpected different behaviour of 0 (integer vs. string) as a value in Hiera and as a default value for class parameters

2014-06-06 Thread Andreas Papst (JIRA)
Title: Message Title










 

 Andreas Papst created an issue


















 Puppet /  PUP-2735



  unexpected different behaviour of 0 (integer vs. string) as a value in Hiera and as a default value for class parameters 










Issue Type:

  Bug




Affects Versions:


 3.6.1




Assignee:


 Unassigned




Created:


 06/Jun/14 4:34 AM




Environment:


$ facter | grep oper operatingsystem = Debian operatingsystemmajrelease = 7 operatingsystemrelease = 7.5
$ puppet -V 3.6.1
$ dpkg -l | grep puppet ii facter 2.0.1-1puppetlabs1 amd64 Ruby module for collecting simple facts about a host operating system ii hiera 1.3.3-1puppetlabs1 all A simple pluggable Hierarchical Database. ii puppet 3.6.1-1puppetlabs1 all Centralized configuration management - agent startup and compatibility scripts ii puppet-common 3.6.1-1puppetlabs1 all Centralized configuration management ii puppet-lint 0.1.13-2 all check puppet manifests for style guide conformity ii puppetdb 2.0.0-1puppetlabs1 all PuppetDB Centralized Storage. ii puppetdb-terminus 2.0.0-1puppetlabs1 all Connect Puppet to PuppetDB by setting up a terminus for PuppetDB. ii puppetlabs-release 1.0-7 all Package to install Puppet Labs gpg key and apt repo ii puppetmaster 3.6.1-1puppetlabs1 all Centralized configuration management - master startup and compatibility scripts ii puppetmaster-common 3.6.1-1puppetlabs1 all Puppet master common scripts ii puppetmaster-passenger 3.6.1-1puppetlabs1 all Centralised configuration management - master setup to run under mod passenger ii ruby-rgen 0.6.5-1puppetlabs1 all A framework supporting Model Driven Software Development (MDSD) ii vim-puppet 3.6.1-1puppetlabs1 all syntax highlighting for puppet manifests in vim




Priority:

  Normal




Reporter:

 Andreas Papst

 

Jira (PDB-699) Ability to have different puppetdb servers for agent vs master

2014-06-06 Thread JIRA
Title: Message Title










 

 Erik Daln commented on an issue


















  Re: Ability to have different puppetdb servers for agent vs master 










Yeah, the use case for us is that the puppet master for the laptops and desktops is a client to the production puppetdb (master less). So it needs to be started with a different --confdir atm. Haven't figured out how to do that through passenger yet.
As for implementation I'm also unsure how to do it. Would really be good if puppet allowed arbitrary config values. On 6 Jun 2014 12:48, Kenneth Barber (JIRA) issue-upda...@puppetlabs.com












   

 Add Comment

























 PuppetDB /  PDB-699



  Ability to have different puppetdb servers for agent vs master 







 It should be possible to specify different puppetdb config files for the agent, apply and master applications. Atm all of them will read puppetdb.conf from the confdir, and the confdir is tricky to configure in the puppet config file.















 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 

Jira (PUP-837) FFI Puppet::Util::Windows::SID module

2014-06-06 Thread Rob Reynolds (JIRA)
Title: Message Title










 

 Rob Reynolds commented on an issue


















  Re: FFI Puppet::Util::Windows::SID module 










Merged into master at 482cd2d.












   

 Add Comment

























 Puppet /  PUP-837



  FFI Puppet::Util::Windows::SID module 







 Use FFI to define and invoke Windows APIs. Always call the wide-version, where applicable, e.g. ConvertStringSidtoSidW. Also don't do things like:   {code}  strncpy(sid_buf, str_ptr.unpack('L')[0], sid_buf.size - 1)  sid_buf[sid_buf.size - 1] = 0.chr  return sid_buf.strip  {code}















 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-2730) source attribute not honored for gem provider

2014-06-06 Thread Adrien Thebo (JIRA)
Title: Message Title










 

 Adrien Thebo updated an issue


















 Puppet /  PUP-2730



  source attribute not honored for gem provider 










Change By:

 Adrien Thebo









 Whenattemptingtoprovideanothersourceforapackageresourceusingthegemprovider,theinstallfails.Erroroutputfrom'puppetagent-tv': pre {noformat} Error:Executionof'/usr/bin/geminstall--include-dependencies--sourcehttp://internal.gemrepo.com/passenger'returned1:ERROR:Couldnotfindavalidgem'passenger'(=0)inanyrepositoryERROR:Whileexecutinggem...(Gem::RemoteFetcher::FetchError)Errno::ETIMEDOUT:Connectiontimedout-connect(2)(http://rubygems.org/latest_specs.4.8.gz)INFO:`geminstall-y`isnowdefaultandwillberemovedINFO:use--ignore-dependenciestoinstallonlythegemsyoulistError:/Stage[main]/Puppet::Master/Package[passenger]/ensure:changefromabsenttopresentfailed:Executionof'/usr/bin/geminstall--include-dependencies--sourcehttp://internal.gemrepo.com/passenger'returned1:ERROR:Couldnotfindavalidgem'passenger'(=0)inanyrepositoryERROR:Whileexecutinggem...(Gem::RemoteFetcher::FetchError)Errno::ETIMEDOUT:Connectiontimedout-connect(2)(http://rubygems.org/latest_specs.4.8.gz)INFO:`geminstall-y`isnowdefaultandwillberemovedINFO:use--ignore-dependenciestoinstallonlythegemsyoulistFinishedcatalogrunin106.88secondsghickey@slc4b01c-69c8:rack:6$gemsource***CURRENTSOURCES***http://rubygems.org/ghickey@slc4b01c-69c8:rack:0$sudogeminstall--include-dependencies--sourcehttp://internal.gemrepo.com/passenger[sudo]passwordforghickey:INFO:`geminstall-y`isnowdefaultandwillberemovedINFO:use--ignore-dependenciestoinstallonlythegemsyoulistFetching:fastthread-1.0.7.gem(100%)Buildingnativeextensions.Thiscouldtakeawhile...Fetching:daemon_controller-1.1.0.gem(100%)Fetching:passenger-3.0.18.gem(100%)Successfullyinstalledfastthread-1.0.7Successfullyinstalleddaemon_controller-1.1.0Successfullyinstalledpassenger-3.0.183gemsinstalledInstallingridocumentationforfastthread-1.0.7...Installingridocumentationfordaemon_controller-1.1.0...Installingridocumentationforpassenger-3.0.18...InstallingRDocdocumentationforfastthread-1.0.7...InstallingRDocdocumentationfordaemon_controller-1.1.0...InstallingRDocdocumentationforpassenger-3.0.18... /pre {noformat} Thesystemthatproducedtheoutputisbehindafirewallandcannotdirectlyconnecttorubygems.org.Thereisaninternalgemrepoinsidethefirewallthatcontainsmirroredgemsforthepurposeofdistributingwithinthefirewall.Asyoucanseeifthesamecommandisexecutedfromthecommandline,itsucceeds.












   

 Add Comment









   

Jira (PUP-2730) source attribute not honored for gem provider

2014-06-06 Thread Adrien Thebo (JIRA)
Title: Message Title










 

 Adrien Thebo updated an issue


















 Puppet /  PUP-2730



  source attribute not honored for gem provider 










Change By:

 Adrien Thebo









 Whenattemptingtoprovideanothersourceforapackageresourceusingthegemprovider,theinstallfails.Erroroutputfrom'puppetagent-tv':{noformat}Error:Executionof'/usr/bin/geminstall--include-dependencies--sourcehttp://internal.gemrepo.com/passenger'returned1:ERROR:Couldnotfindavalidgem'passenger'(=0)inanyrepositoryERROR:Whileexecutinggem...(Gem::RemoteFetcher::FetchError)Errno::ETIMEDOUT:Connectiontimedout-connect(2)(http://rubygems.org/latest_specs.4.8.gz)INFO:`geminstall-y`isnowdefaultandwillberemovedINFO:use--ignore-dependenciestoinstallonlythegemsyoulistError:/Stage[main]/Puppet::Master/Package[passenger]/ensure:changefromabsenttopresentfailed:Executionof'/usr/bin/geminstall--include-dependencies--sourcehttp://internal.gemrepo.com/passenger'returned1:ERROR:Couldnotfindavalidgem'passenger'(=0)inanyrepositoryERROR:Whileexecutinggem...(Gem::RemoteFetcher::FetchError)Errno::ETIMEDOUT:Connectiontimedout-connect(2)(http://rubygems.org/latest_specs.4.8.gz)INFO:`geminstall-y`isnowdefaultandwillberemovedINFO:use--ignore-dependenciestoinstallonlythegemsyoulistFinishedcatalogrunin106.88seconds {noformat}{noformat} ghickey@slc4b01c-69c8:rack:6$gemsource***CURRENTSOURCES***http://rubygems.org/ghickey@slc4b01c-69c8:rack:0$sudogeminstall--include-dependencies--sourcehttp://internal.gemrepo.com/passenger[sudo]passwordforghickey:INFO:`geminstall-y`isnowdefaultandwillberemovedINFO:use--ignore-dependenciestoinstallonlythegemsyoulistFetching:fastthread-1.0.7.gem(100%)Buildingnativeextensions.Thiscouldtakeawhile...Fetching:daemon_controller-1.1.0.gem(100%)Fetching:passenger-3.0.18.gem(100%)Successfullyinstalledfastthread-1.0.7Successfullyinstalleddaemon_controller-1.1.0Successfullyinstalledpassenger-3.0.183gemsinstalledInstallingridocumentationforfastthread-1.0.7...Installingridocumentationfordaemon_controller-1.1.0...Installingridocumentationforpassenger-3.0.18...InstallingRDocdocumentationforfastthread-1.0.7...InstallingRDocdocumentationfordaemon_controller-1.1.0...InstallingRDocdocumentationforpassenger-3.0.18...{noformat}Thesystemthatproducedtheoutputisbehindafirewallandcannotdirectlyconnecttorubygems.org.Thereisaninternalgemrepoinsidethefirewallthatcontainsmirroredgemsforthepurposeofdistributingwithinthefirewall.Asyoucanseeifthesamecommandisexecutedfromthecommandline,itsucceeds.












   

 Add Comment








   

Jira (PUP-2724) Puppet not installable on precise

2014-06-06 Thread Adrien Thebo (JIRA)
Title: Message Title










 

 Adrien Thebo commented on an issue


















  Re: Puppet not installable on precise 










Yolanda is this resolved?












   

 Add Comment

























 Puppet /  PUP-2724



  Puppet not installable on precise 







 Using puppet repository to install that on precise, we are getting this error:   The following packages have unmet dependencies:  puppet : Depends: puppet-common (= 2.7.25-1puppetlabs1) but it is not going to be installed  Unable to correct problems, you have held broken packages.















 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-2707) Puppet loads ZFS module on FreeBSD when ZFS is not enabled

2014-06-06 Thread Adrien Thebo (JIRA)
Title: Message Title










 

 Adrien Thebo commented on an issue


















  Re: Puppet loads ZFS module on FreeBSD when ZFS is not enabled 










Can you test running `facter` and see if this triggers the behavior without running a full puppet agent?












   

 Add Comment

























 Puppet /  PUP-2707



  Puppet loads ZFS module on FreeBSD when ZFS is not enabled 







 When puppet starts it triggers loading of the ZFS kernel module. This also happens when the machine does not have ZFS.   root@w4:~ # kldstat  Id Refs Address Size Name  1 1 0x8020 15b9558 kernel  root@w4:~ # puppet agent -v --test  Info: Retrieving plugin  [cut for brevity]  Notice: Finished catalog run in 17.58 seconds  ...















 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-2707) Puppet loads ZFS module on FreeBSD when ZFS is not enabled

2014-06-06 Thread Adrien Thebo (JIRA)
Title: Message Title










 

 Adrien Thebo updated an issue


















 Puppet /  PUP-2707



  Puppet loads ZFS module on FreeBSD when ZFS is not enabled 










Change By:

 Adrien Thebo




Assignee:

 RemkoCatersels












   

 Add Comment






















 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-2635) user purge_ssh_keys not purged

2014-06-06 Thread Rob Reynolds (JIRA)
Title: Message Title










 

 Rob Reynolds commented on an issue


















  Re: user purge_ssh_keys not purged 










Passed CI on https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Stable/job/Puppet-Package-Acceptance-stable/431 , https://jenkins.puppetlabs.com/job/Puppet-Acceptance-Windows-stable-vcloud-and-github/293/ (Windows) and https://jenkins.puppetlabs.com/job/Puppet-Acceptance-Solaris-stable-vcloud-and-github/261/ (Solaris) 












   

 Add Comment

























 Puppet /  PUP-2635



  user purge_ssh_keys not purged 







 I'm using Puppet 3.6.0 on Ubuntu 12.04 and I'm trying to purge unmanaged ssh authorized keys.   I've added this code to my manifest:   {code}  user { 'ubuntu':  purge_ssh_keys = true,  home = '/home/ubuntu',  }  {code}   However, no keys are purged. I do see the following lines in the agent debug output:   {noformat}  Debug: /Stage[main]/Role...















 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.

Jira (PUP-2650) 3.6.1 issues warning message for deprecation

2014-06-06 Thread Rob Reynolds (JIRA)
Title: Message Title










 

 Rob Reynolds commented on an issue


















  Re: 3.6.1 issues warning message for deprecation 










Passed CI on https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Stable/job/Puppet-Package-Acceptance-stable/431 , https://jenkins.puppetlabs.com/job/Puppet-Acceptance-Windows-stable-vcloud-and-github/293/ (Windows) and https://jenkins.puppetlabs.com/job/Puppet-Acceptance-Solaris-stable-vcloud-and-github/261/ (Solaris) 












   

 Add Comment

























 Puppet /  PUP-2650



  3.6.1 issues warning message for deprecation 







 Message is issued from agent runs at the warning level for a deprecation message.   Warning: The package type's allow_virtual parameter will be changing its default value from false to true in a future release. If you do not want to allow virtual packages, please explicitly set allow_virtual to false. (at /usr/lib/ruby/site_ruby/1.8/puppet/type.rb:816:in...















 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 

Jira (PUP-2705) Regression with external facts pluginsync not preserving executable bit

2014-06-06 Thread Rob Reynolds (JIRA)
Title: Message Title










 

 Rob Reynolds commented on an issue


















  Re: Regression with external facts pluginsync not preserving executable bit 










Passed CI on https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Stable/job/Puppet-Package-Acceptance-stable/431 , https://jenkins.puppetlabs.com/job/Puppet-Acceptance-Windows-stable-vcloud-and-github/293/ (Windows) and https://jenkins.puppetlabs.com/job/Puppet-Acceptance-Solaris-stable-vcloud-and-github/261/ (Solaris) 












   

 Add Comment

























 Puppet /  PUP-2705



  Regression with external facts pluginsync not preserving executable bit 







 As per the subject, the external facts feature in puppet 3.6.1 is partially broken.   I've tried to add a script into the module/facts.d path and given it executable permissions too.   Once the agent runs, it successfully syncs the plugin across in the external facts directory (/var/lib/puppet/facts.d). However, the script lacks the original permissions.















 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 

Jira (PUP-2705) Regression with external facts pluginsync not preserving executable bit

2014-06-06 Thread Rob Reynolds (JIRA)
Title: Message Title










 

 Rob Reynolds commented on an issue


















  Re: Regression with external facts pluginsync not preserving executable bit 










Moved to resolved as Adrien Thebo mentioned.












   

 Add Comment

























 Puppet /  PUP-2705



  Regression with external facts pluginsync not preserving executable bit 







 As per the subject, the external facts feature in puppet 3.6.1 is partially broken.   I've tried to add a script into the module/facts.d path and given it executable permissions too.   Once the agent runs, it successfully syncs the plugin across in the external facts directory (/var/lib/puppet/facts.d). However, the script lacks the original permissions.















 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-2656) FFI Puppet::Util::Windows::Registry

2014-06-06 Thread Rob Reynolds (JIRA)
Title: Message Title










 

 Rob Reynolds assigned an issue to Rob Reynolds


















 Puppet /  PUP-2656



  FFI Puppet::Util::Windows::Registry 










Change By:

 Rob Reynolds




Assignee:

 RobReynolds












   

 Add Comment






















 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-06-06 Thread Andy Parker (JIRA)
Title: Message Title










 

 Andy Parker updated an issue


















 Puppet /  PUP-2700



  Puppet 3.6.1 File recurse improperly handles spaces in filenames 










Change By:

 Andy Parker




Priority:

 Normal Critical












   

 Add Comment






















 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-06-06 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg commented on an issue


















  Re: Puppet 3.6.1 File recurse improperly handles spaces in filenames 










That makes sense. Before that commit the code was just `source.to_s`, now it's going through uri library which is presumably introducing the additional escaping. Not sure why webrick is unaffected though.












   

 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 

Jira (PUP-855) On Windows allow using root path for file type

2014-06-06 Thread Rob Reynolds (JIRA)
Title: Message Title










 

 Rob Reynolds commented on an issue


















  Re: On Windows allow using root path for file type 










The concern here is that this could cause inconsistent changes if someone had moved the systemdrive to not C or applications Program files over to another drive.












   

 Add Comment

























 Puppet /  PUP-855



  On Windows allow using root path for file type 







 This would allow full path in a way that doesn't require specifying the drive to look at. When this is specified, we will use SYSTEMDRIVE. This would allow multiple computers with different system drives to be able to use the same manifests. This could also open the door for more platforms using the same manifest with less use of selectors based on the O...















 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-2404) Merge puppet 3.6 into pe-puppet 3.3.x

2014-06-06 Thread Joshua Partlow (JIRA)
Title: Message Title










 

 Joshua Partlow assigned an issue to Joshua Partlow


















 Puppet /  PUP-2404



  Merge puppet 3.6 into pe-puppet 3.3.x 










Change By:

 Joshua Partlow




Assignee:

 JoshuaPartlow












   

 Add Comment






















 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-2736) the hosts resource should match on the IP address

2014-06-06 Thread Lee Lowder (JIRA)
Title: Message Title










 

 Lee Lowder updated an issue


















 Puppet /  PUP-2736



  the hosts resource should match on the IP address 










Change By:

 Lee Lowder




Labels:

 Support












   

 Add Comment






















 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-2736) the hosts resource should match on the IP address

2014-06-06 Thread Lee Lowder (JIRA)
Title: Message Title










 

 Lee Lowder created an issue


















 Puppet /  PUP-2736



  the hosts resource should match on the IP address 










Issue Type:

  Improvement




Assignee:


 Unassigned




Created:


 06/Jun/14 9:45 AM




Priority:

  Normal




Reporter:

 Lee Lowder










[from a customer]
In my opinion, the host resource type has a deficiency. 
The primary key of /etc/hosts file is ip address, not the host name.  so if the IP address set by the Œhost resource conflicts with other entry, it  should either be corrected or at least have an error generated to expose the  conflict.












   

 Add Comment






















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




  

Jira (PUP-2635) user purge_ssh_keys not purged

2014-06-06 Thread Adrien Thebo (JIRA)
Title: Message Title










 

 Adrien Thebo assigned an issue to Adrien Thebo


















 Puppet /  PUP-2635



  user purge_ssh_keys not purged 










Change By:

 Adrien Thebo




Assignee:

 AdrienThebo












   

 Add Comment






















 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-2650) 3.6.1 issues warning message for deprecation

2014-06-06 Thread Kurt Wall (JIRA)
Title: Message Title










 

 Kurt Wall assigned an issue to Unassigned


















 Puppet /  PUP-2650



  3.6.1 issues warning message for deprecation 










Change By:

 Kurt Wall




Assignee:

 KurtWall












   

 Add Comment






















 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-1807) Empty string should not equal undef

2014-06-06 Thread Adrien Thebo (JIRA)
Title: Message Title










 

 Adrien Thebo commented on an issue


















  Re: Empty string should not equal undef 










Merged in 4ae571f.












   

 Add Comment

























 Puppet /  PUP-1807



  Empty string should not equal undef 







 Currently {{ == undef}}, which is insane. They should not be equal. Only {{undef}} should equal {{undef}}.















 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-06-06 Thread Charlie Sharpsteen (JIRA)
Title: Message Title










 

 Charlie Sharpsteen updated an issue


















 Puppet /  PUP-2700



  Puppet 3.6.1 File recurse improperly handles spaces in filenames 










Change By:

 Charlie Sharpsteen




Affects Version/s:

 3.6.1




Affects Version/s:

 3.6.0












   

 Add Comment






















 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-2635) user purge_ssh_keys not purged

2014-06-06 Thread Adrien Thebo (JIRA)
Title: Message Title










 

 Adrien Thebo commented on an issue


















  Re: user purge_ssh_keys not purged 










Verified against 2d6948d:
Old behavior on 3.6.1:


[root@default puppet]# bundle exec puppet apply ~/purge-ssh.pp 
Warning: Could not retrieve fact fqdn
Notice: Compiled catalog for default in environment production in 0.12 seconds
Notice: /Stage[main]/Main/Ssh_authorized_key[florp]/ensure: removed
Error: /Stage[main]/Main/Ssh_authorized_key[florp]: Could not evaluate: Cannot write SSH authorized keys without user
Notice: /Stage[main]/Main/Ssh_authorized_key[vagrant]/ensure: removed
Error: /Stage[main]/Main/Ssh_authorized_key[vagrant]: Could not evaluate: Cannot write SSH authorized keys without user
Notice: Finished catalog run in 0.04 seconds



Against stable:


[root@default puppet]# bundle exec puppet apply ~/purge-ssh.pp 
Warning: Could not retrieve fact fqdn
Notice: Compiled catalog for default in environment production in 0.12 seconds
Notice: /Stage[main]/Main/Ssh_authorized_key[florp]/ensure: removed
Notice: /Stage[main]/Main/Ssh_authorized_key[vagrant]/ensure: removed
Notice: Finished catalog run in 0.05 seconds



I noticed that if there are spaces in the ssh key comment then that authorized_key cannot be removed, but that's not directly related to this issue.












   

 Add Comment

























 Puppet /  PUP-2635



  user purge_ssh_keys not purged 







 I'm using Puppet 3.6.0 on Ubuntu 12.04 and I'm trying to purge unmanaged ssh authorized 

Jira (PUP-2737) user purge_ssh_keys cannot remove keys with spaces in the comment

2014-06-06 Thread Adrien Thebo (JIRA)
Title: Message Title










 

 Adrien Thebo created an issue


















 Puppet /  PUP-2737



  user purge_ssh_keys cannot remove keys with spaces in the comment 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 06/Jun/14 10:33 AM




Priority:

  Normal




Reporter:

 Adrien Thebo










Given the following:


# /root/.ssh/authorized_keys
# HEADER: This file was autogenerated at Fri Jun 06 16:59:39 + 2014
# HEADER: by puppet.  While it can still be managed manually, it
# HEADER: is definitely not recommended.
ssh-rsa B3NzaC1yc2EBIwAAAQEA6NF8iallvQVp22WDkTkyrtvp9eWW6A8YVr+kz4TjGYe7gHzIw+niNltGEFHzD8+v1I2YJ6oXevct1YeS0o9HZyN1Q9qgCgzUFtdOKLv6IedplqoPkcmF0aYet2PkEDo3MlTBckFXPITAMzF8dJSIFo9D8HfdOV0IAdx4O7PtixWKn5y2hMNG0zQPyUecp4pzC6kivAIhyfHilFR61RGL+GPXQ2MWZWFYbAGjyiYJnAmCP3NOTd0jMZEnDkbUvxhMmBYSdETk1rRgm+R4LOzFUGaHqHDLKLX+FIPKcF96hrucXzcWyLbIbEgE98OHlnVYCzRdK8jlqm8tehUc9c9WhQ== vagrant insecure public key






user { 'root':
  purge_ssh_keys = true,
  home = '/root'
}








[root@default puppet]# bundle exec puppet apply ~/purge-ssh.pp --noop --debug Warning: Could not retrieve fact fqdn Debug: Failed to load library 'shadow' for feature 'libshadow' Notice: Compiled catalog for default in environment production in 0.13 seconds [snip] Debug: Finishing transaction -610461438 Debug: Loaded state in 0.00 seconds Debug: Loaded state in 0.00 seconds Info: Applying 

Jira (PUP-2635) user purge_ssh_keys not purged

2014-06-06 Thread Adrien Thebo (JIRA)
Title: Message Title










 

 Adrien Thebo commented on an issue


















  Re: user purge_ssh_keys not purged 










PUP-2737 linked for the discovered defect; closing this issue out.












   

 Add Comment

























 Puppet /  PUP-2635



  user purge_ssh_keys not purged 







 I'm using Puppet 3.6.0 on Ubuntu 12.04 and I'm trying to purge unmanaged ssh authorized keys.   I've added this code to my manifest:   {code}  user { 'ubuntu':  purge_ssh_keys = true,  home = '/home/ubuntu',  }  {code}   However, no keys are purged. I do see the following lines in the agent debug output:   {noformat}  Debug: /Stage[main]/Role...















 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-2656) FFI Puppet::Util::Windows::Registry

2014-06-06 Thread Ethan Brown (JIRA)
Title: Message Title










 

 Ethan Brown assigned an issue to Ethan Brown


















 Puppet /  PUP-2656



  FFI Puppet::Util::Windows::Registry 










Change By:

 Ethan Brown




Assignee:

 EthanBrown












   

 Add Comment






















 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-2656) FFI Puppet::Util::Windows::Registry

2014-06-06 Thread Ethan Brown (JIRA)
Title: Message Title










 

 Ethan Brown commented on an issue


















  Re: FFI Puppet::Util::Windows::Registry 










One very minor code issue.
Also fails the Travis builds b/c the FFI include isn't guarded on non-Windows platforms.












   

 Add Comment

























 Puppet /  PUP-2656



  FFI Puppet::Util::Windows::Registry 







 Need to FFI   {panel}  require 'windows/national'  Windows::National::GetACP.call  {panel}















 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-2656) FFI Puppet::Util::Windows::Registry

2014-06-06 Thread Ethan Brown (JIRA)
Title: Message Title










 

 Ethan Brown assigned an issue to Rob Reynolds


















 Puppet /  PUP-2656



  FFI Puppet::Util::Windows::Registry 










Change By:

 Ethan Brown




Assignee:

 EthanBrown RobReynolds












   

 Add Comment






















 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-06-06 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg updated an issue


















 Puppet /  PUP-2700



  Puppet 3.6.1 File recurse improperly handles spaces in filenames 










Change By:

 Kylo Ginsberg




Sprint:

 Week2014-6-4to2014-6-11












   

 Add Comment






















 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-121) Remove relative namespacing

2014-06-06 Thread Joshua Partlow (JIRA)
Title: Message Title










 

 Joshua Partlow assigned an issue to Unassigned


















 Puppet /  PUP-121



  Remove relative namespacing 










Change By:

 Joshua Partlow




Assignee:

 JoshuaPartlow












   

 Add Comment






















 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-2514) Remove support to search for Type in String

2014-06-06 Thread Joshua Partlow (JIRA)
Title: Message Title










 

 Joshua Partlow commented on an issue


















  Re: Remove support to search for Type in String 










Merged to master in a5e24f












   

 Add Comment

























 Puppet /  PUP-2514



  Remove support to search for Type in String 







 The idea to support search for Type in String with the rationale that if String is an array of characters, then any slice of that string is also a String, and thus searching for a substring with matching types should be allowed.   The implementation does this now, but not in a comprehensive way, and does not support string length, pattern, variant etc.  ...















 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-2656) FFI Puppet::Util::Windows::Registry

2014-06-06 Thread Ethan Brown (JIRA)
Title: Message Title










 

 Ethan Brown assigned an issue to Ethan Brown


















 Puppet /  PUP-2656



  FFI Puppet::Util::Windows::Registry 










Change By:

 Ethan Brown




Assignee:

 EthanBrown












   

 Add Comment






















 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 (FACT-234) Add Facts showing the UUID of partitions

2014-06-06 Thread Adrien Thebo (JIRA)
Title: Message Title










 

 Adrien Thebo updated an issue


















 Facter /  FACT-234



  Add Facts showing the UUID of partitions 










Change By:

 Adrien Thebo




Sprint:

 Week2014-6- 11 4 to2014-6- 18 11












   

 Add Comment






















 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-1362) Rubyize yumhelper.py to remove dependency on python

2014-06-06 Thread Adrien Thebo (JIRA)
Title: Message Title










 

 Adrien Thebo updated an issue


















 Puppet /  PUP-1362



  Rubyize yumhelper.py to remove dependency on python 










Change By:

 Adrien Thebo




Sprint:

 Week2014-6- 11 4 to2014-6- 18 11












   

 Add Comment






















 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 (FACT-482) processor.rb crashes Facter within MCollective on MS Windows

2014-06-06 Thread Ethan Brown (JIRA)
Title: Message Title










 

 Ethan Brown updated an issue


















 Facter /  FACT-482



  processor.rb crashes Facter within MCollective on MS Windows 










Change By:

 Ethan Brown









 Theuseoffacterfactsplugin [1] formcollectivecausesthefollowingerroronMSWindowsonly:in`rescueinblockinget_fact'Failedtoloadfacts:ThreadError:deadlock;recursivelockingThissetupworksverywellon*nixoperatingsystemsthough.Canthecodeatlib/facter/processor.rb:120withThread::exclusivedoberefactoredtoallowsuchause?IhavealsolistedthisasaknownissueundermyMSIbuildinstructionsformcollectiveat[ 1 2 ].Currentresolutionistodeletetheprocessor.rbaltogethertoavoiddelvingintoit.[1]https://github.com/ puppetlabs/mcollective-facter-facts[2]https://github.com/ new23d/MCollective-MSI












   

 Add Comment






















 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-1843) 3.4.0 broke compatibility with plugins using the hiera indirector terminus

2014-06-06 Thread Kurt Wall (JIRA)
Title: Message Title










 

 Kurt Wall assigned an issue to Kurt Wall


















 Puppet /  PUP-1843



  3.4.0 broke compatibility with plugins using the hiera indirector terminus 










Change By:

 Kurt Wall




Assignee:

 KurtWall












   

 Add Comment






















 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 (FACT-234) Add Facts showing the UUID of partitions

2014-06-06 Thread Adrien Thebo (JIRA)
Title: Message Title










 

 Adrien Thebo assigned an issue to Adrien Thebo


















 Facter /  FACT-234



  Add Facts showing the UUID of partitions 










Change By:

 Adrien Thebo




Assignee:

 AdrienThebo












   

 Add Comment






















 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-1362) Rubyize yumhelper.py to remove dependency on python

2014-06-06 Thread Josh Cooper (JIRA)
Title: Message Title










 

 Josh Cooper assigned an issue to Josh Cooper


















 Puppet /  PUP-1362



  Rubyize yumhelper.py to remove dependency on python 










Change By:

 Josh Cooper




Assignee:

 JoshCooper












   

 Add Comment






















 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-2737) user purge_ssh_keys cannot remove keys with spaces in the comment

2014-06-06 Thread Felix Frank (JIRA)
Title: Message Title










 

 Felix Frank assigned an issue to Felix Frank


















 Puppet /  PUP-2737



  user purge_ssh_keys cannot remove keys with spaces in the comment 










Change By:

 Felix Frank




Assignee:

 FelixFrank












   

 Add Comment






















 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-2737) user purge_ssh_keys cannot remove keys with spaces in the comment

2014-06-06 Thread Felix Frank (JIRA)
Title: Message Title










 

 Felix Frank commented on an issue


















  Re: user purge_ssh_keys cannot remove keys with spaces in the comment 










Oh, so that's valid? Interesting.
It bothered me from the beginning that the purging implements its own trivial parsing logic, and now I'm paying up.












   

 Add Comment

























 Puppet /  PUP-2737



  user purge_ssh_keys cannot remove keys with spaces in the comment 







 Given the following:   {noformat}  # /root/.ssh/authorized_keys  # HEADER: This file was autogenerated at Fri Jun 06 16:59:39 + 2014  # HEADER: by puppet. While it can still be managed manually, it  # HEADER: is definitely not recommended.  ssh-rsa B3NzaC1yc2EBIwAAAQEA6NF8iallvQVp22WDkTkyrtvp9eWW6A8YVr+kz4TjGYe7gHzIw+niNltGEFHzD8+v1I2YJ6oXev...















 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 

Jira (PUP-2656) FFI Puppet::Util::Windows::Registry

2014-06-06 Thread Ethan Brown (JIRA)
Title: Message Title










 

 Ethan Brown commented on an issue


















  Re: FFI Puppet::Util::Windows::Registry 










Merged to master in https://github.com/puppetlabs/puppet/commit/45a3abb18dcfba3ebae95e6be6ed79297ae22bef, pending release in 3.7.0












   

 Add Comment

























 Puppet /  PUP-2656



  FFI Puppet::Util::Windows::Registry 







 Need to FFI   {panel}  require 'windows/national'  Windows::National::GetACP.call  {panel}















 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-2737) user purge_ssh_keys cannot remove keys with spaces in the comment

2014-06-06 Thread Felix Frank (JIRA)
Title: Message Title










 

 Felix Frank updated an issue


















 Puppet /  PUP-2737



  user purge_ssh_keys cannot remove keys with spaces in the comment 










Change By:

 Felix Frank




Affects Version/s:

 3.6.0












   

 Add Comment






















 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-2737) user purge_ssh_keys cannot remove keys with spaces in the comment

2014-06-06 Thread Felix Frank (JIRA)
Title: Message Title










 

 Felix Frank updated an issue


















 Puppet /  PUP-2737



  user purge_ssh_keys cannot remove keys with spaces in the comment 










Change By:

 Felix Frank




Component/s:

 TypesandProviders












   

 Add Comment






















 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-2737) user purge_ssh_keys cannot remove keys with spaces in the comment

2014-06-06 Thread Felix Frank (JIRA)
Title: Message Title










 

 Felix Frank updated an issue


















 Puppet /  PUP-2737



  user purge_ssh_keys cannot remove keys with spaces in the comment 










Change By:

 Felix Frank




Fix Version/s:

 3.6.2












   

 Add Comment






















 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-2656) FFI Puppet::Util::Windows::Registry

2014-06-06 Thread Rob Reynolds (JIRA)
Title: Message Title










 

 Rob Reynolds commented on an issue


















  Re: FFI Puppet::Util::Windows::Registry 










Fixed up minor code issues 












   

 Add Comment

























 Puppet /  PUP-2656



  FFI Puppet::Util::Windows::Registry 







 Need to FFI   {panel}  require 'windows/national'  Windows::National::GetACP.call  {panel}















 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-1843) 3.4.0 broke compatibility with plugins using the hiera indirector terminus

2014-06-06 Thread Kurt Wall (JIRA)
Title: Message Title










 

 Kurt Wall updated an issue


















 Puppet /  PUP-1843



  3.4.0 broke compatibility with plugins using the hiera indirector terminus 










Change By:

 Kurt Wall




Assignee:

 KurtWall












   

 Add Comment






















 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-2733) Puppet squats on the PuppetX::Puppetlabs and PuppetX::Puppet namespaces

2014-06-06 Thread Henrik Lindberg (JIRA)
Title: Message Title










 

 Henrik Lindberg commented on an issue


















  Re: Puppet squats on the PuppetX::Puppetlabs and PuppetX::Puppet namespaces 










Well, the idea here is that Puppet defines well known extension points to which others can provide implementations. There are also default implementations of such extensions that may be used, or be replaced by some other implementation. What these names and namespaces are does not matter - and when I selected names I was not aware of the use of any current use of PuppetX.












   

 Add Comment

























 Puppet /  PUP-2733



  Puppet squats on the PuppetX::Puppetlabs and PuppetX::Puppet namespaces 







 The implementation of the heredoc syntax validators added logic into the PuppetX module, took the names PuppetX::Puppetlabs and PuppetX::Puppet and added an implementation into PuppetX::Puppetlabs for json syntax validation and some interfaces into PuppetX::Puppet.   The PuppetX module needs to remain as a convention for code *external* to puppet to have...















 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 

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

2014-06-06 Thread Josh Cooper (JIRA)
Title: Message Title










 

 Josh Cooper updated an issue


















 Puppet /  PUP-2700



  Puppet 3.6.1 File recurse improperly handles spaces in filenames 










Change By:

 Josh Cooper




Story Points:

 2












   

 Add Comment






















 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-1362) Rubyize yumhelper.py to remove dependency on python

2014-06-06 Thread Josh Cooper (JIRA)
Title: Message Title










 

 Josh Cooper commented on an issue


















  Re: Rubyize yumhelper.py to remove dependency on python 










Adrien Thebo should I reopen the existing PR or was there a different one? https://github.com/puppetlabs/puppet/pull/2670#event-128477064












   

 Add Comment

























 Puppet /  PUP-1362



  Rubyize yumhelper.py to remove dependency on python 







 There are several bugs (bug 11380 being one that triggered this patch) that highlight the fact that the version of python used as the default on a system running puppet can break yumhelper.py.   This refactor removes yumhelper.py and moves the functionality into the Yum provider in puppet.















 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-06-06 Thread Charlie Sharpsteen (JIRA)
Title: Message Title










 

 Charlie Sharpsteen commented on an issue


















  Re: Puppet 3.6.1 File recurse improperly handles spaces in filenames 










So, the core issue appears to be taking place on the client in Type::File::Content#get_from_source. Prior to commit 89b8ac1, we would take the string representation of a path, such as dir/foo bar, and pass it to indirection2uri which would perform escaping and return the path with an escaped space:



dir/foo%20bar



Now, we take the URI representation, which is escaped, and end up with a double-escaped request after indirection2uri is finished:



dir/foo%2520bar



The string %2520 is the result of %-escaping a space to get %20 and then %-escaping the percent sign to get %2520. The result of this double encoding is that the server tries to find a file named dir/foo%20bar instead of dir/foo bar.
Not sure at the moment why the double-encoding problem does not seem to affect Webrick.












   

 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...

   

Jira (PUP-2738) Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer

2014-06-06 Thread Ethan Brown (JIRA)
Title: Message Title










 

 Ethan Brown created an issue


















 Puppet /  PUP-2738



  Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 06/Jun/14 3:21 PM




Priority:

  Major




Reporter:

 Ethan Brown










As of the merge for 

PUP-2657
, we've noticed some intermittent test failures (in both CI and locally) in semi-random locations. The merge commit is as follows:
https://github.com/puppetlabs/puppet/commit/d38153bd712167e2777bdd4c63d37e2e8d1cdb39
The commit itself has been reviewed and it doesn't seem to have issues itself, but it's likely it's triggered FFI memory pressure that might have been building up to this point.
Locally, failures include


rspec ./spec/unit/util/storage_spec.rb:178 # Puppet::Util::Storage when storing to the state file should create the state file if it does not exist rspec ./spec/unit/util/storage_spec.rb:196 # Puppet::Util::Storage when storing to the state file should load() the same information that it store()s rspec ./spec/unit/util/yaml_spec.rb:16 # Puppet::Util::Yaml writes data formatted as YAML to disk rspec ./spec/unit/util_spec.rb:438 # Puppet::Util#replace_file should copy 0555 permissions from the target file by default rspec ./spec/unit/util_spec.rb:438 # Puppet::Util#replace_file should copy 0660 permissions from the target file by default rspec ./spec/unit/util_spec.rb:438 # Puppet::Util#replace_file should copy 0770 permissions from the target file by default rspec ./spec/unit/util_spec.rb:465 # Puppet::Util#replace_file should use the default permissions if the source file doesn't exist rspec ./spec/unit/util_spec.rb:503 # Puppet::Util#replace_file should support string 

Jira (PUP-2738) Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer

2014-06-06 Thread Rob Reynolds (JIRA)
Title: Message Title










 

 Rob Reynolds commented on an issue


















  Re: Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer 










I like the idea of block form... be more explicit.












   

 Add Comment

























 Puppet /  PUP-2738



  Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer 







 As of the merge for PUP-2657, we've noticed some intermittent test failures (in both CI and locally) in semi-random locations. The merge commit is as follows:   https://github.com/puppetlabs/puppet/commit/d38153bd712167e2777bdd4c63d37e2e8d1cdb39   The commit itself has been reviewed and it doesn't seem to have issues itself, but it's likely it's trigge...















 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-121) Remove relative namespacing

2014-06-06 Thread Henrik Lindberg (JIRA)
Title: Message Title










 

 Henrik Lindberg commented on an issue


















  Re: Remove relative namespacing 










Pushed update to the PR to fix the issues found in review.












   

 Add Comment

























 Puppet /  PUP-121



  Remove relative namespacing 







 This is the issue where `include apache` actually means “try to declare class `current namespace::apache`, class `parent of current namespace::apache`, and so on, eventually declaring `apache` as a last resort.   This bites people in the wild frequently, and seem to be getting a steady stream of customer complaints about it.   We seem to have nea...















 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-2739) Deprecation warnings for legacy environment sections in puppet.conf are not disabled by a disable_warnings set in puppet.conf

2014-06-06 Thread Joshua Partlow (JIRA)
Title: Message Title










 

 Joshua Partlow created an issue


















 Puppet /  PUP-2739



  Deprecation warnings for legacy environment sections in puppet.conf are not disabled by a disable_warnings set in puppet.conf 










Issue Type:

  Bug




Affects Versions:


 3.6.2




Assignee:

 Andy Parker




Components:


 Server




Created:


 06/Jun/14 5:30 PM




Priority:

  Normal




Reporter:

 Joshua Partlow










The warnings for legacy sections in puppet conf come from lib/puppet/settings/config_file.rb. It is warning directly, and will need to be adjusted to register it's warnings with the main Settings, since we can't read the disable_warnings setting from puppet.conf while in the midst of parsing it.












   

 Add Comment





 

Jira (PUP-2738) Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer

2014-06-06 Thread Ethan Brown (JIRA)
Title: Message Title










 

 Ethan Brown updated an issue


















 Puppet /  PUP-2738



  Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer 










Change By:

 Ethan Brown




Sprint:

 Week2014-6-4to2014-6-11












   

 Add Comment






















 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-2738) Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer

2014-06-06 Thread Ethan Brown (JIRA)
Title: Message Title










 

 Ethan Brown assigned an issue to Ethan Brown


















 Puppet /  PUP-2738



  Investigate FFI Memory Pressure / Deterministically Release FFI MemoryPointer 










Change By:

 Ethan Brown




Assignee:

 EthanBrown












   

 Add Comment






















 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.