Jira (PUP-2872) Problem with variable in array for template
Title: Message Title
Vincent commented on an issue
Re: Problem with variable in array for template
There is absolutely no difference!
Notice: datadir = log-file = /var/log/my.hostname.com
I don't have datadir = /home test log-file = /var/log/my.hostname.com here, so the problem isn't from the code. Maybe syntax? Escape characters? Use of class parameter variable within an array, even if it works with facter variable?
Why $ {fqdn}
works correctly but not $ {datadir}
? There is a special reason ?
Add Comment
Puppet / PUP-2872
Problem with variable in array for template
I have the following parameters in my class manifest : {code} $datadir = '/home/test', $confarray = [datadir = ${datadir},log-file = /var/log/${fqdn}], {code} And the following in my conf template : {code} %- @confarray.each do |conf| -% %= conf % %- end -% {code} The output on my conf file is : {code} datadir = log-file = /var/log...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1177) sshkey creates /etc/ssh/ssh_known_hosts with mode 600
Title: Message Title Josh Cooper commented on an issue Re: sshkey creates /etc/ssh/ssh_known_hosts with mode 600 Follow up commit in 635d7d8 Add Comment Puppet / PUP-1177 sshkey creates /etc/ssh/ssh_known_hosts with mode 600 Using the sshkey type /etc/ssh/ssh_known_hosts is created with mode 600 by default. This seems undesirable in most situations. I think the default should be 644. I didn't see anything obvious in the sshkey code that set it strictly on purpose. Does puppet default to 600 somewhere? And is there a simple way to tweak a type to use a different mode? Th... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-391) Validate FFI'ed native windows code against Ruby 2 x64
Title: Message Title
Josh Cooper commented on an issue
Re: Validate FFI'ed native windows code against Ruby 2 x64
sys-admin gem removed from 1.9.3-x86 in 3d7a6173 and 2.0.0-x64 in aace2da. Note that sys-admin still is a development dependency for win32-security 0.2.5, but that won't affect us.
Add Comment
Puppet / PUP-391
Validate FFI'ed native windows code against Ruby 2 x64
Puppet makes some x86 assumptions in win32 native code. Once ruby 2.x x64 builds are available, we need to validate that our FFI'ed code continues to run on x64, and that we are not making bad assumptions, e.g. {code}0.chr * 4{code}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-391) Validate FFI'ed native windows code against Ruby 2 x64
Title: Message Title
Josh Cooper commented on an issue
Re: Validate FFI'ed native windows code against Ruby 2 x64
Ethan Brown I had two comments on https://github.com/puppetlabs/puppet/pull/2829. I suspect the rdoc issue is something in my environment, but not sure.
Add Comment
Puppet / PUP-391
Validate FFI'ed native windows code against Ruby 2 x64
Puppet makes some x86 assumptions in win32 native code. Once ruby 2.x x64 builds are available, we need to validate that our FFI'ed code continues to run on x64, and that we are not making bad assumptions, e.g. {code}0.chr * 4{code}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-391) Validate FFI'ed native windows code against Ruby 2 x64
Title: Message Title Josh Cooper updated an issue Puppet / PUP-391 Validate FFI'ed native windows code against Ruby 2 x64 Change By: Josh Cooper Assignee: JoshCooper 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 (FACT-609) automatic puppet run ignores facter environment variable
Title: Message Title
Bjoern commented on an issue
Re: automatic puppet run ignores facter environment variable
I did it now with a custom fact like this:
$ cat puppet/modules/user/lib/facter/main_user.rb
main_user.rb Facter.add('mainuser') do setcode do Facter::Util::Resolution.exec('/bin/cat /etc/system_role') end end
But I guess the other way should work too.
Add Comment
Facter / FACT-609
automatic puppet run ignores facter environment variable
In /etc/profile I defined a facter variable like this: export FACTER_MAINUSER=userXY When I execute puppet agent -t it's working fine and my module user $::mainuser with success. Unfortunately the automatic puppet run triggered by daemon perform my module with a empty $::mainuser. May it's the wrong way to set a global facter variable, bu...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-392) Validate win32 gems on x86 and x64
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-392 Validate win32 gems on x86 and x64 Change By: Josh Cooper Assignee: RobReynolds JoshCooper 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-392) Validate win32 gems on x86 and x64
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-392 Validate win32 gems on x86 and x64 Change By: Josh Cooper Assignee: JoshCooper 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-392) Validate win32 gems on x86 and x64
Title: Message Title
Josh Cooper commented on an issue
Re: Validate win32 gems on x86 and x64
Merged to puppet/master in b6c7015.
Add Comment
Puppet / PUP-392
Validate win32 gems on x86 and x64
Some of the win32 gems that we use contain native code and are not portable to x64. The complete list of gems that we currently vendor is: https://github.com/puppetlabs/puppet-win32-ruby/tree/1.9.3/ruby/lib/ruby/gems/1.9.1/specifications {noformat} bigdecimal-1.1.0 deep_merge-1.0.0 ffi-1.9.0-x86-mingw32 io-console-0.3 json-1.5.5 minitar-0.5.4 mi...
This message was sent by Atlassian JIRA (v6.1.4#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-392) Validate win32 gems on x86 and x64
Title: Message Title
Josh Cooper commented on an issue
Re: Validate win32 gems on x86 and x64
Merged to puppet-win32-ruby/1.9.3-x86 in 3863dab and puppet-win32-ruby/2.0.0-x64 in c5f1f09
Add Comment
Puppet / PUP-392
Validate win32 gems on x86 and x64
Some of the win32 gems that we use contain native code and are not portable to x64. The complete list of gems that we currently vendor is: https://github.com/puppetlabs/puppet-win32-ruby/tree/1.9.3/ruby/lib/ruby/gems/1.9.1/specifications {noformat} bigdecimal-1.1.0 deep_merge-1.0.0 ffi-1.9.0-x86-mingw32 io-console-0.3 json-1.5.5 minitar-0.5.4 mi...
This message was sent by Atlassian JIRA (v6.1.4#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-2872) Problem with variable in array for template
Title: Message Title
Vincent commented on an issue
Re: Problem with variable in array for template
Okay.
Found the solution.
parameter variables in puppet class have no value within parameters section, their values are assigned only when class begin
node my.hostname.com {
include testvincent
}
class (
DEFAULT PARAMETERS VALUES ARE NOT AVAILABLE FOR THE MOMENT, SO CANT BE USED FOR NOW IN OTHER PARAMETERS
) {
HERE ALL IS OK
}
The solution, is to override default parameters value in the node declaration, and, with this the overrided value can be used in another parameter.
So :
node my.hostname.com {
class {testvincent:
datadir = '/home/test',
}
class testvincent (
#This default value for $datadir is relatively useless by the way I use it
$datadir = '/home/test',
$conf = [
test = ${datadir},
log-file = /var/log/${fqdn},
],
) {
echo = inline_template(%= conf %)
notify{$echo:}
}
Give now the right output :
Notice: test = /home/testlog-file = /var/log/my.hostname.com
If there is some good explaination or other workaround not forcing me to override each parameter variable I want to use in another, I love to know it !
Add Comment
Jira (PUP-1471) Puppet Agent windows services accidentally comes of out Paused state
Title: Message Title Glenn Sarti commented on an issue Re: Puppet Agent windows services accidentally comes of out Paused state PUP-1283 has been raised to use the latest Win32 Service Gem. Once implemented work can start to remove the pause message from the daemon.rb file. Add Comment Puppet / PUP-1471 Puppet Agent windows services accidentally comes of out Paused state The Windows Puppet Agent service will not stay in a paused stated, instead it will go back into a running state after a short period of time. This is an issue in the Win32-Service ruby code. Raised bug https://github.com/djberg96/win32-service/issues/11 and is fixed in version 0.8.3. Because the Pause feature is so rarely used, there is no point in... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-1515) Invalid parameter provider for custom types/providers
Title: Message Title Martin Mrner commented on an issue Re: Invalid parameter provider for custom types/providers Please fix this bug as any currently advocated development method with environments and usage of r10k builds works against this. Especially when using official modules like puppetlabs/mysql: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter provider on Mysql_database[foo] at /etc/puppet/environments/dev_mysql/modules/mysql/manifests/db.pp:27 on node... /etc/puppet/puppet.conf [main] environment = production confdir = /etc/puppet logdir = /var/log/puppet vardir = /var/lib/puppet ssldir = /var/lib/puppet/ssl rundir = /var/run/puppet factpath = $vardir/lib/facter pluginsync = true [master] environment = production environmentpath = $confdir/environments autosign = false ssl_client_header = SSL_CLIENT_S_DN ssl_client_verify_header = SSL_CLIENT_VERIFY storeconfigs = true storeconfigs_backend = puppetdb reports = puppetdb [agent] environment = production server = *** report = true 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
Jira (PDB-729) Update documentation indexes for new major release
Title: Message Title Ryan Senior assigned an issue to Ryan Senior PuppetDB / PDB-729 Update documentation indexes for new major release 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 (PDB-157) Postgresql: invalid byte sequence for encoding UTF8: 0x00
Title: Message Title Christian Berg commented on an issue Re: Postgresql: invalid byte sequence for encoding UTF8: 0x00 I'm having the same issue running PuppetDB 2.0. It occurs when the value of a custom fact contains the Null character (\u). We fixed the custom fact, but there are thousands of messages going through the retry loop. I'm not sure if this can or should be addressed in PuppetDB (e.g. by not doing retries for this sort of Exception). A nice enhancement would be to give up on retries for a 'replace facts' command as soon as a new 'replace facts' command for the same host is processed. Add Comment PuppetDB / PDB-157 Postgresql: invalid byte sequence for encoding UTF8: 0x00 Puppetdb installed by puppet module (from git) with postgresql. In log I see many of: `2013-02-08 12:47:24,130 ERROR [command-proc-44] [puppetdb.command] [7c83ade4-f3cf-4237-b8b8-a2e6a3ebf2d8] [replace facts] Retrying after attempt 10, due to: org.postgresql.util.PSQLException: ERROR: invalid byte sequence for encoding UTF8: 0x00` System: ubuntu 1... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-751) Support Access Control Lists in PuppetDB
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-751 Support Access Control Lists in PuppetDB Issue Type: Epic Assignee: Unassigned Created: 03/Jul/14 4:50 AM Priority: Normal Reporter: Ryan Senior PuppetDB can potentially store sensitive information such as user's passwords. Currently PuppetDB (through PE) only supports an all or nothing access via certificate white lists. This epic is intended to catch some of the ideas around what would need to be restricted. Here is a conversation over in the Puppetboard repo. In that example, there are particular resources that shouldn't be returned. PDB-558 Discusses restricting the results at an environment level, which is a different approach, more for walling off a test environment from production. Add Comment
Jira (PDB-711) Factset endpoint for simplifying structure fact export and full retrieval
Title: Message Title Ryan Senior assigned an issue to Ryan Senior PuppetDB / PDB-711 Factset endpoint for simplifying structure fact export and full retrieval 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 (PDB-49) Change terminus to send unflattened structured facts
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-49 Change terminus to send unflattened structured facts 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-729) Update documentation indexes for new major release
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-729 Update documentation indexes for new major release Change By: Kenneth Barber Assignee: RyanSenior 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 (PUP-1281) Remove win32console gem in ruby 2.0 on windows
Title: Message Title Ethan Brown commented on an issue Re: Remove win32console gem in ruby 2.0 on windows Josh Cooper good idea, but looks like we might need to still do a workaround of some sort. It's pry that drags it in, and I don't think we want a spurious warning when debugging tools are installed. C:\source\puppetdel gemfile.lock C:\source\puppettype gemfile.lock The system cannot find the file specified. C:\source\puppetbundle install --path .bundle/gems DL is deprecated, please use Fiddle Fetching gem metadata from https://rubygems.org/. Fetching additional metadata from https://rubygems.org/.. Resolving dependencies... Using rake 10.1.1 Using i18n 0.6.9 Using multi_json 1.10.1 Using builder 3.0.4 Using arel 3.0.3 Using tzinfo 0.3.39 Using debug_inspector 0.0.2 Using columnize 0.8.9 Using debugger-linecache 1.2.0 Using coderay 1.1.0 Using mime-types 1.25.1 Using diff-lcs 1.1.3 Using ffi 1.9.3 Using json_pure 1.8.1 Using metaclass 0.0.4 Using method_source 0.8.2 Using minitar 0.5.4 Using msgpack 0.5.8 Using net-ssh 2.9.1 Using slop 3.5.0 Using win32console 1.3.2 Using puppet-lint 0.3.2 Using rspec-core 2.11.1 Using rspec-mocks 2.11.3 Using rack 1.5.2 Using rgen 0.6.5 Using ruby-prof 0.15.1 Using sqlite3 1.3.9 Using stomp 1.3.2 Using structured_warnings 0.1.4 Using bundler 1.6.3 Using activesupport 3.2.19 Using binding_of_caller 0.7.2 Using byebug 2.7.0 Using rest-client 1.6.7 Using rspec-expectations 2.11.3 Using win32-dir 0.4.9 Using win32-security 0.2.5 Using win32-eventlog 0.6.1 Using win32-process 0.7.4 Using win32-service 0.8.5 Using hiera 1.3.4 Using mocha 0.10.5 Using pry 0.10.0 Using win32-taskscheduler 0.3.0 Using activemodel 3.2.19 Using couchrest 1.2.0 Using rspec 2.11.0 Using facter 2.1.0 Using pry-byebug 1.3.3 Using pry-stack_explorer 0.4.9.1 Using activerecord 3.2.19 Using rspec-puppet 1.0.1 Using yarjuf 1.0.5 Using puppetlabs_spec_helper 0.6.0 Using puppet 3.6.2 from source at C:/source/puppet Your bundle is complete! It was installed into ./.bundle/gems C:\source\puppettype gemfile.lock PATH remote: . specs: puppet (3.6.2) facter (= 1.7, 3) hiera (~ 1.0) GEM remote: https://rubygems.org/ specs: activemodel (3.2.19) activesupport (= 3.2.19) builder (~ 3.0.0) activerecord (3.2.19) activemodel (= 3.2.19) activesupport (= 3.2.19) arel (~ 3.0.2) tzinfo (~ 0.3.29) activesupport (3.2.19) i18n (~ 0.6, = 0.6.4) multi_json (~ 1.0) arel (3.0.3) binding_of_caller (0.7.2) debug_inspector (= 0.0.1) builder (3.0.4) byebug (2.7.0) columnize (~ 0.3) debugger-linecache (~ 1.2) coderay (1.1.0) columnize (0.8.9) couchrest (1.2.0) mime-types (~ 1.15) multi_json (~ 1.0) rest-client (~ 1.6.1) debug_inspector (0.0.2) debugger-linecache (1.2.0) diff-lcs (1.1.3) facter (2.1.0-x64-mingw32) ffi (~ 1.9.3) win32-dir (~ 0.4.8) win32-security (~ 0.2.5) ffi (1.9.3-x64-mingw32) hiera (1.3.4) json_pure i18n (0.6.9)
Jira (PDB-729) Update documentation indexes for new major release
Title: Message Title Kenneth Barber commented on an issue Re: Update documentation indexes for new major release Docs ticket is here: https://github.com/puppetlabs/puppet-docs/pull/346 Add Comment PuppetDB / PDB-729 Update documentation indexes for new major release The current documentation indexes need to be updated for a final release. The main index needs the release to be moved into the stable section, and the index for this release needs the pre-release meesage removed. This message was sent by Atlassian JIRA (v6.1.4#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-391) Validate FFI'ed native windows code against Ruby 2 x64
Title: Message Title
Ethan Brown commented on an issue
Re: Validate FFI'ed native windows code against Ruby 2 x64
It's not you, it's me.
Was getting late, and I kicked off 1.9.3 specs, expecting to see them pass when I got up in the AM. Prematurely moved this ticket over.
Ticket has been rebased and pushed up anew, but I'm doing a little more verification before putting back into ready for merge.
Add Comment
Puppet / PUP-391
Validate FFI'ed native windows code against Ruby 2 x64
Puppet makes some x86 assumptions in win32 native code. Once ruby 2.x x64 builds are available, we need to validate that our FFI'ed code continues to run on x64, and that we are not making bad assumptions, e.g. {code}0.chr * 4{code}
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (PDB-729) Update documentation indexes for new major release
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-729 Update documentation indexes for new major release Change By: Kenneth Barber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-708) Storage for structured facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-708 Storage for structured facts Change By: Kenneth Barber Nowthatthecommandsprotocolsupportsreceivingstructuredfacts,weshouldbeabletostoretheminaformatthatisqueryableasdefinedinourdesign. Thisisawaitingontheresearchworkforthedifferentstoragetypeoptionsfirst. Moredetailshere:https://docs.google.com/a/puppetlabs.com/document/d/1vWE6tBmsPmMIYKQWV8Pwes_NIR9lEMTYjUH8zJ_AlMI/edit# 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-855) On Windows allow using root path for file type
Title: Message Title
Rob Reynolds commented on an issue
Re: On Windows allow using root path for file type
Henrik Lindberg One can do those things now. This is more meant to bring more parity with other platforms. You can't create any fact that is going to allow you to set the path like so /temp/somedirectory and use it across both windows and *nix. Or can you?
Interesting though... somewhat pseudo-code here:
case $::operatinsystem {
windows: { $rp = $::systemdrive + '/' }
default: { $rp = '' }
}
file {$rp/somedirectory:
ensure = directory,
}
Add Comment
Puppet / PUP-855
On Windows allow using root path for file type
This would allow full path in a way that doesn't require specifying the drive to look at. When this is specified, we will use SYSTEMDRIVE. This would allow multiple computers with different system drives to be able to use the same manifests. This could also open the door for more platforms using the same manifest with less use of selectors based on the O...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1281) Remove win32console gem in ruby 2.0 on windows
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-1281 Remove win32console gem in ruby 2.0 on windows Change By: Rob Reynolds Assignee: RobReynolds 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-1281) Remove win32console gem in ruby 2.0 on windows
Title: Message Title Rob Reynolds commented on an issue Re: Remove win32console gem in ruby 2.0 on windows I'd say it might be more bundler that is pulling it in. Add Comment Puppet / PUP-1281 Remove win32console gem in ruby 2.0 on windows Ruby 2.0 on windows supports ANSI escape sequences, so the win32console gem is unnecessary. Also, ruby 2.0 likely support unicode character output correctly (such as the unicode box characters used in module tool output), so the windows-specific code in `lib/puppet/util/colors.rb` to force wide character output can be removed. See https://github.com/l... This message was sent by Atlassian JIRA (v6.1.4#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-2812) Update Windows Installer license file to reference FFI change from LGPL-3 to BSD
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2812 Update Windows Installer license file to reference FFI change from LGPL-3 to BSD Change By: Rob Reynolds Sprint: Week2014- 6 7 - 25 9 to2014-7- 9 23 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 updated an issue Puppet / PUP-2881 Upgrade win32-taskscheduler (or replace) Change By: Ethan Brown Flagged: Impediment 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-2521) Remove windows-pr gem as a Windows dependency
Title: Message Title Ethan Brown commented on an issue Re: Remove windows-pr gem as a Windows dependency The PRs to puppet and puppet-win32-ruby are ready to go, but still waiting on a resolution for the win32-taskscheduler gem issues as part of PUP-2881. There will need to be a PR that updates project_data.yaml with the new gem version, and a PR each to upgrade that gem on Ruby 1.9.3-x86 and Ruby 2.0.0-x64. Add Comment Puppet / PUP-2521 Remove windows-pr gem as a Windows dependency The scope of this is unknown at this point, but it appears to be rather large. We currently use native Windows API calls defined in the windows-pr gem. Unfortunately, an FFI version of windows-pr was never released, and therefore the calls we directly make use of are *not* FFI'd. As such they will need replacement in preparation for x64. A more ex... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PUP-2881) Upgrade win32-taskscheduler (or replace)
Title: Message Title Rob Reynolds commented on an issue Re: Upgrade win32-taskscheduler (or replace) We can also monkey patch but yuck. 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-2887) IPv6 failover using srv records doesn't work as expected
Title: Message Title Mike Hendon created an issue Puppet / PUP-2887 IPv6 failover using srv records doesn't work as expected Issue Type: Bug Affects Versions: 3.6.2 Assignee: Kylo Ginsberg Components: Client Created: 03/Jul/14 8:17 AM Environment: Client / Server both running CentOS 6.5 x64 puppet 3.6.2. Labels: SRV IPv6 Priority: Major Reporter: Mike Hendon The clients are configured to look up the master servers using DNS SRV records. Expected behaviour - if one master server times out or doesn't respond at all then the client should fall back to trying to talk to the same server using IPv4. If there is still no response of the server times out then use the next SRV record (IPv6 first then IPv4). Actual behaviour - the client stubbornly refuses to retry the current request.
Jira (PDB-752) Change main docs index and 2.1 index once PuppetDB 2.1.0 is released
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-752 Change main docs index and 2.1 index once PuppetDB 2.1.0 is released Issue Type: Sub-task Assignee: Unassigned Created: 03/Jul/14 8:32 AM Priority: Normal Reporter: Kenneth Barber Our main index would have to be changed to reflect that 2.1 is released, and the 2.1 specific index will need its warning removed. 2.0 should probably have a warning put in about it being old also. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2872) Problem with variable in array for template
Title: Message Title
Henrik Lindberg commented on an issue
Re: Problem with variable in array for template
Vincent Sorry, I should have seen that mistake. It is undefined behavior when you access a parameter value from another parameter's default value _expression_. The order in which they are evaluated is not specified - it may work in some versions / combinations of names, but it is only by chance.
You simply have to move the computations of the values inside the body of the class, and assign other values to mean use default.
Add Comment
Puppet / PUP-2872
Problem with variable in array for template
I have the following parameters in my class manifest : {code} $datadir = '/home/test', $confarray = [datadir = ${datadir},log-file = /var/log/${fqdn}], {code} And the following in my conf template : {code} %- @confarray.each do |conf| -% %= conf % %- end -% {code} The output on my conf file is : {code} datadir = log-file = /var/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
Jira (PUP-855) On Windows allow using root path for file type
Title: Message Title Henrik Lindberg commented on an issue Re: On Windows allow using root path for file type I guess the value of having a root of / map to someplace depends on what is being managed - if it is windows stuff, then the paths and layouts are different from any *nix stuff, and vice versa. Unless there are *nix like tools being managed on windows referencing things like /etc/something, /opt/var/something, /user etc. isn't the automatic mapping just going to make people silently drop files on to windows boxes in places where they are at best just ignored and harmless, but worst case screw something up? The alternative is to have some kind of symbolic mapping / abstraction that works across all platforms - sort of like mount points. This could take place agent side, but the agent would need to know how to do the mapping, so it probably should be something that is configured in the catalog it gets, constructed out of facts it provided. Add Comment Puppet / PUP-855 On Windows allow using root path for file type This would allow full path in a way that doesn't require specifying the drive to look at. When this is specified, we will use SYSTEMDRIVE. This would allow multiple computers with different system drives to be able to use the same manifests. This could also open the door for more platforms using the same manifest with less use of selectors based on the O... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2553) Redhat service enable does not honour chkconfig or LSB Headers.
Title: Message Title Adrien Thebo commented on an issue Re: Redhat service enable does not honour chkconfig or LSB Headers. Note for posterity: changes to this need to take into account https://github.com/puppetlabs/puppet/commit/775d0dc7 when trying to add the requested functionality. Add Comment Puppet / PUP-2553 Redhat service enable does not honour chkconfig or LSB Headers. Using chkconfig service on blindly sets the service on in runlevel 2,3,4,5. puppet should use chkconfig service resetpriorities. when enabling services so that it honours the settings in the chkconfig and LSB Headers. This message was sent by Atlassian JIRA (v6.1.4#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
Adrien Thebo updated an issue
Puppet / PUP-2878
puppet-kick.8.gz conflict upgrading from 2.7.26 to 3.6.2
Change By:
Adrien Thebo
{ { noformat} #apt-getinstallpuppetfacterpuppet-commonruby-rgenReadingpackagelists...DoneBuildingdependencytreeReadingstateinformation...DoneThefollowingextrapackageswillbeinstalled:hieralibjson-rubyruby-jsonvirt-whatSuggestedpackages:puppet-elvim-puppetruby-selinuxlibselinux-ruby1.8librrd-ruby1.9.1librrd-ruby1.8ThefollowingNEWpackageswillbeinstalledhieralibjson-rubyruby-jsonruby-rgenvirt-whatThefollowingpackageswillbeupgraded:facterpuppetpuppet-common3toupgrade,5tonewlyinstall,0toremoveand3nottoupgrade.Needtoget1,583kBofarchives.Afterthisoperation,2,330kBofadditionaldiskspacewillbeused.Doyouwanttocontinue[Y/n]?(Readingdatabase...97569filesanddirectoriescurrentlyinstalled.)Preparingtoreplacepuppet-common2.7.26-1puppetlabs1(using.../puppet-common_3.6.2-1puppetlabs1_all.deb)...Unpackingreplacementpuppet-common...dpkg:errorprocessing/var/cache/apt/archives/puppet-common_3.6.2-1puppetlabs1_all.deb(--unpack):tryingtooverwrite'/usr/share/man/man8/puppet-kick.8.gz',whichisalsoinpackagepuppet2.7.26-1puppetlabs1NoapportreportwrittenbecauseMaxReportshasalreadybeenreacheddpkg-deb:error:subprocesspastewaskilledbysignal(Brokenpipe)Preparingtoreplacepuppet2.7.26-1puppetlabs1(using.../puppet_3.6.2-1puppetlabs1_all.deb)...*Stoppingpuppetagent[OK]Unpackingreplacementpuppet...Selectingpreviouslyunselectedpackageruby-json.Unpackingruby-json(from.../ruby-json_1.6.3-1_i386.deb)...Selectingpreviouslyunselectedpackagelibjson-ruby.Unpackinglibjson-ruby(from.../libjson-ruby_1.6.3-1_all.deb)...Selectingpreviouslyunselectedpackagehiera.Unpackinghiera(from.../hiera_1.3.4-1puppetlabs1_all.deb)...Selectingpreviouslyunselectedpackageruby-rgen.Unpackingruby-rgen(from.../ruby-rgen_0.6.5-1puppetlabs1_all.deb)...Selectingpreviouslyunselectedpackagevirt-what.Unpackingvirt-what(from.../virt-what_1.11-1_i386.deb)...Preparingtoreplacefacter1.6.18-1puppetlabs1(using.../facter_2.0.2-1puppetlabs1_i386.deb)...Unpackingreplacementfacter...Processingtriggersforman-db...Processingtriggersforureadahead...Errorswereencounteredwhileprocessing:/var/cache/apt/archives/puppet-common_3.6.2-1puppetlabs1_all.debE:Sub-process/usr/bin/dpkgreturnedanerrorcode(1) {noformat } }
Add Comment
Jira (PUP-2888) invalid parameter 'mode' when using nagios_host
Title: Message Title
Krystle Bennett created an issue
Puppet / PUP-2888
invalid parameter 'mode' when using nagios_host
Issue Type:
Bug
Affects Versions:
3.4.3
Assignee:
Unassigned
Created:
03/Jul/14 9:36 AM
Priority:
Normal
Reporter:
Krystle Bennett
Hello, I'm trying to export my nodes for nagios using puppet. my config is:
#exporting host class nagios_client::targets { @@nagios_host { $::fqdn: ensure = present, alias = $::hostname, address = $::ipaddress, use = 'linux-server', hostgroups = 'all-hosts', target = /etc/nagios3/objects/hosts/${::hostname}.cfg, mode = '0640', } } #importing nagios services class nagios_server::import{
Nagios_host || { notify = Class['nagios_server::service'], require = File['hosts'], }
}
except when I run this, I get the following error:
Error: Invalid parameter mode at /var/lib/puppet/repository/modules/nagios_client/manifests/targets.pp:12 on node hostname
I saw a bug fix for this, and I'm on a version of puppet where this should be pushed out. Are these not implemented on this version? or is this a reopened bug?
Jira (PUP-392) Validate win32 gems on x86 and x64
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-392 Validate win32 gems on x86 and x64 Change By: Josh Cooper Assignee: JoshCooper 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-392) Validate win32 gems on x86 and x64
Title: Message Title
Josh Cooper commented on an issue
Re: Validate win32 gems on x86 and x64
Latest win32-eventlog gem fails on 2003, because it tries to load a library that isn't available on older systems
Add Comment
Puppet / PUP-392
Validate win32 gems on x86 and x64
Some of the win32 gems that we use contain native code and are not portable to x64. The complete list of gems that we currently vendor is: https://github.com/puppetlabs/puppet-win32-ruby/tree/1.9.3/ruby/lib/ruby/gems/1.9.1/specifications {noformat} bigdecimal-1.1.0 deep_merge-1.0.0 ffi-1.9.0-x86-mingw32 io-console-0.3 json-1.5.5 minitar-0.5.4 mi...
This message was sent by Atlassian JIRA (v6.1.4#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-195) Remove 1.8.x support?
Title: Message Title Michael Stahnke commented on an issue Re: Remove 1.8.x support? Kylo Ginsberg sorry, I think we had this conversation in other venues. Yes, we keep 1.8 for now. Add Comment Facter / FACT-195 Remove 1.8.x support? This is just a proposal at this time. Needs to be vetted. This message was sent by Atlassian JIRA (v6.1.4#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-500) Test CollectExpressions
Title: Message Title Andy Parker assigned an issue to Henrik Lindberg Puppet / PUP-500 Test CollectExpressions Change By: Andy Parker Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2711) The manifests directory should be recursively loaded when using directory environments
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2711 The manifests directory should be recursively loaded when using directory environments Change By: Andy Parker Assignee: 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-2794) Specify signatures for blocks of block-accepting methods
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2794 Specify signatures for blocks of block-accepting methods Change By: Andy Parker Assignee: 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-855) On Windows allow using root path for file type
Title: Message Title Rob Reynolds commented on an issue Re: On Windows allow using root path for file type And it looks like David Schmitt already follows this as a common pattern. Good that there is already a pattern established out there. Add Comment Puppet / PUP-855 On Windows allow using root path for file type This would allow full path in a way that doesn't require specifying the drive to look at. When this is specified, we will use SYSTEMDRIVE. This would allow multiple computers with different system drives to be able to use the same manifests. This could also open the door for more platforms using the same manifest with less use of selectors based on the O... This message was sent by Atlassian JIRA (v6.1.4#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-392) Validate win32 gems on x86 and x64
Title: Message Title Josh Cooper updated an issue Puppet / PUP-392 Validate win32 gems on x86 and x64 Change By: Josh Cooper Assignee: JoshCooper RobReynolds 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-610) Change windows facter to return same hardware model as linux
Title: Message Title Adrien Thebo updated an issue Facter / FACT-610 Change windows facter to return same hardware model as linux Change By: Adrien Thebo 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 (FACT-610) Change windows facter to return same hardware model as linux
Title: Message Title Adrien Thebo commented on an issue Re: Change windows facter to return same hardware model as linux Since this changes the value of an existing fact resolution this is backwards incompatible; we won't be able to release this change until Facter 3. Add Comment Facter / FACT-610 Change windows facter to return same hardware model as linux facter's fact hardwaremodel on windows is returned as x64 for 64 bit hardware systems. This is not the same as what is returned by Linux systems. On linux hardwaremodel is x86_64. This causes a separate hardwaremodel group to be created when they are actually the same thing. I am attaching the patched file hardwaremodel.rb but I'm not familiar w... This message was sent by Atlassian JIRA (v6.1.4#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 (FACT-610) Change windows facter to return same hardware model as linux
Title: Message Title Adrien Thebo updated an issue Facter / FACT-610 Change windows facter to return same hardware model as linux Change By: Adrien Thebo Fix Version/s: 3.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-2745) Puppet 3.6.1 issue with Forge API v3
Title: Message Title Brandon High assigned an issue to Brandon High Puppet / PUP-2745 Puppet 3.6.1 issue with Forge API v3 Change By: Brandon High Assignee: BrandonHigh 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-547) Limit the output of prtdiag on Solaris
Title: Message Title Adrien Thebo commented on an issue Re: Limit the output of prtdiag on Solaris Merged in bba2746. Add Comment Facter / FACT-547 Limit the output of prtdiag on Solaris prtdiag is used to determine manufacturer and productname on Solaris If you run it on a big box like a SPARC T5 it produces a lot of output, and might take some time. On a SPARC T5 this can cause timeouts. Will provide a PR This message was sent by Atlassian JIRA (v6.1.4#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-547) Limit the output of prtdiag on Solaris
Title: Message Title Adrien Thebo updated an issue Facter / FACT-547 Limit the output of prtdiag on Solaris Change By: Adrien Thebo Fix Version/s: 2.2.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-1806) Varargs support for the new function API
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1806 Varargs support for the new function API Change By: Henrik Lindberg Sprint: Week2014-7- 9 23 to2014- 7 8 - 23 6 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-909) Speed up type inference
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-909 Speed up type inference Change By: Henrik Lindberg Sprint: Week2014-7- 9 23 to2014- 7 8 - 23 6 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-2411) Remove 1.8.7 multibyte string support in Lexer2
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2411 Remove 1.8.7 multibyte string support in Lexer2 Change By: Henrik Lindberg Sprint: Week2014-7- 9 23 to2014- 7 8 - 23 6 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-2857) Add a Default type
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2857 Add a Default type Change By: Henrik Lindberg Sprint: Week2014-7-9to2014-7-23 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-494) Make future parser/evaluator have acceptable performance
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-494 Make future parser/evaluator have acceptable performance Change By: Henrik Lindberg Sprint: Week2014-7- 9 23 to2014- 7 8 - 23 6 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-2858) remove --evaluator current switch for future parser
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2858 remove --evaluator current switch for future parser Change By: Henrik Lindberg Sprint: Week2014-7-9to2014-7-23 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 Henrik Lindberg updated an issue Puppet / PUP-2693 LiteralString class parameters get parsed with positioning information that includes a negative length Change By: Henrik Lindberg 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-2824) Make $title and $name Reserved Words
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2824 Make $title and $name Reserved Words Change By: Henrik Lindberg Sprint: Week2014-7-9to2014-7-23 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-2859) specify call by name / call by position
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2859 specify call by name / call by position Change By: Henrik Lindberg Sprint: Week2014-7-9to2014-7-23 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-2883) epp does not handle empty template
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2883 epp does not handle empty template Change By: Henrik Lindberg Sprint: Week2014-7-9to2014-7-23 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-2886) future parser should validate class/resource names that are types
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2886 future parser should validate class/resource names that are types Change By: Henrik Lindberg Sprint: Week2014-7-9to2014-7-23 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-2860) Optimize startup of puppet apply (future parser)
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2860 Optimize startup of puppet apply (future parser) Change By: Henrik Lindberg Sprint: Week2014-7-9to2014-7-23 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-2412) Remove 1.8.7 function API support
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2412 Remove 1.8.7 function API support Change By: Henrik Lindberg Sprint: Week2014-7- 9 23 to2014- 7 8 - 23 6 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-2757) Apply parses everything twice
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2757 Apply parses everything twice Change By: Henrik Lindberg Sprint: Week2014-7-9to2014-7-23 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-2873) puppet master --compile right now unconditionally spews logs to standard output
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2873 puppet master --compile right now unconditionally spews logs to standard output Change By: Henrik Lindberg Sprint: Week2014-7-23to2014-8-6 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 Henrik Lindberg updated an issue Puppet / PUP-2693 LiteralString class parameters get parsed with positioning information that includes a negative length Change By: Henrik Lindberg Sprint: Week2014-7-9to2014-7-23 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-2714) Future parser returns nil when parsing a source that contains no statements
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2714 Future parser returns nil when parsing a source that contains no statements Change By: Henrik Lindberg Sprint: Week2014-7-9to2014-7-23 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-392) Validate win32 gems on x86 and x64
Title: Message Title
Rob Reynolds commented on an issue
Re: Validate win32 gems on x86 and x64
Creating a separate ticket for win32-eventlog
Add Comment
Puppet / PUP-392
Validate win32 gems on x86 and x64
Some of the win32 gems that we use contain native code and are not portable to x64. The complete list of gems that we currently vendor is: https://github.com/puppetlabs/puppet-win32-ruby/tree/1.9.3/ruby/lib/ruby/gems/1.9.1/specifications {noformat} bigdecimal-1.1.0 deep_merge-1.0.0 ffi-1.9.0-x86-mingw32 io-console-0.3 json-1.5.5 minitar-0.5.4 mi...
This message was sent by Atlassian JIRA (v6.1.4#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-2587) circular inheritance causes stack too deep error
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2587 circular inheritance causes stack too deep error Change By: Henrik Lindberg Sprint: Week2014-7-9to2014-7-23 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-2831) Puppet does not work with RGen 0.7.0
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2831 Puppet does not work with RGen 0.7.0 Change By: Henrik Lindberg 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-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 Sprint: Week2014-7- 9 23 to2014- 7 8 - 23 6 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-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 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-2824) Make $title and $name Reserved Words
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2824 Make $title and $name Reserved Words Change By: Henrik Lindberg 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-2040) Allow excluding content from Puppet module tool built packages
Title: Message Title Anderson Mills updated an issue Puppet / PUP-2040 Allow excluding content from Puppet module tool built packages Change By: Anderson Mills Sprint: Week2014-6-25to2014-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-2304) Implement requirements support for the PMT
Title: Message Title Anderson Mills updated an issue Puppet / PUP-2304 Implement requirements support for the PMT Change By: Anderson Mills Fix Version/s: 3.7.0 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-392) Validate win32 gems on x86 and x64
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-392 Validate win32 gems on x86 and x64 Change By: Rob Reynolds Flagged: Impediment 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-392) Validate win32 gems on x86 and x64
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-392 Validate win32 gems on x86 and x64 Change By: Josh Cooper Assignee: JoshCooper 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-2040) Allow excluding content from Puppet module tool built packages
Title: Message Title Anderson Mills updated an issue Puppet / PUP-2040 Allow excluding content from Puppet module tool built packages Change By: Anderson Mills Sprint: Week2014-6-25to2014-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-2881) Upgrade win32-taskscheduler (or replace)
Title: Message Title Ethan Brown commented on an issue Re: Upgrade win32-taskscheduler (or replace) In testing, have also discovered that bundle exec puppet resource scheduled_task fails to work properly with the error Error: Could not run: activate: The system cannot find the file specified. This is even with the patched gem. 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 (FACT-610) Change windows facter to return same hardware model as linux
Title: Message Title
Josh Cooper commented on an issue
Re: Change windows facter to return same hardware model as linux
Windows and Linux use different identifiers to signify 64-bit. Sadly Windows uses both x64 and x86_64 making it even more confusing, see https://projects.puppetlabs.com/issues/10261#note-10. The choice of x64 for the architecture fact was done intentionally because that is how most windows packages are published. That way you can do:
package { mypackage:
ensure = installed,
source = path/to/mypackage-${architecture}.msi
}
And puppet will do the right thing. I'm not sure if it's important for the hardwaremodel fact to match the architecture fact...
Add Comment
Facter / FACT-610
Change windows facter to return same hardware model as linux
facter's fact hardwaremodel on windows is returned as x64 for 64 bit hardware systems. This is not the same as what is returned by Linux systems. On linux hardwaremodel is x86_64. This causes a separate hardwaremodel group to be created when they are actually the same thing. I am attaching the patched file hardwaremodel.rb but I'm not familiar w...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-392) Validate win32 gems on x86 and x64
Title: Message Title
Josh Cooper commented on an issue
Re: Validate win32 gems on x86 and x64
revert of puppet/master merged in 35b1abc1b, revert of puppet-win32-ruby/1.9.3-x86 was merged in 67a8f4e0.
puppet-win32-ruby/2.0.0-x64 does not need to be reverted.
Add Comment
Puppet / PUP-392
Validate win32 gems on x86 and x64
Some of the win32 gems that we use contain native code and are not portable to x64. The complete list of gems that we currently vendor is: https://github.com/puppetlabs/puppet-win32-ruby/tree/1.9.3/ruby/lib/ruby/gems/1.9.1/specifications {noformat} bigdecimal-1.1.0 deep_merge-1.0.0 ffi-1.9.0-x86-mingw32 io-console-0.3 json-1.5.5 minitar-0.5.4 mi...
This message was sent by Atlassian JIRA (v6.1.4#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-2889) Upgrade win32-eventlog
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2889 Upgrade win32-eventlog Change By: Rob Reynolds Story Points: 3 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-2889) Upgrade win32-eventlog
Title: Message Title Josh Cooper created an issue Puppet / PUP-2889 Upgrade win32-eventlog Issue Type: Task Assignee: Unassigned Components: Client Created: 03/Jul/14 12:28 PM Fix Versions: 3.7.0 Labels: windows Priority: Normal Reporter: Josh Cooper 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. Add Comment
Jira (PUP-2521) Remove windows-pr gem as a Windows dependency
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2521 Remove windows-pr gem as a Windows dependency Change By: Josh Cooper Flagged: Impediment 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-392) Validate win32 gems on x86 and x64
Title: Message Title Josh Cooper updated an issue Puppet / PUP-392 Validate win32 gems on x86 and x64 Change By: Josh Cooper Flagged: Impediment 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-2889) Upgrade win32-eventlog
Title: Message Title Josh Cooper commented on an issue Re: Upgrade win32-eventlog Upstream PR submitted https://github.com/djberg96/win32-eventlog/pull/10 As part of fixing this, we should write a spec test that only runs on windows, and asserts that Puppet.features.eventlog? is true. This would have caught the issue on 2003 more directly. Also win32-eventlog version 0.2.x is not backwards compatible with 0.1.x due to the constants being redefined. We should redefine these constants in puppet so that we don't have this backwards compatibility problem. Add Comment Puppet / PUP-2889 Upgrade win32-eventlog 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
Jira (PUP-2889) Upgrade win32-eventlog
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-2889 Upgrade win32-eventlog Change By: Rob Reynolds Weneedtoeitherupgradeorreplacetheuseofwin32- taskscheduler eventlog .Duringsomeupgradingwefoundissues,whichleadtothisparticularticketoutofPUP-392. 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-2889) Upgrade win32-eventlog
Title: Message Title Rob Reynolds commented on an issue Re: Upgrade win32-eventlog Are those methods used anywhere? Add Comment Puppet / PUP-2889 Upgrade win32-eventlog We need to either upgrade or replace the use of win32-eventlog. 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-2785) Error Max Connections (30) reached - try again later whiile trying rsync yum.puppetlabs.com::packages/yum/el
Title: Message Title Dustin J. Mitchell commented on an issue Re: Error Max Connections (30) reached - try again later whiile trying rsync yum.puppetlabs.com::packages/yum/el This appears to be OK now. Nathaniel, do you see the same? Add Comment Puppet / PUP-2785 Error Max Connections (30) reached - try again later whiile trying rsync yum.puppetlabs.com::packages/yum/el [root@mirror1ext puppet]# rsync -avSHP --stats --copy-links --exclude 5* --exclude 7* --exclude SRPMS --exclude sources --exclude apt --exclude apt-enterprise yum.puppetlabs.com::packages/yum/el . @ERROR: max connections (30) reached -- try again later rsync error: error starting client-server protocol (code 5) at main.c(1503) [receiver=3.0.6] This message was sent by Atlassian JIRA (v6.1.4#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-2804) Remove deprecation warnings introduced into Windows code during FFI
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2804 Remove deprecation warnings introduced into Windows code during FFI Change By: Josh Cooper Sprint: Week2014-7-23to2014-8-6 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 Josh Cooper commented on an issue Re: Upgrade win32-taskscheduler (or replace) Ethan Brown Sounds like this is not ready for merge? 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-500) Test CollectExpressions
Title: Message Title Henrik Lindberg commented on an issue Re: Test CollectExpressions Spec PR-6 merged. Add Comment Puppet / PUP-500 Test CollectExpressions Implement evaluation of CollectExpression, Query, ExportedQuery, VirtualQuery to support the equivalent 3x expressions. This message was sent by Atlassian JIRA (v6.1.4#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-2890) Puppet Resource Interface errors in unsupported environments
Title: Message Title Ethan Brown created an issue Puppet / PUP-2890 Puppet Resource Interface errors in unsupported environments Issue Type: Bug Affects Versions: 3.6.2 Assignee: Kylo Ginsberg Components: Client Created: 03/Jul/14 1:52 PM Priority: Normal Reporter: Ethan Brown Clone source Install gems locally with bundler bundle exec puppet resource interface The response should be something like Error: Could not run: whit has no providers and has not overridden 'instances' Instead, we get a non-descript Error with a crash
Jira (PUP-1281) Remove win32console gem in ruby 2.0 on windows
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-1281 Remove win32console gem in ruby 2.0 on windows Change By: Josh Cooper Assignee: JoshCooper 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 assigned an issue to Ethan Brown Puppet / PUP-2881 Upgrade win32-taskscheduler (or replace) 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-500) Test CollectExpressions
Title: Message Title Henrik Lindberg commented on an issue Re: Test CollectExpressions Merged to master 8ac08ee Add Comment Puppet / PUP-500 Test CollectExpressions Implement evaluation of CollectExpression, Query, ExportedQuery, VirtualQuery to support the equivalent 3x expressions. This message was sent by Atlassian JIRA (v6.1.4#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-2552) Future parser breaks concat module
Title: Message Title
Andy Parker commented on an issue
Re: Future parser breaks concat module
Nitzan Raz, thank you for the report. I think the behavior you are seeing is because you are specifying the fragment order like so: order = 001. Under the current parser 001 is actually treated as a bareword string, which means that it is equivalent to 001. However, the new parser is treating anything that is a numeric literal as a number, which causes 001 to be treated as the octal number 1. When the number is then interpolated into the string to construct the filename it is then stringified as the decimal representation of the number 1, which is simply 1.
You can fix this in your manifests by specifying the value 001 as a string literal of 001.
Add Comment
Puppet / PUP-2552
Future parser breaks concat module
When enabling future parser by specifying {quote} parser = future {quote} in puppet.conf, leading zeroes are removed from integers, disrupting file order in concat. For example, with future parser, keepalived creates this fragment: {quote} 1_keepalived.conf_header {quote} and not: {quote} 001_keepalived.conf_header {quote} Creating bad orderin...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2552) Future parser breaks concat module
Title: Message Title Andy Parker assigned an issue to Nitzan Raz Nitzan Raz, I'm assigning this back to you so that you can confirm that I've assessed the problem correctly and the suggested fix works. If that does work, then I'll close this as won't fix as this is just a side effect of the new number semantics. Puppet / PUP-2552 Future parser breaks concat module Change By: Andy Parker Assignee: AndyParker NitzanRaz 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.
