Jira (PUP-2706) Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
Title: Message Title Kenneth Barber updated an issue Puppet / PUP-2706 Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build Change By: Kenneth Barber Summary: Intermittent 'chage' PuppetinstallationfailureonUbuntu14.04duringPDBbuild 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-2706) Intermittent Puppet installation failure on Ubuntu 14.04 during PDB build
Title: Message Title Kenneth Barber created an issue Puppet / PUP-2706 Intermittent Puppet installation failure on Ubuntu 14.04 during PDB build Issue Type: Bug Assignee: Unassigned Created: 02/Jun/14 5:59 AM Priority: Normal Reporter: Kenneth Barber We keep getting this error during Puppet installation for our PuppetDB builds: Setting up ruby-augeas (0.5.0-2) ... Setting up libaugeas-ruby (0.5.0-2) ... Setting up ruby-shadow (2.2.0-1) ... Setting up ruby-json (1.8.0-1build1) ... Setting up hiera (1.3.3-1puppetlabs1) ... Setting up puppet-common (3.6.1-1puppetlabs1) ... chage: the shadow password file is not present /usr/bin/chage failed with return code 15, shadow not enabled, password aging cannot be set. Continuing. chfn: PAM: Authentication failure adduser: `/usr/bin/chfn -f Puppet configuration management daemon puppet' returned error code 1. Exiting. dpkg: error processing package puppet-common (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of puppet: puppet depends on puppet-common (= 3.6.1-1puppetlabs1); however: Package puppet-common is not configured yet. dpkg: error processing package puppet (--configure): dependency problems - leaving unconfigured Processing triggers for libc-bin (2.19-0ubuntu6) ... Processing triggers for ca-certificates (20130906ubuntu2) ... Updating certificates in /etc/ssl/certs... 164 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.ddone. Errors were encountered while processing: puppet-common puppet E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: Setting up puppet-common (3.6.1-1puppetlabs1) ... Setting up puppet (3.6.1-1puppetlabs1) ... initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused invoke-rc.d: policy-rc.d denied execution of start.
Jira (PUP-2706) Intermittent Puppet installation failure on Ubuntu 14.04 during PDB build
Title: Message Title
Kenneth Barber commented on an issue
Re: Intermittent Puppet installation failure on Ubuntu 14.04 during PDB build
Moses Mendoza Matthaus Owens a ticket to track the chage problem as requested.
Add Comment
Puppet / PUP-2706
Intermittent Puppet installation failure on Ubuntu 14.04 during PDB build
We keep getting this error during Puppet installation for our PuppetDB builds: {code} Setting up ruby-augeas (0.5.0-2) ... Setting up libaugeas-ruby (0.5.0-2) ... Setting up ruby-shadow (2.2.0-1) ... Setting up ruby-json (1.8.0-1build1) ... Setting up hiera (1.3.3-1puppetlabs1) ... Setting up puppet-common (3.6.1-1puppetlabs1) ... chage: the sha...
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-280) Measure PuppetDB AWS costs by integrating it fully into Cloudability
Title: Message Title Kenneth Barber commented on an issue Re: Measure PuppetDB AWS costs by integrating it fully into Cloudability The filter can be modified to look for Project (value) = PuppetDB. Since most beaker projects should be using the project field by now. I've created an alternate filter called PuppetDB testing (kbarber) to show an example of this. I think this can be closed, its been open for ages and I don't see what else needs to be done now. Add Comment PuppetDB / PDB-280 Measure PuppetDB AWS costs by integrating it fully into Cloudability [~alice] [~ken] and [~deepak] I made you all User accounts in Cloudability, you should have invites to your work address. It was suggested there that I assign this straight to you Alice. Adding [~jrod] and [~zach] as cloud service owners in Ops. We'd like to measure the cost of PuppetDB testing in AWS so we know whether we should bring it in house, ... 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 (PDB-697) Document and test new query features from query engine refactor
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-697 Document and test new query features from query engine refactor Issue Type: New Feature Assignee: Unassigned Created: 02/Jun/14 6:50 AM Priority: Normal Reporter: Ryan Senior PDB-658 added a lot of new queryable fields and query operators to existing queries by refactoring it to use the new engine. Ultimately, an extensive test suite around the engine itself (query combinations etc) would be best. Probably the easiest thing now is to create some basic tests for each endpoint to verify the new fields/operators and document the new stuff at the same time. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2691) Real-world module skeletons still use the 'description' metadata property
Title: Message Title Peter Souter updated an issue Puppet / PUP-2691 Real-world module skeletons still use the 'description' metadata property Change By: Peter Souter Assignee: PietervandeBruggen 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-698) Use underscores instead of dashes in responses
Title: Message Title Erik Daln created an issue PuppetDB / PDB-698 Use underscores instead of dashes in responses Issue Type: Improvement Assignee: Unassigned Created: 02/Jun/14 7:31 AM Priority: Normal Reporter: Erik Daln It would be good if the PuppetDB API used underscores instead of dashes. Especially for _javascript_ it is cleaner if you can write stuff like node.catalog_timestamp instead of having to write node[catalog-timestamp]. This is mostly a issue in the response formats, and to a lesser extent in the parameter names. Not really a issue IMO in the endpoint names, but can perhaps be a value in consistency here. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-698) Use underscores instead of dashes in responses
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-698 Use underscores instead of dashes in responses Change By: Kenneth Barber Story Points: 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/d/optout.
Jira (PDB-698) Use underscores instead of dashes in responses
Title: Message Title Daniele Sluijters commented on an issue Re: Use underscores instead of dashes in responses +1, it feels really weird from Python too. Add Comment PuppetDB / PDB-698 Use underscores instead of dashes in responses It would be good if the PuppetDB API used underscores instead of dashes. Especially for _javascript_ it is cleaner if you can write stuff like node.catalog_timestamp instead of having to write node[catalog-timestamp]. This is mostly a issue in the response formats, and to a lesser extent in the parameter names. Not really a issue IMO in the endpoint na... 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-698) Use underscores instead of dashes in responses
Title: Message Title Kenneth Barber commented on an issue Re: Use underscores instead of dashes in responses Daniele Sluijters can you provide code examples to back up that statement in python? Add Comment PuppetDB / PDB-698 Use underscores instead of dashes in responses It would be good if the PuppetDB API used underscores instead of dashes. Especially for _javascript_ it is cleaner if you can write stuff like node.catalog_timestamp instead of having to write node[catalog-timestamp]. This is mostly a issue in the response formats, and to a lesser extent in the parameter names. Not really a issue IMO in the endpoint na... 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-698) Use underscores instead of dashes in responses
Title: Message Title
Daniele Sluijters commented on an issue
Re: Use underscores instead of dashes in responses
As I said it's mostly feel, but the same principle that Erik Daln showed applies. I can do node.catalog_timestamp in Python but {{node.catalog-timestamp{{ is just weird and illegal because the hyphen would be interpreted as the subtraction operator.
Having a look at PEP-* everything recommends underscores.
Add Comment
PuppetDB / PDB-698
Use underscores instead of dashes in responses
It would be good if the PuppetDB API used underscores instead of dashes. Especially for _javascript_ it is cleaner if you can write stuff like node.catalog_timestamp instead of having to write node[catalog-timestamp]. This is mostly a issue in the response formats, and to a lesser extent in the parameter names. Not really a issue IMO in the endpoint na...
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-2708) No puppetdoc for subclass not preceded by resource or another subclass
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-2708
No puppetdoc for subclass not preceded by resource or another subclass
Change By:
Charlie Sharpsteen
Using0.24.8onSolaris10.Considerthismodules/test/manifests/init.pp: pre {code} #Testclassclasstest{#Testsubclassclasssubclass{}} /pre {code} puppetdoc(rdocmode)includesbothTestclassandTestsubclasscommentsintheappropriateplaces.However,thiscode: pre {code} #Testclassclasstest{$foo=1#Testsubclassclasssubclass{}} /pre {code} ThistimepuppetdocdoesnotincludeTestsubclassinthepagefortest::subclass.WithsomeexperimentationIfoundthattheprecedingcommentforasubclassdoesgetparsedifthecodebeforeitisa}thatendsaresourceoranothersubclass.Othercode(liketheassignmentabove,orevena}endinganifblock)willcausethesubclassdocblocktobemissed.
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-2708) No puppetdoc for subclass not preceded by resource or another subclass
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-2708
No puppetdoc for subclass not preceded by resource or another subclass
Issue Type:
Bug
Assignee:
Unassigned
Created:
02/Jun/14 8:00 AM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
Using 0.24.8 on Solaris 10. Consider this modules/test/manifests/init.pp: pre
Test class class test {
Test subclass class subclass { } } /pre
puppetdoc (rdoc mode) includes both Test class and Test subclass comments in the appropriate places. However, this code: pre
Test class class test { $foo = 1
Test subclass class subclass { } } /pre This time puppetdoc does not include Test subclass in the page for test::subclass.
With some experimentation I found that the preceding comment for a subclass does get parsed if the code before it is a }
Jira (PUP-2708) Fix puppet doc errors and misbehaviors
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-2708
Fix puppet doc errors and misbehaviors
This is a clone of a Redmine ticket that was cross-references to many other issues. Converting to an epic so that this ticket can better serve as a collection point for {puppet doc}
issues.
Change By:
Charlie Sharpsteen
Component/s:
Modules
Issue Type:
Bug Epic
Summary:
Nopuppetdocforsubclassnotprecededbyresourceoranothersubclass Fixpuppetdocerrorsandmisbehaviors
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
Jira (PUP-2708) Fix puppet doc errors and misbehaviors
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2708 Fix puppet doc errors and misbehaviors Change By: Charlie Sharpsteen Epic Name: puppetdoc 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-2097) Could not evaluate: Failed to get security information: Incorrect function
Title: Message Title
Louis Mayorga commented on an issue
Re: Could not evaluate: Failed to get security information: Incorrect function
This is fixed.
Add Comment
Puppet / PUP-2097
Could not evaluate: Failed to get security information: Incorrect function
It seems that Puppet is not able to get the file permissions using vagrant basic mounted drives. {code} Could not evaluate: Failed to get security information: Incorrect function. Could not retrieve file metadata for puppet:///packages/webpicmd/files/Microsoft.Web.PlatformInstaller.dll: Failed to get security information: Incorrect function. {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-2709) Puppet Agent: fails to run on non english Windows
Title: Message Title Armindo Silva created an issue Puppet / PUP-2709 Puppet Agent: fails to run on non english Windows Issue Type: Bug Affects Versions: 3.6.1 Assignee: Kylo Ginsberg Components: Client Created: 02/Jun/14 8:24 AM Environment: Windows 7 Professional 64 bits PT (Portuguese) Labels: windows Priority: Normal Reporter: Armindo Silva Agent fails on non english Windows with the following error: Running Puppet agent on demand ... Error: Could not run: \xE7 to UTF-8 in conversion from ASCII-8BIT to UTF-8 to UTF-16LE Prima qualquer tecla para continuar . . . Trace:
Jira (PDB-651) PR (962): Allow configurable url prefix - cprice404
Title: Message Title gepetto-bot commented on an issue Re: PR (962): Allow configurable url prefix - cprice404 kbarber commented: @cprice404 looks like a travis test has failed on the / route ^^ Add Comment PuppetDB / PDB-651 PR (962): Allow configurable url prefix - cprice404 h2. Allow configurable url prefix * Author: Chris Price * Company: * Github ID: [cprice404|https://github.com/cprice404] * [Pull Request 962 Discussion|https://github.com/puppetlabs/puppetdb/pull/962] * [Pull Request 962 File Diff|https://github.com/puppetlabs/puppetdb/pull/962/files] h2. Pull Request Description This PR makes it possible... 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-1930) PR (235): [WIP] Add some acceptance tests for functions. - apenney
Title: Message Title Andy Parker updated an issue Puppet / PUP-1930 PR (235): [WIP] Add some acceptance tests for functions. - apenney Change By: Andy Parker Assignee: EricSorenson 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-2710) Audit of mtime/ctime for files on ext4 reports spurious changes (only ruby 1.9+)
Title: Message Title
Kylo Ginsberg created an issue
Puppet / PUP-2710
Audit of mtime/ctime for files on ext4 reports spurious changes (only ruby 1.9+)
Issue Type:
Bug
Assignee:
Kylo Ginsberg
Components:
Catalog Application
Created:
02/Jun/14 8:49 AM
Priority:
Normal
Reporter:
Kylo Ginsberg
[root@master323-centos ~]# puppet --version
3.4.3 (Puppet Enterprise 3.2.3)
[root@master323-centos ~]# /opt/puppet/bin/ruby --version
ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux]
[root@master323-centos ~]# mkdir /tmp/test/
[root@master323-centos ~]# puppet apply -e file { '/tmp/test/watch_me': ensure = directory, audit = [ 'mtime', 'ctime' ] }
Notice: Compiled catalog for master323-centos in environment production in 0.17 seconds
Notice: /Stage[main]/Main/File[/tmp/test/watch_me]/ensure: created
Notice: Finished catalog run in 0.33 seconds
[root@master323-centos ~]# puppet apply -e file { '/tmp/test/watch_me': ensure = directory, audit = [ 'mtime', 'ctime' ] }
Notice: Compiled catalog for master323-centos in environment production in 0.18 seconds
Notice: /Stage[main]/Main/File[/tmp/test/watch_me]/mtime: audit change: previously recorded value absent has been changed to 2014-05-29 18:38:33 +
Notice: /Stage[main]/Main/File[/tmp/test/watch_me]/ctime: audit change: previously recorded value absent has been changed to 2014-05-29 18:38:33 +
Notice: Finished catalog run in 0.31 seconds
[root@master323-centos ~]# puppet apply -e file { '/tmp/test/watch_me': ensure = directory, audit = [ 'mtime', 'ctime' ] }
Notice: Compiled catalog for master323-centos in environment production in 0.16 seconds
Notice: /Stage[main]/Main/File[/tmp/test/watch_me]/mtime: audit change: previously recorded value
Jira (PUP-2710) Audit of mtime/ctime for files on ext4 reports spurious changes (only ruby 1.9+)
Title: Message Title
Kylo Ginsberg commented on an issue
Re: Audit of mtime/ctime for files on ext4 reports spurious changes (only ruby 1.9+)
The root cause here is that when we serialize time objects to a yaml file we preserve nanoseconds, but when we deserialize from a yaml file we only preserve microseconds.
E.g.
[root@w8ydxv4f4qkciox pe-puppet]# bundle exec irb
1.9.3-p547 :001 require 'puppet'
= true
1.9.3-p547 :002 x = Time.now
= 2014-05-29 18:01:12 -0700
1.9.3-p547 :003 x.nsec
= 859338923
1.9.3-p547 :004 Puppet::Util::Yaml.dump(x, '/tmp/foo.yaml')
= #Pathname:/tmp/foo.yaml
1.9.3-p547 :005 after = Puppet::Util::Yaml.load_file('/tmp/foo.yaml')
= 2014-05-29 18:01:12 -0700
1.9.3-p547 :006 after.nsec
= 859338000
I haven't verified this next part, but this may be due to this logic in the yaml library:
https://github.com/puppetlabs/puppet/blob/3.6.1/lib/puppet/vendor/safe_yaml/lib/safe_yaml/parse/date.rb#L21-L23
Note that this would only be seen on filesystems that provide nanosecond granularity in ctime/mtime, e.g. on ext4. And this would only be seen with ruby 1.9+ as it was somewhere in the 1.9 series that nanosecond granularity in the Time object was introduced.
Add Comment
Puppet / PUP-2710
Audit of mtime/ctime for files on ext4 reports spurious changes (only ruby 1.9+)
{noformat} [root@master323-centos ~]# puppet --version 3.4.3 (Puppet Enterprise 3.2.3) [root@master323-centos ~]# /opt/puppet/bin/ruby --version ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux] [root@master323-centos ~]# mkdir /tmp/test/ [root@master323-centos ~]# puppet apply -e file {
Jira (PUP-2692) Puppet master passenger processes keep growing
Title: Message Title Andy Parker assigned an issue to Henrik Lindberg Puppet / PUP-2692 Puppet master passenger processes keep growing Change By: Andy Parker Assignee: HenrikLindberg 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-2211) Confusing ArgumentError exception message when using future parser
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Puppet / PUP-2211 Confusing ArgumentError exception message when using future parser Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen 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-2659) Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
Title: Message Title
Ethan Brown commented on an issue
Re: Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
This has failed CI
See tests/concurrency.ticket_2659_concurrent_catalog_requests.rb
https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/Stable/job/Puppet-Acceptance-Future-Parser-stable-vcloud-and-github/62/label=acc-coord,platform=fedora19/testReport/junit/(root)/tests_concurrency/ticket_2659_concurrent_catalog_requests_rb/
Add Comment
Puppet / PUP-2659
Puppet stops working with error 'Attempted to pop, but already at root of the context stack.'
After upgrading puppet to version 3.6.1, the following error occurs: {noformat} Attempted to pop, but already at root of the context stack. {noformat} And afterwards log is flooded with following message: {noformat} no 'environments' in {:root_environment=#Puppet::Node::Environment:0x7fe1930f5a38 @manifest=/, @modulepath=[], @name=:*root*...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the
Jira (PUP-2583) mode attribute of file type doesn't behave like chmod when given X
Title: Message Title Michal Bryx assigned an issue to Michal Bryx Puppet / PUP-2583 mode attribute of file type doesn't behave like chmod when given X Change By: Michal Bryx Assignee: MichalBryx 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
Title: Message Title Rob Reynolds commented on an issue Re: 3.6.1 issues warning message for deprecation Kylo Ginsberg - what would the default be? 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 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-481) Infinite loop if EC2 metadata server times out
Title: Message Title Adrien Thebo assigned an issue to Adrien Thebo Facter / FACT-481 Infinite loop if EC2 metadata server times out 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-2576) Implement behavioral change in the crontab provider to allow more drastic purging
Title: Message Title Ethan Brown updated an issue Puppet / PUP-2576 Implement behavioral change in the crontab provider to allow more drastic purging Change By: Ethan Brown Sprint: Week2014-6-11to2014-6-18 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-2506) Trivial Ruby bug in Puppet::Resource::Ral
Title: Message Title Carlos Salazar assigned an issue to Carlos Salazar Puppet / PUP-2506 Trivial Ruby bug in Puppet::Resource::Ral Change By: Carlos Salazar Assignee: KyloGinsberg CarlosSalazar 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-2097) Could not evaluate: Failed to get security information: Incorrect function
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2097 Could not evaluate: Failed to get security information: Incorrect function Change By: Joshua Cooper Assignee: LouisMayorga 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-481) Infinite loop if EC2 metadata server times out
Title: Message Title Adrien Thebo commented on an issue Re: Infinite loop if EC2 metadata server times out I was unable to duplicate this on a virtualbox instance: [vagrant@centos6 facter]$ git rev-parse --abbrev-ref HEAD facter-2 [vagrant@centos6 facter]$ git rev-parse HEAD 1a2577f90bec8f9e627c3fbdb16a49883c9e76a2 [vagrant@centos6 facter]$ git branch * facter-2 feature/facter-2/fact-451-cumulus-linux master revert/master/sync-master-and-facter-2 revert/stable/ec2-facts stable [vagrant@centos6 facter]$ FACTER_virtual='' bundle exec bin/facter [...] It returns nearly instantly. Kurt, judging by the errors in the output of facter there might be another installation of facter on the machine you were using, could you check to see if that could be the case? Add Comment Facter / FACT-481 Infinite loop if EC2 metadata server times out On a Rackspace VM, Facter gets into an infinite loop when trying to contact the EC2 metadata server. The retry loop in lib/facter/ec2/rest.rb doesn't increment the counter on each iteration. This causes the Puppet agent to permanently hang. To reproduce on a non-Rackspace system, just run: FACTER_virtual=xen bin/facter (Assuming there's no metada... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-481) Infinite loop if EC2 metadata server times out
Title: Message Title Kurt Wall commented on an issue Re: Infinite loop if EC2 metadata server times out Adrien Thebo Meh. Now I can't reproduce it. PEBKAC. Closing. Add Comment Facter / FACT-481 Infinite loop if EC2 metadata server times out On a Rackspace VM, Facter gets into an infinite loop when trying to contact the EC2 metadata server. The retry loop in lib/facter/ec2/rest.rb doesn't increment the counter on each iteration. This causes the Puppet agent to permanently hang. To reproduce on a non-Rackspace system, just run: FACTER_virtual=xen bin/facter (Assuming there's no metada... 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-2705) External facts pluginsync not preserving executable bit
Title: Message Title Joshua Cooper commented on an issue Re: External facts pluginsync not preserving executable bit Hi Matteo, thank you for debugging the problem and submitting a PR. I've left a comment on the PR. Add Comment Puppet / PUP-2705 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-1498) scheduled_task won't update command
Title: Message Title Rob Reynolds commented on an issue Re: scheduled_task won't update command Perhaps our updates of the gems will help resolve this issue then. Add Comment Puppet / PUP-1498 scheduled_task won't update command if you update a scheduled_task's command, Puppet does not make the change in the task scheduler. Other changes, e.g. the trigger, appear to work, but not the command. I've had to work around by deleting the old task and creating a new one with a different name. 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-2404) Merge puppet 3.6 into pe-puppet 3.3.x
Title: Message Title Kylo Ginsberg commented on an issue Re: Merge puppet 3.6 into pe-puppet 3.3.x Merged up in https://github.com/puppetlabs/pe-puppet/commit/46a118235affc2282d02a202b571f2d9db281941. This bring pe-puppet up to 3.6.1 + part of the 3.6.2 payload. Add Comment Puppet / PUP-2404 Merge puppet 3.6 into pe-puppet 3.3.x pe-puppet/3.3.x is based on puppet 3.6.x 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-1498) scheduled_task won't update command
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-1498 scheduled_task won't update command Change By: Rob Reynolds Component/s: Client 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-2710) Audit of mtime/ctime for files on ext4 reports spurious changes (only ruby 1.9+)
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2710 Audit of mtime/ctime for files on ext4 reports spurious changes (only ruby 1.9+) Change By: Kylo Ginsberg Sprint: Week2014-5-28to2014-6-4 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 (HI-68) PR (165): Use the same kind of gem source switching as Puppet - justinstoller
Title: Message Title Joshua Cooper commented on an issue Re: PR (165): Use the same kind of gem source switching as Puppet - justinstoller This was merged in https://github.com/puppetlabs/hiera/commit/2aa5bfb3be86ca031d3105c48893b06fa0dfffc5 and released in hiera 1.3.1 Add Comment Hiera / HI-68 PR (165): Use the same kind of gem source switching as Puppet - justinstoller h2. Use the same kind of gem source switching as Puppet * Author: Justin Stoller justin.stol...@gmail.com * Company: * Github ID: [justinstoller|https://github.com/justinstoller] * [Pull Request 165 Discussion|https://github.com/puppetlabs/hiera/pull/165] * [Pull Request 165 File Diff|https://github.com/puppetlabs/hiera/pull/165/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 options, visit
Jira (HI-68) PR (165): Use the same kind of gem source switching as Puppet - justinstoller
Title: Message Title Joshua Cooper updated an issue Hiera / HI-68 PR (165): Use the same kind of gem source switching as Puppet - justinstoller Change By: Joshua Cooper Fix Version/s: 1.3.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/d/optout.
Jira (PUP-2660) purging ssh_authorized_key fails because of missing user value
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2660 purging ssh_authorized_key fails because of missing user value 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 (HI-67) PR (164): use pooling api - justinstoller
Title: Message Title Joshua Cooper commented on an issue Re: PR (164): use pooling api - justinstoller This was merged to stable in 9248fa4e and released in 1.3.1 Add Comment Hiera / HI-67 PR (164): use pooling api - justinstoller h2. use pooling api * Author: Justin Stoller justin.stol...@gmail.com * Company: * Github ID: [justinstoller|https://github.com/justinstoller] * [Pull Request 164 Discussion|https://github.com/puppetlabs/hiera/pull/164] * [Pull Request 164 File Diff|https://github.com/puppetlabs/hiera/pull/164/files] h2. Pull Request Description @sschneid ... 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-1142) puppetlabs_spec_helper requires rspec-puppet
Title: Message Title William Van Hevelingen updated an issue Puppet / PUP-1142 puppetlabs_spec_helper requires rspec-puppet Change By: William Van Hevelingen Component/s: TestInfrastructure 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 (HI-70) PR (166): (maint) Add fedora 20 to mock list - melissaanne
Title: Message Title Joshua Cooper commented on an issue Re: PR (166): (maint) Add fedora 20 to mock list - melissaanne Merged to stable in 498416eff released in 1.3.1 Add Comment Hiera / HI-70 PR (166): (maint) Add fedora 20 to mock list - melissaanne h2. (maint) Add fedora 20 to mock list * Author: Melissa * Company: * Github ID: [melissaanne|https://github.com/melissaanne] * [Pull Request 166 Discussion|https://github.com/puppetlabs/hiera/pull/166] * [Pull Request 166 File Diff|https://github.com/puppetlabs/hiera/pull/166/files] h2. Pull Request Description (webhooks-id: d052e... 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-481) Infinite loop if EC2 metadata server times out
Title: Message Title Dominic Cleal commented on an issue Re: Infinite loop if EC2 metadata server times out Just to add, my nightly builds of facter-2 running on Rackspace have been working reliably since the merge. Add Comment Facter / FACT-481 Infinite loop if EC2 metadata server times out On a Rackspace VM, Facter gets into an infinite loop when trying to contact the EC2 metadata server. The retry loop in lib/facter/ec2/rest.rb doesn't increment the counter on each iteration. This causes the Puppet agent to permanently hang. To reproduce on a non-Rackspace system, just run: FACTER_virtual=xen bin/facter (Assuming there's no metada... 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-2708) Fix puppet doc errors and misbehaviors
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Puppet / PUP-2708 Fix puppet doc errors and misbehaviors Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen 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-2711) The manifests directory should be recursively loaded when using directory environments
Title: Message Title William Van Hevelingen created an issue Puppet / PUP-2711 The manifests directory should be recursively loaded when using directory environments Issue Type: Bug Assignee: Unassigned Created: 02/Jun/14 10:53 AM Priority: Normal Reporter: William Van Hevelingen We have a manifest directory with multiples subdirectories full of node definitions. We would prefer to stay with this layout rather than moving all the node definition files into the manifests directory. It would also make migration easier to directory environments as all one would need to do is remove the import function calls. manifests domain cs.pp ece.pp mme.pp [...] This is documented in the following link: Puppet will only read the first level of files in a manifest directory; it won’t descend into subdirectories. http://docs.puppetlabs.com/puppet/latest/reference/dirs_manifest.html#directory-behavior-vs-single-file Add Comment
Jira (FACT-197) processorcount counting CPU cores on Solaris
Title: Message Title
Branan Purvine-Riley commented on an issue
Re: processorcount counting CPU cores on Solaris
Eric Sorenson, I think this should be considered for backport from master to facter-2.
Add Comment
Facter / FACT-197
processorcount counting CPU cores on Solaris
The processorcount fact on Solaris is counting CPU cores {noformat} physicalprocessorcount = 1 processor0 = SPARC-T4 processor1 = SPARC-T4 processor2 = SPARC-T4 processor3 = SPARC-T4 processorcount = 1 {noformat} and on linux it counts CPU threads. This was reported as http://projects.puppetlabs.com/issues/18215 and a working fix is...
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-192) PR (593): 21868/stable/cherry pick mavericks pkging - MosesMendoza
Title: Message Title Joshua Cooper commented on an issue Re: PR (593): 21868/stable/cherry pick mavericks pkging - MosesMendoza Merged into stable in 833e019f2 and released in 1.7.5 Add Comment Facter / FACT-192 PR (593): 21868/stable/cherry pick mavericks pkging - MosesMendoza h2. 21868/stable/cherry pick mavericks pkging * Author: * Company: * Github ID: [MosesMendoza|https://github.com/MosesMendoza] * [Pull Request 593 Discussion|https://github.com/puppetlabs/facter/pull/593] * [Pull Request 593 File Diff|https://github.com/puppetlabs/facter/pull/593/files] h2. Pull Request Description This PR includes the c... 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-2706) Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
Title: Message Title
Matthaus Owens commented on an issue
Re: Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
Kenneth Barber When I was playing with this a bit, my investigation led me to believe that it is because the debian puppet package uses adduser instead of useradd. adduser does some things under the hood that require PAM to be configured, which it isn't in the build environment. Updating the call in https://github.com/puppetlabs/puppet/blob/stable/ext/debian/puppet-common.postinst#L9-L12 to use useradd with similar flags should alleviate the problem.
Add Comment
Puppet / PUP-2706
Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
We keep getting this error during Puppet installation for our PuppetDB builds: {code} Setting up ruby-augeas (0.5.0-2) ... Setting up libaugeas-ruby (0.5.0-2) ... Setting up ruby-shadow (2.2.0-1) ... Setting up ruby-json (1.8.0-1build1) ... Setting up hiera (1.3.3-1puppetlabs1) ... Setting up puppet-common (3.6.1-1puppetlabs1) ... chage: the sha...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you
Jira (FACT-183) PR (590): Extract Facter execution methods to mixin - adrienthebo
Title: Message Title Joshua Cooper commented on an issue Re: PR (590): Extract Facter execution methods to mixin - adrienthebo Merged into facter-2 in commit 2ff7ae91064d and released in 2.0.1 Add Comment Facter / FACT-183 PR (590): Extract Facter execution methods to mixin - adrienthebo h2. Extract Facter execution methods to mixin * Author: Adrien Thebo git+git...@somethingsinistral.net * Company: Puppet Labs * Github ID: [adrienthebo|https://github.com/adrienthebo] * [Pull Request 590 Discussion|https://github.com/puppetlabs/facter/pull/590] * [Pull Request 590 File Diff|https://github.com/puppetlabs/facter/pull/590/files] h2 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-199) PR (595): Update detection of GCE instances - apchamberlain
Title: Message Title Joshua Cooper commented on an issue Re: PR (595): Update detection of GCE instances - apchamberlain Per https://github.com/puppetlabs/facter/pull/595#issuecomment-41826962, we decided to close this and reinvestigate GCE detection. Add Comment Facter / FACT-199 PR (595): Update detection of GCE instances - apchamberlain h2. Update detection of GCE instances * Author: Alex Chamberlain * Company: Puppet Labs, Inc. * Github ID: [apchamberlain|https://github.com/apchamberlain] * [Pull Request 595 Discussion|https://github.com/puppetlabs/facter/pull/595] * [Pull Request 595 File Diff|https://github.com/puppetlabs/facter/pull/595/files] h2. Pull Request Description ... 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-200) PR (596): (maint) Redirect dmidecode stderr to /dev/null - haus
Title: Message Title Joshua Cooper commented on an issue Re: PR (596): (maint) Redirect dmidecode stderr to /dev/null - haus Merged into stable in 28c0bec5a and was released in 1.7.5 Add Comment Facter / FACT-200 PR (596): (maint) Redirect dmidecode stderr to /dev/null - haus h2. (maint) Redirect dmidecode stderr to /dev/null * Author: Matthaus Owens mlitte...@gmail.com * Company: Puppet Labs * Github ID: [haus|https://github.com/haus] * [Pull Request 596 Discussion|https://github.com/puppetlabs/facter/pull/596] * [Pull Request 596 File Diff|https://github.com/puppetlabs/facter/pull/596/files] h2. Pull Request Descrip... 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-377) Does not detect LXC virtualization
Title: Message Title Branan Purvine-Riley updated an issue Facter / FACT-377 Does not detect LXC virtualization Change By: Branan Purvine-Riley Fix Version/s: 2.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/d/optout.
Jira (PUP-2710) Audit of mtime/ctime for files on ext4 reports spurious changes (only ruby 1.9+)
Title: Message Title
Kylo Ginsberg commented on an issue
Re: Audit of mtime/ctime for files on ext4 reports spurious changes (only ruby 1.9+)
At this point my ideas to fix this are:
monkey patch the equality comparison on Time objects to ignore nanoseconds (or truncate to usecs)
monkey patch yaml either to store only usecs, or to parse nsecs correctly - this seems sticky atm b/c of the different yaml libraries involved
special case the audit equality comparison to compare the to_s of the previous and historical values
None of these options seems super great to me, but I have some more avenues to explore.
Add Comment
Puppet / PUP-2710
Audit of mtime/ctime for files on ext4 reports spurious changes (only ruby 1.9+)
{noformat} [root@master323-centos ~]# puppet --version 3.4.3 (Puppet Enterprise 3.2.3) [root@master323-centos ~]# /opt/puppet/bin/ruby --version ruby 1.9.3p484 (2013-11-22 revision 43786) [x86_64-linux] [root@master323-centos ~]# mkdir /tmp/test/ [root@master323-centos ~]# puppet apply -e file { '/tmp/test/watch_me': ensure = directory, audit = [...
Jira (FACT-377) Does not detect LXC virtualization
Title: Message Title Branan Purvine-Riley commented on an issue Re: Does not detect LXC virtualization PR 630 was merged into facter-2 and master. Add Comment Facter / FACT-377 Does not detect LXC virtualization Facter does not detect when run in an LXC virtual environment. It reports is_virtual = false and virtual = physical. 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-2692) Puppet master passenger processes keep growing
Title: Message Title Joshua Hoblitt commented on an issue Re: Puppet master passenger processes keep growing It appears that with the default 5s environment_timeout, assuming that 3.6.1 has similar across the board CPU usage as 3.6.0, that CPU usage has increased ~20%. Add Comment Puppet / PUP-2692 Puppet master passenger processes keep growing [~jhoblitt] reported on IRC in #puppet-dev that after upgrading from 3.6.0 to 3.6.1 his master processes started growing to 1.5GB. 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-2692) Puppet master passenger processes keep growing
Title: Message Title Joshua Hoblitt updated an issue Puppet / PUP-2692 Puppet master passenger processes keep growing Memory usage for the last week. 3.6.0 - (upgrade fun) - 3.6.1 w/ env dirs + functions.patch. Change By: Joshua Hoblitt Attachment: graph.php.png 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-2404) Merge puppet 3.6 into pe-puppet 3.3.x
Title: Message Title Kylo Ginsberg commented on an issue Re: Merge puppet 3.6 into pe-puppet 3.3.x @branan this morning's merge cleared pe-puppet specs so is ready for promotion AFAICT. Note that this doesn't have fixes for the intermittent failures, but does have other changes we'd like tested. Add Comment Puppet / PUP-2404 Merge puppet 3.6 into pe-puppet 3.3.x pe-puppet/3.3.x is based on puppet 3.6.x 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-2660) purging ssh_authorized_key fails because of missing user value
Title: Message Title Kurt Wall updated an issue Puppet / PUP-2660 purging ssh_authorized_key fails because of missing user value 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-2702) Change environment_timeout default to unlimited
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2702 Change environment_timeout default to unlimited 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-2706) Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
Title: Message Title
Kenneth Barber commented on an issue
Re: Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
Matthaus Owens sounds like a plan, I think the only crack in your thinking is that it should be happening all the time if it was indeed the lack of PAM causing it shrug. Perhaps upstart is starting things in the background, and this is causing a race of some kind?
Add Comment
Puppet / PUP-2706
Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
We keep getting this error during Puppet installation for our PuppetDB builds: {code} Setting up ruby-augeas (0.5.0-2) ... Setting up libaugeas-ruby (0.5.0-2) ... Setting up ruby-shadow (2.2.0-1) ... Setting up ruby-json (1.8.0-1build1) ... Setting up hiera (1.3.3-1puppetlabs1) ... Setting up puppet-common (3.6.1-1puppetlabs1) ... chage: the sha...
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
Jira (PUP-2360) Yumrepo type allows invalid values
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-2360 Yumrepo type allows invalid values 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-1070) puppetd doesn't always cleanup lockfile properly
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-1070 puppetd doesn't always cleanup lockfile properly 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-464) Mandrake osfamily is missing in stable/facter-2
Title: Message Title Branan Purvine-Riley commented on an issue Re: Mandrake osfamily is missing in stable/facter-2 Eric Sorenson If this indeed works for master, we should consider it for backport to 2.1 Add Comment Facter / FACT-464 Mandrake osfamily is missing in stable/facter-2 In master, the osfamily fact returns Mandrake for the following operating systems: - Mandrake - Mandriva - Mageia This is missing for both facter stable (2.0.1) and facter-2 (2.1.0). 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-684) Namevar over 1024 characters is not caught and results in invalid yaml with accompanying errors
Title: Message Title
Daniel Dreier commented on an issue
Re: Namevar over 1024 characters is not caught and results in invalid yaml with accompanying errors
I've been able to reproduce what looks like the same problem on master:
[root@poss-head-centos ~]# puppet --version 3.6.1 [root@poss-head-centos ~]# rm /var/lib/puppet/state/state.yaml rm: remove regular file `/var/lib/puppet/state/state.yaml'? y [root@poss-head-centos ~]# cat test_good.pp ssh_authorized_key { '': ensure = present, user = 'root', key = 'foo', }
[root@poss-head-centos ~]# puppet apply test_good.pp Notice: Compiled catalog for poss-head-centos.puppetdebug.vlan in environment production in 0.09 seconds Notice: Finished catalog run in 0.10 seconds [root@poss-head-centos ~]# puppet apply test_good.pp Notice: Compiled catalog for poss-head-centos.puppetdebug.vlan in environment production in 0.08 seconds Notice: Finished catalog run in 0.21 seconds [root@poss-head-centos ~]# puppet apply test_good^Cp [root@poss-head-centos ~]# cat test_bad.pp ssh_authorized_key { '': ensure = present, user = 'root', key = 'foo', }
[root@poss-head-centos ~]# puppet apply test_bad.pp Notice: Compiled catalog for poss-head-centos.puppetdebug.vlan in environment production in 0.09 seconds Notice: Finished catalog run in 0.11 seconds [root@poss-head-centos ~]# puppet apply test_bad.pp Notice: Compiled catalog for poss-head-centos.puppetdebug.vlan in environment production in 0.09 seconds Error: Checksumfile /var/lib/puppet/state/state.yaml is corrupt ((/var/lib/puppet/state/state.yaml): could not find expected ':' while scanning a simple key at line 63 column 3); replacing Notice: Finished catalog run in 0.10 seconds
Jira (PUP-684) Namevar over 1024 characters is not caught and results in invalid yaml with accompanying errors
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-684 Namevar over 1024 characters is not caught and results in invalid yaml with accompanying errors Change By: Daniel Dreier Affects Version/s: 3.6.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/d/optout.
Jira (PUP-2712) puppet does not set execution bit for custom facts
Title: Message Title Banio Carpenter created an issue Puppet / PUP-2712 puppet does not set execution bit for custom facts Issue Type: Bug Affects Versions: 3.6.1 Assignee: Unassigned Created: 02/Jun/14 12:03 PM Environment: CentOS 6.5; puppet 3.6.1; ruby 1.8.7 Fix Versions: 3.x Priority: Normal Reporter: Banio Carpenter Puppet correctly puts custom facts into the directory /var/lib/puppet/facts.d/ on the client, but doesn't make them executable. Add Comment
Jira (PUP-2706) Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
Title: Message Title
Matthaus Owens commented on an issue
Re: Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
Kenneth Barber Yea I had the same question and all I could come up with either PAM isn't a core service in trusty, and was earlier, or there was some change to the upstart dependency graph that is showing this behavior. As you say, since it is intermittent, it seems like a race of some kind.
Add Comment
Puppet / PUP-2706
Intermittent 'chage' Puppet installation failure on Ubuntu 14.04 during PDB build
We keep getting this error during Puppet installation for our PuppetDB builds: {code} Setting up ruby-augeas (0.5.0-2) ... Setting up libaugeas-ruby (0.5.0-2) ... Setting up ruby-shadow (2.2.0-1) ... Setting up ruby-json (1.8.0-1build1) ... Setting up hiera (1.3.3-1puppetlabs1) ... Setting up puppet-common (3.6.1-1puppetlabs1) ... chage: the sha...
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-1295) Yum provider purge target runs irrespective of package installation status
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-1295 Yum provider purge target runs irrespective of package installation status Change By: Daniel Dreier Fix Version/s: 3.6.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/d/optout.
Jira (PUP-1295) Yum provider purge target runs irrespective of package installation status
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-1295 Yum provider purge target runs irrespective of package installation status Change By: Daniel Dreier Fix Version/s: 3.6.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/d/optout.
Jira (PUP-1295) Yum provider purge target runs irrespective of package installation status
Title: Message Title Daniel Dreier updated an issue Puppet / PUP-1295 Yum provider purge target runs irrespective of package installation status Change By: Daniel Dreier Affects Version/s: 3.6.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/d/optout.
Jira (PUP-1295) Yum provider purge target runs irrespective of package installation status
Title: Message Title
Daniel Dreier commented on an issue
Re: Yum provider purge target runs irrespective of package installation status
I've confirmed this again on master / 3.6.1 on CentOS 6.5. yum remove is run each time. The yum remove should only run if the package is actually installed.
Add Comment
Puppet / PUP-1295
Yum provider purge target runs irrespective of package installation status
It seems the yum provider will try to purge an absent package: pre [root@test ~]# cat test.pp package { logwatch: ensure = purged; } [root@test ~]# /bin/rpm -q logwatch --nosignature --nodigest --qf '%{NAME} %|EPOCH?{%{EPOCH}}:{0}| %{VERSION} %{RELEASE} %{ARCH}' package logwatch is not installed [root@test ~]# puppet -d -v test.pp debug: P...
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
Jira (FACT-464) Mandrake osfamily is missing in stable/facter-2
Title: Message Title Branan Purvine-Riley commented on an issue Re: Mandrake osfamily is missing in stable/facter-2 On second thought, this is small enough I can backport this afternoon. If it ends up sitting in a PR for a while so be it. Add Comment Facter / FACT-464 Mandrake osfamily is missing in stable/facter-2 In master, the osfamily fact returns Mandrake for the following operating systems: - Mandrake - Mandriva - Mageia This is missing for both facter stable (2.0.1) and facter-2 (2.1.0). 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-464) Mandrake osfamily is missing in stable/facter-2
Title: Message Title Branan Purvine-Riley assigned an issue to Branan Purvine-Riley Facter / FACT-464 Mandrake osfamily is missing in stable/facter-2 Change By: Branan Purvine-Riley Assignee: EricSorenson BrananPurvine-Riley 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-1989) puppet doc doesn't clean up after itself
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Puppet / PUP-1989 puppet doc doesn't clean up after itself Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen 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-197) processorcount counting CPU cores on Solaris
Title: Message Title Branan Purvine-Riley assigned an issue to Branan Purvine-Riley Facter / FACT-197 processorcount counting CPU cores on Solaris Change By: Branan Purvine-Riley Assignee: EricSorenson BrananPurvine-Riley 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-197) processorcount counting CPU cores on Solaris
Title: Message Title
Branan Purvine-Riley commented on an issue
Re: processorcount counting CPU cores on Solaris
I'm just gonna go ahead and open a PR for the backport
Add Comment
Facter / FACT-197
processorcount counting CPU cores on Solaris
The processorcount fact on Solaris is counting CPU cores {noformat} physicalprocessorcount = 1 processor0 = SPARC-T4 processor1 = SPARC-T4 processor2 = SPARC-T4 processor3 = SPARC-T4 processorcount = 1 {noformat} and on linux it counts CPU threads. This was reported as http://projects.puppetlabs.com/issues/18215 and a working fix is...
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-1989) puppet doc doesn't clean up after itself
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: puppet doc doesn't clean up after itself
This is re-producible under Pupet 3.6.1 with Ruby 1.9.3. It does not appear to happen when using Ruby 1.8.7. A noticeable place the behavior shows up is in the manifests directory. A .html file will show up for each .pp file.
Add Comment
Puppet / PUP-1989
puppet doc doesn't clean up after itself
After running {{puppet doc --all --mode rdoc --outputdir /var/www/html/puppet/doc --debug --modulepath /etc/puppetlabs/puppet/modules}} from {{/etc/puppetlabs/puppet/modules}} there are a lot of {{.html}} files left laying around in the modules. {noformat} [root@pe-320-master pe-320-master.puppetdebug.vlan]# cd /etc/puppetlabs/puppet/modules/ntp/ [root...
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 (HI-230) Allow options to be passed to deep merge
Title: Message Title Rob Nelson assigned an issue to Rob Nelson Hiera / HI-230 Allow options to be passed to deep merge Change By: Rob Nelson Assignee: RobNelson 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 (HI-230) Allow options to be passed to deep merge
Title: Message Title Rob Nelson updated an issue Hiera / HI-230 Allow options to be passed to deep merge Change By: Rob Nelson Assignee: RobNelson HenrikLindberg 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-1989) puppet doc doesn't clean up after itself
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-1989 puppet doc doesn't clean up after itself Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen 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 (HI-230) Allow options to be passed to deep merge
Title: Message Title Rob Nelson commented on an issue Re: Allow options to be passed to deep merge Henrik, can you provide some status on where this ticket stands, maybe a reference to the relevant merge? Add Comment Hiera / HI-230 Allow options to be passed to deep merge There is currently no way to pass additional options to the deep hash merge gem being used for processing deep merges. 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 (HI-30) New YAML shorthand for class params blocks existing form of class param lookup when enabled
Title: Message Title
Rob Nelson commented on an issue
Re: New YAML shorthand for class params blocks existing form of class param lookup when enabled
Eric, these tickets need some status to determine how to proceed.
Add Comment
Hiera / HI-30
New YAML shorthand for class params blocks existing form of class param lookup when enabled
The new shorthand YAML data format (added by redmine #18577) is currently implemented as all-or-nothing. If you enable it (set {{:yaml: :hash_delimiter: ::}} in hiera.yaml), ALL lookups formatted as {{class::parameter}} will be interpreted as hash elements, and any keys stored in the data sources using full parameter names will become inaccessible; tryi...
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 (HI-31) Setting to enable new YAML shorthand is too general
Title: Message Title
Rob Nelson commented on an issue
Re: Setting to enable new YAML shorthand is too general
Eric, these tickets need some status to determine how to proceed.
Add Comment
Hiera / HI-31
Setting to enable new YAML shorthand is too general
The new feature for mapping namespace::key lookups onto YAML hashes is enabled with a setting called {{:hash_delimiter}}, which can be set to anything. In the context of Puppet, the only useful value for this setting is {{::}}. Additionally, the name of the setting doesn't describe its actual use in the context of Puppet. I'm of the belief that th...
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-1474) puppet doc fails against forge.puppetlabs.com/ispavailability/logstash
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-1474
puppet doc fails against forge.puppetlabs.com/ispavailability/logstash
Change By:
Charlie Sharpsteen
I'llbepostingthisbugtherealso.Summary:puppetdocfailsagainstforge.puppetlabs.com/ispavailability/logstashStepstoReproduce:1.Installhttp://forge.puppetlabs.com/ispavailability/logstash/0.1.0.tar.gzintomodulesdirectory.2.puppetdoc--verbose--trace--all--environmentproduction--moderdoc--outputdir/www/sites/example.com/files/html/doc--manifestdir/etc/puppet/manifests--modulepath/etc/puppet/modulesExpectedResults:Noerror.ActualResults: {code}
Jira (HI-230) Allow options to be passed to deep merge
Title: Message Title Henrik Lindberg commented on an issue Re: Allow options to be passed to deep merge It is merged to master as noted in a comment above. That means that when 1.4.0 is released, the merged fix will be included. Add Comment Hiera / HI-230 Allow options to be passed to deep merge There is currently no way to pass additional options to the deep hash merge gem being used for processing deep merges. 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-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Brian Wilkins commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log Had it happen again today.. Here from /var/log/messages on the client: Jun 2 15:37:07 host puppet-agent[10513]: Unable to fetch my node definition, but the agent run will continue: Jun 2 15:37:07 host puppet-agent[10513]: SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: sslv3 alert certificate revoked Jun 2 15:37:07 host puppet-agent[10513]: (/File[/home/bwilkins/.puppet/var/facts.d]) Failed to generate additional resources using 'eval_generate': SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: sslv3 alert certificate revoked Jun 2 15:37:07 host puppet-agent[10513]: (/File[/home/bwilkins/.puppet/var/facts.d]) Could not evaluate: Could not retrieve file metadata for puppet://puppet/pluginfacts: SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: sslv3 alert certificate revoked Jun 2 15:37:07 host puppet-agent[10513]: (/File[/home/bwilkins/.puppet/var/facts.d]) Wrapped exception: Jun 2 15:37:07 host puppet-agent[10513]: (/File[/home/bwilkins/.puppet/var/facts.d]) SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: sslv3 alert certificate revoked Jun 2 15:37:08 host puppet-agent[10513]: (/File[/home/bwilkins/.puppet/var/lib]) Failed to generate additional resources using 'eval_generate': SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: sslv3 alert certificate revoked Jun 2 15:37:08 host puppet-agent[10513]: (/File[/home/bwilkins/.puppet/var/lib]) Could not evaluate: Could not retrieve file metadata for puppet://puppet/plugins: SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: sslv3 alert certificate revoked Jun 2 15:37:08 host puppet-agent[10513]: (/File[/home/bwilkins/.puppet/var/lib]) Wrapped exception: Jun 2 15:37:08 host puppet-agent[10513]: (/File[/home/bwilkins/.puppet/var/lib]) SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: sslv3 alert certificate revoked Jun 2 15:37:08 host puppet-agent[10513]: Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation Jun 2 15:37:08 host puppet-agent[10513]: Failed to apply catalog: Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation Jun 2 15:37:08 host puppet-agent[10513]: Could not send report: SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: sslv3 alert certificate revoked I don't know why my cert is jacked up, but there's the Log message again. Add Comment
Jira (HI-230) Allow options to be passed to deep merge
Title: Message Title Henrik Lindberg commented on an issue Re: Allow options to be passed to deep merge Also note that it is in Ready for Review since it is merged, and all that is needed is for the expected functionality to be reviewed before it is released. (i.e. please don't change status back to needs information). If you want to, you can grab the particular commit (or master head) and see if the fix does what you want/need, and then give your +1. Add Comment Hiera / HI-230 Allow options to be passed to deep merge There is currently no way to pass additional options to the deep hash merge gem being used for processing deep merges. 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-1513) 'puppet doc' does not correctly parse hashes with facts on the left hand side.
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: 'puppet doc' does not correctly parse hashes with facts on the left hand side.
Re-produced under both Ruby 1.8.7 and Ruby 1.9.3. Here's an example class:
# This is a docstring.
class rdoc_bugs::fact_hash {
$foo = {
$::fqdn = 'bar'
}
}
This bug is particularly bad as it halts the entire documentation generation process.
Add Comment
Puppet / PUP-1513
'puppet doc' does not correctly parse hashes with facts on the left hand side.
Parsing the following code block fails with the error: Error: Could not generate documentation: Syntax error at '::fqdn'; expected '}'. {code} $foo = { $::fqdn = 'bar' } {code} This code parses correctly using puppet lint and applies properly in production.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed
Jira (PUP-2506) Error when evaluating #type in Puppet::Error message interpolation for Puppet::Resource::Ral
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2506 Error when evaluating #type in Puppet::Error message interpolation for Puppet::Resource::Ral Change By: Rob Reynolds Summary: TrivialRubybug Errorwhenevaluating#type inPuppet:: ErrormessageinterpolationforPuppet:: Resource::Ral 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-1522) Hash in class parameter breaks doc generation
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Hash in class parameter breaks doc generation
It appears this was indeed fixed in 3.5.0 by commit 64f1a1a.
Add Comment
Puppet / PUP-1522
Hash in class parameter breaks doc generation
Having a hash in a class parameter makes the Class documentation to be discarded when running puppetdoc Running `puppet doc --mode rdoc --manifestdir test/manifests/test.pp --modulepath ./` {{test/manifests/test.pp}} {code} # Class: test # # test class. This comment is ignored by puppetdoc class test( $p = {} ) { } # Class: test2 # # ...
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-1522) Hash in class parameter breaks doc generation
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-1522 Hash in class parameter breaks doc generation Change By: Charlie Sharpsteen 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/d/optout.
Jira (PUP-2692) Puppet master passenger processes keep growing
Title: Message Title Henrik Lindberg commented on an issue Re: Puppet master passenger processes keep growing merged: b6a2561 Add Comment Puppet / PUP-2692 Puppet master passenger processes keep growing [~jhoblitt] reported on IRC in #puppet-dev that after upgrading from 3.6.0 to 3.6.1 his master processes started growing to 1.5GB. 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-1081) Bring in rich module documentation feature
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-1081 Bring in rich module documentation feature Change By: Charlie Sharpsteen `puppetdoc--moderdoc`justisn'tenough.Itdoesn'tworkonrecentruby(1.9),itgeneratestextdocumentationthatisn'tsearchable/browseable/useful.WhatI'dliketoseeissomethingakinto ahref=""> [TypeReference| http://docs.puppetlabs.com/references/latest/type.html TypeReference/a ] onPuppetwebsite,butwithTOCandmenuontheleftthatwouldallowmetosearchandselectwhatdocumentationsection/typeI'dliketobrowse.Forex.,I'dliketoseeallfunctionsthatmymoduledefines,theirnames,description,numberofarguments,type.Samewithcustomtypes.Thedocoutputformatcouldbehtml,butanystructuralwouldwork,too.Maybexmlwithgoodxslttransformsheet?OrjustJSONthatcanbeeasilyconvertedtohtml?Wouldbenicetohave,youknow... 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-1081) Bring in rich module documentation feature
Title: Message Title Charlie Sharpsteen assigned an issue to Charlie Sharpsteen Puppet / PUP-1081 Bring in rich module documentation feature Change By: Charlie Sharpsteen Assignee: CharlieSharpsteen 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-25) Resource defaults aren't completely evaluated by the compiler
Title: Message Title Henrik Lindberg commented on an issue Re: Resource defaults aren't completely evaluated by the compiler In 4.0 this will continue to work as it does in 3x. New catalog builder not until Puppet 5.0. Add Comment Puppet / PUP-25 Resource defaults aren't completely evaluated by the compiler Resource defaults are merged in when [finish is called on resources|https://github.com/puppetlabs/puppet/blob/3.2.0/lib/puppet/parser/compiler.rb#L358] by the compiler [which leads to|https://github.com/puppetlabs/puppet/blob/3.2.0/lib/puppet/parser/resource.rb#L107] the [add_defaults method|https://github.com/puppetlabs/puppet/blob/3.2.0/lib/puppet/parse... 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-1474) puppet doc fails against forge.puppetlabs.com/ispavailability/logstash
Title: Message Title Richard Pijnenburg commented on an issue Re: puppet doc fails against forge.puppetlabs.com/ispavailability/logstash Hi, the new module ( https://forge.puppetlabs.com/elasticsearch/logstash ) should not have this issue anymore. Can some one validate? Add Comment Puppet / PUP-1474 puppet doc fails against forge.puppetlabs.com/ispavailability/logstash I'll be posting this bug there also. Summary: puppet doc fails against forge.puppetlabs.com/ispavailability/logstash Steps to Reproduce: 1. Install http://forge.puppetlabs.com/ispavailability/logstash/0.1.0.tar.gz into modules directory. 2. puppet doc --verbose --trace --all --environment production --mode rdoc --outputdir /www/sites/example.com/f... 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-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Joshua Cooper commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log Brian Wilkins It looks like the agent's cert was revoked on the server side. You can confirm that by looking at the list of revoked certs (by serial number) on the master: # openssl crl -in `puppet master --configprint cacrl` -noout -text ... Revoked Certificates: Serial Number: 02 Revocation Date: Jun 2 20:15:12 2014 GMT More importantly, are you able to run the daemonized agent with --trace? Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log 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-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Brian Wilkins commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log Oddly it doesn't show any on the master, but thats a side issue Anyways, so I tried it again. To get the error to go away, I removed pluginsync = true from my puppet.conf on the agent. The error didn't happen anymore. I had the agent running as a service for several days. I had to turn it off to debug some erb I am writing so I could run the agent on demand. Starting seeing these errors when I would run the agent on demand at the command line. Looked at my puppet.conf, removed pluginsync = true. The errors stopped. I just added back in pluginsync = true and the errors don't happen again. Add Comment Puppet / PUP-724 Could not autoload puppet /util /instrumentation /listeners /log 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-2711) The manifests directory should be recursively loaded when using directory environments
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2711 The manifests directory should be recursively loaded when using directory environments Change By: Henrik Lindberg Story Points: 3 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.
