Jira (PUP-2685) Could not prefetch package provider 'pip'...ExecutionFailure
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-2685 Could not prefetch package provider 'pip'...ExecutionFailure Change By: Joshua Cooper Assignee: KyloGinsberg AndreHurano 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-2685) Could not prefetch package provider 'pip'...ExecutionFailure
Title: Message Title
Joshua Cooper updated an issue
Puppet / PUP-2685
Could not prefetch package provider 'pip'...ExecutionFailure
Change By:
Joshua Cooper
Iamgettingthiserror,usinga3.6.1clientandserver.Theerrordidnotoccurbeforetheupgradeto3.6series(Iwason3.5.1before):{ quote noformat }Info:Applyingconfigurationversion'1401250438'Info:/Stage[main]/Python::Config/File[/root/.pip/pip.conf]:Filebucketed/root/.pip/pip.conftopuppetwithsum286e59a60ff697fd7d10713b1b8a96d7Notice:/Stage[main]/Python::Config/File[/root/.pip/pip.conf]/content:contentchanged'{md5}286e59a60ff697fd7d10713b1b8a96d7'to'{md5}9ab398869278153ae8c7dc63fd65effa'Error:Couldnotprefetchpackageprovider'pip':#Puppet::ExecutionFailure:0x7fdd14c3a610Error:/Package[supervisor]:Couldnotevaluate:#Puppet::ExecutionFailure:0x7fdd14c31740Error:/Package[supervisor-wildcards]:Couldnotevaluate:#Puppet::ExecutionFailure:0x7fdd14c24f90{ quote noformat }Theerrormessageisnotveryuseful...whatisanExecutionFailureandwhydiditfail?
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-2685) Could not prefetch package provider 'pip'...ExecutionFailure
Title: Message Title
Joshua Cooper commented on an issue
Re: Could not prefetch package provider 'pip'...ExecutionFailure
Can you include a small manifest that demonstrates the problem, run the agent with --trace, and include the stacktrace in this ticket?
Add Comment
Puppet / PUP-2685
Could not prefetch package provider 'pip'...ExecutionFailure
I am getting this error, using a 3.6.1 client and server. The error did not occur before the upgrade to 3.6 series (I was on 3.5.1 before): {noformat} Info: Applying configuration version '1401250438' Info: /Stage[main]/Python::Config/File[/root/.pip/pip.conf]: Filebucketed /root/.pip/pip.conf to puppet with sum 286e59a60ff697fd7d10713b1b8a96d7 Noti...
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-148) Support multiple backends of the same type
Title: Message Title Spencer Krum commented on an issue Re: Support multiple backends of the same type I would like to see this as well. I think my requirements are a bit less stringent. I'd like to see the yaml backend support multiple data dirs. Right now I hack it by setting the datadir to something way up the filesystem such as '/etc/puppet/' Then I reach into two separate locations by using the hierarchy. This is awesome for keeping the insecure data with the puppet code and the secure data in a separate directory/repository with a lower surface area. I would like to simply provide a list of data directories, and have hiera run the entire hierarchy on them in order. Add Comment Hiera / HI-148 Support multiple backends of the same type It would be great if Hiera could support multiple backends of the same type. Currently I make my own modifications to hiera and hiera-json to support multiple JSON data stores. My code is terrible, but available here: https://github.com/lukebigum/hiera https://github.com/lukebigum/hiera-json And it works with a configuration file like this: ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
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 I am using Apache httpd with mod_passenger. I originally commented on this error because I saw it all weekend. I am NOT seeing it currently. I do not know why. I had to make the suggested configuration change, but then I took it out and removed the `puppet` entry from my `/etc/hosts`. I have my puppetmaster defined in the server config section of my `puppet.conf`. So I shouldn't have needed that setting. It is a very odd error. One thing of note is the puppet agent and puppetmaster are running on VMWare VMs. I am not sure if that makes a difference. This is my ruby version: ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]. I am running puppet 3.6 I would get you the trace, but I don't think it is helpful because I am not currently experiencing the error. 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-2348) Puppet run randomly fails with Unknown function function at manifest on node node
Title: Message Title Henrik Lindberg commented on an issue Re: Puppet run randomly fails with Unknown function function at manifest on node node No need to try 3.6.1, I think the problem manifests itself there as well as reported in PUP-2684 Add Comment Puppet / PUP-2348 Puppet run randomly fails with Unknown function function at manifest on node node After upgrading puppetmaster to 3.5.1 we started experiencing random manifests failures. A given (manifest, function, node) tuple can work several times and then fail, only to succeed on the next run (with the exact same code base). Running the agent and the master in debug does not bring any more information on why the function cannot be found. ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-2684) Function is_hash not defined despite being loaded!
Title: Message Title
Henrik Lindberg commented on an issue
Re: Function is_hash not defined despite being loaded!
Is Webrick in use on the master?
Add Comment
Puppet / PUP-2684
Function is_hash not defined despite being loaded!
I get this error on the server: {quote} Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Function Call, Function is_hash not defined despite being loaded! at /etc/puppet/environments/goosy/modules/apache/manifests/vhost.pp:410:9 {quote} (puppetforge module versions): stdlib 4.2
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2129) Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2:
Title: Message Title Henrik Lindberg commented on an issue Re: Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2: That is a different issue. Will move it to a separate ticket. Add Comment Puppet / PUP-2129 Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2:0x00031a3cb0 at /etc/puppet/external/modules/python/manifests/config.pp:20:31 on node The module where this is happening can be 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-2686) []= is given nil while evaluating VirtualQuery in future parser
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-2686 []= is given nil while evaluating VirtualQuery in future parser Issue Type: Bug Assignee: Andy Parker Components: DSL Created: 28/May/14 4:47 AM Fix Versions: 3.7.0 Priority: Normal Reporter: Henrik Lindberg This error appears when using the Python module under 3.6.1. Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Virtual Query, undefined method `[]=' for nil:NilClass at /etc/puppet/environments/goosy/modules/python/manifests/config.pp:18:31 on node dev02.corp.f7 Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run
Jira (PUP-2686) []= on nil while evaluating VirtualQuery in future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2686 []= on nil while evaluating VirtualQuery in future parser Change By: Henrik Lindberg Labels: future-parser 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-2129) Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2:
Title: Message Title Henrik Lindberg commented on an issue Re: Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2: Andre Hurano I logged PUP-2686 Add Comment Puppet / PUP-2129 Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Virtual Query, undefined local variable or method `slurpfunc' for #Puppet::Pops::Parser::Lexer2:0x00031a3cb0 at /etc/puppet/external/modules/python/manifests/config.pp:20:31 on node The module where this is happening can be 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-2686) []= is given nil while evaluating VirtualQuery in future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2686 []= is given nil while evaluating VirtualQuery in future parser Change By: Henrik Lindberg Reporter: HenrikLindberg AndreHurano 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-2686) []= on nil while evaluating VirtualQuery in future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2686 []= on nil while evaluating VirtualQuery in future parser Change By: Henrik Lindberg Summary: []= isgiven on nilwhileevaluatingVirtualQueryinfutureparser 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-2686) []= on nil while evaluating VirtualQuery in future parser
Title: Message Title
Henrik Lindberg commented on an issue
Re: []= on nil while evaluating VirtualQuery in future parser
It would be very helpful if you could do a run with --trace turned on to get the ruby stacktrace
Add Comment
Puppet / PUP-2686
[]= on nil while evaluating VirtualQuery in future parser
This error appears when using the Python module under 3.6.1. {code} Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Virtual Query, undefined method `[]=' for nil:NilClass at /etc/puppet/environments/goosy/modules/python/manifests/config.pp:18:31 on node dev02.corp.f7 Warning: Not usi...
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-2686) []= on nil while evaluating VirtualQuery in future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2686 []= on nil while evaluating VirtualQuery in future parser Change By: Henrik Lindberg Assignee: AndyParker AndreHurano 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-2686) []= on nil while evaluating VirtualQuery in future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2686 []= on nil while evaluating VirtualQuery in future parser Change By: Henrik Lindberg Fix Version/s: 3.7.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-2686) []= on nil while evaluating VirtualQuery in future parser
Title: Message Title
Henrik Lindberg commented on an issue
Re: []= on nil while evaluating VirtualQuery in future parser
I think you are using Webrick, and is also bit by PUP-2659. Therefore please try a puppet apply with --trace to avoid hitting one of the problems that PUP-2659 causes).
Add Comment
Puppet / PUP-2686
[]= on nil while evaluating VirtualQuery in future parser
This error appears when using the Python module under 3.6.1. {code} Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Virtual Query, undefined method `[]=' for nil:NilClass at /etc/puppet/environments/goosy/modules/python/manifests/config.pp:18:31 on node dev02.corp.f7 Warning: Not usi...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (PUP-2687) File Names with ? cause failures with recursive copies
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-2687
File Names with ? cause failures with recursive copies
Issue Type:
Bug
Assignee:
Unassigned
Created:
28/May/14 5:07 AM
Labels:
redmine customer
Priority:
Normal
Reporter:
redmine.exporter
File names that contain ? cause runs to fail and reports that it can't find a file name by section before the ?, and seemingly drops the ? and anything after.
Example code: pre file { '/tmp/foo': ensure = directory, recurse = true, purge = true, force = true, owner = 'root', group = 'root', mode = '0644', source = puppet:///modules/foobar/foo, }
/pre
Example directory/file structure: pre ├── foobar │ └── files │ └── foo │ ├── a │ ├── b │ ├── c │ └── test?moretest
/pre
Error: pre Error: Could not set 'file' on ensure: Error 404 on SERVER: Not Found: Could not find file_content modules/foobar/foo/test Error: Could not set 'file' on ensure: Error 404 on SERVER: Not Found: Could not find file_content modules/foobar/foo/test Wrapped exception: Error 404 on SERVER: Not Found: Could not find file_content modules/foobar/foo/test Error: /File[/tmp/foo/test?moretest]/ensure: change from absent to file failed: Could not set 'file' on ensure: Error 404 on SERVER: Not Found: Could not find file_content modules/foobar/foo/test /pre
Jira (PUP-2348) Puppet run randomly fails with Unknown function function at manifest on node node
Title: Message Title
Henrik Lindberg commented on an issue
Re: Puppet run randomly fails with Unknown function function at manifest on node node
Actually, PUP-2684 could be a different issue related to Webrick.
The issues that are relevant in 3.6.1 are:
PUP-2607
- environmentpath does not work in master section of config
PUP-2610
- Rack masters lose track of environment loaders
As these touch upon various places where an environment/context is selected/configured. The problem with a function intermittently going missing can be caused by a mismatch in environment. When a function is called (say 'foo') it is being called as the method 'function_foo' on Scope. Scope in turn has a method_missing implementation that looks up the function in a module that is maintained by Puppet::ParserFunctions. This lookup is made with the name of the environment and the name of the function ('foo'). Two problem can occur, it has loaded the function, but it cannot find the method that was defined for it (a case of this is found in PUP-2684), or it simply cannot find and load the function in the environment that it given to it (which is the case in this issue).
Since the same setup works with an older version of puppet, I strongly suspect the internal handling of setting up/passing around an environment as this is the major area of change in 3.5 - 3.6.
Add Comment
Puppet / PUP-2348
Puppet run randomly fails with Unknown function function at manifest on node node
Jira (PUP-2687) File Names with ? cause failures with recursive copies
Title: Message Title
Henrik Lindberg commented on an issue
Re: File Names with ? cause failures with recursive copies
This reproduces the error
file { '/tmp/source':
ensure = directory,
}
file { 'problem_file':
ensure = file,
path = '/tmp/source/?',
}
file { '/tmp/dest':
ensure = directory,
recurse = true,
purge = true,
force = true,
source = '/tmp/source',
require = File['problem_file'],
}
Add Comment
Puppet / PUP-2687
File Names with ? cause failures with recursive copies
File names that contain ? cause runs to fail and reports that it can't find a file name by section before the ?, and seemingly drops the ? and anything after. Example code: pre file { '/tmp/foo': ensure = directory, recur...
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
Jira (PUP-2687) File Names with ? cause failures with recursive copies
Title: Message Title Henrik Lindberg commented on an issue Re: File Names with ? cause failures with recursive copies And here is a resulting stack trace /Users/henrik/git/puppet/lib/puppet/file_system/file19.rb:3:in `binread' /Users/henrik/git/puppet/lib/puppet/file_system/file19.rb:3:in `binread' /Users/henrik/git/puppet/lib/puppet/file_system/file19.rb:3:in `binread' /Users/henrik/git/puppet/lib/puppet/file_system.rb:137:in `binread' /Users/henrik/git/puppet/lib/puppet/file_serving/content.rb:37:in `content' /Users/henrik/git/puppet/lib/puppet/type/file/source.rb:106:in `content' /Users/henrik/git/puppet/lib/puppet/type/file/content.rb:186:in `each_chunk_from' /Users/henrik/git/puppet/lib/puppet/type/file/content.rb:169:in `block in write' /Users/henrik/git/puppet/lib/puppet/util/checksums.rb:99:in `md5_stream' /Users/henrik/git/puppet/lib/puppet/type/file/checksum.rb:32:in `sum_stream' /Users/henrik/git/puppet/lib/puppet/type/file/content.rb:168:in `write' /Users/henrik/git/puppet/lib/puppet/type/file.rb:897:in `write_content' /Users/henrik/git/puppet/lib/puppet/type/file.rb:801:in `block in write' /Users/henrik/git/puppet/lib/puppet/util.rb:429:in `replace_file' /Users/henrik/git/puppet/lib/puppet/type/file.rb:799:in `write' /Users/henrik/git/puppet/lib/puppet/type/file/content.rb:149:in `sync' /Users/henrik/git/puppet/lib/puppet/type/file/ensure.rb:65:in `block (2 levels) in module:Puppet' /Users/henrik/git/puppet/lib/puppet/property.rb:197:in `call_valuemethod' /Users/henrik/git/puppet/lib/puppet/property.rb:498:in `set' /Users/henrik/git/puppet/lib/puppet/property.rb:581:in `sync' /Users/henrik/git/puppet/lib/puppet/type/file/ensure.rb:183:in `sync' /Users/henrik/git/puppet/lib/puppet/transaction/resource_harness.rb:191:in `sync' /Users/henrik/git/puppet/lib/puppet/transaction/resource_harness.rb:128:in `sync_if_needed' /Users/henrik/git/puppet/lib/puppet/transaction/resource_harness.rb:81:in `perform_changes' /Users/henrik/git/puppet/lib/puppet/transaction/resource_harness.rb:20:in `evaluate' /Users/henrik/git/puppet/lib/puppet/transaction.rb:174:in `apply' /Users/henrik/git/puppet/lib/puppet/transaction.rb:187:in `eval_resource' /Users/henrik/git/puppet/lib/puppet/transaction.rb:117:in `call' /Users/henrik/git/puppet/lib/puppet/transaction.rb:117:in `block (2 levels) in evaluate' /Users/henrik/git/puppet/lib/puppet/util.rb:327:in `block in thinmark' /Users/henrik/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/benchmark.rb:295:in `realtime' /Users/henrik/git/puppet/lib/puppet/util.rb:326:in `thinmark' /Users/henrik/git/puppet/lib/puppet/transaction.rb:117:in `block in evaluate' /Users/henrik/git/puppet/lib/puppet/graph/relationship_graph.rb:118:in `traverse' /Users/henrik/git/puppet/lib/puppet/transaction.rb:108:in `evaluate' /Users/henrik/git/puppet/lib/puppet/resource/catalog.rb:169:in `block in apply' /Users/henrik/git/puppet/lib/puppet/util/log.rb:149:in `with_destination' /Users/henrik/git/puppet/lib/puppet/transaction/report.rb:112:in `as_logging_destination' /Users/henrik/git/puppet/lib/puppet/resource/catalog.rb:168:in `apply' /Users/henrik/git/puppet/lib/puppet/configurer.rb:117:in `block in apply_catalog' /Users/henrik/git/puppet/lib/puppet/util.rb:161:in `block in benchmark' /Users/henrik/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/benchmark.rb:295:in `realtime' /Users/henrik/git/puppet/lib/puppet/util.rb:160:in `benchmark' /Users/henrik/git/puppet/lib/puppet/configurer.rb:116:in `apply_catalog' /Users/henrik/git/puppet/lib/puppet/configurer.rb:198:in `run' /Users/henrik/git/puppet/lib/puppet/application/apply.rb:288:in `apply_catalog' /Users/henrik/git/puppet/lib/puppet/application/apply.rb:228:in `block in main' /Users/henrik/git/puppet/lib/puppet/context.rb:64:in `override'
Jira (PUP-2687) File Names with ? cause failures with recursive copies
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2687 File Names with ? cause failures with recursive copies Change By: Henrik Lindberg Component/s: TypesandProviders Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2687) File Names with ? cause failures with recursive copies
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2687 File Names with ? cause failures with recursive copies Change By: Henrik Lindberg Assignee: KyloGinsberg 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-658) Refactor remaining query endpoints to new query language code
Title: Message Title Ryan Senior assigned an issue to Ryan Senior PuppetDB / PDB-658 Refactor remaining query endpoints to new query language code Change By: Ryan Senior Assignee: RyanSenior 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-2687) File Names with ? cause failures with recursive copies
Title: Message Title
Rmi commented on an issue
Re: File Names with ? cause failures with recursive copies
Hello,
I've got a similar problem since my update in 3.6.1. With this manifest :
file { ${mcollective_plugin_path}/agent:
ensure = directory,
recurse = true,
purge = true,
mode= '0644',
tag = ['mcolplugin', 'mcolagents'],
source = 'puppet:///modules/mcollective/agent',
notify = Class['mcollective::service'],
}
With a 3.6.1 agent :
# rm /usr/share/mcollective/plugins/mcollective/agent/__ATTENTION\ REP\ PUPPET__
# puppet agent -t
[...]
Error: Could not set 'file' on ensure: Error 404 on SERVER: Not Found: Could not find file_content modules/mcollective/agent/__ATTENTION%20REP%20PUPPET__
Error: Could not set 'file' on ensure: Error 404 on SERVER: Not Found: Could not find file_content modules/mcollective/agent/__ATTENTION%20REP%20PUPPET__
Wrapped exception:
Error 404 on SERVER: Not Found: Could not find file_content modules/mcollective/agent/__ATTENTION%20REP%20PUPPET__
Error: /Stage[main]/Mcollective::Plugin/File[/usr/share/mcollective/plugins/mcollective/agent/__ATTENTION REP PUPPET__]/ensure: change from absent to file failed: Could not set 'file' on ensure: Error 404 on SERVER: Not Found: Could not find file_content modules/mcollective/agent/__ATTENTION%20REP%20PUPPET__
Notice: /Stage[main]/Mcollective::Service/Service[mcollective]: Dependency File[/usr/share/mcollective/plugins/mcollective/agent/__ATTENTION REP PUPPET__] has failures: true
Warning: /Stage[main]/Mcollective::Service/Service[mcollective]: Skipping because of failed dependencies
And with a 3.5.1 agent :
Info: Applying configuration version '1401282140'
Notice: /Stage[main]/Mcollective::Plugin/File[/usr/share/mcollective/plugins/mcollective/agent/__ATTENTION REP PUPPET__]/ensure: defined content as '{md5}d41d8cd98f00b204e9800998ecf8427e'
Info: /usr/share/mcollective/plugins/mcollective/agent: Scheduling refresh of Class[Mcollective::Service]
Info: Class[Mcollective::Service]: Scheduling refresh of Service[mcollective]
Notice: /Stage[main]/Mcollective::Service/Service[mcollective]: Triggered 'refresh' from 1 events
Thanks for your help
Add Comment
Jira (PUP-2688) Debian service provider falsely reports enabled
Title: Message Title John Cooper created an issue Puppet / PUP-2688 Debian service provider falsely reports enabled Issue Type: Bug Affects Versions: 2.7.25 Assignee: Kylo Ginsberg Components: Client Created: 28/May/14 7:02 AM Priority: Normal Reporter: John Cooper The code in debian.rb https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/service/debian.rb Seems to check if the startup script can be started with the invoke-rc.d on line 34 and then returns true for enabled. This is broken as invoke-rc.d will return 104 for all good scripts if they are enabled or not. It should use update-rc.d -n servicename defaults and look for already exists Add Comment
Jira (PUP-2689) A node can't always collect its own exported resources
Title: Message Title Lee Lowder created an issue Puppet / PUP-2689 A node can't always collect its own exported resources Issue Type: Bug Affects Versions: 3.4.3 Assignee: Unassigned Attachments: exported resource bug - Table of results.pdf Created: 28/May/14 7:29 AM Labels: support Priority: Normal Reporter: Lee Lowder Depending on how tags are applied, a node does not collect its own resources. Setting the tag metaparameter in a resource default results in none of the test nodes collecting this resource. When the tag function is used, then each node collects the other nodes resources, but not it's own. When the resource has a tag = metaparameter applied directly, then all resources are collected. However, even when the tag is given as a string rather than an array, the resource is collected ( at least on some resource types, notify, setting the tag as a string did not fully work for a concat resource )
Jira (FACT-453) selinux fact fails on centos/lxc
Title: Message Title fc commented on an issue Re: selinux fact fails on centos/lxc +1 Add Comment Facter / FACT-453 selinux fact fails on centos/lxc facter v2.0.1 spits out this on CentOS 6.5 in lxc. Could not retrieve fact='selinux', resolution='anonymous': Invalid argument - /proc/self/attr/current This was not a problem with the latest version of facter, before 2.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-2689) A node can't always collect its own exported resources
Title: Message Title
Henrik Lindberg commented on an issue
Re: A node can't always collect its own exported resources
I am not surprised that setting tags via defaults does not make the values available for collection as defaults are applied last. I hope the desire is not to change this as this probably has wide spread consequences.
(Continuing with investigation of the difference between the tag metaparameter and the tag function)
Add Comment
Puppet / PUP-2689
A node can't always collect its own exported resources
Depending on how tags are applied, a node does not collect its own resources. Setting the {{tag}} metaparameter in a resource default results in none of the test nodes collecting this resource. When the {{tag}} function is used, then each node collects the other nodes resources, but not it's own. When the resource has a {{tag =}} metaparameter ...
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-1744) User creation fails on OS X 10.9 if user is added to more than one group
Title: Message Title
Graham Gilbert commented on an issue
Re: User creation fails on OS X 10.9 if user is added to more than one group
I'm seeing this on 10.9 with Puppet 3.6.1.
Add Comment
Puppet / PUP-1744
User creation fails on OS X 10.9 if user is added to more than one group
When I try to create a user with more then one group on Mac OS X 10.9 with puppet 3.4.3 errors are thrown: {noformat} change from absent to admin,wheel failed: undefined method `split' for :absent:Symbol Could not prefetch user provider 'directoryservice': invalid byte sequence in US-ASCII undefined method `split' for :absent:Symbol ---...
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-2689) A node can't always collect its own exported resources
Title: Message Title
Lee Lowder commented on an issue
Re: A node can't always collect its own exported resources
My main desires are to have things work in a more consistent manner, for things to work as expected based on the documentation, and also to have better documentation where there differences/exceptions.
What that winds up looking like, I don't really care.
I was simply trying to document what I found, and also provide as much information to those who could investigate more deeply than I could.
Add Comment
Puppet / PUP-2689
A node can't always collect its own exported resources
Depending on how tags are applied, a node does not collect its own resources. Setting the {{tag}} metaparameter in a resource default results in none of the test nodes collecting this resource. When the {{tag}} function is used, then each node collects the other nodes resources, but not it's own. When the resource has a {{tag =}} metaparameter ...
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
Jira (PUP-2404) Merge puppet 3.6 into pe-puppet 3.3.x
Title: Message Title Kylo Ginsberg assigned an issue to Kylo Ginsberg Puppet / PUP-2404 Merge puppet 3.6 into pe-puppet 3.3.x Change By: Kylo Ginsberg Assignee: KyloGinsberg 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-2690) puppetlabs/apache module httpd.conf.erb template breaks with puppetboard/puppetmaster-passenger
Title: Message Title Thomas Steinert created an issue Puppet / PUP-2690 puppetlabs/apache module httpd.conf.erb template breaks with puppetboard/puppetmaster-passenger Issue Type: Bug Affects Versions: 3.6.1, 3.6.0, 3.5.1, 3.4.3 Assignee: Andy Parker Components: Modules Created: 28/May/14 9:40 AM Labels: puppetlabs-apache Priority: Normal Reporter: Thomas Steinert Hi there, As I summarized in the headline when I use the puppetlabs/apache module to install puppetboard with the nibalizer/puppetboard receipt in conjunction with the debian or ubuntu puppetmaster-passenger package the puppetmaster breaks after a puppet run. The reason is that the apache2 configuration (/etc/apache2/apache2.conf) will be replaced with one that is build from the httpd.conf.erb template of puppetlabs/apache module. Within this template the included sites are (per regexp) limited to sites within the /etc/apache2/sites-enabled/ folder ending with .conf. The puppetmaster site (and most of the other debian/ubuntu sites) usually use no endings and therefore will not be recognized.
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title
Rudy McComb commented on an issue
Re: Could not autoload puppet /util /instrumentation /listeners /log
Im on OSX 10.9.3. ruby --version ruby 2.0.0p451 (2014-02-24 revision 45167) [universal.x86_64-darwin13]
from agent cabimd010855:~ madmin$ sudo puppet agent -t --test --trace Password: Info: Retrieving pluginfacts Info: Retrieving plugin Info: Loading facts in /var/lib/puppet/lib/facter/concat_basedir.rb Info: Loading facts in /var/lib/puppet/lib/facter/esx_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/facter_dot_d.rb Info: Loading facts in /var/lib/puppet/lib/facter/git_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/has_compiler.rb Info: Loading facts in /var/lib/puppet/lib/facter/httpd_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_battery_charge_percent.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_battery_charging.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_battery_cycles.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_battery_health.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_current_user.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_encryption_enabled.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_flash_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_has_wireless.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_java_vendor.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_java_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_laptop.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_memory_in_gb.rb Info: Loading facts in /var/lib/puppet/lib/facter/mac_timezone.rb Info: Loading facts in /var/lib/puppet/lib/facter/mysql_client_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/mysql_server_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/operatingsystemversion.rb Info: Loading facts in /var/lib/puppet/lib/facter/os_maj_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/pe_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/php_rpm_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/php_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/printers.rb Info: Loading facts in /var/lib/puppet/lib/facter/puppet_vardir.rb Info: Loading facts in /var/lib/puppet/lib/facter/rabbitmq_erlang_cookie.rb Info: Loading facts in /var/lib/puppet/lib/facter/root_home.rb Info: Loading facts in /var/lib/puppet/lib/facter/rpm_version_httpd.rb Info: Loading facts in /var/lib/puppet/lib/facter/rpm_version_mysql.rb Info: Loading facts in /var/lib/puppet/lib/facter/rpm_version_php.rb Info: Loading facts in /var/lib/puppet/lib/facter/rvm_installed.rb Info: Loading facts in /var/lib/puppet/lib/facter/rvm_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/user_online.rb Info: Loading facts in /var/lib/puppet/lib/facter/vmwaretools_version.rb Info: Loading facts in /var/lib/puppet/lib/facter/warranty.rb Info: Loading facts in /var/lib/puppet/lib/facter/windows_productkey.rb Info: Loading facts in /var/lib/puppet/lib/facter/windows_sid.rb Info: Loading facts in /var/lib/puppet/lib/facter/windows_systemtype.rb Could not retrieve fact='mac_battery_charge_percent', resolution='anonymous': invalid value for Float(): Could not retrieve fact='mac_battery_charge_percent', resolution='anonymous': invalid value for Float(): sed: 1: 1 {p;q}
: extra characters at the end of q command Info: Caching catalog for cabimd010855.harborfreight.com Info: Applying configuration version '1401293317' Notice: /Stage[main]/Macmodule::Clientconfig/Exec[display msg at login screen]/returns: executed successfully Notice: /Stage[main]/Macmodule::Clientconfig/Exec[display sysinfo at login screen]/returns: executed successfully Notice: Finished catalog run in 13.55 seconds
Jira (PUP-2691) Real-world module skeletons still use the 'description' metadata property
Title: Message Title Pieter van de Bruggen created an issue Puppet / PUP-2691 Real-world module skeletons still use the 'description' metadata property Issue Type: Bug Affects Versions: 3.6.0 Assignee: Pieter van de Bruggen Created: 28/May/14 9:54 AM Priority: Normal Reporter: Pieter van de Bruggen As per https://github.com/garethr/puppet-module-skeleton/issues/13 Changes to the way modules are generated in Puppet 3.6 mean that where users could previously rely on the presence of certain absent properties, they no longer can. The most prevalent example of this is the description property –including a template in your module skeleton which depends on that property causes template expansion to be aborted mid-run. Add Comment
Jira (PUP-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Andy Parker commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log Rudy McComb, yes that is consistent with what we have seen from others. I think Joshua Cooper forgot about that wrinkle in the whole thing. The error only seems to come up after the agent has run a few times in daemon mode. In our investigation we found that the mtime on some files appeared to change and that caused it to try to reload the files. We were never able to determine why the mtime was changing, however. 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-2691) Real-world module skeletons still use the 'description' metadata property
Title: Message Title
Pieter van de Bruggen commented on an issue
Re: Real-world module skeletons still use the 'description' metadata property
PR: https://github.com/puppetlabs/puppet/pull/2701
Add Comment
Puppet / PUP-2691
Real-world module skeletons still use the 'description' metadata property
As per https://github.com/garethr/puppet-module-skeleton/issues/13 Changes to the way modules are generated in Puppet 3.6 mean that where users could previously rely on the presence of certain absent properties, they no longer can. The most prevalent example of this is the {{description}} property –including a template in your module skeleton which d...
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 Joshua Partlow commented on an issue Re: Merge puppet 3.6 into pe-puppet 3.3.x On Tuesday, May 27, 2014, Kylo Ginsberg (JIRA) issue-upda...@puppetlabs.com https://ci3.googleusercontent.com/proxy/Kv-cRGWju5b1NaXUOxVKiIKgmeDTtPqOQ8jDEJtc_2i9byW_BszptvaG_tqmT9yOaklI3FK_DJIxVl42rmVWZqhU9_jComgNkixXPs6aRbJTpl75CV6Ts-6wU3wl8xtoTlIY=s0-d-e1-ft#https://secure.gravatar.com/avatar/86ceae58ac8b7a41c36457f47819693e?d=mms=48 Kylo Ginsberg commented on an issue ... ./tests/environment/use_environment_from_environmentpath.rb any thoughts on those? Not yet but I will look into then when I get in. https://ci4.googleusercontent.com/proxy/6vzL32S5DYFNkklUKYYfVCrPGtTRgEUwVGSBifTjB57vJnEUjwHeIAEgctK18P0_isVHnSOMpID7mpTVisTuRAwpflV-ysOAcKqGTMyg9bKk=s0-d-e1-ft#https://tickets.puppetlabs.com/images/mail/comment-icon.png Add Comment https://ci4.googleusercontent.com/proxy/Qu-MBo5XibEDTxe3fWjiIJYNg8VHmeGKY8PLCPMJDWcEavn6mDznAgSb6HuasaGZCR59rQEc4fDn1NJhNt-zReh1rG0TQKXPEdjLAmiQhdWWDP-zkA=s0-d-e1-ft#https://tickets.puppetlabs.com/images/icons/issuetypes/task.png PUP-2404 https://ci3.googleusercontent.com/proxy/kg69Illf3xKUr020-j8EfAIpqDh2kUBfBsiZmiKzswLT8znnc3KC3X3UTi-pEIWY-ZHLyK-i-gHDVLHdg0vNq1voNb68ynRSYkK3FrQ635GHmKKw9cDHgg=s0-d-e1-ft#https://tickets.puppetlabs.com/images/mail/footer-desktop-logo.png – Josh Partlow jpart...@puppetlabs.com Developer, Puppet Labs Join us at PuppetConf 2014, September 22-24 in San Francisco - http://puppetconf.com Register by May 30th to take advantage of the Early Adopter discount —save $349! 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
Jira (PUP-2356) Add yum repo extra options
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2356 Add yum repo extra options Change By: Kylo Ginsberg Assignee: KyloGinsberg 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-2658) Provide Latest Windows MSI Package URL for Quick Download
Title: Message Title Matthaus Owens commented on an issue Re: Provide Latest Windows MSI Package URL for Quick Download The reason we stopped laying down latest files for other downloads, like tarballs, is because it is difficult to automate sanely (there are a few edge cases). Without automation, adding more manual steps to the release process is something we'd like to avoid. However, it does seem to be a common request, as I recall seeing something similar requested for apple packages. Add Comment Puppet / PUP-2658 Provide Latest Windows MSI Package URL for Quick Download Provide a Quick Download URL pointing to the latest version of puppet for windows. 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-2356) Add yum repo extra options
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2356 Add yum repo extra options Change By: Charlie Sharpsteen Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2356) Add yum repo extra options
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2356 Add yum repo extra options Change By: Charlie Sharpsteen 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 (PUP-2356) (PR 2577) Add yum repo extra options
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2356 (PR 2577) Add yum repo extra options Change By: Charlie Sharpsteen Summary: (PR2577) Addyumrepoextraoptions 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-2658) Provide Latest Windows MSI Package URL for Quick Download
Title: Message Title Louis Mayorga commented on an issue Re: Provide Latest Windows MSI Package URL for Quick Download I believe chef used to have it http://www.getchef.com/chef/install/ it seems that it would be nice to set something on the HTTP GET parameters to get the right version of the puppet installer. Add Comment Puppet / PUP-2658 Provide Latest Windows MSI Package URL for Quick Download Provide a Quick Download URL pointing to the latest version of puppet for windows. 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-1381) cron type and provider only return resources for ENV[USER] or root, not all users
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-1381 cron type and provider only return resources for ENV[USER] or root, not all users Change By: Andy Parker Assignee: FelixFrank AndyParker 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-1031) Improve Puppet's handling of non-ASCII character encodings
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-1031 Improve Puppet's handling of non-ASCII character encodings Change By: Kenn Hussey Fix Version/s: 4.x 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-410) Complete Implementation of Language based on the EGrammar
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-410 Complete Implementation of Language based on the EGrammar Change By: Kenn Hussey Fix Version/s: 3.7.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-850) Puppet 3.x Deprecations in Preparation for Puppet 4
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-850 Puppet 3.x Deprecations in Preparation for Puppet 4 Change By: Kenn Hussey Fix Version/s: 3.7.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-1381) cron type and provider only return resources for ENV[USER] or root, not all users
Title: Message Title
Andy Parker updated an issue
Puppet / PUP-1381
cron type and provider only return resources for ENV[USER] or root, not all users
Change By:
Andy Parker
*NOTE*:Thisticketnowonlytrackstheaddingofawarningabouttheupcomingfix.Therewillbeaseparatetickettotrackthefixitself.Originalreportbelow.Whenusing {{ resources \ {cron:purge=true \ } }} ,onlytherootuserscrontabispurged.Thisworks:{code}cron{foo:command=ls,ensure=present,user=root,}{code}(andthenproceedtocommenttheaboveout):{code}notice:/Cron[foo]/ensure:removed{code}Thisdoesnotwork:{code}cron{bar:command=ls,ensure=present,user=nick,}{code}Thiscrontabwillstillexistifcommentedout.Brokenin2.6andlateststable.
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-1381) cron type and provider only return resources for ENV[USER] or root, not all users
Title: Message Title
Andy Parker updated an issue
Puppet / PUP-1381
cron type and provider only return resources for ENV[USER] or root, not all users
Change By:
Andy Parker
*NOTE*:Thisticketnowonlytrackstheaddingofawarningabouttheupcomingfix.Therewillbeaseparatetickettotrackthefixitself.Originalreportbelow.Whenusing { { code} resources \ {cron:purge=true \ } {code } }, onlytherootuserscrontabispurged. Thisworks:{code}cron{foo:command=ls,ensure=present,user=root,}{code}(andthenproceedtocommenttheaboveout):{code}notice:/Cron[foo]/ensure:removed{code}Thisdoesnotwork:{code}cron{bar:command=ls,ensure=present,user=nick,}{code}Thiscrontabwillstillexistifcommentedout.Brokenin2.6andlateststable.
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-2242) Improve transaction event handling and propagation
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-2242 Improve transaction event handling and propagation Change By: Kenn Hussey Fix Version/s: 4.x Fix Version/s: 4.0.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-2555) Puppet 4.x Deprecations in Preparation for Puppet 5
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-2555 Puppet 4.x Deprecations in Preparation for Puppet 5 Change By: Kenn Hussey Fix Version/s: 4.x 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-1793) Cleanup, reduce, and improve stdlib based on new Puppet 4 features
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-1793 Cleanup, reduce, and improve stdlib based on new Puppet 4 features Change By: Kenn Hussey Fix Version/s: 4.0.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-536) Create endpoint for enumerating environments
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-536 Create endpoint for enumerating environments Change By: Kenn Hussey Fix Version/s: 3.6.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1805) Drop Ruby 1.8.7 support
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-1805 Drop Ruby 1.8.7 support Change By: Kenn Hussey Epic Name: Deprecate Ruby 1.8.7 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-552) Structured Facts support in Puppet
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-552 Structured Facts support in Puppet Change By: Kenn Hussey 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-552) Structured Facts support in Puppet
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-552 Structured Facts support in Puppet Change By: Kenn Hussey Epic Status: ToDo Done 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-233) Fact to add DHCP Server Details
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-233 Fact to add DHCP Server Details Change By: Kylo Ginsberg Sprint: Week2014-4-30to2014-5-7,Week2014-5-7to2014-5-14,Week2014-5- 28 21 to2014- 6 5 - 4 28 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-1381) cron type and provider only return resources for ENV[USER] or root, not all users
Title: Message Title
Andy Parker commented on an issue
Re: cron type and provider only return resources for ENV[USER] or root, not all users
Merged into master in 8516d9.
Add Comment
Puppet / PUP-1381
cron type and provider only return resources for ENV[USER] or root, not all users
*NOTE*: This ticket now only tracks the adding of a warning about the upcoming fix. There will be a separate ticket to track the fix itself. Original report below. When using {code}resources { cron: purge = true }{code} only the root users crontab is purged. This works: {code} cron {foo: command = ls, ensure =...
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-1125) Exec checks should be turned into metaparameters
Title: Message Title Colin Hudler commented on an issue Re: Exec checks should be turned into metaparameters Arguments beginning with a definition of what puppet is are not very constructive. Not only does that target move, but your operational model is not mine (hint: it only exists in your mind). Asserting some local notion of forward-looking purity of that vision just asks that we worship your ideal. Unless you have commit rights or otherwise speak for PL as a whole, I'm not on for that ride. Realize that this tool's workplace is often nasty, fiddly, and loaded with inconsistency (you know, like the whole rest of this world). That is nothing new. You won't have a sparkling clean feature set free from ugly beasts and burdens foisted from deep down in POSIX, et al. Theoretical correctness is a luxury and only maybe warrants a mention in passing, just as a reminder. Maybe we can get back to the question at hand now? (my 2 cents...) Felix Frank outlined the three needs well enough to proceed. But the change is maybe large, so I can only echo the suggestion to have it work just as the exec metaparam. Obviously you can save us a lot of time by closing the conversation when it is known to violate some community and/or constitutional principle which would outweigh those particular circumstances with which we devote so much of our time. Add Comment Puppet / PUP-1125 Exec checks should be turned into metaparameters The 'checks' in Exec -- refreshonly, onlyif and unless -- should be changed into metaparameters, so they're available for all resource types. My guess is that this will require defining a new type of metaparameter, in the same way that the Exec checks are a slightly different type of parameter.
Jira (PUP-1381) cron type and provider only return resources for ENV[USER] or root, not all users
Title: Message Title Andy Parker updated an issue Puppet / PUP-1381 cron type and provider only return resources for ENV[USER] or root, not all users Change By: Andy Parker Sprint: Week2014-5- 28 21 to2014- 6 5 - 4 28 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-724) Could not autoload puppet /util /instrumentation /listeners /log
Title: Message Title Rudy McComb commented on an issue Re: Could not autoload puppet /util /instrumentation /listeners /log Puppetmaster is Ubuntu 12.04LTS and 3.5.1 for Puppet. # ruby --version ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux] Joshua Cooper, I added the --trace for passenger and syslog is still reporting the same error with no more information May 28 10:59:46 calfrmprd01 puppet-master[31917]: (//calmacsdprd01.harborfreight.com//File[/var/lib/puppet/lib]) Failed to generate additional resources using 'eval_generate': undefined method `exist?' for Puppet::FileSystem:Module May 28 10:59:46 calfrmprd01 puppet-master[31917]: (//calmacsdprd01.harborfreight.com/Puppet) Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation May 28 10:59:46 calfrmprd01 puppet-master[31917]: (//calmacsdprd01.harborfreight.com/Puppet) Failed to apply catalog: Could not autoload puppet/util/instrumentation/listeners/log: Class Log is already defined in Puppet::Util::Instrumentation 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)
Jira (PUP-1070) puppetd doesn't always cleanup lockfile properly
Title: Message Title Ethan Brown updated an issue Puppet / PUP-1070 puppetd doesn't always cleanup lockfile properly Change By: Ethan Brown Sprint: Week2014-5- 28 21 to2014- 6 5 - 4 28 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 Andy Parker updated an issue Puppet / PUP-2692 Puppet master passenger processes keep growing The memory usage on the master graph shows the upgrade from 3.6.0 to 3.6.1 on Tuesday at about 16:00. Immediately after that the passenger processes quickly grew and started swapping. ps showed: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 31578 puppet20 0 1758m 1.6g 2564 R 84.2 13.4 66:36.38 ruby 15792 puppet20 0 1728m 1.5g 2476 S 5.2 13.3 40:15.84 ruby 10220 puppet20 0 1716m 1.5g 2484 R 67.7 13.1 44:31.14 ruby 25291 puppet20 0 1442m 1.3g 2568 R 98.2 10.9 34:07.42 ruby 27753 puppet20 0 973m 822m 2476 R 79.1 6.9 25:25.86 ruby 18022 puppet20 0 704m 584m 2484 R 97.7 4.9 13:00.75 ruby 12813 puppet20 0 548m 429m 3840 S 0.5 3.6 8:43.32 ruby 30465 foreman 20 0 614m 261m 2044 S 0.0 2.2 15:29.27 ruby 17145 foreman 20 0 614m 204m 3048 S 0.0 1.7 10:53.72 ruby 12128 foreman 20 0 614m 201m 2064 S 0.0 1.7 5:04.61 ruby 13193 foreman 20 0 626m 190m 1932 S 8.8 1.6 7:27.82 ruby 11999 foreman 20 0 614m 180m 2044 S 0.0 1.5 10:05.63 ruby Change By: Andy Parker Attachment: Memoryusageonmaster.jpg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (FACT-233) Fact to add DHCP Server Details
Title: Message Title Kylo Ginsberg commented on an issue Re: Fact to add DHCP Server Details Sigh. This doesn't work on RHEL7, b/c nmcli there defaults to return fewer fields. I'll patch that up. Add Comment Facter / FACT-233 Fact to add DHCP Server Details Add per interface fact that shows the DHCP server IP for that interface if the interface IP is DHCP assigned. e.g. 'dhcp_server_eth0' Also add a 'dhcp_server' fact if the interface the machine uses to reach the default gateway is dhcp enabled. PR created: https://github.com/puppetlabs/facter/pull/559 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 Andy Parker created an issue Puppet / PUP-2692 Puppet master passenger processes keep growing Issue Type: Bug Affects Versions: 3.6.1 Assignee: Unassigned Created: 28/May/14 11:35 AM Environment: passenger, ruby 1.9.3 software collections library Priority: Normal Reporter: Andy Parker Joshua Hoblitt 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. Add Comment
Jira (PUP-1070) puppetd doesn't always cleanup lockfile properly
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-1070 puppetd doesn't always cleanup lockfile properly Change By: Ethan Brown Assignee: KyloGinsberg EthanBrown Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1070) puppetd doesn't always cleanup lockfile properly
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-1070 puppetd doesn't always cleanup lockfile properly Change By: Ethan Brown Assignee: EthanBrown Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1070) puppetd doesn't always cleanup lockfile properly
Title: Message Title Ethan Brown updated an issue Puppet / PUP-1070 puppetd doesn't always cleanup lockfile properly Change By: Ethan Brown 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 (PDB-690) PR (974): Typo in v4/reports.markdown - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-690 PR (974): Typo in v4/reports.markdown - kbarber Change By: Kenneth Barber Issue Type: Task Bug Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-672) resource from puppetmaster deleted immediately after insertion
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-672 resource from puppetmaster deleted immediately after insertion Change By: Kenneth Barber Assignee: KennethBarber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-672) resource from puppetmaster deleted immediately after insertion
Title: Message Title
Kenneth Barber commented on an issue
Re: resource from puppetmaster deleted immediately after insertion
Ping Chris Lee can you provide more information, see above.
Add Comment
PuppetDB / PDB-672
resource from puppetmaster deleted immediately after insertion
I am using the backuppc module that has the following code for the client: {code} @@file { ${backuppc::params::config_directory}/pc/${::fqdn}.pl: ensure = $ensure, content = template(${module_name}/host.pl.erb), owner = 'backuppc', group = $backuppc::params::group_apache, mode = '0640', tag = backuppc...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PDB-672) resource from puppetmaster deleted immediately after insertion
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-672 resource from puppetmaster deleted immediately after insertion Change By: Kenneth Barber Assignee: KennethBarber ChrisLove 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-688) java.lang.OutOfMemoryError
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-688 java.lang.OutOfMemoryError Change By: Kenneth Barber Assignee: jonyeargers 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-685) PR (128): add parameter 'max_threads' to define value in jetty.ini - mklette
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-685 PR (128): add parameter 'max_threads' to define value in jetty.ini - mklette Change By: Kenneth Barber Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-688) java.lang.OutOfMemoryError
Title: Message Title Kenneth Barber commented on an issue Re: java.lang.OutOfMemoryError jon yeargers has this made any difference? Add Comment PuppetDB / PDB-688 java.lang.OutOfMemoryError Upgraded to v 2.0 via 'yum update'. Restarted puppetdb via 'service puppetdb start' Let clients connect. Wait a day. Notice that puppetdb isn't running any more. Look at /var/log/puppetdb/puppetdb-daemon.log See messages like: Java.lang.OutOfMemoryError: Java heap space Dumping heap to 'file name' Heap dump created [large number in 2.5 sec... 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-688) java.lang.OutOfMemoryError
Title: Message Title jon yeargers commented on an issue Re: java.lang.OutOfMemoryError Stable so far. 14390 puppetdb 20 0 5086m 582m 13m S 0.0 1.8 116:12.87 /usr/lib/jvm/jre-1.7.0-openjdk.x86_64/bin/java -XX:_OnOutOfMemoryError_=kill -9 %p -Xmx512m -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/puppetdb/puppetdb-oom.hprof -Djava.security.egd=file:/dev/urandom -cp /usr/share/puppetdb/puppetdb.jar clojure.main -m com.puppetlabs.puppetdb.core services -c /etc/puppetdb/conf.d Add Comment PuppetDB / PDB-688 java.lang.OutOfMemoryError Upgraded to v 2.0 via 'yum update'. Restarted puppetdb via 'service puppetdb start' Let clients connect. Wait a day. Notice that puppetdb isn't running any more. Look at /var/log/puppetdb/puppetdb-daemon.log See messages like: Java.lang.OutOfMemoryError: Java heap space Dumping heap to 'file name' Heap dump created [large number in 2.5 sec... 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
Jira (FACT-233) Fact to add DHCP Server Details
Title: Message Title Kylo Ginsberg commented on an issue Re: Fact to add DHCP Server Details RHEL7 patch pushed in https://github.com/puppetlabs/facter/commit/8bbad973b37335b78d8ac317098440ffa9c9dce6. Add Comment Facter / FACT-233 Fact to add DHCP Server Details Add per interface fact that shows the DHCP server IP for that interface if the interface IP is DHCP assigned. e.g. 'dhcp_server_eth0' Also add a 'dhcp_server' fact if the interface the machine uses to reach the default gateway is dhcp enabled. PR created: https://github.com/puppetlabs/facter/pull/559 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-672) resource from puppetmaster deleted immediately after insertion
Title: Message Title
Chris Love commented on an issue
Re: resource from puppetmaster deleted immediately after insertion
Kenneth Barber been a crazy couple of weeks. I will get you an update shortly.
Add Comment
PuppetDB / PDB-672
resource from puppetmaster deleted immediately after insertion
I am using the backuppc module that has the following code for the client: {code} @@file { ${backuppc::params::config_directory}/pc/${::fqdn}.pl: ensure = $ensure, content = template(${module_name}/host.pl.erb), owner = 'backuppc', group = $backuppc::params::group_apache, mode = '0640', tag = backuppc...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1843) 3.4.0 broke compatibility with plugins using the hiera indirector terminus
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-1843 3.4.0 broke compatibility with plugins using the hiera indirector terminus Change By: Joshua Partlow Sprint: Week2014-5-21to2014-5-28 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-2693) LiteralString class parameters get parsed with positioning information that includes a negative length
Title: Message Title
Charlie Sharpsteen created an issue
Puppet / PUP-2693
LiteralString class parameters get parsed with positioning information that includes a negative length
Issue Type:
Bug
Affects Versions:
3.6.1
Assignee:
Henrik Lindberg
Components:
DSL
Created:
28/May/14 12:12 PM
Labels:
future-parser
Priority:
Normal
Reporter:
Charlie Sharpsteen
When using the future parser, any class parameter with a LiteralString value receive positioning information with a negative length:
# param_test.rb
require 'puppet'
require 'puppet/pops'
parser = Puppet::Pops::Parser::Parser.new
result = parser.parse_string -EOM
class test::class (
$param_one = undef,
$param_two = 'some string',
$param_three = true,
$param_four = 'another string',
$param_five = $some::varaible::somewhere,
) {}
EOM
result.current.definitions.each do |d|
d.parameters.each do |p|
puts #{p.name}: #{p.value.length}
end
end
Jira (PUP-2692) Puppet master passenger processes keep growing
Title: Message Title Chuck Schweizer commented on an issue Re: Puppet master passenger processes keep growing I have seen this on RHEL 6.5 with puppet 3.6.1, ruby 1.8.7 and passenger 4.0.18. I had to set PassengerMaxRequests to 5000 in my environment to keep this in check. 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-1843) 3.4.0 broke compatibility with plugins using the hiera indirector terminus
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-1843 3.4.0 broke compatibility with plugins using the hiera indirector terminus Change By: Joshua Partlow Story Points: 1 Fix Version/s: 3.7.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-1843) 3.4.0 broke compatibility with plugins using the hiera indirector terminus
Title: Message Title Joshua Partlow updated an issue Puppet / PUP-1843 3.4.0 broke compatibility with plugins using the hiera indirector terminus Change By: Joshua Partlow Component/s: Community 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 Kylo Ginsberg updated an issue Puppet / PUP-1070 puppetd doesn't always cleanup lockfile properly Change By: Kylo Ginsberg Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-672) resource from puppetmaster deleted immediately after insertion
Title: Message Title
Chris Love commented on an issue
Re: resource from puppetmaster deleted immediately after insertion
see this test https://gist.github.com/chrislovecnm/639c593554f5235ec249
@@notify is working
Add Comment
PuppetDB / PDB-672
resource from puppetmaster deleted immediately after insertion
I am using the backuppc module that has the following code for the client: {code} @@file { ${backuppc::params::config_directory}/pc/${::fqdn}.pl: ensure = $ensure, content = template(${module_name}/host.pl.erb), owner = 'backuppc', group = $backuppc::params::group_apache, mode = '0640', tag = backuppc...
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 http://jenkins-enterprise.delivery.puppetlabs.net/job/PE%20Puppet%20Acceptance%20Tests/85/#showFailuresLink had 72 failures: 56 are the tests/modules/lists/with_supported_pe_version.rb which I didn't correctly patch up. I'll fix that shortly. 7 are tests/environment/use_environment_from_environmentpath.rb so there may be something there I haven't looked at the other 9 yet. 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)
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 the puppet processes are leaking memory until the Linux OOM kicks in (my dmesg is full of OOM message). Here's what top looked like about 20 minutes after what Andy cut'n'pasted. top - 11:38:39 up 8 days, 20:19, 2 users, load average: 42.33, 24.24, 12.80 Tasks: 473 total, 1 running, 469 sleeping, 0 stopped, 3 zombie Cpu(s): 1.6%us, 13.2%sy, 0.8%ni, 0.0%id, 84.5%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 12137736k total, 11958116k used, 179620k free, 3044k buffers Swap: 2097144k total, 959332k used, 1137812k free,31372k cached PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 31578 puppet20 0 2196m 1.9g 1900 D 0.0 16.1 79:20.31 ruby 10220 puppet20 0 1974m 1.8g 1892 D 4.6 15.3 57:01.99 ruby 15792 puppet20 0 1947m 1.8g 1920 D 0.0 15.2 53:44.97 ruby 25291 puppet20 0 1795m 1.6g 1896 D 0.0 13.8 44:05.28 ruby 27753 puppet20 0 1114m 961m 1920 D 0.0 8.1 34:19.15 ruby 18022 puppet20 0 1080m 956m 2092 D 0.0 8.1 20:05.17 ruby 12813 puppet20 0 871m 747m 2108 D 0.0 6.3 20:30.50 ruby 30465 foreman 20 0 614m 254m 1708 S 0.0 2.2 15:41.30 ruby 17145 foreman 20 0 614m 203m 1912 S 0.0 1.7 11:05.40 ruby 13193 foreman 20 0 626m 190m 1692 S 0.0 1.6 7:46.49 ruby 11999 foreman 20 0 614m 177m 1912 S 0.0 1.5 10:56.76 ruby 12128 foreman 20 0 614m 156m 1820 S 0.0 1.3 5:50.51 ruby 20897 activemq 20 0 4198m 85m 900 S 0.0 0.7 0:32.14 java 6801 mysql 20 0 1461m 44m 2540 S 0.0 0.4 1144:30 mysqld 23666 apache20 0 2177m 42m 2748 S 0.0 0.4 0:26.37 httpd.worker 15151 apache20 0 2175m 39m 2768 S 0.0 0.3 0:29.48 httpd.worker 20720 apache20 0 2171m 36m 2744 S 0.0 0.3 0:02.60 httpd.worker I'm working on trying to get the heap_dump gem to work (at all) and then with the SCL ruby193 that foreman is providing. Add Comment Puppet /
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 Chuck Schweizer I'm on SL6.5 and using the foreman ruby193 SCL packages: ruby193-ruby-1.9.3.327-29.el6.x86_64 ruby193-rubygem-passenger-4.0.5-3.el6.x86_64 puppet-server-3.6.1-1.el6.noarch 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
Jira (PDB-672) resource from puppetmaster deleted immediately after insertion
Title: Message Title
Chris Love commented on an issue
Re: resource from puppetmaster deleted immediately after insertion
I am still seeing the insert and then the delete in the puppetdb logs
2014-05-28 19:21:36,594 DEBUG [command-proc-64] [bonecp.PreparedStatementHandle] SELECT type, title, tags, exported, file, line, resourceFROM catalog_resources WHERE catalog_id = 6
// a bunch on more work
976 2014-05-28 19:21:36,627 DEBUG [command-proc-64] [bonecp.PreparedStatementHandle] SELECT DISTINCT resource FROM resource_params_cache WHERE resource IN a bunch of guids
2014-05-28 19:21:35,929 DEBUG [command-proc-65] [bonecp.PreparedStatementHandle] INSERT INTO catalog_resources (catalog_id,resource,type,title,tags,exported,file,line) VALUES (6,'14be980772ccedd05d2c7e8d31563f20159b71a1','File','/etc/backuppc/pc/icinga01a.igivefirst.com.pl',(array of type7),true,'/etc/puppet/modules/backuppc/manifests/client.pp',418)
2014-05-28 19:21:36,649 DEBUG [command-proc-64] [bonecp.StatementHandle] DELETE FROM catalog_resources WHERE catalog_id = 6 and type = 'File' and title = '/etc/backuppc/pc/puppetmaster.pl'
Add Comment
PuppetDB / PDB-672
resource from puppetmaster deleted immediately after insertion
I am using the backuppc module that has the following code for the client: {code} @@file { ${backuppc::params::config_directory}/pc/${::fqdn}.pl: ensure = $ensure, content = template(${module_name}/host.pl.erb), owner = 'backuppc', group = $backuppc::params::group_apache, mode = '0640', tag = backuppc...
Jira (PDB-672) resource from puppetmaster deleted immediately after insertion
Title: Message Title Chris Love assigned an issue to Kenneth Barber added updates sending back your way. Let me know if I can do more debugging PuppetDB / PDB-672 resource from puppetmaster deleted immediately after insertion Change By: Chris Love Assignee: ChrisLove KennethBarber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-672) resource from puppetmaster deleted immediately after insertion
Title: Message Title
Chris Love commented on an issue
Re: resource from puppetmaster deleted immediately after insertion
What is the syntax to do a file add and then access it via the api? Also should I update to puppet db 2?
Add Comment
PuppetDB / PDB-672
resource from puppetmaster deleted immediately after insertion
I am using the backuppc module that has the following code for the client: {code} @@file { ${backuppc::params::config_directory}/pc/${::fqdn}.pl: ensure = $ensure, content = template(${module_name}/host.pl.erb), owner = 'backuppc', group = $backuppc::params::group_apache, mode = '0640', tag = backuppc...
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-233) Fact to add DHCP Server Details
Title: Message Title Kylo Ginsberg commented on an issue Re: Fact to add DHCP Server Details The acceptance tests for the 3 nmcli platforms we test against (fedora 19, fedora 20, rhel 7) all confirmed this is working. That works for FR for me. Add Comment Facter / FACT-233 Fact to add DHCP Server Details Add per interface fact that shows the DHCP server IP for that interface if the interface IP is DHCP assigned. e.g. 'dhcp_server_eth0' Also add a 'dhcp_server' fact if the interface the machine uses to reach the default gateway is dhcp enabled. PR created: https://github.com/puppetlabs/facter/pull/559 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-121) Remove relative namespacing
Title: Message Title Ethan Brown assigned an issue to Unassigned Puppet / PUP-121 Remove relative namespacing Change By: Ethan Brown Assignee: EthanBrown Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2694) Scope replacing webrick with a rack-based lightweight server, e.g. thin
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-2694 Scope replacing webrick with a rack-based lightweight server, e.g. thin Issue Type: Improvement Assignee: Unassigned Created: 28/May/14 1:02 PM Fix Versions: 4.0.0 Priority: Normal Reporter: Kylo Ginsberg This would be an improvement from a maintenance perspective (not supporting both webrick and rack), from a testing perspective (we are sometimes bitten by testing against webrick-only), and possibly from a performance perspective (webrick is slow). This will require some scoping effort up front and that's what this ticket is for. Add Comment
Jira (PUP-2383) Need x64 win-builder to generate both 32 and 64bit MSIs
Title: Message Title Moses Mendoza commented on an issue Re: Need x64 win-builder to generate both 32 and 64bit MSIs Joshua Cooper setting up a new x64 builder would be done by the Infrastructure and Tooling team, I believe, so a ticket in the INFTOOL project to set it up and get it connected to the appropriate jenkins would be the next step there. Add Comment Puppet / PUP-2383 Need x64 win-builder to generate both 32 and 64bit MSIs Need to verify that existing win-builders are x64 and can generate MSIs for both platforms. If win-builders are x32, then we will need to provision new x64 builders. 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 Joshua Partlow commented on an issue Re: Merge puppet 3.6 into pe-puppet 3.3.x I just ran the use_environment_from_environmentpath.rb on oracle5 32m-32d-32c and it passed. So it may be intermittent or test state spill over from previous tests or both. I'm trying the scientific5 32mcd, and will look at run 85's 7 failures. 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-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2650 3.6.1 issues warning message for deprecation Change By: Kylo Ginsberg Fix Version/s: 3.6.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2650) 3.6.1 issues warning message for deprecation
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2650 3.6.1 issues warning message for deprecation Change By: Kylo Ginsberg Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2692) Puppet master passenger processes keep growing
Title: Message Title Andy Parker updated an issue Puppet / PUP-2692 Puppet master passenger processes keep growing Change By: Andy Parker Fix Version/s: 3.6.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
