Jira (PUP-2719) Windows mount provider (smb/cifs)
Title: Message Title Nicholas Albion commented on an issue Re: Windows mount provider (smb/cifs) The provider implementation is attached, but I did not find the type implementation - I suppose it would be trivial... Add Comment Puppet / PUP-2719 Windows mount provider (smb/cifs) Since UNC paths are not supported and packages cannot be sourced from the puppet master directly (instead you have to create a file resource whose source is the puppet master and then install the package from the local file), it would be nice to have a mount provider on Windows that could mount network shares, e.g. net use z:. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this 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-2719) Windows mount provider (smb/cifs)
Title: Message Title
Paul Tötterman commented on an issue
Re: Windows mount provider (smb/cifs)
The implementation is in the attachment.
Sample usage is something like:
mapped_drive { 'I:' ensure => present, remote => '\\server\share', }
Doesn't seem to support username and password. I don't have the need or time to fix that. If I were to do this again, I would go with the powershell module: https://forge.puppetlabs.com/puppetlabs/powershell
Add Comment
Puppet / PUP-2719
Windows mount provider (smb/cifs)
Since UNC paths are not supported and packages cannot be sourced from the puppet master directly (instead you have to create a file resource whose source is the puppet master and then install the package from the local file), it would be nice to have a mount provider on Windows that could mount network shares, e.g. net use z:.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop re
Jira (PUP-2939) puppet (enterprise) doesn't restart web server after doing a "ca revoke"
Title: Message Title Geoff Williams commented on an issue Re: puppet (enterprise) doesn't restart web server after doing a "ca revoke" spec tests ~line 90 ./spec/unit/indirector/ssl_file_spec.rb Add Comment Puppet / PUP-2939 puppet (enterprise) doesn't restart web server after doing a "ca revoke" Very very occasionally someone will have an emergency and need to revoke a certificate with "puppet ca revoke". On this day, I guarantee that they will forget to also restart apache, leaving this person open to attack. In today's last ever puppet advanced course we taught students to restart apache after doing a revoke -- lets make their lives easie... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this 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-2719) Windows mount provider (smb/cifs)
Title: Message Title Nicholas Albion commented on an issue Re: Windows mount provider (smb/cifs) ...also need to be able to specify username & password to connect to a remote share Add Comment Puppet / PUP-2719 Windows mount provider (smb/cifs) Since UNC paths are not supported and packages cannot be sourced from the puppet master directly (instead you have to create a file resource whose source is the puppet master and then install the package from the local file), it would be nice to have a mount provider on Windows that could mount network shares, e.g. net use z:. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this 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-2719) Windows mount provider (smb/cifs)
Title: Message Title Nicholas Albion commented on an issue Re: Windows mount provider (smb/cifs) Paul Tötterman would you also be able to provide the type implementation and example usage? Thanks Add Comment Puppet / PUP-2719 Windows mount provider (smb/cifs) Since UNC paths are not supported and packages cannot be sourced from the puppet master directly (instead you have to create a file resource whose source is the puppet master and then install the package from the local file), it would be nice to have a mount provider on Windows that could mount network shares, e.g. net use z:. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this 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-2924) Puppet searches disk for whit classes
Title: Message Title
Kylo Ginsberg commented on an issue
Re: Puppet searches disk for whit classes
I'd like to see if we can get this done for 3.7, so I'm optimistically scheduling it for 3.7. That release is running tight though, so no guarantees on that.
Meanwhile Peter Bakkum if you get a chance to try out Charlie's patch that would be nice confirmation.
Add Comment
Puppet / PUP-2924
Puppet searches disk for whit classes
Our Puppet instance has been pretty slow lately so we traced a puppet agent run to see what it was doing. In the trace we see a bunch of lines like this: stat("/opt/local/lib/ruby/site_ruby/2.0.0/puppet/vendor/semantic/lib/puppet/type/completed_stage.rb", 0xFD7FFFDFE4A0) Err#2 ENOENT stat("/etc/puppet/modules/admin/lib/puppet/type/completed_stage
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this 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@googlegro
Jira (PUP-2937) Windows: Unable to reference packages with UTF-8 Characters in their names
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2937 Windows: Unable to reference packages with UTF-8 Characters in their names Change By: Kylo Ginsberg Affects Version/s: 3.x Affects 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-2924) Puppet searches disk for whit classes
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2924 Puppet searches disk for whit classes Change By: Kylo Ginsberg 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-2924) Puppet searches disk for whit classes
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2924 Puppet searches disk for whit classes Change By: Kylo Ginsberg Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2939) puppet (enterprise) doesn't restart web server after doing a "ca revoke"
Title: Message Title Geoff Williams commented on an issue Re: puppet (enterprise) doesn't restart web server after doing a "ca revoke" Initial research identifies this code should go in the file: /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/ssl/certificate_revocation_list.rb in the revoke() method ~line 62 Will get to work on a PR during my no travel week Add Comment Puppet / PUP-2939 puppet (enterprise) doesn't restart web server after doing a "ca revoke" Very very occasionally someone will have an emergency and need to revoke a certificate with "puppet ca revoke". On this day, I guarantee that they will forget to also restart apache, leaving this person open to attack. In today's last ever puppet advanced course we taught students to restart apache after doing a revoke -- lets make their lives easie... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it
Jira (PUP-2939) puppet (enterprise) doesn't restart web server after doing a "ca revoke"
Title: Message Title Geoff Williams created an issue Puppet / PUP-2939 puppet (enterprise) doesn't restart web server after doing a "ca revoke" Issue Type: Bug Affects Versions: 3.2.3 Assignee: Geoff Williams Created: 15/Jul/14 9:41 PM Environment: linux/puppet-enterprise Priority: Normal Reporter: Geoff Williams Very very occasionally someone will have an emergency and need to revoke a certificate with "puppet ca revoke". On this day, I guarantee that they will forget to also restart apache, leaving this person open to attack. In today's last ever puppet advanced course we taught students to restart apache after doing a revoke – lets make their lives easier by doing something like: PE: After revoking certificate we will restart pe-httpd (graceful or reload to prevent killing active connections) OSS After revoking certificate, print a message along the lines of "don't forget to restart your web server"
Jira (PUP-2937) Windows: Unable to reference packages with UTF-8 Characters in their names
Title: Message Title Ken Sykora commented on an issue Re: Windows: Unable to reference packages with UTF-8 Characters in their names 3.6.2 Add Comment Puppet / PUP-2937 Windows: Unable to reference packages with UTF-8 Characters in their names I'm currently trying to prevent a specific package from continuing its install run on subsequent puppet apply commands. The package in Question is the Windows Azure SDK for .Net 2.3. The package's name listed in the registry contains an endash (–) instead a normal hyphen. See attached screen shot for view from "programs and features" control panel. ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2938) Directory environments should support a global modulepath
Title: Message Title James Sweeny commented on an issue Re: Directory environments should support a global modulepath Thanks Andy Parker, I updated the description to clarify. The fact is, a global modulepath, is not there as it stands when using modulepath in environment.conf. If you have to/can set the same value in every instance, I would hardly call it global. Yes, you could configure it such that each environment has the same "fallback" or "override" module path, but that needs to be done for each environment if you make any per-environment changes to the modulepath. You have the request right that there should be a global overriding modulepath, that is the same regardless of environment. I would argue that it should not be overridden, but whether it is or not may be a choice a user would want (I don't have a strong opinion on it, others may). My only opinion on over-writing is that doing so should be explicit. That is, the user should know that they are replacing a value that was defined somewhere else for some reason. On precedence, you laid out two options, and there's technically a third: 1) environment modules are searched before global 2) global modules are searched before environment 3) configurable I lean strongly towards 1. Configurable precedence (3) would (I imagine) create a lot more work, and definitely some UX questions (how do we set it? more config parameters? where do we set it? etc.). For global-before-environment precedence, I don't have a strong argument, and I'm having trouble thinking of use cases that would not be effective (and I have not seen anyone do this in the wild, though I'm sure I'll be corrected). For environment before global, at least one obvious use case springs to mind: Puppet Enterprise! Granted, it shouldn't matter either way if all the pe_* modules are properly prefixed, but they aren't (in PE 3.3 only 8/19 are). There have been many times in the past where a PE user needed to override a built in module with their own, essentially "taking it out" of PE's control. I'll stop there on that point, since a conversation about the /opt/puppet/share/puppet/modules directory is probably better left to the PE project. Outside of PE, the main use case that comes to mind is companies where the puppet master is a shared service, but independent groups control their own environments. A central infrastructure team manages a set of core modules that are released at a different cadence than the environments themselves, which might all have completely separate release processes (since they serve completely independent business functions). Not to get into the pros and cons of this approach, and the implications about cooperation between teams in the release process, but it's being used in some very large deployments. It would be nice if a single environment's modulepath was the only module path, since every module would be tied to a single rev (likely that of a Puppetfile's repo), but it's not an option for some companies in practice (I won't name them on a public tracker, but feel free to get me 1:1).
Jira (PUP-2924) Puppet searches disk for whit classes
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-2924 Puppet searches disk for whit classes Change By: Charlie Sharpsteen Assignee: Charlie Sharpsteen Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2924) Puppet searches disk for whit classes
Title: Message Title
Charlie Sharpsteen commented on an issue
Re: Puppet searches disk for whit classes
Kylo Ginsberg: The patch above appears to resolve this issue, however we do pass typing information to Puppet::Resource.new. If we can use that to eliminate the need to set resource_type on instances after creation, it might be a better long term solution.
On a CentOS 6 test box, a vanilla Puppet agent makes 1080 calls to stat caused by 40 erroneous whit lookups for 1 node, 1 class and 1 stage. Eliminating the whit lookups shaves 0.1 seconds off of an empty catalog run. Each Class added to the catalog appears to generate 270 additional stat calls. These numbers will be sensitive to the size of the Ruby LOAD_PATH and, by extension, the Puppet MODULE_PATH.
It seems like there are some good performance gains we could get here, kicking this one to you for a scheduling decision.
Add Comment
Puppet / PUP-2924
Puppet searches disk for whit classes
Our Puppet instance has been pretty slow lately so we traced a puppet agent run to see what it was doing. In the trace we see a bunch of lines like this: stat("/opt/local/lib/ruby/site_ruby/2.0.0/puppet/vendor/semantic/lib/puppet/type/completed_stage.rb", 0xFD7FFFDFE4A0) Err#2 ENOENT stat("/etc/puppet/modules/admin/lib/puppet/type/completed_stage
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2938) Directory environments should support a global modulepath
Title: Message Title James Sweeny updated an issue Puppet / PUP-2938 Directory environments should support a global modulepath Change By: James Sweeny Directory environments introduces three new configuration options to replace modulepath: "basemodulepath" and "environmentpath" in puppet.conf and "modulepath" in separate environment.conf files (one for each environment). If a modulepath is specified in an environment's environment.conf file, neither the basemodulepath nor environmentpath are is not used unless directly referenced elsewhere .In the now deprecated method for specifying multiple environments, users often add additional module paths that are global to all environments. A classic example is the path for Puppet Enterprise modules, which would not change from environment to environment on a single master. In the current directory environments implementation, a global module path that is environment independent cannot be set if the environment.conf file uses the modulepath setting. Avoiding the environment.conf setting is not an option, since doing so removes the ability to rename or set multiple modulepaths for an environment.Some possible fixes off the top of my head:1) Make basemodulepath global.2) Add a globalmodulepath option. This is my personal preference, since the name is more intuitive, and also calls out that basemodulepath likely isn't global. However, there is some room for debate about whether this value comes before or after the environment-specified module path. Other options along this line of thinking could get very wordy :)I'd be happy to brainstorm more. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You rec
Jira (PUP-2924) Puppet searches disk for whit classes
Title: Message Title Charlie Sharpsteen commented on an issue Re: Puppet searches disk for whit classes Thanks for reporting this! There is definitely some wasted effort going on here. The core of the problem is that we have a very expensive lookup operation that determines the Type associated with a resource: Puppet::Resource#resource_type. Due to the expense, some methods set the resource_type if this information is known and available when a Resource instance is created. However, when retrieving the state of whits, a Resource instance is created that does not receive available type information: debug call: load /puppetlabs/puppet/lib/puppet/util/autoload.rb:194 name = :completed_stage env = production /puppetlabs/puppet/lib/puppet/util/autoload.rb:194:in `load' /puppetlabs/puppet/lib/puppet/metatype/manager.rb:163:in `type' /puppetlabs/puppet/lib/puppet/resource.rb:242:in `resource_type' /puppetlabs/puppet/lib/puppet/resource.rb:163:in `builtin_type?' /puppetlabs/puppet/lib/puppet/resource.rb:475:in `namevar' /puppetlabs/puppet/lib/puppet/resource.rb:466:in `parameter_name' /puppetlabs/puppet/lib/puppet/resource.rb:140:in `[]=' /puppetlabs/puppet/lib/puppet/type.rb:1032:in `retrieve' /puppetlabs/puppet/lib/puppet/type.rb:1063:in `retrieve_resource' /puppetlabs/puppet/lib/puppet/transaction/resource_harness.rb:223:in `from_resource' /puppetlabs/puppet/lib/puppet/transaction/resource_harness.rb:19:in `evaluate' /puppetlabs/puppet/lib/puppet/transaction.rb:174:in `apply' /puppetlabs/puppet/lib/puppet/transaction.rb:187:in `eval_resource' /puppetlabs/puppet/lib/puppet/transaction.rb:117:in `call' /puppetlabs/puppet/lib/puppet/transaction.rb:117:in `block (2 levels) in evaluate' /puppetlabs/puppet/lib/puppet/util.rb:327:in `block in thinmark' /opt/rh/ruby193/root/usr/share/ruby/benchmark.rb:295:in `realtime' /puppetlabs/puppet/lib/puppet/util.rb:326:in `thinmark' /puppetlabs/puppet/lib/puppet/transaction.rb:117:in `block in evaluate' /puppetlabs/puppet/lib/puppet/graph/relationship_graph.rb:118:in `traverse' /puppetlabs/puppet/lib/puppet/transaction.rb:108:in `evaluate' /puppetlabs/puppet/lib/puppet/resource/catalog.rb:167:in `block in apply' /puppetlabs/puppet/lib/puppet/util/log.rb:149:in `with_destination' /puppetlabs/puppet/lib/puppet/transaction/report.rb:112:in `as_logging_destination' /puppetlabs/puppet/lib/puppet/resource/catalog.rb:166:in `apply' /puppetlabs/puppet/lib/puppet/configurer.rb:117:in `block in apply_catalog' /puppetlabs/puppet/lib/puppet/util.rb:161:in `block in benchmark' /opt/rh/ruby193/root/usr/share/ruby/benchmark.rb:295:in `realtime' /puppetlabs/puppet/lib/puppet/util.rb:160:in `benchmark' /puppetlabs/puppet/lib/puppet/configurer.rb:116:in `apply_catalog' /puppetlabs/puppet/lib/puppet/configurer.rb:191:in `run' /puppetlabs/puppet/lib/puppet/agent.rb:47:in `block (4 levels) in run' /puppetlabs/puppet/lib/puppet/agent/locker.rb:20:in `lock' /puppetlabs/puppet/lib/puppet/agent.rb:47:in `block (3 levels) in run' /puppetlabs/puppet/lib/puppet/agent.rb:117:in `with_client' /puppetlabs/puppet/lib/puppet/agent.rb:44:in `block (2 levels) in run' /puppetlabs/puppet/lib/puppet/agent.rb:82:in `run_in_fork' /puppetlabs/puppet/lib/puppet/agent.rb:43:in `block in run' /puppetlabs/puppet/lib/puppet/application.rb:179:in `call' /puppetlabs/puppet/lib/puppet/application.rb:179:in `controlled_run' /puppetlabs/puppet/lib/puppet/agent.rb:41:in `run' /puppetlabs/puppet/lib/puppet/application/agent.rb:355:in `onetime' /puppetlabs/puppet/lib/puppet/application/agent.rb:321:in `run_command' /puppetlabs/puppet/lib/puppet/application.rb:371:in `block (2 levels) in run' /puppetlabs/puppet
Jira (PUP-2938) Directory environments should support a global modulepath
Title: Message Title Andy Parker commented on an issue Re: Directory environments should support a global modulepath James Sweeny, I think you are misunderstanding some of the options that you outline. environmentpath isn't directly related, nor does it replace, modulepath. It is simply the list of directories in which to find environments. The basemodulepath is needed in order to construct the default modulepath of an environment. It can, however, be referenced from the environment.conf and so the statement that it isn't used is only true if the value in environment.conf doesn't use $basemodulepath. The basic capability of a global modulepath is currently there as the system stands, the user needs to opt-into using the $basemodulepath in the environment.conf. I think what the request here is for is that there is a global set of modules that imposes itself on the environment. However, now the question is: can that set of modules be overridden? Is an environment allowed to place its own module in front of the global modules thereby shadowing it (this would say modulepath=local:$global). Or is it that the global path always takes precedence (this would be modulepath=$global:local). If they can be overridden, can an environment completely opt-out of the global modules? Add Comment Puppet / PUP-2938 Directory environments should support a global modulepath Directory environments introduces three new configuration options to replace modulepath: "basemodulepath" and "environmentpath" in puppet.conf and "modulepath" in separate environment.conf files (one for each environment). If a modulepath is specified in an environment's environment.conf file, neither the basemodulepath nor environmentpath are used. In...
Jira (PUP-2886) future parser should validate class/resource names that are types
Title: Message Title
Joshua Partlow commented on an issue
Re: future parser should validate class/resource names that are types
Merge to master in c31da16
Add Comment
Puppet / PUP-2886
future parser should validate class/resource names that are types
The validator should issue an error if a type name is used as the name of a class or define. {code} define integer { } class data {} {code} The names should be allowed when used in some context e.g. {{MyVeryOwn::Integer}} - this, although most names are computer science like, the type Data may be something that people want to use. There is no ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this 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-2714) Future parser returns nil when parsing a source that contains no statements
Title: Message Title
Joshua Partlow commented on an issue
Re: Future parser returns nil when parsing a source that contains no statements
Merged to master in 0311be1a
Add Comment
Puppet / PUP-2714
Future parser returns nil when parsing a source that contains no statements
Consider the following example: {code} require 'puppet' require 'puppet/pops' parser = Puppet::Pops::Parser::Parser.new result = parser.parse_string('# This is a comment') puts "Result: #{result.inspect}" result = parser.parse_string <<-EOM # This is a comment $foo = 1 EOM puts "Result: #{result.inspect}" {code} The result is: ...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2938) Directory environments should support a global modulepath
Title: Message Title James Sweeny created an issue Puppet / PUP-2938 Directory environments should support a global modulepath Issue Type: Improvement Assignee: Unassigned Created: 15/Jul/14 4:18 PM Priority: Normal Reporter: James Sweeny Directory environments introduces three new configuration options to replace modulepath: "basemodulepath" and "environmentpath" in puppet.conf and "modulepath" in separate environment.conf files (one for each environment). If a modulepath is specified in an environment's environment.conf file, neither the basemodulepath nor environmentpath are used. In the now deprecated method for specifying multiple environments, users often add additional module paths that are global to all environments. A classic example is the path for Puppet Enterprise modules, which would not change from environment to environment on a single master. In the current directory environments implementation, a global module path that is environment independent cannot be set if the environment.conf file uses the modulepath setting. Avoiding the environment.conf setting is not an option, since doing so removes the ability to rename or set multiple modulepaths for an environment. Some possible fixes off the top of my head: 1) Make basemodulepath global. 2) Add a globalmodulepath option. This is my personal preference, since the name is more intuitive, and also calls out that basemodulepath likely isn't global. However, there is some room for debate about whether this value comes before or after the environment-specified module path. Other options along this line of thinking could get very wordy I'd be happy to brainstorm more.
Jira (PUP-2881) Upgrade win32-taskscheduler (or replace)
Title: Message Title Ethan Brown commented on an issue Re: Upgrade win32-taskscheduler (or replace) Josh Cooper or Rob Reynolds feel free to give the puppet-win32-ruby PRs a once over and merge. They are not blockers and they shouldn't cause any conflicts with removing the windows-pr gem and friends from PUP-2521 Add Comment Puppet / PUP-2881 Upgrade win32-taskscheduler (or replace) We need to either upgrade or replace the use of win32-taskscheduler. During some upgrading we found issues, which lead to this particular ticket out of PUP-392. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this 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 at on node "
Title: Message Title Andy Parker assigned an issue to Francois Conil Francois Conil, is this still an issue in the lasted Puppet 3.6 (3.6.2) release? Puppet / PUP-2348 Puppet run randomly fails with "Unknown function at on node " Change By: Andy Parker Assignee: Francois Conil 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-2388) Run Puppet acceptance against ruby 2.0 x64
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-2388 Run Puppet acceptance against ruby 2.0 x64 Change By: Ethan Brown Assignee: Ethan Brown 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-565) Support trusted facts in PuppetDB fact storage
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-565 Support trusted facts in PuppetDB fact storage Change By: Wyatt Alt Sprint: 20140716 20140702 to 20140730 20140716 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-565) Support trusted facts in PuppetDB fact storage
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-565 Support trusted facts in PuppetDB fact storage Change By: Wyatt Alt Assignee: Wyatt Alt 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-565) Support trusted facts in PuppetDB fact storage
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-565 Support trusted facts in PuppetDB fact storage Change By: Wyatt Alt Sprint: 20140730 20140716 to 20140813 20140730 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-2937) Windows: Unable to reference packages with UTF-8 Characters in their names
Title: Message Title Kylo Ginsberg commented on an issue Re: Windows: Unable to reference packages with UTF-8 Characters in their names Ken Sykora what version of puppet are you running? Add Comment Puppet / PUP-2937 Windows: Unable to reference packages with UTF-8 Characters in their names I'm currently trying to prevent a specific package from continuing its install run on subsequent puppet apply commands. The package in Question is the Windows Azure SDK for .Net 2.3. The package's name listed in the registry contains an endash (–) instead a normal hyphen. See attached screen shot for view from "programs and features" control panel. ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2937) Windows: Unable to reference packages with UTF-8 Characters in their names
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2937 Windows: Unable to reference packages with UTF-8 Characters in their names Change By: Rob Reynolds Affects Version/s: 3.5.0 Affects Version/s: 3.5.1 Affects Version/s: 3.6.0 Affects Version/s: 3.6.1 Affects 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 em
Jira (PUP-2937) Windows: Unable to reference packages with UTF-8 Characters in their names
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2937 Windows: Unable to reference packages with UTF-8 Characters in their names Change By: Rob Reynolds Affects Version/s: 3.6.2 Affects Version/s: 3.6.1 Affects Version/s: 3.5.1 Affects Version/s: 3.6.0 Affects Version/s: 3.5.0 Affects Version/s: 3.x Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2937) Windows: Unable to reference packages with UTF-8 Characters in their names
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2937 Windows: Unable to reference packages with UTF-8 Characters in their names Change By: Rob Reynolds Labels: utf8 windows Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2881) Upgrade win32-taskscheduler (or replace)
Title: Message Title Ethan Brown commented on an issue Re: Upgrade win32-taskscheduler (or replace) FYI - win32-taskscheduler PRs that are in links to are not relevant Add Comment Puppet / PUP-2881 Upgrade win32-taskscheduler (or replace) We need to either upgrade or replace the use of win32-taskscheduler. During some upgrading we found issues, which lead to this particular ticket out of PUP-392. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this 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-2937) Windows: Unable to reference packages with UTF-8 Characters in their names
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2937 Windows: Unable to reference packages with UTF-8 Characters in their names Change By: Rob Reynolds Component/s: Client Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2937) Windows: Unable to reference packages with UTF-8 Characters in their names
Title: Message Title Ken Sykora updated an issue Puppet / PUP-2937 Windows: Unable to reference packages with UTF-8 Characters in their names Change By: Ken Sykora Attachment: Screen Shot 2014-06-26 at 9.28.05 AM.png Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2937) Windows: Unable to reference packages with UTF-8 Characters in their names
Title: Message Title Ken Sykora commented on an issue Re: Windows: Unable to reference packages with UTF-8 Characters in their names Here's a link to the discussion with Rob Reynolds in the Puppet Users discussion group: https://groups.google.com/d/msg/puppet-users/EHHzN3b3noM/JR6y738xd-MJ Add Comment Puppet / PUP-2937 Windows: Unable to reference packages with UTF-8 Characters in their names I'm currently trying to prevent a specific package from continuing its install run on subsequent puppet apply commands. The package in Question is the Windows Azure SDK for .Net 2.3. The package's name listed in the registry contains an endash (–) instead a normal hyphen. See attached screen shot for view from "programs and features" control panel. ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For
Jira (PUP-2937) Windows: Unable to reference packages with UTF-8 Characters in their names
Title: Message Title
Ken Sykora created an issue
Puppet / PUP-2937
Windows: Unable to reference packages with UTF-8 Characters in their names
Issue Type:
Bug
Assignee:
Unassigned
Created:
15/Jul/14 2:19 PM
Priority:
Normal
Reporter:
Ken Sykora
I'm currently trying to prevent a specific package from continuing its install run on subsequent puppet apply commands. The package in Question is the Windows Azure SDK for .Net 2.3. The package's name listed in the registry contains an endash (–) instead a normal hyphen.
See attached screen shot for view from "programs and features" control panel.
In puppet, it shows up like this:
PS C:\Users\vagrant> puppet resource package | sls Azure
package { 'Windows Azure Libraries for .NET û v2.3':
I seem to be unable to query for it completely – this is what I can't figure out:
PS C:\Users\vagrant> puppet resource package "Windows Azure Libraries for .NET – v2.3"
package { 'Windows Azure Libraries for .NET û v2.3':
ensure => 'absent',
}
PS C:\Users\vagrant> puppet resource package "Windows Azure Libraries for .NET û v2.3"
package { 'Windows Azure Libraries for .NET √ v2.3':
ensure => 'absent',
}
When I try to reference it in a Puppet manifest, it causes to miss the package completely and always attempts to install it. This isn't a huge issue, but is obviously undesired.
Manifest:
Jira (PUP-2881) Upgrade win32-taskscheduler (or replace)
Title: Message Title Rob Reynolds commented on an issue Re: Upgrade win32-taskscheduler (or replace) Merged into master at bca820be. Add Comment Puppet / PUP-2881 Upgrade win32-taskscheduler (or replace) We need to either upgrade or replace the use of win32-taskscheduler. During some upgrading we found issues, which lead to this particular ticket out of PUP-392. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this 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-2936) PMT appears to change metadata.json after generating checksums.json
Title: Message Title Brandon High created an issue Puppet / PUP-2936 PMT appears to change metadata.json after generating checksums.json Issue Type: Bug Assignee: Unassigned Components: PMT Created: 15/Jul/14 1:43 PM Priority: Normal Reporter: Brandon High 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 emai
Jira (PUP-2732) Validation of Exec-Attribute user limits usability with non-root user.
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2732 Validation of Exec-Attribute user limits usability with non-root user. Change By: Andy Parker Assignee: Andy Parker 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-2878) puppet-kick.8.gz conflict upgrading from 2.7.26 to 3.6.2
Title: Message Title Andy Parker updated an issue Puppet / PUP-2878 puppet-kick.8.gz conflict upgrading from 2.7.26 to 3.6.2 Change By: Andy Parker Sprint: Week 2014-7-9 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-2878) puppet-kick.8.gz conflict upgrading from 2.7.26 to 3.6.2
Title: Message Title Andy Parker updated an issue Puppet / PUP-2878 puppet-kick.8.gz conflict upgrading from 2.7.26 to 3.6.2 Change By: Andy Parker Affects 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-2878) puppet-kick.8.gz conflict upgrading from 2.7.26 to 3.6.2
Title: Message Title
Andy Parker commented on an issue
Re: puppet-kick.8.gz conflict upgrading from 2.7.26 to 3.6.2
Merged into stable in 9bbc73
Add Comment
Puppet / PUP-2878
puppet-kick.8.gz conflict upgrading from 2.7.26 to 3.6.2
{noformat} # apt-get install puppet facter puppet-common ruby-rgen Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: hiera libjson-ruby ruby-json virt-what Suggested packages: puppet-el vim-puppet ruby-selinux libselinux-ruby1.8 librrd-ruby1.9.1 librr...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this 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-2878) puppet-kick.8.gz conflict upgrading from 2.7.26 to 3.6.2
Title: Message Title Andy Parker updated an issue Puppet / PUP-2878 puppet-kick.8.gz conflict upgrading from 2.7.26 to 3.6.2 Change By: Andy Parker Component/s: RE 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-2878) puppet-kick.8.gz conflict upgrading from 2.7.26 to 3.6.2
Title: Message Title Andy Parker updated an issue Puppet / PUP-2878 puppet-kick.8.gz conflict upgrading from 2.7.26 to 3.6.2 Change By: Andy Parker Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2878) puppet-kick.8.gz conflict upgrading from 2.7.26 to 3.6.2
Title: Message Title Andy Parker updated an issue Puppet / PUP-2878 puppet-kick.8.gz conflict upgrading from 2.7.26 to 3.6.2 Change By: Andy Parker Fix Version/s: 3.6.3 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-2881) Upgrade win32-taskscheduler (or replace)
Title: Message Title
Ethan Brown commented on an issue
Re: Upgrade win32-taskscheduler (or replace)
Above repro steps are not reproducible on my system. Per latest changes in https://github.com/Iristyle/puppet/commit/ca0b242413c9c1790ea2e59982c60dbc98900589, task manifests seem to work properly locally.
There were two minor bugs in the code that were addressed – when calling the COM SetTrigger method, the Ruby trigger} hash was being passed instead of the {{trigger_struct which is a pointer to the struct that the COM call expects. Furthermore, the first member of the struct was set to the wrong size – again, set to trigger.size when it should have been COM::TASK_TRIGGER.size.
Those issues have been resolved and rebased into the original PR, which has been force pushed up.
Add Comment
Puppet / PUP-2881
Upgrade win32-taskscheduler (or replace)
We need to either upgrade or replace the use of win32-taskscheduler. During some upgrading we found issues, which lead to this particular ticket out of PUP-392.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You rec
Jira (PUP-2935) Error deserializing JSON in CentOS
Title: Message Title
adrian created an issue
Puppet / PUP-2935
Error deserializing JSON in CentOS
Issue Type:
Bug
Affects Versions:
3.6.2
Assignee:
Andy Parker
Attachments:
client1-catalog.json
Components:
DSL
Created:
15/Jul/14 11:10 AM
Environment:
puppet 3.6.2 ruby 1.8.7 (2011-06-30 patchlevel 352) json 1.8.1 (gem) CentOS 6.4
Priority:
Normal
Reporter:
adrian
With that environment, if I execute:
# puppet apply --catalog client1-catalog.json
Error: Could not run: Could not deserialize catalog from pson: Could not intern from pson: Could not intern from data: Could not find relationship target "Notify[{\"type\"=>\"A\"}]"
Jira (PUP-2867) Support user home directories (Unix) in file resources
Title: Message Title Andy Parker assigned an issue to Raphaël Pinson Puppet / PUP-2867 Support user home directories (Unix) in file resources Change By: Andy Parker Assignee: Raphaël Pinson 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-622) changes to ordering in custom facts breaks things
Title: Message Title Tim Hartmann updated an issue Facter / FACT-622 changes to ordering in custom facts breaks things Change By: Tim Hartmann *edit* Looks like this also exists in 2.0.1 - so this may just mean that our custom facts aren't backwards compatible with the new loading logic. Is there a way to order facts if they are sourced from two different files, so that one depends correctly on the other, without filename precedence? *edit* We have a set of custom fact called node_type.rb which requires the output of a fact called "puppet_classes" which is in puppet_classes.rb, in with facter 2.0.1, puppet_classes is loaded *first* and then node_type runs, creating a set of facts that we use, however in version 2.0.2 this isn't the case. Renaming the puppet_classes.rb file to something like "apuppet_classes.rb" resolved the issue. It's unclear from the facter docs how to explicitly set the ordering in the code, is this a place where we should be using a confine? Facter precedence with weighting? I know this is something we can fix on our end, but having it break unexpectedly was a bit of a shocker. Thanks for taking a look! facter]# facter -p | grep _nodegluster_node => falsegpu_node => falseholyoke_node => falselustre_node => falsemv puppet_classes.rb apuppet_classes.rbfacter]# facter -p | grep _nodeaccess_node => falsebackup_node => falsecompute_node => falsegluster_node => falsegpu_node => falseholyoke_node => falsehybrid_node => falsekvm_node => falselustre_node => falsencf_node => false 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 unsu
Jira (FACT-622) changes to ordering in custom facts breaks things
Title: Message Title Tim Hartmann updated an issue Facter / FACT-622 changes to ordering in custom facts breaks things Change By: Tim Hartmann Affects Version/s: 2.0.1 *edit* Looks like this also exists in 2.0.1 - so this may just mean that our custom facts aren't backwards compatible with the new loading logic. Is there a way to order facts if they are sourced from two different files, so that one depends correctly on the other, without filename precedence? We have a set of custom fact called node_type.rb which requires the output of a fact called "puppet_classes" which is in puppet_classes.rb, in with facter 2.0.1, puppet_classes is loaded *first* and then node_type runs, creating a set of facts that we use, however in version 2.0.2 this isn't the case. Renaming the puppet_classes.rb file to something like "apuppet_classes.rb" resolved the issue. It's unclear from the facter docs how to explicitly set the ordering in the code, is this a place where we should be using a confine? Facter precedence with weighting? I know this is something we can fix on our end, but having it break unexpectedly was a bit of a shocker. Thanks for taking a look! facter]# facter -p | grep _nodegluster_node => falsegpu_node => falseholyoke_node => falselustre_node => falsemv puppet_classes.rb apuppet_classes.rbfacter]# facter -p | grep _nodeaccess_node => falsebackup_node => falsecompute_node => falsegluster_node => falsegpu_node => falseholyoke_node => falsehybrid_node => falsekvm_node => falselustre_node => falsencf_node => false Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2898) Long form Resource Type reference fools "future parser" this is an override
Title: Message Title Brian LaMetterey updated an issue Puppet / PUP-2898 Long form Resource Type reference fools "future parser" this is an override Change By: Brian LaMetterey Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2881) Upgrade win32-taskscheduler (or replace)
Title: Message Title Rob Reynolds commented on an issue Re: Upgrade win32-taskscheduler (or replace) Trying to create a task though: C:/code/puppetlabs/puppet/lib/puppet/util/windows/com.rb:117:in `block in UseInstance' C:/code/puppetlabs/puppet/lib/puppet/util/windows/com.rb:114:in `initialize' C:/code/puppetlabs/puppet/lib/puppet/util/windows/com.rb:114:in `new' C:/code/puppetlabs/puppet/lib/puppet/util/windows/com.rb:114:in `UseInstance' C:/code/puppetlabs/puppet/lib/puppet/util/windows/taskscheduler.rb:527:in `block (2 levels) in new_work_item' C:/code/puppetlabs/puppet/lib/puppet/util/windows/taskscheduler.rb:522:in `initialize' C:/code/puppetlabs/puppet/lib/puppet/util/windows/taskscheduler.rb:522:in `new' C:/code/puppetlabs/puppet/lib/puppet/util/windows/taskscheduler.rb:522:in `block in new_work_item' C:/code/puppetlabs/puppet/lib/puppet/util/windows/taskscheduler.rb:516:in `initialize' C:/code/puppetlabs/puppet/lib/puppet/util/windows/taskscheduler.rb:516:in `new' C:/code/puppetlabs/puppet/lib/puppet/util/windows/taskscheduler.rb:516:in `new_work_item' C:/code/puppetlabs/puppet/lib/puppet/util/windows/taskscheduler.rb:187:in `initialize' C:/code/puppetlabs/puppet/lib/puppet/provider/scheduled_task/win32_taskscheduler.rb:212:in `new' C:/code/puppetlabs/puppet/lib/puppet/provider/scheduled_task/win32_taskscheduler.rb:212:in `create' C:/code/puppetlabs/puppet/lib/puppet/property/ensure.rb:16:in `block in defaultvalues' C:/code/puppetlabs/puppet/lib/puppet/property.rb:197:in `call_valuemethod' C:/code/puppetlabs/puppet/lib/puppet/property.rb:498:in `set' C:/code/puppetlabs/puppet/lib/puppet/property.rb:581:in `sync' C:/code/puppetlabs/puppet/lib/puppet/transaction/resource_harness.rb:204:in `sync' C:/code/puppetlabs/puppet/lib/puppet/transaction/resource_harness.rb:128:in `sync_if_needed' C:/code/puppetlabs/puppet/lib/puppet/transaction/resource_harness.rb:81:in `perform_changes' C:/code/puppetlabs/puppet/lib/puppet/transaction/resource_harness.rb:20:in `evaluate' C:/code/puppetlabs/puppet/lib/puppet/transaction.rb:203:in `apply' C:/code/puppetlabs/puppet/lib/puppet/transaction.rb:216:in `eval_resource' C:/code/puppetlabs/puppet/lib/puppet/transaction.rb:146:in `call' C:/code/puppetlabs/puppet/lib/puppet/transaction.rb:146:in `block (2 levels) in evaluate' C:/code/puppetlabs/puppet/lib/puppet/util.rb:327:in `block in thinmark' C:/ruby193/lib/ruby/1.9.1/benchmark.rb:295:in `realtime' C:/code/puppetlabs/puppet/lib/puppet/util.rb:326:in `thinmark' C:/code/puppetlabs/puppet/lib/puppet/transaction.rb:146:in `block in evaluate' C:/code/puppetlabs/puppet/lib/puppet/graph/relationship_graph.rb:118:in `traverse' C:/code/puppetlabs/puppet/lib/puppet/transaction.rb:137:in `evaluate' C:/code/puppetlabs/puppet/lib/puppet/resource/catalog.rb:167:in `block in apply' C:/code/puppetlabs/puppet/lib/puppet/util/log.rb:149:in `with_destination' C:/code/puppetlabs/puppet/lib/puppet/transaction/report.rb:112:in `as_logging_destination' C:/code/puppetlabs/puppet/lib/puppet/resource/catalog.rb:166:in `apply' C:/code/puppetlabs/puppet/lib/puppet/configurer.rb:117:in `block in apply_catalog' C:/code/puppetlabs/puppet/lib/puppet/util.rb:161:in `block in benchmark' C:/ruby193/lib/ruby/1.9.1/benchmark.rb:295:in `realtime' C:/code/puppetlabs/puppet/lib/puppet/util.rb:160:in `benchmark' C:/code/puppetlabs/puppet/lib/puppet/configurer.rb:116:in `apply_catalog' C:/code/puppetlabs/puppet/lib/puppet/configurer.rb:198:in `run' C:/code/puppetlabs/puppet/lib/puppet/application/apply.rb:295:in `apply_catalog' C:/code/puppetlabs/puppet/lib/puppet/application/apply.rb:229:in `block in main' C:/code/puppetlabs/puppet/lib/puppet/context.rb:64:in `override' C:/code/puppetlabs/puppet/lib/puppet.rb:237:in `override' C:/code/puppetlabs/puppet/lib/puppet/appli
Jira (PUP-2881) Upgrade win32-taskscheduler (or replace)
Title: Message Title
Rob Reynolds commented on an issue
Re: Upgrade win32-taskscheduler (or replace)
If you modify existing tasks, it seems to work better than the current task_scheduler (shows up in task scheduler snap in)
scheduled_task { 'Notepad':
ensure=> 'present',
#arguments => '',
command => 'C:\Windows\notepad.exe',
enabled => 'true',
trigger => {every => '1', 'schedule' => 'daily', 'start_date' => '2014-6-19', 'start_time' => '06:29'},
user => 'system',
}
Add Comment
Puppet / PUP-2881
Upgrade win32-taskscheduler (or replace)
We need to either upgrade or replace the use of win32-taskscheduler. During some upgrading we found issues, which lead to this particular ticket out of PUP-392.
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop recei
Jira (PUP-2891) creating a resource override for a Class fails (future parser)
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-2891 creating a resource override for a Class fails (future parser) Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2891) creating a resource override for a Class fails (future parser)
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-2891 creating a resource override for a Class fails (future parser) Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2881) Upgrade win32-taskscheduler (or replace)
Title: Message Title
Rob Reynolds commented on an issue
Re: Upgrade win32-taskscheduler (or replace)
Attempting to create a resource:
scheduled_task { 'Notepad':
ensure=> 'present',
#arguments => '',
command => 'C:\Windows\notepad.exe',
enabled => 'true',
trigger => {every => '1', 'schedule' => 'daily', 'start_date' => '2014-6-19', 'start_time' => '06:29'},
user => 'system',
}
Error: /Stage[main]/Main/Scheduled_task[Notepad]: Could not evaluate: Failed to call #::GetAccountInformation with HRESULT: -2147216625.: No account information could be found in the Task Scheduler security database for the task indicated.
C:/code/puppetlabs/puppet/lib/puppet/util/windows/com.rb:142:in `block (3 levels) in []'
C:/code/puppetlabs/puppet/lib/puppet/util/windows/taskscheduler.rb:347:in `block in account_information'
C:/code/puppetlabs/puppet/lib/puppet/util/windows/taskscheduler.rb:346:in `initialize'
C:/code/puppetlabs/puppet/lib/puppet/util/windows/taskscheduler.rb:346:in `new'
C:/code/puppetlabs/puppet/lib/puppet/util/windows/taskscheduler.rb:346:in `account_information'
C:/code/puppetlabs/puppet/lib/puppet/provider/scheduled_task/win32_taskscheduler.rb:59:in `user'
C:/code/puppetlabs/puppet/lib/puppet/property.rb:471:in `retrieve'
C:/code/puppetlabs/puppet/lib/puppet/type.rb:1058:in `block in retrieve'
C:/code/puppetlabs/puppet/lib/puppet/type.rb:1053:in `each'
C:/code/puppetlabs/puppet/lib/puppet/type.rb:1053:in `retrieve'
[...snip...]
Add Comment
Puppet / PUP-2881
Upgrade win32-taskscheduler (or replace)
Jira (FACT-622) changes to ordering in custom facts breaks things
Title: Message Title Tim Hartmann created an issue Facter / FACT-622 changes to ordering in custom facts breaks things Issue Type: Bug Affects Versions: 2.0.2 Assignee: Eric Sorenson Created: 15/Jul/14 8:47 AM Priority: Normal Reporter: Tim Hartmann We have a set of custom fact called node_type.rb which requires the output of a fact called "puppet_classes" which is in puppet_classes.rb, in with facter 2.0.1, puppet_classes is loaded first and then node_type runs, creating a set of facts that we use, however in version 2.0.2 this isn't the case. Renaming the puppet_classes.rb file to something like "apuppet_classes.rb" resolved the issue. It's unclear from the facter docs how to explicitly set the ordering in the code, is this a place where we should be using a confine? Facter precedence with weighting? I know this is something we can fix on our end, but having it break unexpectedly was a bit of a shocker. Thanks for taking a look! facter]# facter -p | grep _node gluster_node => false gpu_node => false holyoke_node => false lustre_node => false mv puppet_classes.rb apuppet_classes.rb facter]# facter -p | grep _node access_node => false backup_node => false compute_node => false gluster_node => false gpu_node => false holyoke_node => false hybrid_node => false kvm_node => false lustre_node => false ncf_node => false
Jira (PUP-2881) Upgrade win32-taskscheduler (or replace)
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2881 Upgrade win32-taskscheduler (or replace) Change By: Rob Reynolds Attachment: actual_triggers.jpg Attachment: Scheduled_tasks.jpg 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-2881) Upgrade win32-taskscheduler (or replace)
Title: Message Title
Rob Reynolds commented on an issue
Re: Upgrade win32-taskscheduler (or replace)
I'm about to describe behavior of scheduled tasks, even before this change. Mostly a learning experience.
Scheduled tasks can only see one trigger.
scheduled_task { 'GoogleUpdateTaskMachineCore':
ensure=> 'present',
arguments => '/c',
command => 'C:\Program Files (x86)\Google\Update\GoogleUpdate.exe',
enabled => 'true',
trigger => {'enabled' => 'true', 'every' => '1', 'index' => '1', 'schedule' => 'daily', 'start_date' => '2014-6-19', 'start_time' => '06:29'},
user => 'system',
}
And what the task actually has: https://cloud.githubusercontent.com/assets/63502/3587160/bf2301da-0c36-11e4-88f7-81d6f2178857.png
With respect to scheduled tasks - puppet can only manage/see tasks that are configured for Windows Server 2003, Windows XP, or Windows 2000.
If you create a task in the scheduled tasks management console snap in, you cannot select this level. If you edit one of the tasks that are at this level and move it up to the next level, you cannot downgrade it. And you can no longer manage it with puppet once you make this change.
For reference: https://cloud.githubusercontent.com/assets/63502/3587061/c1607b2c-0c35-11e4-80e4-0ff96a90ceaf.png
Add Comment
Puppet / PUP-2881
Upgrade win32-taskscheduler (or replace)
We need to either upgrade or replace the use of win32-taskscheduler. During some upgrading we found issues, which lead to this particular ticket out of PUP-392.
Jira (PUP-2642) selector expression default should be matched last
Title: Message Title Peter Van Biesen commented on an issue Re: selector _expression_ default should be matched last Just for the benefit of other people finding this issue: there's also an improvement requested on the postgresql module : MODULES-1000 Add Comment Puppet / PUP-2642 selector _expression_ default should be matched last The future evaluator treats a default in a selector _expression_ just like any other value (historically puppet regular did this too - although I may be wrong). It should instead defer matching against a default until no other entry matched (just like the case _expression_ does). This will bite all users that have not followed the advice to place the defau... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this 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@goo
Jira (PUP-2757) Apply parses everything twice
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2757 Apply parses everything twice Change By: Henrik Lindberg Story Points: 0 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-2642) selector expression default should be matched last
Title: Message Title Peter Van Biesen commented on an issue Re: selector _expression_ default should be matched last Sorry for this, I misread, I thought it was patched in 3.5.1. Add Comment Puppet / PUP-2642 selector _expression_ default should be matched last The future evaluator treats a default in a selector _expression_ just like any other value (historically puppet regular did this too - although I may be wrong). It should instead defer matching against a default until no other entry matched (just like the case _expression_ does). This will bite all users that have not followed the advice to place the defau... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this 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-2757) Apply parses everything twice
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2757 Apply parses everything twice Change By: Henrik Lindberg Assignee: Joshua Partlow 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-1515) Invalid parameter provider for custom types/providers
Title: Message Title Tom De Vylder commented on an issue Re: Invalid parameter provider for custom types/providers I'm running into the same behavior with: 3.6.2-1puppetlabs1 3.6.1-1puppetlabs1 3.5.1-1puppetlabs1 (from apt.puppetlabs.com) ... using puppet apply on Puppetlabs' current Debian 7 Vagrant box (http://puppet-vagrant-boxes.puppetlabs.com/debian-73-x64-virtualbox-puppet.box). Add Comment Puppet / PUP-1515 Invalid parameter provider for custom types/providers In Puppet 3 I am getting an error on all definitions for custom types. It says "Error 400 on SERVER: Invalid parameter provider...". Provider should be a given parameter for custom types because otherwise there is no way to specify which provider should be used with it. This is potentially a very major bug. Please let me know how I can help so you're ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emai
Jira (PUP-2642) selector expression default should be matched last
Title: Message Title
Peter Van Biesen commented on an issue
Re: selector _expression_ default should be matched last
root@vbxl124:~#puppet --version
3.6.2
root@vbxl124:~#cat x.pp
notice 3 ? { default => 'the default', 3 => 'the three' }
root@vbxl124:~#puppet apply x.pp --parser future
Notice: the default
Notice: Compiled catalog for vbxl124.servers.vaph.be in environment production in 0.47 seconds
Notice: Finished catalog run in 0.11 seconds
Add Comment
Puppet / PUP-2642
selector _expression_ default should be matched last
The future evaluator treats a default in a selector _expression_ just like any other value (historically puppet regular did this too - although I may be wrong). It should instead defer matching against a default until no other entry matched (just like the case _expression_ does). This will bite all users that have not followed the advice to place the defau...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this
Jira (PUP-2642) selector expression default should be matched last
Title: Message Title Peter Van Biesen commented on an issue Re: selector _expression_ default should be matched last This issue resurfaces in 3.6.2-1puppetlabs1 . If I set parser=future, the postgresql module produces a lot of errors due to incorrectly set variables. The selectors in postgresql/manifests/validate_db_connection.pp all have the default selector FIRST. Changing the order of the selector, fixes the problem. Add Comment Puppet / PUP-2642 selector _expression_ default should be matched last The future evaluator treats a default in a selector _expression_ just like any other value (historically puppet regular did this too - although I may be wrong). It should instead defer matching against a default until no other entry matched (just like the case _expression_ does). This will bite all users that have not followed the advice to place the defau... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this 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 gro
Jira (PUP-2934) Cron type wiping an existing crontab if it contains invalid entries
Title: Message Title
Stefan Goethals created an issue
Puppet / PUP-2934
Cron type wiping an existing crontab if it contains invalid entries
Issue Type:
Bug
Affects Versions:
3.6.2, 3.4.2
Assignee:
Unassigned
Created:
15/Jul/14 6:22 AM
Environment:
Red Hat Enterprise Linux Server release 6.5
CentOS release 6.5
Priority:
Normal
Reporter:
Stefan Goethals
When puppet runs on a crontab that has an invalid entry, all entries are removed and only the new puppet entries remain.
Either puppet should not touch the existing entries or it should stop processing the file altogether and issue an error/warning
[root@stditop ~]# cat c.pp
cron { 'test':
ensure => present,
command => 'ls',
}
[root@stditop ~]# crontab -l
* * * * * date > /tmp/date1
* * date > /tmp/date2
[root@stditop ~]# puppet apply c.pp
Notice: Compiled catalog for stditop.vm.super-visions.com in environment production in 0.11 seconds
Error
