Jira (PUP-2940) Installing and using puppet with CentOS7 RHEL7
Title: Message Title Eric Shamow commented on an issue Re: Installing and using puppet with CentOS7 RHEL7 Wondering if the gem provider does an update - I'll do a --debug run. I don't run any gem update explicitly, but I do install a few packages using the gem provider via the DSL. -Eric Add Comment Puppet / PUP-2940 Installing and using puppet with CentOS7 RHEL7 Hi, Has anyone successfully installed and used puppet on Centos7/RHEL7. I have added the EL7 Puppet labs repo and installed the RPM and its installing ruby from the CentOS base repo which is version 2.0, added the below dependancies that have been installed. However when trying to run commands I am getting the below. I had to install RVM with 1.9... 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
Jira (PUP-2940) Installing and using puppet with CentOS7 RHEL7
Title: Message Title Eric Shamow commented on an issue Re: Installing and using puppet with CentOS7 RHEL7 Yup, looks like it does: Debug: Executing '/bin/gem list --local' Debug: Executing '/bin/gem list --local ^rubygems-update$' Debug: Executing '/bin/gem install --no-rdoc --no-ri rubygems-update' And looking at the package type code, it looks like it calls update on the provider as the first step when being initialized. So by default that command's going to run if you use the gem provider at all. -Eric Add Comment Puppet / PUP-2940 Installing and using puppet with CentOS7 RHEL7 Hi, Has anyone successfully installed and used puppet on Centos7/RHEL7. I have added the EL7 Puppet labs repo and installed the RPM and its installing ruby from the CentOS base repo which is version 2.0, added the below dependancies that have been installed. However when trying to run commands I am getting the below. I had to install RVM with 1.9... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3319) client should retry if connection to master fails
Title: Message Title Julien Pivotto commented on an issue Re: client should retry if connection to master fails Implemented in PR https://github.com/puppetlabs/puppet/pull/3107 Add Comment Puppet / PUP-3319 client should retry if connection to master fails It would be nice if the client retried several times over say a 30-second period when it can't connect to the master. Use case 1: Restart the puppetmaster while a client is busy processing a catalog. At present, the client will fail to fetch any files with puppet:/// source URLs, leading to many error messages on the client. Use case 2: Run puppe... 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-3325) logrotate entry doubled for puppetmaster logfile
Title: Message Title
Reiner Keller created an issue
Puppet / PUP-3325
logrotate entry doubled for puppetmaster logfile
Issue Type:
Bug
Assignee:
Unassigned
Created:
22/Sep/14 4:50 AM
Priority:
Normal
Reporter:
Reiner Keller
Hello, we get regulary this failure message by logrotate:
# /etc/cron.daily/logrotate
error: puppetmaster:1 duplicate log entry for /var/log/puppet/masterhttp.log
A short look shows that it's a little misconfiguration by your package logrotate setup:
# grep /var/log/puppet *
puppet:/var/log/puppet/*log {
puppet-dashboard:/var/log/puppet-dashboard/*/*.log {
puppetmaster:/var/log/puppet/masterhttp.log {
# dpkg -S /etc/logrotate.d/puppet
puppet: /etc/logrotate.d/puppet
# dpkg -S /etc/logrotate.d/puppetmaster
puppetmaster: /etc/logrotate.d/puppetmaster
# aptitude show puppet puppetmaster | grep -e Package -e Version -e Maintainer -e ^$
Package: puppet
Version: 2.7.26-1puppetlabs1
Maintainer: Puppet Labs i...@puppetlabs.com
Package: puppetmaster
Version: 2.7.26-1puppetlabs1
Maintainer: Puppet Labs i...@puppetlabs.com
Problem: puppet and puppetmaster seems not use own logfiles but logs both to syslog ... so this is an uneccesary bug, too Would be nice if this can be fixed within next updates nearby. Thx.
Jira (PUP-2940) Installing and using puppet with CentOS7 RHEL7
Title: Message Title Charlie Sharpsteen commented on an issue Re: Installing and using puppet with CentOS7 RHEL7 Eric Shamow: Are you using the puppetlabs-ruby module? I know the current version of that module updates rubygems by default unless you specify rubygems_update = false in the class parameters. Add Comment Puppet / PUP-2940 Installing and using puppet with CentOS7 RHEL7 Hi, Has anyone successfully installed and used puppet on Centos7/RHEL7. I have added the EL7 Puppet labs repo and installed the RPM and its installing ruby from the CentOS base repo which is version 2.0, added the below dependancies that have been installed. However when trying to run commands I am getting the below. I had to install RVM with 1.9... 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,
Jira (PUP-3326) Sun package provider versionable
Title: Message Title
Jay Wallace created an issue
Puppet / PUP-3326
Sun package provider versionable
Issue Type:
New Feature
Affects Versions:
3.6.2
Assignee:
Kylo Ginsberg
Components:
Types and Providers
Created:
22/Sep/14 7:42 AM
Labels:
customer
Priority:
Normal
Reporter:
Jay Wallace
If one runs
puppet resource package packagename
a resource similar to a versionable one is returned, though the sun package provider is currently not versionable.
Example:
# /opt/puppet/bin/puppet resource package SUNWxvnc
package { 'SUNWxvnc':
ensure = '6.6.2.0500,REV=0.2008.02.15',
}
Jira (PDB-854) PR (1072): (maint)(packaging) Updates to packaging for improved systemd support and PID dir handling - shrug
Title: Message Title gepetto-bot commented on an issue Re: PR (1072): (maint)(packaging) Updates to packaging for improved systemd support and PID dir handling - shrug kbarber commented: Obligatory ping . Add Comment PuppetDB / PDB-854 PR (1072): (maint)(packaging) Updates to packaging for improved systemd support and PID dir handling - shrug h2. (maint)(packaging) Updates to packaging for improved systemd support and PID dir handling * Author: * Company: * Github ID: [shrug|https://github.com/shrug] * [Pull Request 1072 Discussion|https://github.com/puppetlabs/puppetdb/pull/1072] * [Pull Request 1072 File Diff|https://github.com/puppetlabs/puppetdb/pull/1072/files] h2. Pull Reques... 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,
Jira (PDB-864) PR (138): Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini - robinbowes
Title: Message Title gepetto-bot commented on an issue Re: PR (138): Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini - robinbowes kbarber commented: @robinbowes not sure if you have seen my comments yet ^^ Add Comment PuppetDB / PDB-864 PR (138): Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini - robinbowes h2. Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini * Author: Robin Bowes robin.bo...@yo61.com * Company: YO61 Ltd * Github ID: [robinbowes|https://github.com/robinbowes] * [Pull Request 138 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/138] * [Pull Request 138 File Diff|https://github.com/puppetlab... 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-3314) Assign new OID in registeredExtensions space for 'pp_role'
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3314 Assign new OID in registeredExtensions space for 'pp_role' Change By: Charlie Sharpsteen Issue Type: Bug Improvement 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-3284) Write scripts to compile profile data
Title: Message Title Britt Gresham updated an issue Puppet / PUP-3284 Write scripts to compile profile data Change By: Britt Gresham Sprint: Platform2014-10-01 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-864) PR (138): Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini - robinbowes
Title: Message Title gepetto-bot commented on an issue Re: PR (138): Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini - robinbowes robinbowes commented: Hey Ken - I did, but have not had chance to revisit yet. Will maybe look today at the contributor summit. Are you here? Add Comment PuppetDB / PDB-864 PR (138): Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini - robinbowes h2. Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini * Author: Robin Bowes robin.bo...@yo61.com * Company: YO61 Ltd * Github ID: [robinbowes|https://github.com/robinbowes] * [Pull Request 138 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/138] * [Pull Request 138 File Diff|https://github.com/puppetlab... 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
Jira (PUP-3327) puppet error in puppetmaster
Title: Message Title Dawn Foster moved an issue Puppet / PUP-3327 puppet error in puppetmaster Change By: Dawn Foster Workflow: Engineering Platform Workflow Key: ASK PUP - 56 3327 Project: AskWebsite Puppet 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-3327) puppet error in puppetmaster
Title: Message Title
Dawn Foster commented on an issue
Re: puppet error in puppetmaster
This was mis-filed in the ask.puppetlabs.com website bug project. I've moved it to the Puppet project for further triage.
Add Comment
Puppet / PUP-3327
puppet error in puppetmaster
{noformat} err: /File[/var/lib/puppet/lib]: Failed to generate additional resources using 'eval_generate: SSL_connect returned=1 errno=0 state=SSLv3 read finished A: tlsv1 alert decrypt error err: /File[/var/lib/puppet/lib]: Could not evaluate: SSL_connect returned=1 errno=0 state=SSLv3 read finished A: tlsv1 alert decrypt error Could not retrieve 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-3239) Add a validate method to Puppet::Node::Environment so the Compiler can easily halt for environments with bad configuration.
Title: Message Title Britt Gresham assigned an issue to Britt Gresham Puppet / PUP-3239 Add a validate method to Puppet::Node::Environment so the Compiler can easily halt for environments with bad configuration. Change By: Britt Gresham Assignee: BrittGresham 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-2940) Installing and using puppet with CentOS7 RHEL7
Title: Message Title Eric Shamow commented on an issue Re: Installing and using puppet with CentOS7 RHEL7 Charlie Sharpsteen indeed I am, and here's an interesting thing I found: If I install via the RPMs, you are correct, the gem update screws the pooch. Without even using puppetlabs-ruby, just installing the dependencies and running gem update does it. If however I install puppet via gem, it does not. Neither puppet apply -e 'include ruby' nor gem update causes the json lookup to fail. This suggests a packaging problem to me for el7...? Add Comment Puppet / PUP-2940 Installing and using puppet with CentOS7 RHEL7 Hi, Has anyone successfully installed and used puppet on Centos7/RHEL7. I have added the EL7 Puppet labs repo and installed the RPM and its installing ruby from the CentOS base repo which is version 2.0, added the below dependancies that have been installed. However when trying to run commands I am getting the below. I had to install RVM with 1.9... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-661) macauthorization provider is broken on 10.9 (mavericks)
Title: Message Title Nigel Kersten commented on an issue Re: macauthorization provider is broken on 10.9 (mavericks) Gary Larizza have you worked on this much lately? We're looking at sorting this out at the contributor summit. Do you think it's critical to switch to to two types? I'd quite like to keep backwards compatibility on the interface, and add 10.9 support to the existing base and two types breaks that. (this is all with the goal of pulling things out of core) Add Comment Puppet / PUP-661 macauthorization provider is broken on 10.9 (mavericks) In OS X 10.9, `/etc/authorization` has been deprecated; as of the GM, the update will move `/etc/authorization` to `/etc/authorization.deprecated`. There is now `/System/Library/Security/authorization.plist` but it seems to just be the defaults; changing a right with the `security authorizationdb` command doesn't change that file, but instead updates... 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
Jira (PUP-2517) Puppet fails with XML output when trying to provision from .pp file
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2517 Puppet fails with XML output when trying to provision from .pp file Change By: Josh Cooper Labels: windows 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-2517) Puppet fails with XML output when trying to provision from .pp file
Title: Message Title Ethan Brown commented on an issue Re: Puppet fails with XML output when trying to provision from .pp file Apparently this was fixed in Vagrant 1.6.5. Closing as won't fix. Add Comment Puppet / PUP-2517 Puppet fails with XML output when trying to provision from .pp file The output when trying to provision from vagrant: == default: Running Puppet with site.pp... INFO interface: info: # CLIXML INFO interface: info: == default: # CLIXML == default: # CLIXML INFO interface: info: Objs Version=1.1.0.1 xmlns=http://schemas.microsoft.c om/powershell/2004/04S S=ErrorUnexpected token 'env:FACTER_... 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-661) macauthorization provider is broken on 10.9 (mavericks)
Title: Message Title Gary Larizza commented on an issue Re: macauthorization provider is broken on 10.9 (mavericks) I really haven't, no. There was a reason I split them out, but it's been so long I forgot. Honestly I just coded it up to see if it would work, so I'm open to other designs. Add Comment Puppet / PUP-661 macauthorization provider is broken on 10.9 (mavericks) In OS X 10.9, `/etc/authorization` has been deprecated; as of the GM, the update will move `/etc/authorization` to `/etc/authorization.deprecated`. There is now `/System/Library/Security/authorization.plist` but it seems to just be the defaults; changing a right with the `security authorizationdb` command doesn't change that file, but instead updates... 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 (PDB-864) PR (138): Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini - robinbowes
Title: Message Title gepetto-bot commented on an issue Re: PR (138): Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini - robinbowes robinbowes commented: tl;dr: what behaviour do you want here? I've reviewed this, and I think the current behaviour is sane. If $ssl_set_cert_paths is true, then the cert paths are set. But if it's something else then you wouldn't necessarily want to remove any cert paths. It might make sense to add some additional checks and, eg. fail if $ssl_set_cert_paths = true and $disable_ssl = true ? Thoughts? R. Add Comment PuppetDB / PDB-864 PR (138): Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini - robinbowes h2. Add the ability to a) deploy ssl keys, b) set paths to ssl keys in jetty.ini * Author: Robin Bowes robin.bo...@yo61.com * Company: YO61 Ltd * Github ID: [robinbowes|https://github.com/robinbowes] * [Pull Request 138 Discussion|https://github.com/puppetlabs/puppetlabs-puppetdb/pull/138] * [Pull Request 138 File Diff|https://github.com/puppetlab... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (HI-183) Really need the ability to lookup hashes and arrays from other parts of Hiera.
Title: Message Title Dan Bode commented on an issue Re: Really need the ability to lookup hashes and arrays from other parts of Hiera. I took at stab at updating Michael's code and submitted it as: https://github.com/puppetlabs/hiera/pull/213 Add Comment Hiera / HI-183 Really need the ability to lookup hashes and arrays from other parts of Hiera. So, back in the old Redmine system, there was feature #23323 (http://projects.puppetlabs.com/issues/23323), which needed to be able to look up hashes and arrays from other parts of Hiera. I would like to reinstate that request here since the current solution only partially meets common data management consolidation needs. For instance, consider this... 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-2940) Installing and using puppet with CentOS7 RHEL7
Title: Message Title Charlie Sharpsteen commented on an issue Re: Installing and using puppet with CentOS7 RHEL7 This suggests a packaging problem to me for el7...? Of sorts. So, the problem is: If you install a RPM that packages a gem, such as rubygem-json, then you must install the packaged version of rubygems and never update it outside of yum or rpm. Running gem update --system installs a new version of rubygems that is disconnected from the gems installed by RPM packages. Gems installed directly through gem instead of delivered via RPM seem to remain functional after rubygems updates. I think the core of the issue is that using one package manager (rpm) to install and manage artifacts created and managed by another package manager (gem) is just asking for trouble. In contrast, Debian does not have a rubygems-json package, they have a ruby-json package that installs the module into /usr/lib/ruby/site_ruby instead of trying to integrate it into /usr/lib/ruby/gems. Add Comment Puppet / PUP-2940 Installing and using puppet with CentOS7 RHEL7 Hi, Has anyone successfully installed and used puppet on Centos7/RHEL7. I have added the EL7 Puppet labs repo and installed the RPM and its installing ruby from the CentOS base repo which is version 2.0, added the below dependancies that have been installed. However when trying to run commands I am getting the below. I had to install RVM with 1.9...
Jira (PUP-3328) tidy should follow symlinks
Title: Message Title
Cosmin Lehene created an issue
Puppet / PUP-3328
tidy should follow symlinks
Issue Type:
Bug
Affects Versions:
3.x
Assignee:
Cosmin Lehene
Components:
Types and Providers
Created:
22/Sep/14 5:40 PM
Fix Versions:
3.7.2
Priority:
Normal
Reporter:
Cosmin Lehene
tidy uses Fileset which will use either stat or lstat (see code ) depending on :links = :manage | :follow and defaults to {{:manage }}(see code )
As tidy doesn't explicitly set :follow the results may vary if the target dir is a symlink. For example, if trying to tidy /etc/init.d which is a symlink to /etc/rc./d/init.d on CentOS 6/7 it won't work. However tidying /etc/init.d/ (trailing slash) will work.
Again this is consistent with how stat/lstat works
[root@localhost puppet]# stat /etc/init.d/
File: ‘/etc/init.d/’
Size: 4096 Blocks: 8 IO Block: 4096 directory
Device: fd01h/64769d Inode: 75105 Links: 2
Access:
Jira (PUP-3328) tidy should follow symlinks
Title: Message Title
Cosmin Lehene updated an issue
Puppet / PUP-3328
tidy should follow symlinks
Change By:
Cosmin Lehene
tidyusesFilesetwhichwilluseeitherstatorlstat([seecode|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/file_serving/fileset.rb#L80])dependingon{{:links=:manage|:follow}}anddefaultsto{{:manage}}([seecode|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/file_serving/fileset.rb#L40])Astidydoesn'texplicitlyset{{:follow}}theresultsmayvaryifthetargetdirisasymlink.Forexample,iftryingtotidy{{/etc/init.d}}whichisasymlinkto{{/etc/rc./d/init.d}}onCentOS6/7itwon'twork.Howevertidying{{/etc/init.d/}}(trailingslash)willwork.Againthisisconsistentwithhowstat/lstatworks{noformat}[root@localhostpuppet]#stat/etc/init.d/File:‘/etc/init.d/’Size:4096 Blocks:8IOBlock:4096directoryDevice:fd01h/64769d Inode:75105Links:2Access:(0755/drwxr-xr-x)Uid:(0/root)Gid:(0/root)Access:2014-09-2305:22:27.351955472+0900Modify:2014-09-1703:34:15.521690654+0900Change:2014-09-1703:34:15.521690654+0900Birth:-[root@localhostpuppet]#stat/etc/init.dFile:‘/etc/init.d’-‘rc.d/init.d’Size:11 Blocks:0IOBlock:4096symboliclinkDevice:fd01h/64769d Inode:67139111Links:1Access:(0777/lrwxrwxrwx)Uid:(0/root)Gid:(0/root)Access:2014-09-2302:08:38.295890037+0900Modify:2014-08-1802:53:43.335191310+0900Change:2014-08-1802:53:43.335191310+0900Birth:-[root@localhostpuppet]#stat-L/etc/init.dFile:‘/etc/init.d’Size:4096 Blocks:8IOBlock:4096directoryDevice:fd01h/64769d Inode:75105Links:2Access:(0755/drwxr-xr-x)Uid:(0/root)Gid:(0/root)Access:2014-09-2305:22:27.351955472+0900Modify:2014-09-1703:34:15.521690654+0900Change:2014-09-1703:34:15.521690654+0900Birth:-{noformat}Insteadtidyshouldexplicitlyset{{:links=:follow}}oratleasthaveitconfigurable(orboth).
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3328) tidy should follow symlinks
Title: Message Title Cosmin Lehene updated an issue Puppet / PUP-3328 tidy should follow symlinks Attached patch. Note that I tested this change (in tidy) directly on a VM. I added a test, but was unable (yet) to run the test locally (hints are welcome). Change By: Cosmin Lehene Attachment: 0001-PUP-3328-tidy-should-follow-symlinks.patch 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-1531) Puppet Master unable to find module if the directory is a symlink
Title: Message Title Cosmin Lehene commented on an issue Re: Puppet Master unable to find module if the directory is a symlink I found this issue while searching jira for symlink. I'm not sure what the code path for master is, but it may be related to use of stat vs lstat. see PUP-3328. Add Comment Puppet / PUP-1531 Puppet Master unable to find module if the directory is a symlink During development of a module, I had a git checkout in my home directory and symlinked it into /etc/puppet/modules. Then I classified the output via dashboard. I found that Puppet Master would not find the class/module since the module was a symlink. I searched other tickets and didn't see this already filed, but it very well could be. Testing on 2... 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,
Jira (PUP-3328) tidy should follow symlinks
Title: Message Title
Cosmin Lehene updated an issue
Puppet / PUP-3328
tidy should follow symlinks
Change By:
Cosmin Lehene
tidyusesFilesetwhichwilluseeitherstatorlstat([seecode|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/file_serving/fileset.rb#L80])dependingon{{:links=:manage|:follow}}anddefaultsto{{:manage}}([seecode|https://github.com/puppetlabs/puppet/blob/master/lib/puppet/file_serving/fileset.rb#L40])Astidydoesn'texplicitlyset{{:follow}}theresultsmayvaryifthetargetdirisasymlink.Forexample,iftryingtotidy{{/etc/init.d}}whichisasymlinkto{{/etc/rc./d/init.d}}onCentOS6/7itwon'twork. -- Howevertidying{{/etc/init.d/}}(trailingslash)willwork .Againthisisconsistentwithhowstat/lstatworks{noformat}[root@localhostpuppet]#stat/etc/init.d/File:‘/etc/init.d/’Size:4096 Blocks:8IOBlock:4096directoryDevice:fd01h/64769d Inode:75105Links:2Access:(0755/drwxr - xr - x)Uid:(0/root)Gid:(0/root)Access:2014-09-2305:22:27 . 351955472+0900 Modify:2014-09-1703:34:15.521690654+0900 Change:2014-09-1703:34:15.521690654+0900Birth:-[root@localhostpuppet]#stat/etc/init.dFile:‘/etc/init.d’-‘rc.d/init.d’Size:11 Blocks:0IOBlock:4096symboliclinkDevice:fd01h/64769d Inode:67139111Links:1Access:(0777/lrwxrwxrwx)Uid:(0/root)Gid:(0/root)Access:2014-09-2302:08:38.295890037+0900Modify:2014-08-1802:53:43.335191310+0900Change:2014-08-1802:53:43.335191310+0900Birth:-[root@localhostpuppet]#stat-L/etc/init.dFile:‘/etc/init.d’Size:4096 Blocks:8IOBlock:4096directoryDevice:fd01h/64769d Inode:75105Links:2Access:(0755/drwxr-xr-x)Uid:(0/root)Gid:(0/root)Access:2014-09-2305:22:27.351955472+0900Modify:2014-09-1703:34:15.521690654+0900Change:2014-09-1703:34:15.521690654+0900Birth:-{noformat} Insteadtidyshouldexplicitlyset{{:links=:follow}}oratleasthaveitconfigurable(orboth).
Add Comment
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-3328) tidy should follow symlinks
Title: Message Title
Cosmin Lehene commented on an issue
Re: tidy should follow symlinks
Updated description. It doesn't work when having the symlink with a trailing slash either (I saw local change artefact) as Filset's initialize chomps it (here )
Add Comment
Puppet / PUP-3328
tidy should follow symlinks
tidy uses Fileset which will use either stat or lstat ([see code | https://github.com/puppetlabs/puppet/blob/master/lib/puppet/file_serving/fileset.rb#L80]) depending on {{:links = :manage | :follow}} and defaults to {{:manage }} ([see code | https://github.com/puppetlabs/puppet/blob/master/lib/puppet/file_serving/fileset.rb#L40]) As tidy doesn't exp...
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.
