date:20140225

Title: Message Title










 

 gepetto-bot created an issue











 






 Puppet /  PUP-1764



  PR (2387): Respect Yum's lock - seveas 










Issue Type:

  Task




Assignee:

 Eric Sorenson




Components:


 Community




Created:


 25/Feb/14 12:58 AM




Labels:


 github




Priority:

  Normal




Reporter:

 gepetto-bot










Respect Yum's lock


Author: Dennis Kaarsemaker 


Company: Booking.com


Github ID: seveas


Pull Request 2387 Discussion


Pull Request 2387 File Diff


Pull Request Description

We're seeing RPM DB corruption relatively frequently these days and have narrowed it down to the y

Jira (PUP-1764) PR (2387): Respect Yum's lock - seveas

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2387): Respect Yum's lock - seveas 










puppetcla commented:
Waiting for CLA signature by @seveas
@seveas - We require a Contributor License Agreement (CLA) for people who contribute to Puppet, but we have an easy click-through license with instructions, which is available at https://cla.puppetlabs.com/
Note: if your contribution is trivial and you think it may be exempt from the CLA, please post a short reply to this comment with details. http://docs.puppetlabs.com/community/trivial_patch_exemption.html












   

 Add Comment











 













 Puppet /  PUP-1764



  PR (2387): Respect Yum's lock - seveas 







 h2. Respect Yum's lock   * Author: Dennis Kaarsemaker   * Company: Booking.com  * Github ID: [seveas|https://github.com/seveas]  * [Pull Request 2387 Discussion|https://github.com/puppetlabs/puppet/pull/2387]  * [Pull Request 2387 File Diff|https://github.com/puppetlabs/puppet/pull/2387/files]  h2. Pull Request Description   We...















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

Jira (PUP-1764) PR (2387): Respect Yum's lock - seveas

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2387): Respect Yum's lock - seveas 










puppetcla commented:
CLA signed by all contributors.












   

 Add Comment











 













 Puppet /  PUP-1764



  PR (2387): Respect Yum's lock - seveas 







 h2. Respect Yum's lock   * Author: Dennis Kaarsemaker   * Company: Booking.com  * Github ID: [seveas|https://github.com/seveas]  * [Pull Request 2387 Discussion|https://github.com/puppetlabs/puppet/pull/2387]  * [Pull Request 2387 File Diff|https://github.com/puppetlabs/puppet/pull/2387/files]  h2. Pull Request Description   We...















 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/groups/opt_out.

Jira (PUP-1765) puppet apply --modulepath not respected when /etc/puppet/environments/production exists

Title: Message Title










 

 Dominic Cleal created an issue











 






 Puppet /  PUP-1765



  puppet apply --modulepath not respected when /etc/puppet/environments/production exists 










Issue Type:

  Bug




Affects Versions:


 3.5.0




Assignee:


 Unassigned




Created:


 25/Feb/14 5:41 AM




Environment:


puppet-3.4.3.919-1.el6.noarch




Priority:

  Major




Reporter:

 Dominic Cleal










This appears to be a strange condition since the new directory environments work went in. When /etc/puppet/environments/production exists, puppet apply stops obeying --modulepath and instead attempts to look up the module in /etc only. For example:


# mkdir /etc/puppet/environments/production
# puppet module install -i /tmp/test saz/ntp
Notice: Preparing to install into /tmp/test ...
Notice: Created target directory /tmp/test
Notice: Downloading from https://forge.puppetlabs.com ...
Notice: Installing -- do not interrupt ...
/tmp/test
└── saz-ntp (v2.2.0)
# puppet apply --modulepath /tmp/test -e 'include ntp' --noop
Error: Could not find class ntp for foreman-el6.example.com on node foreman-el6.example.com
Error: Could not find class ntp for foreman-el6.example.com on node foreman-el6.example.com
# cp -a /tmp/test/ntp /etc/puppet/environments/production/modules/
# puppet apply --modulepath /tmp/test -e 'include ntp' --noop
Warning: Config file /etc/puppet/hie

Jira (PUP-1765) puppet apply --modulepath not respected when /etc/puppet/environments/production exists

Title: Message Title










 

 Dominic Cleal updated an issue











 






 Puppet /  PUP-1765



  puppet apply --modulepath not respected when /etc/puppet/environments/production exists 










Change By:

 Dominic Cleal









 This appears to be a strange condition since the new directory environments work went in.  When /etc/puppet/environments/production exists, puppet apply stops obeying --modulepath and instead attempts to look up the module in /etc only.  For example:{noformat}# mkdir /etc/puppet/environments/production# puppet module install -i /tmp/test saz/ntpNotice: Preparing to install into /tmp/test ...Notice: Created target directory /tmp/testNotice: Downloading from https://forge.puppetlabs.com ...Notice: Installing -- do not interrupt .../tmp/test└── saz-ntp (v2.2.0)# puppet apply --modulepath /tmp/test -e 'include ntp' --noopError: Could not find class ntp for foreman-el6.example.com on node foreman-el6.example.comError: Could not find class ntp for foreman-el6.example.com on node foreman-el6.example.com# cp -a /tmp/test/ntp /etc/puppet/environments/production/modules/# puppet apply --modulepath /tmp/test -e 'include ntp' --noopWarning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaultsNotice: Compiled catalog for foreman-el6.example.com in environment production in 0.53 secondsNotice: /Stage[main]/Ntp/Package[ntp]/ensure: current_value absent, should be present (noop)^CExiting{noformat} But if I remove that directory:{noformat}[root@foreman-el6 ~]# rm -rf /etc/puppet/environments/production/[root@foreman-el6 ~]# ll /etc/puppet/environmentstotal 0# puppet apply --modulepath /tmp/test -e 'include ntp' --noopWarning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaultsNotice: Compiled catalog for foreman-el6.example.com in environment production in 0.53 secondsNotice: /Stage[main]/Ntp/Package[ntp]/ensure: current_value absent, should be present (noop)^CExiting{noformat}












   

 Add Comment











 










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

Jira (PUP-1765) puppet apply --modulepath not respected when /etc/puppet/environments/production exists

Title: Message Title










 

 Dominic Cleal updated an issue











 






 Puppet /  PUP-1765



  puppet apply --modulepath not respected when /etc/puppet/environments/production exists 










Change By:

 Dominic Cleal









 This appears to be a strange condition since the new directory environments work went in.  When /etc/puppet/environments/production exists, puppet apply stops obeying --modulepath and instead attempts to look up the module in /etc only.  For example:{noformat}# mkdir /etc/puppet/environments/production# puppet module install -i /tmp/test saz/ntpNotice: Preparing to install into /tmp/test ...Notice: Created target directory /tmp/testNotice: Downloading from https://forge.puppetlabs.com ...Notice: Installing -- do not interrupt .../tmp/test└── saz-ntp (v2.2.0)# puppet apply --modulepath /tmp/test -e 'include ntp' --noopError: Could not find class ntp for foreman-el6.example.com on node foreman-el6.example.comError: Could not find class ntp for foreman-el6.example.com on node foreman-el6.example.com# cp -a /tmp/test/ntp /etc/puppet/environments/production/modules/# puppet apply --modulepath /tmp/test -e 'include ntp' --noopWarning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaultsNotice: Compiled catalog for foreman-el6.example.com in environment production in 0.53 secondsNotice: /Stage[main]/Ntp/Package[ntp]/ensure: current_value absent, should be present (noop)^CExiting{noformat}But if I remove that directory:{noformat} [root@foreman-el6 ~] # rm -rf /etc/puppet/environments/production/ [root@foreman-el6 ~] # ll /etc/puppet/environmentstotal 0# puppet apply --modulepath /tmp/test -e 'include ntp' --noopWarning: Config file /etc/puppet/hiera.yaml not found, using Hiera defaultsNotice: Compiled catalog for foreman-el6.example.com in environment production in 0.53 secondsNotice: /Stage[main]/Ntp/Package[ntp]/ensure: current_value absent, should be present (noop)^CExiting{noformat}












   

 Add Comment











 










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

Jira (PUP-1766) Make systemd the default provider for RHEL7

Title: Message Title










 

 Kylo Ginsberg created an issue











 






 Puppet /  PUP-1766



  Make systemd the default provider for RHEL7 










Issue Type:

  Bug




Assignee:

 Kylo Ginsberg




Created:


 25/Feb/14 6:50 AM




Priority:

  Normal




Reporter:

 Kylo Ginsberg












   

 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/groups/opt_out.

Jira (PUP-1766) Make systemd the default provider for RHEL7

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1766



  Make systemd the default provider for RHEL7 










Change By:

 Kylo Ginsberg




Sprint:

 Week 2014-2-19 to 2014-2-26












   

 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/groups/opt_out.

Jira (PUP-1244) Yum provider using "version-release" to validate installation.

2014-02-25 Thread Felix Frank (JIRA)

Title: Message Title










 

 Felix Frank updated an issue











 






 Puppet /  PUP-1244



  Yum provider using "version-release" to validate installation. 










Change By:

 Felix Frank









 When using yum provider Puppet complains(error output) when using only the version(string) of the package to install or installed at the time of verification.  {code} $snmp_version = "5.3.2.2"package { "net-snmp": ensure => "${snmp_version}"; }Client output:debug: //Node[client.example.com]/snmp::base/Package[net-snmp]: Changing ensuredebug: //Node[client.example.com]/snmp::base/Package[net-snmp]: 1 change(s)debug: Package[net-snmp](provider=yum): Ensuring => 5.3.2.2**(1)** debug: Puppet::Type::Package::ProviderYum: Executing '/usr/bin/yum -d 0 -e 0 -y install net-snmp-5.3.2.2'**(2)** debug: Puppet::Type::Package::ProviderYum: Executing '/bin/rpm -q net-snmp --nosignature --nodigest --qf %{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}'err: //Node[client.example.com]/snmp::base/Package[net-snmp]/ensure: change from 5.3.2.2-7.el5_4.2 to 5.3.2.2 failed: Could not update: Failed to update to version 5.3.2.2, got version 5.3.2.2-7.el5_4.2 instead at /opt/git/development/modules/snmp/manifests/init.pp:26notice: //Node[client.example.com]/snmp::base/File[/etc/snmp/snmpd.conf]: Dependency package[net-snmp] has 1 failureswarning: //Node[labtest40-v3.ea-colo.ea.com]/snmp::base/File[/etc/snmp/snmpd.conf]: Skipping because of failed dependencies  {code} The package is installed **(1)** but the error is still shown at the time of validation **(2)**, same situation if package is already installed.in .../provider/package/yum.rb:  {code} def install chop lines ---is = self.queryunless israise Puppet::Error, "Could not find package %s" % self.nameend# FIXME: Should we raise an exception even if should == :latest# and yum updated us to a version other than @param_hash[:ensure] ?if should && should != is[:ensure]raise Puppet::Error, "Failed to update to version #{should}, got version #{is[:ensure]} instead"end  {code} The error arises as **should** is not equal to **is[:ensure]**in .../provider/package/rpm.rb the query define comment says it will provide the **"version-release"**  {code} # Find the fully versioned package name and the version alone. Returns# a hash with entries :instance => fully versioned package name, and# :ensure => version-releasedef query  {code} The validation is made in the ensure attribute($snmp_version) string against "version-release" installed.  It makes sense when somebody defines something like ensure => "${snmp_version}-${snmp-release}", but not in this use case.Tested in 0.24.8 but reported also on 0.25.4.rpm.rb and yum.rb are not behaving in the same way as yum cli behaves.












   

 Add Comment

Jira (PUP-1765) puppet apply --modulepath not respected when /etc/puppet/environments/production exists

Title: Message Title










 

 Dominic Cleal commented on an issue











 






  Re: puppet apply --modulepath not respected when /etc/puppet/environments/production exists 










It seems the way Puppet::Environments works with multiple environment loaders is part of the cause here, since it will prefer (via the "combined" loader) environments defined via environmentpath over those defined via the settings system. Since --modulepath on the command line is inherited through the settings system, this means the environmentpath always take precedence if the environment is known.
Setting --environment foobar is a workaround, since you're then specifying an environment that's unknown to the environmentpath loader, but it'll fallback to the modulepath specified via --modulepath/settings.












   

 Add Comment











 













 Puppet /  PUP-1765



  puppet apply --modulepath not respected when /etc/puppet/environments/production exists 







 This appears to be a strange condition since the new directory environments work went in. When /etc/puppet/environments/production exists, puppet apply stops obeying --modulepath and instead attempts to look up the module in /etc only. For example:   {noformat}  # mkdir /etc/puppet/environments/production  # puppet module install -i /tmp/test saz/ntp  ...















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

Jira (PUP-1639) Some modules fail to install into target_dir

2014-02-25 Thread Rob Nelson (JIRA)

Title: Message Title

Rob Nelson commented on an issue

Re: Some modules fail to install into target_dir

Andrew Parker: It doesn't appear isolated to puppetlabs-apache, it's any module that has a nodeset file for rspec-system, it's not unpacking and preserving the symlinks properly. default.yml points to centos-64-x64.yml which doesn't exist, it errors - maybe the order of copying files from the temporary directory to the permanent directory is copying the symlink first and generating an error?
Andy Buckingham: You can either git clone the module from github, if available, or find the tarball under "/var/lib/puppet/puppet-module/cache/https_forge_puppetlabs_com-*/" and expand it into your $modulepath location. I haven't made the shift to r10k yet, which may also solve this issue, but these two workarounds are solid for me. Be sure to --force uninstall the broken module first.

Add Comment

Puppet / PUP-1639

Some modules fail to install into target_dir

puppet module install puppetlabs/apache -i puppet/forge-modules Notice: Preparing to install into /home/www/puppet/forge-modules ... Notice: Created target directory /home/www/puppet/forge-modules Notice: Downloading from https://forge.puppetlabs.com ... Notice: Installing -- do not interrupt ... Error: No such file or directory - /home/www/puppet/...

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

Jira (PUP-1680) "incorrect header check" using Ruby 2.1.0

2014-02-25 Thread Nickolay Peregudov (JIRA)

Title: Message Title










 

 Nickolay Peregudov commented on an issue











 






  Re: "incorrect header check" using Ruby 2.1.0 










Same with apache, mod_deflate












   

 Add Comment











 













 Puppet /  PUP-1680



  "incorrect header check" using Ruby 2.1.0 







 I haven't found anything out there so far, so I thought I'd just document it while I'm at it.   We ran into some other problem with the changes in net/http Ruby 2.1.0 introduced around the handling of gzip/deflate encoded content. This MIGHT be related.  So far we haven't been able to fix it.   {code}  Error: incorrect header check  Error: /Stage[main]/...















 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/groups/opt_out.

Jira (PDB-475) PR (122): Use $is_pe for PE determination - reidmv

Title: Message Title










 

 gepetto-bot created an issue











 






 PuppetDB /  PDB-475



  PR (122): Use $is_pe for PE determination - reidmv 










Issue Type:

  Task




Assignee:


 Unassigned




Created:


 25/Feb/14 9:00 AM




Labels:


 github module




Priority:

  Normal




Reporter:

 gepetto-bot










Use $is_pe for PE determination


Author: Reid Vandewiele 


Company: Puppet Labs


Github ID: reidmv


Pull Request 122 Discussion


Pull Request 122 File Diff


Pull Request Description

...rather than the custom logic that was used previously. Using a uniform canon fact across all modules that need to differentiate between PE and POSS makes unusual situations (such as having a missing /opt/puppet/pe_version file) more, well, uniform.

(webhooks-id: a26cd8ff4093926eda87184

Jira (PUP-542) Provide access to all facts in a single structure

2014-02-25 Thread Henrik Lindberg (JIRA)

Title: Message Title










 

 Henrik Lindberg assigned an issue to Henrik Lindberg











 






 Puppet /  PUP-542



  Provide access to all facts in a single structure 










Change By:

 Henrik Lindberg




Assignee:

 Henrik Lindberg












   

 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/groups/opt_out.

Jira (PDB-475) PR (122): Use $is_pe for PE determination - reidmv

2014-02-25 Thread Kenneth Barber (JIRA)

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-475



  PR (122): Use $is_pe for PE determination - reidmv 










Change By:

 Kenneth Barber




Story Points:

 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/groups/opt_out.

Jira (PDB-113) Remove swank

2014-02-25 Thread Kenneth Barber (JIRA)

Title: Message Title










 

 Kenneth Barber commented on an issue











 






  Re: Remove swank 










PR is here: https://github.com/puppetlabs/puppetdb/pull/870












   

 Add Comment











 













 PuppetDB /  PDB-113



  Remove swank 







 Deprecate swank in favour of nrepl.















 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/groups/opt_out.

Jira (PDB-475) PR (122): Use $is_pe for PE determination - reidmv

2014-02-25 Thread Kenneth Barber (JIRA)

Title: Message Title










 

 Kenneth Barber updated an issue











 






 PuppetDB /  PDB-475



  PR (122): Use $is_pe for PE determination - reidmv 










Change By:

 Kenneth Barber




Sprint:

 20140219 to 20140226












   

 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/groups/opt_out.

Jira (PUP-1751) PR (2383): Suse chkconfig --check boot. always returns 1 whether the service is enabled/disabled. - m4ce

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2383): Suse chkconfig --check boot. always returns 1 whether the service is enabled/disabled. - m4ce 










puppetcla commented:
CLA signed by all contributors.












   

 Add Comment











 













 Puppet /  PUP-1751



  PR (2383): Suse chkconfig --check boot. always returns 1 whether the service is enabled/disabled. - m4ce 







 h2. Suse chkconfig --check boot. always returns 1 whether the service is enabled/disabled.   * Author: Matteo <>  * Company:   * Github ID: [m4ce|https://github.com/m4ce]  * [Pull Request 2383 Discussion|https://github.com/puppetlabs/puppet/pull/2383]  * [Pull Request 2383 File Diff|https://github.com/puppetlabs/puppet/pull/2383/files]  h2. Pull ...















 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 op

Jira (PUP-1722) Yumrepo doesn't permit HTTPS URLs

2014-02-25 Thread Peter Huene (JIRA)

Title: Message Title










 

 Peter Huene assigned an issue to Peter Huene











 






 Puppet /  PUP-1722



  Yumrepo doesn't permit HTTPS URLs 










Change By:

 Peter Huene




Assignee:

 Peter Huene












   

 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/groups/opt_out.

Jira (PUP-1722) Yumrepo doesn't permit HTTPS URLs

2014-02-25 Thread Peter Huene (JIRA)

Title: Message Title










 

 Peter Huene assigned an issue to Unassigned











 






 Puppet /  PUP-1722



  Yumrepo doesn't permit HTTPS URLs 










Change By:

 Peter Huene




Assignee:

 Peter Huene












   

 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/groups/opt_out.

Jira (PUP-847) Manage security descriptor owner & group

2014-02-25 Thread Peter Huene (JIRA)

Title: Message Title










 

 Peter Huene assigned an issue to Unassigned











 






 Puppet /  PUP-847



  Manage security descriptor owner & group 










Change By:

 Peter Huene




Assignee:

 Peter Huene












   

 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/groups/opt_out.

Jira (PUP-897) package type should accept virtual package for rpm

2014-02-25 Thread Adrien Thebo (JIRA)

Title: Message Title










 

 Adrien Thebo assigned an issue to Adrien Thebo











 






 Puppet /  PUP-897



  package type should accept virtual package for rpm 










Change By:

 Adrien Thebo




Assignee:

 Adrien Thebo












   

 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/groups/opt_out.

Jira (PUP-1732) 'puppet resource service' with systemd provider shows lots of non-services

Title: Message Title










 

 Kylo Ginsberg commented on an issue











 






  Re: 'puppet resource service' with systemd provider shows lots of non-services 










Adrien Thebo Yeah that's a good point about the questionable services; I saw a couple of the remaining weirdo ones like that and balked at first. But I don't know how we'd do better than reporting the ones that the underlying tools, here systemctl, claim are services so ... yeah shrug. If it becomes an issue we could perhaps apply a bag of blacklist regexes to further filter the list.












   

 Add Comment











 













 Puppet /  PUP-1732



  'puppet resource service' with systemd provider shows lots of non-services 














 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/groups/opt_out.

Jira (PUP-1732) 'puppet resource service' with systemd provider shows lots of non-services

2014-02-25 Thread Adrien Thebo (JIRA)

Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: 'puppet resource service' with systemd provider shows lots of non-services 










Eh, let's just call it systemd's problem and happily move on with things.












   

 Add Comment











 













 Puppet /  PUP-1732



  'puppet resource service' with systemd provider shows lots of non-services 














 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/groups/opt_out.

Jira (PUP-1735) Puppet::Node::Environment.current should reroute with deprecation warning

2014-02-25 Thread Adrien Thebo (JIRA)

Title: Message Title










 

 Adrien Thebo commented on an issue











 






  Re: Puppet::Node::Environment.current should reroute with deprecation warning 










Verified with the following:



#!/usr/bin/env ruby

require 'puppet'


Puppet.initialize_settings()
Puppet::Util::Log.level = :debug
Puppet::Util::Log.newdestination(:console)

p Puppet::Node::Environment.current

Puppet.override(:current_environment => :production) do
  p Puppet::Node::Environment.current
end






[root@fedora puppet]# ./deprecate.rb 
Warning: Puppet::Node::Environment.current has been replaced by Puppet.lookup(:current_environment), see http://links.puppetlabs.com/current-env-deprecation
   (at ./deprecate.rb:10:in `')
*root*
Warning: Puppet::Node::Environment.current has been replaced by Puppet.lookup(:current_environment), see http://links.puppetlabs.com/current-env-deprecation
   (at ./deprecate.rb:13:in `block in ')
:production















   

 Add Comment











 













 Puppet /  PUP-1735



  Puppet::Node::Environment.current should reroute with deprecation warning 







 PUP-1118 in commit ecb317b removed Puppet::Node::Environment.current, which I've seen used in two places:   * kafo  * fancy template headers (e.g. https://github.com/theforeman/puppet-puppet/blob/master/templates/_header.erb)   I'm worried that there might be other users of this, so would suggest it's rerouted to the `Puppet.lookup(:current_environment)...

Jira (PDB-401) PR (826): Port to trapperkeeper 0.3.0 - cprice404

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (826): Port to trapperkeeper 0.3.0 - cprice404 










cprice404 commented:
rebased.












   

 Add Comment











 













 PuppetDB /  PDB-401



  PR (826): Port to trapperkeeper 0.3.0 - cprice404 







 h2. Port to trapperkeeper 0.3.0   * Author: Chris Price <>  * Company:   * Github ID: [cprice404|https://github.com/cprice404]  * [Pull Request 826 Discussion|https://github.com/puppetlabs/puppetdb/pull/826]  * [Pull Request 826 File Diff|https://github.com/puppetlabs/puppetdb/pull/826/files]  h2. Pull Request Description   This commit updates PuppetD...















 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/groups/opt_out.

Jira (PUP-1752) notes_url cannot handle hash-tags (#) within URLs for anchors in html pages

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1752



  notes_url cannot handle hash-tags (#) within URLs for anchors in html pages 










Change By:

 Charlie Sharpsteen









 We tried to add a notes URL to one of our checks like this: {code} nagios_service { "check_postgresql_cluster_connection":ensure  => present,host_name   => 'postgresql-cluster.example.com',service_description => 'Check PG-Cluster Connection',check_command   => "check_postgresql_cluster_connection!10.10.10.5",notes_url   => 'http://bucardo.org/check_postgres/check_postgres.pl.html#connection',use => 'generic-service',} {code}   The notes_url is used correctly and i can click that URL in nagios and it works like expected but with EVERY puppet run the check is modified like this: {code} notice: /Stage[main]/Nagios::Server/Nagios_service[check_postgresql_cluster_connection]/notes_url: notes_url changed 'http://bucardo.org/check_postgres/check_postgres.pl.html' to 'http://bucardo.org/check_postgres/check_postgres.pl.html#connection'info: /Stage[main]/Nagios::Server/Nagios_service[check_postgresql_cluster_connection]: Scheduling refresh of Service[omd] {code}   Can anyone help? I just tried to urlencode the # to %23 but then the Server returns a 404.












   

 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 ht

Jira (PDB-401) PR (826): Port to trapperkeeper 0.3.0 - cprice404

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (826): Port to trapperkeeper 0.3.0 - cprice404 










pljenkinsro commented:
:red_circle: Test failed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/262/












   

 Add Comment











 













 PuppetDB /  PDB-401



  PR (826): Port to trapperkeeper 0.3.0 - cprice404 







 h2. Port to trapperkeeper 0.3.0   * Author: Chris Price <>  * Company:   * Github ID: [cprice404|https://github.com/cprice404]  * [Pull Request 826 Discussion|https://github.com/puppetlabs/puppetdb/pull/826]  * [Pull Request 826 File Diff|https://github.com/puppetlabs/puppetdb/pull/826/files]  h2. Pull Request Description   This commit updates PuppetD...















 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

Jira (PUP-1738) Resource provider should be able to specify suitability and weight

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1738



  Resource provider should be able to specify suitability and weight 










Change By:

 Charlie Sharpsteen




Issue Type:

 Bug New Feature












   

 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/groups/opt_out.

Jira (PUP-1701) No timeout on puppetmaster connections

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1701



  No timeout on puppetmaster connections 










Change By:

 Charlie Sharpsteen









 I'm dealing with an environment with some networking limitations (read 'silly firewalls') that when puppet is performing its duties, there is no timeout on the connection to the puppet master. This results in a puppet session that never ends, and never cleans up its lock file, preventing any future puppet runs. {code} root  8913  0.0  1.0 176276 86596 ?SFeb09   0:02 puppet agent: applying configuratroot 28065  0.0  0.5 110904 42892 ?Ss   Feb02   0:10 /usr/bin/ruby /usr/bin/puppet agentpuppet  8913 root4u  IPv4   80859330  0t0  TCP server:55565->puppet-master:8140 (ESTABLISHED) {code}   The connection has been idle for days and is gone as far as the puppet-master knows. Granted this is poor behavior of the network in between, it should be accounted for.












   

 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/groups/opt_out.

Jira (PUP-1701) No timeout on puppetmaster connections

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Puppet /  PUP-1701



  No timeout on puppetmaster connections 










Change By:

 Charlie Sharpsteen




Assignee:

 Kal McFate












   

 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/groups/opt_out.

Jira (PUP-1701) No timeout on puppetmaster connections

Title: Message Title










 

 Charlie Sharpsteen commented on an issue











 






  Re: No timeout on puppetmaster connections 










Generally, the agent should time out after 2 minutes if it does not receive a catalog from the master. In order to figure out what is going on here, we'll need to know where in the agent run the hangup is happening.
For a hanging run, could you provide a log of:



puppet agent -t --debug















   

 Add Comment











 













 Puppet /  PUP-1701



  No timeout on puppetmaster connections 







 I'm dealing with an environment with some networking limitations (read 'silly firewalls') that when puppet is performing its duties, there is no timeout on the connection to the puppet master. This results in a puppet session that never ends, and never cleans up its lock file, preventing any future puppet runs.   {code}  root 8913 0.0 1.0 176276 8...















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




 














-- 
You receiv

Jira (HI-216) Merge into pe branch if final release

2014-02-25 Thread Melissa Stone (JIRA)

Title: Message Title










 

 Melissa Stone updated an issue











 






 Hiera /  HI-216



  Merge into pe branch if final release 










Change By:

 Melissa Stone




Summary:

 Merge into pe branch  if final release












   

 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/groups/opt_out.

Jira (PDB-401) PR (826): Port to trapperkeeper 0.3.0 - cprice404

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (826): Port to trapperkeeper 0.3.0 - cprice404 










pljenkinsro commented:
:red_circle: Test failed. Refer to this link for build results: https://jenkins.puppetlabs.com/job/PuppetDB%20Acceptance%20-%20Pull%20Requests/263/












   

 Add Comment











 













 PuppetDB /  PDB-401



  PR (826): Port to trapperkeeper 0.3.0 - cprice404 







 h2. Port to trapperkeeper 0.3.0   * Author: Chris Price <>  * Company:   * Github ID: [cprice404|https://github.com/cprice404]  * [Pull Request 826 Discussion|https://github.com/puppetlabs/puppetdb/pull/826]  * [Pull Request 826 File Diff|https://github.com/puppetlabs/puppetdb/pull/826/files]  h2. Pull Request Description   This commit updates PuppetD...















 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

Jira (PUP-1708) PR (2361): (maint) Improve Puppet::Util::Docs.scrub's handling of one-liners - nfagerlund

Title: Message Title










 

 gepetto-bot commented on an issue











 






  Re: PR (2361): (maint) Improve Puppet::Util::Docs.scrub's handling of one-liners - nfagerlund 










Pull request (maint) Improve Puppet::Util::Docs.scrub's handling of one-liners has been closed.












   

 Add Comment











 













 Puppet /  PUP-1708



  PR (2361): (maint) Improve Puppet::Util::Docs.scrub's handling of one-liners - nfagerlund 







 h2. (maint) Improve Puppet::Util::Docs.scrub's handling of one-liners   * Author: Nick Fagerlund <>  * Company:   * Github ID: [nfagerlund|https://github.com/nfagerlund]  * [Pull Request 2361 Discussion|https://github.com/puppetlabs/puppet/pull/2361]  * [Pull Request 2361 File Diff|https://github.com/puppetlabs/puppet/pull/2361/files]  h2. Pull Request De...















 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://g

Jira (HI-220) Interpolation functions can cause infinite recursion when used in the settings file

Title: Message Title










 

 Charlie Sharpsteen created an issue











 






 Hiera /  HI-220



  Interpolation functions can cause infinite recursion when used in the settings file 










Issue Type:

  Bug




Affects Versions:


 1.3.0




Assignee:


 Unassigned




Created:


 25/Feb/14 8:05 PM




Environment:


CentOS 6.5 Hiera 1.3.1 from PL yum repos




Priority:

  Normal




Reporter:

 Charlie Sharpsteen










Given the following hiera.yaml file where an interpolation function is used to define the hierarchy:



---
:backends:
  - yaml
:logger: console
:hierarchy:
  - "roles/%{hiera('role')}"
  - common

:yaml:
   :datadir: /etc/puppet/environments/%{environment}/extdata



This will result in infinite recursion on any lookup:



# hiera foo -d
DEBUG: Tue Feb 25 19:57:34 -0800 2014: Hiera YAML backend starting
DEBUG: Tue Feb 25 19:57:34 -0800 2014: Looking up foo in YAML backend
DEBUG: Tue Feb 25 19:57:34 -0800 2014: Looking up role in YAML backend

... repeats for a bit ...
DEBUG: Tue Feb 25 19:57:34 -0800 2014: Looking up role in YAML backend
DEBUG: Tue Feb 25 19:57:39 -0800

Jira (HI-220) Interpolation functions can cause infinite recursion when used in the settings file

Title: Message Title










 

 Charlie Sharpsteen updated an issue











 






 Hiera /  HI-220



  Interpolation functions can cause infinite recursion when used in the settings file 










Change By:

 Charlie Sharpsteen









 Given the following {{hiera.yaml}} file where an interpolation function is used to define the hierarchy:{code}---:backends:  - yaml:logger: console:hierarchy:  - "roles/%{hiera('role')}"  - common:yaml:   :datadir: /etc/puppet/environments/%{environment}/extdata{code}This will result in infinite recursion on any lookup:{code}# hiera foo -dDEBUG: Tue Feb 25 19:57:34 -0800 2014: Hiera YAML backend startingDEBUG: Tue Feb 25 19:57:34 -0800 2014: Looking up foo in YAML backendDEBUG: Tue Feb 25 19:57:34 -0800 2014: Looking up role in YAML backend... repeats for a bit ...  DEBUG: Tue Feb 25 19:57:34 -0800 2014: Looking up role in YAML backendDEBUG: Tue Feb 25 19:57:39 -0800 2014: Looking up role in YAML backendDEBUG: Tue Feb 25 19:57:39 -0800 2014: Looking up role in YAML backend/usr/lib/ruby/site_ruby/1.8/hiera/backend.rb:172:in `lookup': stack level too deep (SystemStackError) from /usr/lib/ruby/site_ruby/1.8/hiera/backend.rb:171:in `each' from /usr/lib/ruby/site_ruby/1.8/hiera/backend.rb:171:in `lookup' from /usr/lib/ruby/site_ruby/1.8/hiera/interpolate.rb:43:in `hiera_interpolate' from /usr/lib/ruby/site_ruby/1.8/hiera/interpolate.rb:13:in `send' from /usr/lib/ruby/site_ruby/1.8/hiera/interpolate.rb:13:in `interpolate' from /usr/lib/ruby/site_ruby/1.8/hiera/recursive_guard.rb:16:in `check' from /usr/lib/ruby/site_ruby/1.8/hiera/interpolate.rb:11:in `interpolate' from /usr/lib/ruby/site_ruby/1.8/hiera/backend.rb:93:in `parse_string'  ... 1747 levels... from /usr/lib/ruby/site_ruby/1.8/hiera/backend.rb:171:in `each' from /usr/lib/ruby/site_ruby/1.8/hiera/backend.rb:171:in `lookup' from /usr/lib/ruby/site_ruby/1.8/hiera.rb:60:in `lookup' from /usr/bin/hiera:221{code}The [docs mention|http://docs.puppetlabs.com/hiera/1/variables.html#the-hiera-lookup-function] that using {{hiera()}}:{quote}...generally nonsensical and not useful in Hiera’s settings{quote}However, there are some semi-useful use cases. For example, the following hierarchy is functional:{code}:hierarchy:  -  "  %{::certname} "  # <-- "role" is defined here. Always.  - "roles/%{hiera('role')}"  - common{code}Given that infinite recursion is A Bad Thing™, we should either guard this use case or disallow the use of interpolation functions in the Hiera settings file.












   

 Add Comment

Jira (PUP-1510) ensure => absent on user resource with forcelocal => true does not work as expected.

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1510



  ensure => absent on user resource with forcelocal => true does not work as expected. 










Change By:

 Kylo Ginsberg




Fix Version/s:

 3.5.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/groups/opt_out.

Jira (PUP-1510) ensure => absent on user resource with forcelocal => true does not work as expected.

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1510



  ensure => absent on user resource with forcelocal => true does not work as expected. 










Change By:

 Kylo Ginsberg




Sprint:

 Week 2014-2-26 to 2014-3-5












   

 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/groups/opt_out.

Jira (PUP-1760) Update win32-security gem to latest (after string_to_sid fix)

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: Update win32-security gem to latest (after string_to_sid fix) 










He's released 0.2.5, but we are explicitly trying to catch Win32::Security::SID::Error in at least one place, and that exception class no longer exists in the ffi branch. So we will need to update puppet before we can bring in the new version of win32-security.












   

 Add Comment











 













 Puppet /  PUP-1760



  Update win32-security gem to latest (after string_to_sid fix) 







 Hoping for 3.5.0 but not a blocker.   We have a small blocker to upgrading to the latest win32-security gem. It seems to truncate the  binary representation of the SID when calling Win32::Security::SID.string_to_sid('some sid'). We rely on this method in several places so we need to get this fixed prior to upgrading our gem. For more information, pleas...















 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@google

Jira (PUP-1510) ensure => absent on user resource with forcelocal => true does not work as expected.

Title: Message Title










 

 Kylo Ginsberg updated an issue











 






 Puppet /  PUP-1510



  ensure => absent on user resource with forcelocal => true does not work as expected. 










Change By:

 Kylo Ginsberg




Story Points:

 1












   

 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/groups/opt_out.

Jira (PUP-1284) win32-security gem doesn't handle 'Authenticated Users' correctly

Title: Message Title










 

 Joshua Cooper assigned an issue to Joshua Cooper











 






 Puppet /  PUP-1284



  win32-security gem doesn't handle 'Authenticated Users' correctly 










Change By:

 Joshua Cooper




Assignee:

 Joshua Cooper












   

 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/groups/opt_out.

Jira (PUP-1284) win32-security gem doesn't handle 'Authenticated Users' correctly

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: win32-security gem doesn't handle 'Authenticated Users' correctly 










Merged into the 1.9.3 branch of puppet-win32-ruby in commit 155ebf0.
Another option would have been to pull in the 0.2.5 win32-security gem that was released today. It addresses both PUP-1284 and PUP-1760, but removes an exception class that puppet explicitly tries to catch. We'll need to resolve that prior to rebasing the vendored gem.












   

 Add Comment











 













 Puppet /  PUP-1284



  win32-security gem doesn't handle 'Authenticated Users' correctly 







 If you attempt to add a user to the 'Authenticated Users' group, the owner/group of a file, etc the win32-security gem incorrectly maps this to SID `S-1-5-0` instead of `S-1-5-11`. The gem calls `String#strip` on the binary SID structure, which is of the form: "...x0bx00", and 0x0b is vertical tab, which ruby considers to be white space, and strips it.  ...















 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

Jira (PUP-1284) win32-security gem doesn't handle 'Authenticated Users' correctly

Title: Message Title










 

 Joshua Cooper commented on an issue











 






  Re: win32-security gem doesn't handle 'Authenticated Users' correctly 










To verify this issue, clone the puppet-win32-ruby repo into C:\work\puppet-win32-ruby



C:\work\puppet-win32-ruby> .\ruby\bin\ruby.exe -r win32/security -e "puts Win32::Security::SID.new('Authenticated Users')"
S-1-5-11



Previously, the win32-security gem would return 'S-1-5-0'












   

 Add Comment











 













 Puppet /  PUP-1284



  win32-security gem doesn't handle 'Authenticated Users' correctly 







 If you attempt to add a user to the 'Authenticated Users' group, the owner/group of a file, etc the win32-security gem incorrectly maps this to SID `S-1-5-0` instead of `S-1-5-11`. The gem calls `String#strip` on the binary SID structure, which is of the form: "...x0bx00", and 0x0b is vertical tab, which ruby considers to be white space, and strips it.  ...















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

Jira (PUP-1284) win32-security gem doesn't handle 'Authenticated Users' correctly