Jira (PUP-1291) scheduled_task : add support for every X minutes or hours mode
Title: Message Title
Dima commented on PUP-1291
Re: scheduled_task : add support for every X minutes or hours mode
Yes, it is trivial to support this, because all the stuff to configure it is already there, it's only the definitions which need to be accepted/taken from the type and using those values. I made a small diff (no support for the other stuff like end_year and end_day which is also already in there) There is 1 small, minor issue though (which I don't care about too much but which should take into account). If you have a scheduled task with repeat triggers and for example a start time. Then you start managing this scheduled task with puppet, leave out the minutes_interval and minutes_duration definition it won't change the repeat triggers when nothing changes (which is what you want because by not defining those optional properties you leave them unmanaged), but when for example the start time changes, the repeat triggers will dissapear because the provider uses a dummy_trigger definition in which they initialize the minutes_interval and minutes_duration to 0. They should take the current values in the scheduled task instead if repeat triggers aren't managed. Actually the current provider has the same issue I guess.
Here's a unified diff for the type and the provider, I hope Puppet can verify this patch and put support for repeat triggers in the next release. Sorry I can't provide a git pull request at this stage.
Type: (No code changes in the type, I only updated the comments and the example using repeat triggers)
diff -u scheduled_task.rb tasktype.rb — scheduled_task.rb 2015-02-13 09:48:29.0 +0100 +++ tasktype.rb 2015-02-13 09:49:56.0 +0100 @@ -100,6 +100,9 @@
`start_date` — The date when the trigger should first become active. Defaults to the current date. You should format dates as -MM-DD, although other date formats may work. (Under the hood, this uses `Date.parse`.) + * `minutes_interval` — The repeat interval in minutes. + * `minutes_duration` — The duration in minutes, needs to be greater or equal to + minutes_interval.
For daily triggers:
`every` — How often the task should run, as a number of days. Defaults to 1. (2 means every other day, 3 means every three days, etc.) @@ -138,7 +141,7 @@ }
Run at 8am on the first Monday of the month for January, March, and May,
# starting after August 31st, 2011. + # starting after August 31st, 2011. Repeat every 10 minutes for 50 minutes. trigger = { schedule = monthly, start_date = '2011-08-31', # Defaults to current date @@ -146,6 +149,8 @@ months = [1,3,5], # Defaults to all which_occurrence = first, # Must be specified day_of_week = [mon], # Must be specified + minutes_interval = 10, + minutes_duration = 60, }
Jira (PUP-3956) Puppet master doesn't free file descriptor during logrotate
Title: Message Title Bartosz Cisek commented on PUP-3956 Re: Puppet master doesn't free file descriptor during logrotate It might be worth testing if those two issues are related. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3956) Puppet master doesn't free file descriptor after USR2
Title: Message Title Bartosz Cisek updated an issue Puppet / PUP-3956 Puppet master doesn't free file descriptor after USR2 Change By: Bartosz Cisek Summary: Puppetmasterdoesn'tfreefiledescriptor duringlogrotate afterUSR2 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4008) Inferred type of empty hash not assignable to HashString,String
Title: Message Title Thomas Hallgren created an issue Puppet / PUP-4008 Inferred type of empty hash not assignable to HashString,String Issue Type: Bug Assignee: Unassigned Components: DSL Created: 2015/02/13 5:40 AM Fix Versions: PUP 3.7.5 Priority: Normal Reporter: Thomas Hallgren An empty hash is correctly considered an instance of Hash[String,String] but its inferred type Hash[Undef,Undef,0,0] is not assignable. This is not correct. The inferred type of an empty hash must be assignable to any Hash type that accepts zero entries. Add Comment
Jira (PUP-3632) Update paths and defaults for the unified FS layout
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-3632 Update paths and defaults for the unified FS layout Change By: Josh Cooper Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4010) Please error on non boolean conditionnal with future parser
Title: Message Title Mathieu Parent updated an issue Puppet / PUP-4010 Please error on non boolean conditionnal with future parser Change By: Mathieu Parent Summary: Error Pleaseerror onnonbooleanconditionnalwithfutureparser Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4011) Spec test failure on ruby 1.8.7: ProviderSystemd should not be the default provider on rhel4
Title: Message Title John Duarte created an issue Puppet / PUP-4011 Spec test failure on ruby 1.8.7: ProviderSystemd should not be the default provider on rhel4 Issue Type: Bug Assignee: Unassigned Created: 2015/02/13 8:50 AM Environment: ruby-1.8.7-p374 Priority: Normal Reporter: John Duarte CI spec test failure on master branch: See CI failure Error Message failed Puppet::Type::Service::ProviderSystemd should not be the default provider on rhel4 Stacktrace not all expectations were satisfied
Jira (PUP-4009) Add Cfacter 0.4.0 to Windows MSI
Title: Message Title Ethan Brown commented on PUP-4009 Re: Add Cfacter 0.4.0 to Windows MSI Kylo Ginsberg if you could add the CFacter 0.4.0 release ticket here as a blocker when it's created, that would be super. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1234) puppetdb service fails to stop on debian6
Title: Message Title Alice Nodelman created an issue PuppetDB / PDB-1234 puppetdb service fails to stop on debian6 Issue Type: Bug Assignee: Unassigned Created: 2015/02/13 9:03 AM Priority: Normal Reporter: Alice Nodelman Discovered in beaker smoketesting. Using puppetdb master, debian6, upgrade. See details in https://tickets.puppetlabs.com/browse/QENG-1763. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-4000) Struct with optional values is not assignable from Hash where key is missing
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-4000 Struct with optional values is not assignable from Hash where key is missing Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4009) Add Cfacter 0.4.0 to Windows MSI
Title: Message Title Ethan Brown created an issue Puppet / PUP-4009 Add Cfacter 0.4.0 to Windows MSI Issue Type: Task Assignee: Unassigned Components: Windows Created: 2015/02/13 7:47 AM Fix Versions: PUP 4.0.0 Labels: windows Priority: Normal Reporter: Ethan Brown CFacter 0.3.0 is the current version that we're bundling with the MSI. However, this version has a number of issues that prevent it from working properly on Windows, and therefore to be able to use cfacter with external facts (CFACT-219), custom facts, on Windows 2003 (CFACT-166) and inside puppet itself via the --cfacter switch ( CFACT-198 / PUP-3821 / CFACT-208 ), we must ship the fully released CFacter 0.4.0. Note that there were also
Jira (PUP-4010) Error on non boolean conditionnal with future parser
Title: Message Title
Mathieu Parent created an issue
Puppet / PUP-4010
Error on non boolean conditionnal with future parser
Issue Type:
New Feature
Assignee:
Unassigned
Components:
Breaking Change
Created:
2015/02/13 8:41 AM
Priority:
Normal
Reporter:
Mathieu Parent
In Puppet 3, an empty string is evaluated as false, but with future parser it is evaluated as true.
Example: if '' { fail('This fails on Puppet4') }
As this is very subtle, I propose to error when a condition is a string.
At least, warn when the condition is an empty string.
See https://github.com/example42/puppet-ntp/pull/29/files, for an example of affected module.
Add Comment
Jira (PUP-4010) Please error on non boolean conditionnal with future parser
Title: Message Title Henrik Lindberg commented on PUP-4010 Re: Please error on non boolean conditionnal with future parser You (and others) would probably not like the output if it always were to warn - as code moves forward you want to interpret the opposite as correct (i.e. '' is indeed true). It would need to be a special mode to find such problems. We are currently discussing ways to help with the migration from 3x. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4005) AIO agent corrupts CSR extensions
Title: Message Title Josh Cooper commented on PUP-4005 Re: AIO agent corrupts CSR extensions Most recently rhel7 acceptance on puppet#master passed and the generated file looks correct: syv0n4ohrysh6l1.delivery.puppetlabs.net (agent) 22:11:04$ cat /tmp/certificate_extensions.PyBLtY/trusted.yaml --- authenticated: remote certname: syv0n4ohrysh6l1.delivery.puppetlabs.net-extensions extensions: pp_uuid: b5e63090-5167-11e3-8f96-0800200c9a66 pp_instance_id: i-3fkva 1.3.6.1.4.1.34380.1.2.1: db-server 1.3.6.1.4.1.34380.1.2.2: webops In puppet#master, the master and agent rhel7 nodes are the same (x86_64), and it appears they are using slightly different ruby openssl versions that AIO. From the
Jira (PDB-1234) puppetdb service fails to stop on debian6
Title: Message Title Alice Nodelman commented on PDB-1234 Re: puppetdb service fails to stop on debian6 Cools, just making sure that this is an acceptable state. We have removed our debian6 testing so we won't hit this in future. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4011) Spec test failure on ruby 1.8.7: ProviderSystemd should not be the default provider on rhel4
Title: Message Title Scott Garman updated an issue Puppet / PUP-4011 Spec test failure on ruby 1.8.7: ProviderSystemd should not be the default provider on rhel4 Change By: Scott Garman Sprint: RE2015-02-25 Scrum Team: ReleaseEngineering Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3978) Change how block is passed to avoid confusion with missing optional parameters
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-3978 Change how block is passed to avoid confusion with missing optional parameters Change By: Eric Thompson Assignee: EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4012) parsed provider destroys file if a line starts with uppercase Q
Title: Message Title Stefan Schulte created an issue Puppet / PUP-4012 parsed provider destroys file if a line starts with uppercase Q Issue Type: Bug Affects Versions: PUP 3.7.3 Assignee: Stefan Schulte Components: Types and Providers Created: 2015/02/13 10:13 AM Priority: Major Reporter: Stefan Schulte if a record in a file starts with an uppercase Q, puppet will merge this line with the previous line when the file is written back to disc, making the file invalid. I know this sounds weired def lines(text) # Remove any trailing separators, and then split based on them
Jira (PUP-3978) Change how block is passed to avoid confusion with missing optional parameters
Title: Message Title
Eric Thompson commented on PUP-3978
Re: Change how block is passed to avoid confusion with missing optional parameters
verified on rhel7 at SHA: e46fb00
others: note the code block here is all puppet. the function is ruby, obviously. the call to yield implicitly finds the block reference. to have the optional arguments work properly arg_count() is required
[root@w6bj64gi8xne3xr functions]# puppet apply -e 'test(3) |$x| {notice(should be second arg: $x)}'
passed a (first arg): 3
passed b (optional arg): 4
Notice: Scope(Class[main]): should be second arg: 4
Notice: Compiled catalog for w6bj64gi8xne3xr.delivery.puppetlabs.net in environment production in 0.37 seconds
Notice: Applied catalog in 0.01 seconds
[root@w6bj64gi8xne3xr functions]# puppet apply -e 'test(3,6) |$x| {notice(should be second arg: $x)}'
passed a (first arg): 3
passed b (optional arg): 6
Jira (PDB-1234) puppetdb service fails to stop on debian6
Title: Message Title Kenneth Barber commented on PDB-1234 Re: puppetdb service fails to stop on debian6 We've dropped Debian 6 support for FOSS in the master branch. So this is totally expected. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4011) Spec test failure on ruby 1.8.7: ProviderSystemd should not be the default provider on rhel4
Title: Message Title Scott Garman assigned an issue to Scott Garman Puppet / PUP-4011 Spec test failure on ruby 1.8.7: ProviderSystemd should not be the default provider on rhel4 Change By: Scott Garman Assignee: ScottGarman Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1234) puppetdb service fails to stop on debian6
Title: Message Title Kenneth Barber commented on PDB-1234 Re: puppetdb service fails to stop on debian6 Just spoke to Matthaus Owens and he double confirmed this, so basically: [17:57] Ken Barber: hey man sorry to bother you, I'm having trouble remembering something about Debian 6 being dropped from FOSS support. Was this true or was I just imagining this conversation? [17:57] Matthaus Owens: it's been dropped as a PE master [17:57] Ken Barber: aaah yes gotcha [17:57] Matthaus Owens: also dropped for anything using ezbake (so puppetdb 3.0) So I think we don't need to care for now. We won't ship packages for this for FOSS as well basically. Add Comment
Jira (PUP-1601) functions accepting regexp string should also accept Regexp
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-1601 functions accepting regexp string should also accept Regexp Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3992) yaml nulls break data binding for class params
Title: Message Title Christopher Wood commented on PUP-3992 Re: yaml nulls break data binding for class params After jcbollinger's followup in that thread, I think the problem here is not that puppet is not accepting the null as undef from hiera, but that the error message seems a bit puzzling. Instead of Must pass param1 perhaps something like Must pass a non-nil value for param1 Because the hiera key is there, it's just that the value associated with the key is unacceptable. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1235) Possible memory leaks / GC issues
Title: Message Title Lee Lowder created an issue PuppetDB / PDB-1235 Possible memory leaks / GC issues Issue Type: Bug Affects Versions: PDB 1.6.3 Assignee: Unassigned Created: 2015/02/13 11:59 AM Labels: support customer Priority: Normal Reporter: Lee Lowder The version of PuppetDB ( 1.6.3) that ships with PE 3.3.2 appears to have either a memory leak, or an issue with garbage collection. From a customer: I’ve bumped the java heap size several times now, and it seems to be able to chew up what ever we bump it up to. This would seem to be an indication of poor garbage collection and/or memory leaks. Currently that heap is at 2.5 gigs, after getting warnings when it was at 1.5 gigs.
Jira (PUP-3979) Windows Package Should Switch between Execute and Install Mode
Title: Message Title Nan Liu commented on PUP-3979 Re: Windows Package Should Switch between Execute and Install Mode Can you use loglevel = debug for the exec? or just use unless = 'change.exe usr /install', if you don't want to see the events? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4012) parsed provider destroys file if a line starts with uppercase Q
Title: Message Title Stefan Schulte commented on PUP-4012 Re: parsed provider destroys file if a line starts with uppercase Q yep. When one of our DBAs told me puppet would mangle the `/var/opt/oracle/oratab` file but only if the database starts with a Q I was staring at the screen in disbelief Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4012) parsed provider destroys file if a line starts with uppercase Q
Title: Message Title Kylo Ginsberg commented on PUP-4012 Re: parsed provider destroys file if a line starts with uppercase Q As for the why? it's been that way since day 1-ish: https://github.com/puppetlabs/puppet/commit/7c8614b0589f7c843d17b9d16720419817394cee#diff-963082f87f2ec3b552add05de272f143R70 But I don't know why. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4012) parsed provider destroys file if a line starts with uppercase Q
Title: Message Title Stefan Schulte commented on PUP-4012 Re: parsed provider destroys file if a line starts with uppercase Q in case you haven't noticed already: I have attached a pull request for this one. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2716) ssl_server_ca_chain and ssl_client_ca_chain are dead settings
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2716 ssl_server_ca_chain and ssl_client_ca_chain are dead settings Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2716) ssl_server_ca_chain and ssl_client_ca_chain are dead settings
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2716 ssl_server_ca_chain and ssl_client_ca_chain are dead settings Change By: Nicholas Fagerlund Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-779) Remove deprecated process execution methods in util
Title: Message Title Nicholas Fagerlund commented on PUP-779 Re: Remove deprecated process execution methods in util The description needs to be updated to explain what was removed, and what to use instead. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3978) Change how block is passed to avoid confusion with missing optional parameters
Title: Message Title
Eric Thompson commented on PUP-3978
Re: Change how block is passed to avoid confusion with missing optional parameters
verified on ubuntu14.04 at SHA: e46fb00
root@vb9b8r45w9v9pkp:/usr/local/lib/site_ruby/1.9.1/puppet/functions# puppet apply -e 'test(3) |$x| {notice(should be second arg: $x)}'
passed a (first arg): 3
passed b (optional arg): 4
Notice: Scope(Class[main]): should be second arg: 4
Notice: Compiled catalog for vb9b8r45w9v9pkp.delivery.puppetlabs.net in environment production in 0.36 seconds
Notice: Applied catalog in 0.01 seconds
root@vb9b8r45w9v9pkp:/usr/local/lib/site_ruby/1.9.1/puppet/functions# puppet apply -e 'test(3, 42) |$x| {notice(should be second arg: $x)}'
passed a (first arg): 3
passed b (optional arg): 42
Jira (PUP-3632) Update paths and defaults for the unified FS layout
Title: Message Title Jeff McCune updated an issue Puppet / PUP-3632 Update paths and defaults for the unified FS layout Change By: Jeff McCune ThecomingupdatetotheFSlayoutforourprojectsrequiresseveralchangestodefaultpathingandconfigfilestoensurethatthecorrectdirectoriesareused.Offthetopofmyheadthisincludesdefaults.rbandpuppet.confbutitmayextendintootherfilesaswell.Defaultloggingisprobablyalsoaffected.Thenewlayoutisdescribedhere:https://confluence.puppetlabs.com/display/DEL/Unified+Puppet+Agent+Layout Andcopy-pasta'dhere:Configfiles:/etc/puppetlabs/agent/$projectLogs:/var/log/puppetlabs/agent/$project.logPrefixis/opt/puppetlabs/agentBinarieslivein/opt/puppetlabs/agent/binLibrariesandheaderslivein/opt/puppetlabs/agent/liband/opt/puppetlabs/agent/include,respectivelyArchitectureindependentdata(manpagesforexample)in/opt/puppetlabs/agent/sharePuppetvardirwillbe/opt/puppetlabs/agent/cachePuppetssldirwillbe/etc/puppetlabs/agent/sslUsermodulepath/etc/puppetlabs/agent/modulesSystemmodulepath(forcorecommunitymodules)/opt/puppetlabs/agent/modulesMCOplugindir:/opt/puppetlabs/agent/plugins Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4009) Add Cfacter 0.4.0 to Windows MSI
Title: Message Title Kylo Ginsberg commented on PUP-4009 Re: Add Cfacter 0.4.0 to Windows MSI Ethan Brown I haven't created the ticket yet b/c I expect the cfacter version to be late binding based on how that work proceeds vs puppet-agent 1.0.0 going final (e.g. it might be cfacter 0.4.0 or it might be cfacter 1.0.0). That said, I'm not clear whether lack of a cfacter release is blocking progress for you or not. If you want to tie to a tag rather than a sha in the meantime, we could certainly push a tag and not bother with the other release festivities. (E.g. similar to what we did (or are doing) for hiera 2.0.0-rc1.) If so, let me know. I'm fine pushing a tag. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3632) Update paths and defaults for the unified FS layout
Title: Message Title Matthaus Owens commented on PUP-3632 Re: Update paths and defaults for the unified FS layout Jeff McCune The layout was copied into the description because confluence isn't available publicly, so users would have no way of knowing the layout. Not ideal to copy it, but I didn't have a better way. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3978) Change how block is passed to avoid confusion with missing optional parameters
Title: Message Title
Eric Thompson commented on PUP-3978
Re: Change how block is passed to avoid confusion with missing optional parameters
verified on windows2012r2-ruby64 at SHA: e46fb00
Administrator@o6b2aha4d0vaw56 /usr/lib/ruby/site_ruby/2.1.0/puppet/functions
$ cmd /c puppet apply -e 'test(3) |$x| {notice(should be second arg: $x)}'
passed a (first arg): 3
passed b (optional arg): 4
Notice: Scope(Class[main]): should be second arg: 4
Notice: Compiled catalog for o6b2aha4d0vaw56.delivery.puppetlabs.net in environment production in 0.45 seconds
Notice: Applied catalog in 0.02 seconds
Administrator@o6b2aha4d0vaw56 /usr/lib/ruby/site_ruby/2.1.0/puppet/functions
$ cmd /c puppet apply -e 'test(3, 2345234634563457) |$x| {notice(should be second arg: $x)}'
Jira (PUP-1413) Support touch command for augeas type
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-1413 Support touch command for augeas type Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1601) functions accepting regexp string should also accept Regexp
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-1601 functions accepting regexp string should also accept Regexp Change By: Nicholas Fagerlund Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1413) Support touch command for augeas type
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-1413 Support touch command for augeas type Change By: Nicholas Fagerlund Labels: augeas docs_reviewed puppet Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3656) Prefetch eats all exceptions, there is no way to fail out.
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3656 Prefetch eats all exceptions, there is no way to fail out. Change By: Nicholas Fagerlund Labels: breaking docs_reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1291) scheduled_task : add support for every X minutes or hours mode
Title: Message Title Rob Reynolds commented on PUP-1291 Re: scheduled_task : add support for every X minutes or hours mode Dima Would you mind providing that patch on https://github.com/puppetlabs/puppet? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3948) Let lookup be the impl for agnostic lookup of data
Title: Message Title Henrik Lindberg commented on PUP-3948 Re: Let lookup be the impl for agnostic lookup of data PUP-3948 brings up the need to distinguish between not found (nil), and bound to nil. When using lookup directly, that probably does not need any changes since you can always use a default value that you can recognize, do things with the block etc. Data Provider implementations must however to also make this distinction and it must be handled in merges etc. Maybe open a separate ticket for that? (Using the PUP-3948 ticket to solve it for hiera - data binding?) Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3992) ensure data binding for class params can produce undef
Title: Message Title
Christopher Wood commented on PUP-3992
Re: ensure data binding for class params can produce undef
I can confirm that hiera+puppet does work with {} or [] or '' in 3.7.2.
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-579) Add automated tests for Windows installer packages
Title: Message Title Kurt Wall updated an issue Puppet / PUP-579 Add automated tests for Windows installer packages Change By: Kurt Wall Component/s: QA Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-579) Add automated tests for Windows installer packages
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-579 Add automated tests for Windows installer packages Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-579) Add automated tests for Windows installer packages
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-579 Add automated tests for Windows installer packages Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3979) Windows Package Should Switch between Execute and Install Mode
Title: Message Title Etienne Lacombe commented on PUP-3979 Re: Windows Package Should Switch between Execute and Install Mode loglevel = debug does get rid of the output but the run still gets recorded as if it had changed something on the node. unless - not sure how I would implement this. I would need to run the package first to know if it will need to install, if it does, then before installing it, then I need to run the exec but if it won't install anything (because it's already installed) then I don't need to run the exec. What I see more workable, but that means changing the windows package provider is that either through a parameter or on its own volition, it runs those commands to change the mode if it determine that it will install the package. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-579) Add automated tests for Windows installer packages
Title: Message Title Kurt Wall commented on PUP-579 Re: Add automated tests for Windows installer packages Nothing for QA to do here. Moving to QENG. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3992) ensure data binding for class params can produce undef
Title: Message Title Henrik Lindberg commented on PUP-3992 Re: ensure data binding for class params can produce undef Note that in Puppet 3.7.5 with future parser, and in 4.0.0 we have reimplemented the hiera functions using the 4x function API to make it possible to differentiate between undef and empty string values (this is not the same issue as this, but worth mentioning). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-579) Add automated tests for Windows installer packages
Title: Message Title Kurt Wall assigned an issue to QE Puppet / PUP-579 Add automated tests for Windows installer packages Change By: Kurt Wall Assignee: KurtWall QE Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-579) Add automated tests for Windows installer packages
Title: Message Title Kurt Wall updated an issue Puppet / PUP-579 Add automated tests for Windows installer packages Change By: Kurt Wall QA Contact: ErikDasher Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-408) Puppet package acceptance is sufficient for a smoke test
Title: Message Title Kurt Wall updated an issue Puppet / PUP-408 Puppet package acceptance is sufficient for a smoke test Change By: Kurt Wall Component/s: QA Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4012) parsed provider destroys file if a line starts with uppercase Q
Title: Message Title Kylo Ginsberg commented on PUP-4012 Re: parsed provider destroys file if a line starts with uppercase Q Wow. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3130) Remove hidden $_timestamp fact
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3130 Remove hidden $_timestamp fact Change By: Nicholas Fagerlund Labels: docs_reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3130) Remove hidden $_timestamp fact
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3130 Remove hidden $_timestamp fact Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4012) parsed provider destroys file if a line starts with uppercase Q
Title: Message Title Stefan Schulte commented on PUP-4012 Re: parsed provider destroys file if a line starts with uppercase Q yeah I also didn't find anything in the code history what the `sub` method intention is. If it is just trailing delimiters, the split already does the job. If it is intended to do something else, it has never worked. AFAIK in perl `\Qsomehing\E` causes something to be treated literal - e.g. if line_seperator would be a simple `.` it will not suddenly match EVERY character. But then the `sub` method would remove every line_seperator which also does not make any sense. So for now I'll go with never worked - obviously not needed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3656) Prefetch eats all exceptions, there is no way to fail out.
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-3656 Prefetch eats all exceptions, there is no way to fail out. Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3978) Change how block is passed to avoid confusion with missing optional parameters
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3978 Change how block is passed to avoid confusion with missing optional parameters Change By: Eric Thompson QA Contact: EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3978) Change how block is passed to avoid confusion with missing optional parameters
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3978 Change how block is passed to avoid confusion with missing optional parameters Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4009) Add Cfacter 0.4.0 to Windows MSI
Title: Message Title Ethan Brown commented on PUP-4009 Re: Add Cfacter 0.4.0 to Windows MSI Kylo Ginsberg the version we select is actually bound only to a package name that's stored somewhere in build.puppetlabs.lan https://github.com/puppetlabs/puppet/blob/master/ext/build_defaults.yaml#L27-L29 cfacter: archive: x86: 'cfacter-0.3.0-x86.zip' x64: 'cfacter-0.3.0-x64.zip' path: 'http://builds.puppetlabs.lan/cfacter/0.3.0/artifacts/windows' Therefore it is possible + grab 0.3.0 + all patches affecting Windows if we want to pick a known good build number that solves the critical / blocker issues. That said, I think that approach might be a bit confusing if we're doing something different in other environments. I would prefer that we stick to an officially blessed / signed off release. At the very least though, we can't use the current 0.3.0 that we're pinned to based on all the reasons in the description for this ticket (essentially it just doesn't work). /cc Melissa Stone Add Comment
Jira (PUP-1291) scheduled_task : add support for every X minutes or hours mode
Title: Message Title Rob Reynolds updated an issue Puppet / PUP-1291 scheduled_task : add support for every X minutes or hours mode Change By: Rob Reynolds Component/s: Windows Component/s: PE Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3992) ensure data binding for class params can produce undef
Title: Message Title Henrik Lindberg commented on PUP-3992 Re: ensure data binding for class params can produce undef Solving this for databinding is problematic since it uses the indirector service and the indirector is incapable of returning anything interesting besides a found value or nil - we have had other problems like this in the past. The real solution is to switch from using the data binding via the indirector and instead use the data provider backends ( PUP-1640 , PUP-3948) also for hiera when they become available. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3809) Separate code (content?) and configuration directories for AIO packaging
Title: Message Title
Eric Sorenson updated an issue
Puppet / PUP-3809
Separate code (content?) and configuration directories for AIO packaging
Change By:
Eric Sorenson
Therehasbeenathreadgoingaroundbetweensomeengineeringfolksandsomereleasefolksabouttheneedforseparatingcode(orcontent)andconfigurationintotwodistinctdirectories.ThiswillmakeiteasiertosynctheappropriatefilesaroundtomultiplemastersviatheforthcomingFileSyncservice.Thefilesystemlayoutshouldlooklike:{code}#locationsfor'puppet*'subcommandconfigfiles(agent,apply,master)/etc/puppetlabs/puppet/{puppet,auth,fileserver}.conf=canonicalconfigdirectory/etc/puppetlabs/puppet/ssl=puppet'ssslcerts#separatepuppetprojectsgettheirownconfigdirectoriesatthislevel/etc/puppetlabs/puppetserver=puppetserverconfigdir/etc/puppetlabs/puppetdb=puppetdbconfigdir#'code'constructs(i.e.inputsintoacatalog)gotonew'code'directory#thisisusuallythecheckoutofar10kcontrolrepo/etc/puppetlabs/code=codedirincludeshiera.yaml,hieradata,modules,manifests/etc/puppetlabs/code/environments/=defaultlocationfor'$environmentpath'#binaries and , libraries ,modulesshippedwiththepackage liveunder/opt/puppetlabs/opt/puppetlabs/bin=symlinktargetfor'puppet','puppetserver','puppetdb',etc./opt/puppetlabs/puppet=newruby-puppetroot(bin,lib,cache,plugins,include,shareunderneath)/opt/puppetlabs/ puppet/modules=systemmodulepath/opt/puppetlabs/ server=serversideappsliveunderneath/opt/puppetlabs/server/puppetserver/ #stateandlogdirectories/var/run/puppetlabs=pidfilesgohere/var/log/puppetlabs=logfilesgohere{code}
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-4000) Struct with optional values is not assignable from Hash where key is missing
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-4000 Struct with optional values is not assignable from Hash where key is missing Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-408) Puppet package acceptance is sufficient for a smoke test
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-408 Puppet package acceptance is sufficient for a smoke test Change By: Kurt Wall Assignee: KurtWall Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3632) Update paths and defaults for the unified FS layout
Title: Message Title Jeff McCune updated an issue Puppet / PUP-3632 Update paths and defaults for the unified FS layout Change By: Jeff McCune ThecomingupdatetotheFSlayoutforourprojectsrequiresseveralchangestodefaultpathingandconfigfilestoensurethatthecorrectdirectoriesareused.Offthetopofmyheadthisincludesdefaults.rbandpuppet.confbutitmayextendintootherfilesaswell.Defaultloggingisprobablyalsoaffected.Thenewlayoutisdescribedhere:https://confluence.puppetlabs.com/display/DEL/Unified+Puppet+Agent+Layout ThelayoutintheunifiedPuppetAgentwillbeasfollows:Puppetpuppetdirwillbe/etc/puppetlabs/puppetPuppetconfdirwillbe/etc/puppetlabs/puppetPuppetcodedirwillbe/etc/puppetlabs/codePuppetvardirwillbe/opt/puppetlabs/agent/cachePuppetssldirwillbe/etc/puppetlabs/puppet/sslConfigfiles:/etc/puppetlabs/$project/$project.confLogs:/var/log/puppetlabs/$project.logPrefixis/opt/puppetlabs/puppetBinarieslivein/opt/puppetlabs/puppet/binLibrariesandheaderslivein/opt/puppetlabs/puppet/liband/opt/puppetlabs/puppet/include,respectivelyArchitectureindependentdata(manpagesforexample)in/opt/puppetlabs/puppet/shareUsermodulepath/etc/puppetlabs/code/modulesSystemmodulepath(forcorecommunitymodules)/opt/puppetlabs/puppet/modulesMCOplugindir:/opt/puppetlabs/mcollective/pluginsPidfiledir:/var/run/puppetlabsThislayoutwillhelpachievethefollowinggoals:EasiermigrationfromFOSStoPEforusers(nomigrationreallyintheunifiedagentworld)IsolationfrompotentialsystemlibraryconflictsSimplifyuserexperiencewithrespecttosoftwarelayoutbetweenFOSS/PESimplifydeploymentsystemsforFOSSandPEIsolateagentandservercomponentsUnifieddocumentationforthepuppetagent Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
Jira (PUP-3632) Update paths and defaults for the unified FS layout
Title: Message Title Jeff McCune commented on PUP-3632 Re: Update paths and defaults for the unified FS layout Matthaus Owens Got it, I copied it back. It was just out-of-date which is why I deleted it. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-408) Puppet package acceptance is sufficient for a smoke test
Title: Message Title Kurt Wall commented on PUP-408 Re: Puppet package acceptance is sufficient for a smoke test Don't think I am the one to make the call that package acceptance testing is equivalent to smoke testing. Feels like a PO's or a lead's call in consultation with the devs Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1291) scheduled_task : add support for every X minutes or hours mode
Title: Message Title Dima commented on PUP-1291 Re: scheduled_task : add support for every X minutes or hours mode Sure, I created a pull request https://github.com/puppetlabs/puppet/pull/3610 Bare with me as this is the first github stuff for me... Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2627) Collecting defined types in masterless configuration
Title: Message Title Nathan Brown commented on PUP-2627 Re: Collecting defined types in masterless configuration Can confirm, this also affects puppet 3.7.3. Super frustrating since this is the only reference to the bug on the entire interwebs. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-336) add spec edge cases to ensure hiera lookup doesn't contain values from outside hierarchy
Title: Message Title Eric Thompson updated an issue Hiera / HI-336 add spec edge cases to ensure hiera lookup doesn't contain values from outside hierarchy Change By: Eric Thompson addsomedoesn'tgrabstuffinthewronghierarchytypespecedgecases... Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-336) add spec edge cases to ensure hiera lookup doesn't contain values from outside hierarchy
Title: Message Title Eric Thompson updated an issue Hiera / HI-336 add spec edge cases to ensure hiera lookup doesn't contain values from outside hierarchy Change By: Eric Thompson Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-336) add spec edge cases to ensure hiera lookup doesn't contain values from outside hierarchy
Title: Message Title Eric Thompson created an issue Hiera / HI-336 add spec edge cases to ensure hiera lookup doesn't contain values from outside hierarchy Issue Type: Task Assignee: QA Components: QA Created: 2015/02/13 1:43 PM Priority: Normal Reporter: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the
Jira (PUP-3992) ensure data binding for class params can produce undef
Title: Message Title Henrik Lindberg commented on PUP-3992 Re: ensure data binding for class params can produce undef Let's have the discussion in the lookup ticket (PUP-3948) Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3992) yaml nulls break data binding for class params
Title: Message Title Henrik Lindberg commented on PUP-3992 Re: yaml nulls break data binding for class params Hiera signals not found by returning nil - with the current implementation it is not possible to differentiate between the two. You should however be able to return an array or hash with a nil value. I am changing the title of this ticket since it is a general hiera problem, not specific to YAML (albeit the fix may need to be made in all backends). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3992) ensure data binding for class params can produce undef
Title: Message Title Thomas Hallgren commented on PUP-3992 Re: ensure data binding for class params can produce undef One solution would be to raise an exception for not found and return nil when the key is there but produces a nil value. Will require a rewrite of parts of the data providers too since they must make the same distinction. We must also answer the question of when the extras and default value should be used. Only when key not found or also when value is nil? And current 'accept_undef' flag must be renamed and re-purposed. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3992) ensure data binding for class params can produce undef
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3992 ensure data binding for class params can produce undef Change By: Henrik Lindberg Summary: yamlnullsbreak ensure databindingforclassparams canproduceundef Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3992) ensure data binding for class params can produce undef
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3992 ensure data binding for class params can produce undef ping Thomas Hallgren - something to consider in the new lookup function wrt to the data provider backend API Change By: Henrik Lindberg Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-407) Place facts in a topscope hash
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-407 Place facts in a topscope hash Change By: Henrik Lindberg Fix Version/s: PUP4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-2452) Refreshable feature on package type
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-2452 Refreshable feature on package type Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-4005) AIO agent corrupts CSR extensions
Title: Message Title William Hopper commented on PUP-4005 Re: AIO agent corrupts CSR extensions Earlier, Josh Cooper recommended that we revert PUP-3560 to address this issue in the AIO pipeline. As a test, I fired off the certificate_extension test with: bundle exec rake ci:test:aio SHA=8642ba76b6166b2bb788a9a6f7e62ee46db2234f TESTS=./tests/ssl/certificate_extensions.rb CONFIG=./config/nodes/rhel7.yaml OPTIONS=--preserve-hosts=always with the intention of manually reverting the commit on the agent in order to see if the correct CSR is generated. The SHA above is the latest puppet-agent build (as of Feb 13: http://builds.puppetlabs.lan/puppet-agent/?C=M;O=D). As we expected, the initial test failed due to the extra leading bytes in the CSR extensions: [root@wyy45yunberlo5m certificate_requests]# openssl req -in before_revert.pem -noout -text Certificate Request: Data: Version: 0 (0x0) Subject: CN=before_revert Subject Public Key Info: Public Key Algorithm: rsaEncryption Public-Key: (4096 bit)
Jira (PUP-4013) Uninstalling windows package adds /repair paramater instead of /uninstall
Title: Message Title Anthony Brown created an issue Puppet / PUP-4013 Uninstalling windows package adds /repair paramater instead of /uninstall Issue Type: Bug Affects Versions: PUP 3.7.4 Assignee: Unassigned Components: Windows Created: 2015/02/13 9:19 PM Environment: Windows agent, using puppet package commands, Windows 2008 Labels: windows Priority: Normal Reporter: Anthony Brown When using the puppet agent on a windows host and attempting to uninstall the 'Microsoft .NET Framework 4.5.1' package using ensure = absent the /repair parameter was passed instead of the /uninstall parameter. This was before any uninstall_options were applied.
Jira (PUP-4013) Uninstalling windows package adds /repair paramater instead of /uninstall
Title: Message Title
Anthony Brown updated an issue
Puppet / PUP-4013
Uninstalling windows package adds /repair paramater instead of /uninstall
Change By:
Anthony Brown
Whenusingthepuppetagentonawindowshostandattemptingtouninstallthe'Microsoft.NETFramework4.5.1'packageusingensure=absentthe/repairparameterwaspassedinsteadofthe/uninstallparameter. Thiswasbeforeanyuninstall_optionswereapplied. Thismeanstheproductwillberepairedandneveruninstalled. Outputfromdebug:{quote}Debug:Executing'cmd.exe/cstartpuppet-uninstall/wC:\Windows\Microsoft.NET\Framework64\v4.0.30319\SetupCache\v4.5.50938\\Setup.exe_*/repair*_/x86/x64'{quote}
Add Comment
This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
