Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage Wyatt Alt, we running 2.3.2. In common it raises but sometimes it falling. Current value is: puppetdb=# select count(*) from fact_values where id not in (select distinct fact_value_id from facts); count 122622 (1 row) [root@eu6-mgmt-2 ~]# facter -p last_run Thu Apr 16 07:50:54 UTC 2015 [root@eu6-mgmt-2 ~]# facter -p last_run Thu Apr 16 07:51:05 UTC 2015
Jira (PUP-4421) Virtual resource collectors incorrectly collect exported resources from same node
Title: Message Title
Fabien Wernli created an issue
Puppet / PUP-4421
Virtual resource collectors incorrectly collect exported resources from same node
Issue Type:
Bug
Affects Versions:
PUP 3.7.5
Assignee:
Unassigned
Created:
2015/04/16 12:57 AM
Environment:
linux EL6 and debian8
Priority:
Major
Reporter:
Fabien Wernli
Virtual resource collectors incorrectly collect exported resources from same node. This can very easily be reproduced using:
puppet apply -e '@@notify {"should not be collected":}
Notify <| |>'
This behaviour also appears in agent/master mode
Add Comment
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko updated an issue PuppetDB / PDB-1124 PuppetDB high CPU usage Change By: Anton Fomenko Attachment: Screen Shot 2015-04-16 at 10.50.00.png Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage Also we have messages like this in puppetdb.log: 2015-04-16 10:32:09,634 ERROR [c.p.p.command] [eb62c0fb-d2dc-41cb-8738-55b9270c7d18] [replace facts] Retrying after attempt 9, due to: java.sql.BatchUpdateException: Batch entry 0 DELETE FROM fact_values fv WHERE fv.id in (72,105271,87092921,343,13,28146635,13,86208955,87092925,53183,264,36,225,105244,87092925,53191,105244,312,29112200,105043,87092921,5,53190,38227884,452,225,111,236,87092923,19,21424983,111,13,236,1049,19,44300,264,87092924,8,53175,608,67265556,111,4060,22067637,27126,104967,28146635,104894,105184,105244,105043,53181,104930,53176,87092922,13,53185,264,53170,111,757) AND NOT EXISTS (SELECT 1 FROM facts f WHERE f.fact_value_id in (72,105271,87092921,343,13,28146635,13,86208955,87092925,53183,264,36,225,105244,87092925,53191,105244,312,29112200,105043,87092921,5,53190,38227884,452,225,111,236,87092923,19,21424983,111,13,236,1049,19,44300,264,87092924,8,53175,608,67265556,111,4060,22067637,27126,104967,28146635,104894,105184,105244,105043,53181,104930,53176,87092922,13,53185,264,53170,111,757) AND f.fact_value_id = fv.id AND (f.factset_id, f.fact_path_id) NOT in ((2023,13),(2023,70),(2023,71),(2023,213),(2023,134),(2023,67),(2023,1475),(2023,4073),(2023,47),(2023,184),(2023,131),(2023,57),(2023,1481),(2023,3351),(2023,1461),(2023,460),(2023,1459),(2023,496),(2023,495),(2023,1457),(2023,1442),(2023,46),(2023,41),(2023,389),(2023,412),(2023,138),(2023,1450),(2023,141),(2023,144),(2023,11),(2023,97),(2023,1449),(2023,1473),(2023,1479),(2023,90),(2023,119),(2023,51),(2023,1436),(2023,74),(2023,23),(2023,455),(2023,504),(2023,3486),(2023,139),(2023,53),(2023,1779),(2023,110),(2023,142),(2023,2),(2023,3048),(2023,529),(2023,96),(2023,18),(2023,29),(2023,120),(2023,75),(2023,28),(2023,62),(2023,
Jira (PUP-4421) Virtual resource collectors incorrectly collect exported resources from same node
Title: Message Title Henrik Lindberg commented on PUP-4421 Re: Virtual resource collectors incorrectly collect exported resources from same node Are you using parser=future? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4421) Virtual resource collectors incorrectly collect exported resources from same node
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-4421
Virtual resource collectors incorrectly collect exported resources from same node
Change By:
Henrik Lindberg
Virtual resource collectors incorrectly collect exported resources from same node. This can very easily be reproduced using: {code} puppet apply -e '@@notify {"should not be collected":} Notify <| |>' {code} This behaviour also appears in agent/master mode
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4421) Virtual resource collectors incorrectly collect exported resources from same node
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4421 Virtual resource collectors incorrectly collect exported resources from same node Change By: Henrik Lindberg Scrum Team: Language Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4421) Virtual resource collectors incorrectly collect exported resources from same node
Title: Message Title Henrik Lindberg assigned an issue to Fabien Wernli Puppet / PUP-4421 Virtual resource collectors incorrectly collect exported resources from same node Change By: Henrik Lindberg Assignee: Fabien Wernli Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2894) lvalue comma asignment should splat* an array
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2894 lvalue comma asignment should splat* an array Change By: Henrik Lindberg Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2894) lvalue comma asignment should splat* an array
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-2894
lvalue comma asignment should splat* an array
Change By:
Henrik Lindberg
when using the future parser, it allows for comma separated statements, and assignment to occur in these.However, I would like to "splat" an array, using a similar syntax which currently is not supported{code}$input = 'example.org:www:filters:gzip text/html'$title, $vhost, $valve, $filter = split_titles($input)notice("\ntitle: ${title}\nvhost: ${vhost}\nvalve: ${valve}\nfilter: ${filter}"){code}This produced (with --parser=future) the following output:{code}title: mainvhost: valve: filter: [example.org, www, filters, gzip text_html]{code}We would like to have a syntax, such as{code}$input = 'example.org:www:filters:gzip text/html'[ $title, $vhost, $valve, $filter ] = split_titles($input)notice("\ntitle: ${title}\nvhost: ${vhost}\nvalve: ${valve}\nfilter: ${filter}"){code}Which produces the following output:{code}title: example.orgvhost: wwwvalve: filtersfilter: gzip text_html{code} FOR DOCS---Multiple variables can be assigned in turn from an array. The variables on the LHS must be in an Array and there must be an equal number ofvalues in the assigned value array. If the value is not an Array it is treated as an Array of one element. Multi variable assignment supports sub-arraysof variables to match sub-arrays of values.{code}# examples[$a, $b, $c] = [1,2,3] # $a = 1, $b = 2, $c = 3[$a, [$b, $c]] = [1,[2,3]] # $a = 1, $b = 2, $c = 3[$a, $b] = [1, [2]] # $a = 1, $b = [2][$a, [$b]] = [1, [2]] # $a = 1, $b = 2{code}QA--- risk: mediumprobability: mediumseverity: medium/low (work arounds available)test layer: unit
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-2862) Validate that default value expression for param does not define variable
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-2862 Validate that default value _expression_ for param does not define variable Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1438) Upgrade to >= ezbake 0.3.3
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1438 Upgrade to >= ezbake 0.3.3 Issue Type: Task Assignee: Unassigned Created: 2015/04/16 4:20 AM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: Kenneth Barber Ezbake 0.3.3 now has removed Fedora 19 as a build target, we should upgrade to this version ASAP. Quote from Jeremy Barlow: "This only incorporates one change - removal of Fedora 19 as a build target. As work to remove Fedora 19 from yum.puppetlabs.com has been recently completed - see https://tickets.puppetlabs.com/browse/RE-3803 for details - any projects using prior ezbake 0.3.x versions as a dependency should be updated as soon as possible to avoid packaging failures in CI." Add Comment
Jira (PDB-1304) Trouble starting PuppetDB service
Title: Message Title Andreas Papst commented on PDB-1304 Re: Trouble starting PuppetDB service With installing Debian package puppetdb 2.3.3-1puppetlabs1 this problem is not experienced any more. thanks Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3895) EPP validator should error when specified template file does not exist
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-3895 EPP validator should error when specified template file does not exist Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3863) hiera('some::key', undef) returns empty string
Title: Message Title
Adrian Muraru commented on PUP-3863
Re: hiera('some::key', undef) returns empty string
This is still listed in 3.7.5 Changelog: https://docs.puppetlabs.com/puppet/latest/reference/release_notes.html#future-parser-fixes-and-updates make it confusing for users
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-1427) PR (1349): (maint) Add knobs to logbook config under test - mullr
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1427 PR (1349): (maint) Add knobs to logbook config under test - mullr Change By: Kenneth Barber Story Points: 0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3863) hiera('some::key', undef) returns empty string
Title: Message Title
Henrik Lindberg commented on PUP-3863
Re: hiera('some::key', undef) returns empty string
Ping Nicholas Fagerlund How about rewriting a bit of history and dropping the mention that this problem was fixed for 3.7.5 since that fix was broken? (See comment before this).
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-1437) PR (1355): (maint) Explain acceptance testing off the VPN - rbrw
Title: Message Title Kenneth Barber assigned an issue to Rob Browning Rob Browning Can you do the necessary with this automatically created ticket? I found it in the backlog. PuppetDB / PDB-1437 PR (1355): (maint) Explain acceptance testing off the VPN - rbrw Change By: Kenneth Barber Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1436) PR (1354): (MAINT) Build pe-puppetdb from this repo. - waynr
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1436 PR (1354): (MAINT) Build pe-puppetdb from this repo. - waynr Change By: Kenneth Barber Sprint: PuppetDB 2015-04-22 Story Points: 0 Scope Change Reason: Wayne is working on building 3.0 for PE, this PR is required for that work Scope Change Category: Adopted Fix Version/s: PDB 3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Googl
Jira (PUP-4422) Catalog fallback on failure
Title: Message Title Klavs Klavsen created an issue Puppet / PUP-4422 Catalog fallback on failure Issue Type: New Feature Assignee: Unassigned Created: 2015/04/16 5:48 AM Priority: Normal Reporter: Klavs Klavsen Currently, when I make a mistake (f.ex. add an apache vhost which uses SSL features but forget to enable ssl module), then the service dies.. and previously working vhosts stops working What I would think would be a great feature, would be for puppet to be able to revert to last known good catalog (configurable).. so if the agent simply saves last catalog that worked.. and on failure (if so configured - or perhaps only for failures on Service types) it tries to run last known good catalog instaed.. hoping the service then works.. That would lessen the impact of mistakes on production environment a great deal.. Add Comment
Jira (PUP-4423) Deprecation warning for non-string file modes is unclear
Title: Message Title Lee Lowder created an issue Puppet / PUP-4423 Deprecation warning for non-string file modes is unclear Issue Type: Improvement Affects Versions: PUP 3.7.4 Assignee: Unassigned Created: 2015/04/16 7:12 AM Labels: support customer Priority: Normal Reporter: Lee Lowder When a file doesn't use a string for the mode,the error given at run time is: Warning: Non-string values for the file mode property are deprecated. It must be a string, either a symbolic mode like 'o+w,a+r' or an octal representation like '0644' or '755'. (at /opt/puppet/lib/ruby/site_ruby/1.9.1/puppet/type/file/mode.rb:69:in `block (2 levels) in ')
Jira (PDB-1427) PR (1349): (maint) Add knobs to logbook config under test - mullr
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1427 PR (1349): (maint) Add knobs to logbook config under test - mullr Change By: Kenneth Barber Fix Version/s: PDB 3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4423) Deprecation warning for non-string file modes is unclear
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4423 Deprecation warning for non-string file modes is unclear Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4423) Deprecation warning for non-string file modes does not show file and line
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4423 Deprecation warning for non-string file modes does not show file and line Change By: Henrik Lindberg Summary: Deprecation warning for non-string file modes is unclear does not show file and line Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4368) Allow loading file_serving terminii from modules
Title: Message Title Daniel Dreier commented on PUP-4368 Re: Allow loading file_serving terminii from modules This would be very useful. This issue was linked from a discussion at https://github.com/puppetlabs/puppetlabs-aws/pull/128#issuecomment-93743358 and the [puppet-riak](https://github.com/basho-labs/puppet-riak) module would also benefit from a native way to download Basho's unpackaged patch updates. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1439) PR (1356): (maint) Bump to latest trapperkeeper/jetty9/kitchensink - kbarber
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1439 PR (1356): (maint) Bump to latest trapperkeeper/jetty9/kitchensink - kbarber Issue Type: Task Assignee: Unassigned Created: 2015/04/16 8:09 AM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Bump to latest trapperkeeper/jetty9/kitchensink Author: Ken Barber Company: Puppet Labs Inc. Github ID: kbarber Pull Request 1356 Discussion Pull Request 1356 File Diff Pull Request Description This bumps us to the latest revision of TK/jetty9 for the purposes of bumping the schema dependency. I've also upgraded to the latest kitchensink just for maint purposes mainly. Signed-off-by: Ke
Jira (PDB-1439) PR (1356): (maint) Bump to latest trapperkeeper/jetty9/kitchensink - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1439 PR (1356): (maint) Bump to latest trapperkeeper/jetty9/kitchensink - kbarber Change By: Kenneth Barber Sprint: PuppetDB 2015-04-22 Story Points: 0 Scope Change Reason: Bug with rolling up our schema bump to master, if we don't upgrade TK also Scope Change Category: Found Fix Version/s: PDB 3.0.0 Fix Version/s: PDB 2.3.x Issue Type: Task Bug Add Comment
Jira (PUP-4343) Add test(s) for the File resource links attribute
Title: Message Title
Kurt Wall commented on PUP-4343
Re: Add test(s) for the File resource links attribute
Broke Windows specs:. For example
1) Puppet::Type::File copying a file that is a link to a directory when the recurse attribute is false should copy the link itself if :links => manage
Failure/Error: expect(File).to be_symlink(copy)
expected `File.symlink?("C:/Windows/Temp/rspecrun20150415-1156-7lafti/copy20150415-1156-1h4iwin")` to return true, got false
# ./spec/integration/type/file_spec.rb:1617:in `block (4 levels) in '
# ./spec/integration/type/file_spec.rb:76:in `block (3 levels) in '
# ./lib/puppet/context.rb:64:in `override'
# ./lib/puppet.rb:223:in `override'
# ./spec/integration/type/file_spec.rb:75:in `block (2 levels) in '
Jira (PUP-4394) Regression: Webrick fails to start if the puppet user and group don't exist
Title: Message Title William Hopper commented on PUP-4394 Re: Regression: Webrick fails to start if the puppet user and group don't exist Josh Cooper if we're root and we check and find that the puppet user/group don't exist, is the idea to just error out more cleanly without actually trying to `chuser`? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1421) PR (1347): (maint) add upgrading from v3 document to stable branch - wkalt
Title: Message Title gepetto-bot commented on PDB-1421 Re: PR (1347): (maint) add upgrading from v3 document to stable branch - wkalt kbarber commented: I think my concern is around the message in that document, it concerns itself with people upgrading from v3 to v4 final, not experimental. Plus it also mentions version 3.0 things. I just think we need to be careful about the message we are sending here, I don't want people to look at the document thinking this is how they go from v3 to v4 experimental etc. Maybe the note you've made already about this not being about v4 experimental needs to be put in highlights, like we do for other notes or something? Whatever we do, we have to be absolutely clear . Otherwise I'm +1 on the concept. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4178) defined() function returns true for undef and empty string, and false for "main"
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-4178 defined() function returns true for undef and empty string, and false for "main" Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4421) Virtual resource collectors incorrectly collect exported resources from same node
Title: Message Title Fabien Wernli commented on PUP-4421 Re: Virtual resource collectors incorrectly collect exported resources from same node Negative Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1439) PR (1356): (maint) Bump to latest trapperkeeper/jetty9/kitchensink - kbarber
Title: Message Title gepetto-bot commented on PDB-1439 Re: PR (1356): (maint) Bump to latest trapperkeeper/jetty9/kitchensink - kbarber pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1040/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4424) Puppet Agent should pin to something besides puppet_for_the_win#master
Title: Message Title Michael Smith moved an issue Puppet / PUP-4424 Puppet Agent should pin to something besides puppet_for_the_win#master Change By: Michael Smith Workflow: Release Engineering Scrum Team Workflow Key: RE PUP -4424 Project: Release Engineering Puppet Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4424) Puppet Agent should pin to something besides puppet_for_the_win#master
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-4424 Puppet Agent should pin to something besides puppet_for_the_win#master Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4424) Puppet Agent should pin to something besides puppet_for_the_win#master
Title: Message Title Michael Smith updated an issue Puppet / PUP-4424 Puppet Agent should pin to something besides puppet_for_the_win#master Change By: Michael Smith Sprint: Client 2015-04-29 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4424) puppet-agent#stable should pin to something besides puppet_for_the_win#master
Title: Message Title Michael Smith updated an issue Puppet / PUP-4424 puppet-agent#stable should pin to something besides puppet_for_the_win#master Change By: Michael Smith Summary: Puppet Agent puppet-agent#stable should pin to something besides puppet_for_the_win#master Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4425) restore deprecated "respository" parameter in metadata.json and ref
Title: Message Title Chris Denneen created an issue Puppet / PUP-4425 restore deprecated "respository" parameter in metadata.json and ref Issue Type: Improvement Assignee: Unassigned Created: 2015/04/16 9:39 AM Labels: puppet gepetto metadata deprecation dependencies Priority: Normal Reporter: Chris Denneen When creating private modules you sometimes need to create dependencies on other private modules or sometimes other modules not on the forge (github, etc). In those cases to conform to module writing standards and give the ability to use an internal forge proxy or just module list with versions showing we would need the ability to refer to a repository and possibly even a ref. Currently repository is still an option but is marked as deprecated in Gepetto UI but still would only reference master branch. Add Comment
Jira (PUP-4426) group resource doesn't work on Windows when members is an array and noop is used
Title: Message Title
Lee Lowder created an issue
Puppet / PUP-4426
group resource doesn't work on Windows when members is an array and noop is used
Issue Type:
Bug
Affects Versions:
PUP 3.7.4
Assignee:
Unassigned
Created:
2015/04/16 9:55 AM
Labels:
customer support
Priority:
Normal
Reporter:
Lee Lowder
The following resource fails:
group { 'administrators':
ensure => present,
Jira (PUP-4308) puppet-agent 1.0.0 2015-04-01 Release
Title: Message Title Melissa Stone commented on PUP-4308 Re: puppet-agent 1.0.0 2015-04-01 Release Kenn Hussey we might still be waiting for docs. I'd check with Nicholas Fagerlund, but I think we still have a few days until docs are completely ready and this ticket is done. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1436) PR (1354): (MAINT) Build pe-puppetdb from this repo. - waynr
Title: Message Title gepetto-bot commented on PDB-1436 Re: PR (1354): (MAINT) Build pe-puppetdb from this repo. - waynr kbarber commented: @waynr what's the syntax to test this mate? ```lein with-profile pe ezbake build``` etc.? I just want to see if I can make it work end-to-end myself as a bit of a functional test, any other pointers would be useful. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4394) Regression: Webrick fails to start if the puppet user and group don't exist
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-4394 Regression: Webrick fails to start if the puppet user and group don't exist Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4390) Regression: Windows service provider fails to retrieve current state on 2003
Title: Message Title Ethan Brown commented on PUP-4390 Re: Regression: Windows service provider fails to retrieve current state on 2003 MSI builds for testing have been produced with the Windows on Demand job at http://jenkins-release.delivery.puppetlabs.net/view/Windows%20Builds/job/Windows%20On%20Demand/38/ http://jenkins-release.delivery.puppetlabs.net/view/Windows%20Builds/job/Windows%20On%20Demand/38/ARCH=x86,label=win-build/artifact/pkg/puppet-3.7.5-76-g89419d8.msi http://jenkins-release.delivery.puppetlabs.net/view/Windows%20Builds/job/Windows%20On%20Demand/ARCH=x64,label=win-build/lastSuccessfulBuild/artifact/pkg/puppet-3.7.5-76-g89419d8-x64.msi Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1124) PuppetDB high CPU usage
Title: Message Title Wyatt Alt commented on PDB-1124 Re: PuppetDB high CPU usage @Anton Fomenko can you change your last_run fact to include milliseconds? We have a known race condition (that the periodic GC is intended to clean up) where an orphan is created when two nodes have the same fact_value for the same fact, and update the value at the exact same time. Under normal conditions this is rare, but I think in your case it's happening more runs than not, since you have about 109 runs per minute that need to fit into 60 unique timestamps. If your fact was accurate down to the millisecond, I think this would happen infrequently enough that the GC could handle it easily. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1439) PR (1356): (maint) Bump to latest trapperkeeper/jetty9/kitchensink - kbarber
Title: Message Title gepetto-bot commented on PDB-1439 Re: PR (1356): (maint) Bump to latest trapperkeeper/jetty9/kitchensink - kbarber Pull request (maint) Bump to latest trapperkeeper/jetty9/kitchensink has been closed. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3613) Add a parameter to the exec resource to support running commands in software collections without always using "scl enable"
Title: Message Title Tim Skirvin commented on PUP-3613 Re: Add a parameter to the exec resource to support running commands in software collections without always using "scl enable" It is important for those of us developing puppet modules on RHEL and other RedHat systems to be able to use the standard ruby tool suite for our work - e.g. rspec-puppet, beaker, etc. But RedHat is still using ruby 1.8.7 by default (and probably will be for years to come). This new feature would improve matters dramatically for us poor RHEL users. Note that I am currently writing a little 'ruby193::gem' definition just to work around this problem locally. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-955) Reports incorrect hardware/architecture facts for 32-bit process on 64-bit OS, and 32-bit OS on 64-bit hardware
Title: Message Title
Eric Thompson updated an issue
Facter / FACT-955
Reports incorrect hardware/architecture facts for 32-bit process on 64-bit OS, and 32-bit OS on 64-bit hardware
Change By:
Eric Thompson
The hardware fact (and the architecture fact, which is based off the hardware fact) was mis-implemented in native facter's re-implementation.The original logic if the processor model came back as {{PROCESSOR_ARCHITECTURE_AMD64}} was to check whether we were running a 32-bit OS on a 64-bit processor, and if so return a 32-bit architecture (the fact corresponds to OS, not physical hardware).The re-implementation instead was verifying a 32-bit process running under 64-bit OS. risk: highprobability: medium (use of hw/arch facts)severity: high (can't trust facts, custom facts workaround?)test layer:
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-958) Acceptance test covering facts based on platform
Title: Message Title Eric Thompson updated an issue Facter / FACT-958 Acceptance test covering facts based on platform Change By: Eric Thompson Component/s: QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-955) Reports incorrect hardware/architecture facts for 32-bit process on 64-bit OS, and 32-bit OS on 64-bit hardware
Title: Message Title
Eric Thompson updated an issue
Facter / FACT-955
Reports incorrect hardware/architecture facts for 32-bit process on 64-bit OS, and 32-bit OS on 64-bit hardware
Change By:
Eric Thompson
The hardware fact (and the architecture fact, which is based off the hardware fact) was mis-implemented in native facter's re-implementation.The original logic if the processor model came back as {{PROCESSOR_ARCHITECTURE_AMD64}} was to check whether we were running a 32-bit OS on a 64-bit processor, and if so return a 32-bit architecture (the fact corresponds to OS, not physical hardware).The re-implementation instead was verifying a 32-bit process running under 64-bit OS.risk: highprobability: medium (use of hw/arch facts)severity: high (can't trust facts, custom facts workaround?)test layer: acceptance (see fact-958)
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-958) Acceptance test covering facts based on platform
Title: Message Title Eric Thompson updated an issue Facter / FACT-958 Acceptance test covering facts based on platform Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-955) Reports incorrect hardware/architecture facts for 32-bit process on 64-bit OS, and 32-bit OS on 64-bit hardware
Title: Message Title Eric Thompson updated an issue Facter / FACT-955 Reports incorrect hardware/architecture facts for 32-bit process on 64-bit OS, and 32-bit OS on 64-bit hardware Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-955) Reports incorrect hardware/architecture facts for 32-bit process on 64-bit OS, and 32-bit OS on 64-bit hardware
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Facter / FACT-955 Reports incorrect hardware/architecture facts for 32-bit process on 64-bit OS, and 32-bit OS on 64-bit hardware Change By: Eric Thompson Assignee: QA Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-952) Update or remove man page
Title: Message Title William Hopper assigned an issue to William Hopper Facter / FACT-952 Update or remove man page Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-955) Reports incorrect hardware/architecture facts for 32-bit process on 64-bit OS, and 32-bit OS on 64-bit hardware
Title: Message Title Eric Thompson commented on FACT-955 Re: Reports incorrect hardware/architecture facts for 32-bit process on 64-bit OS, and 32-bit OS on 64-bit hardware validated on windows2012r2-rubyx64 running facter 32bit at SHA: 237b3ab7bf2485eb0adcafc726a213792e70d0d5 PS C:\facter-2.4.3-1055-g237b3ab-x86> .\bin\facter.exe architecture 2015-04-16 12:07:47.592322 WARN puppetlabs.facter - could not locate a ruby library: custom facts will not be resolved. x64 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received
Jira (PUP-4427) Rake Spec tests fail due to missing dependencies
Title: Message Title Bryan Stopp created an issue Puppet / PUP-4427 Rake Spec tests fail due to missing dependencies Issue Type: Bug Affects Versions: PUP 4.0.0 Assignee: Kylo Ginsberg Components: Platform, Test Infrastructure, Types and Providers Created: 2015/04/16 12:27 PM Environment: Vagrant/VirtualBox CentOS-64 virtual machine; https://vagrantcloud.com/puppetlabs/boxes/centos-7.0-64-puppet Priority: Normal Reporter: Bryan Stopp When running rake/rspec tests, they fail due to an inability to find the plist gem. This only happens on 4.0.0. A good test case is the puppetlabs-tomcat module. I was able to take a baseline puppet VM (same one specified in my environment); get all of the gems installed; when i ran: rake spec I got this error: Puppet::Error: Could not autoload puppet/type/user: Could not autoload puppet/provider/user/directoryservice: cannot load such file – pli
Jira (PUP-4090) Zypper provider doesn't work correctly on SLES 10.4 with install_options set
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4090 Zypper provider doesn't work correctly on SLES 10.4 with install_options set Change By: Eric Thompson Assignee: QA Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-952) Update or remove man page
Title: Message Title William Hopper commented on FACT-952 Re: Update or remove man page We ran into a packaging issue in CI: CMake Error at cmake_install.cmake:44 (file): file INSTALL cannot find "/tmp/buildd/facter-2.4.3.1055/man/man8/facter.8". This is probably because the man/ directory needs to be included in the tarball. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4420) Executable external facts broken in 4.0.0: not executable on agent
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4420 Executable external facts broken in 4.0.0: not executable on agent Change By: Steve Barlow Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4090) Zypper provider doesn't work correctly on SLES 10.4 with install_options set
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-4090
Zypper provider doesn't work correctly on SLES 10.4 with install_options set
Change By:
Eric Thompson
h2. OverviewAttempting to run puppet with {{install_options}} set to disable GPG checks for package installation results in an error from the {{zypper}} command that the {{--name}} and {--no-gpg-checks}} options are not recognised.With the stock puppet zypper provider, its impossible to install packages with option set.h2. Test caseThe following Puppet code was used to attempt to bypass the {{zypper}} GPG signing requirements:{noformat}package { 'REDACTED':, provider => 'zypper', name => REDACTED, ensure => $user_supplied_variable, install_options => [ '--no-gpg-checks' ], }{noformat}Running this code resulted in an error from the {{zypper}} command being returned via a failed Puppet execution:{noformat}# /opt/puppet/bin/puppet agent --testInfo: Retrieving pluginfactsInfo: Retrieving pluginInfo: Loading factsInfo: Caching catalog for REDACTEDInfo: Applying configuration version '1425621321'Error: Could not update: Execution of '/usr/bin/zypper --terse install --auto-agree-with-licenses --no-confirm --name --no-gpg-checks REDACTED(was package name)' returned 2: Unknown option --nameUnknown option --no-gpg-checksWrapped exception:Execution of '/usr/bin/zypper --terse install --auto-agree-with-licenses --no-confirm --name --no-gpg-checks REDACTED' returned 2: Unknown option --nameUnknown option --no-gpg-checksError: /Stage[main]/REDACTED/Package[REDACTED]/ensure: change from absent to latest failed: Could not update: Execution of '/usr/bin/zypper --terse install --auto-agree-with-licenses --no-confirm --name --no-gpg-checks REDACTED' returned 2: Unknown option --nameUnknown option --no-gpg-checksNotice: Finished catalog run in 0.97 seconds{noformat}h2. Experimental workaroundThe {{zypper}} command in this version of SUSE expects the parameters to be ordered in a different way to that which is coded into the {{zypper.rb}} provider. As an experiment, I was able to rearrange things so that the parameters were fed in the order that the program accepts:* --no-gpg-checks must come before the action (install)* --name doesn't seem to be recognised at any position and had to be removed* package name should directly follow the action, eg {{install foobar}}h2. Long term fixDue to the way {{zypper}} is invoked, perhaps we may need two arguments to be passed to different parts of the command to get it to work as advertised, eg:{noformat}zypper $default_options $command_options $subcommand $subcommand_options $package_name{noformat}Or perhaps the invocation of the zypper command has changed between SUSE versions? risk: low probability: low: zypper install options on sles10severity: low (workarounds exist)test layer: unit
Jira (PUP-4090) Zypper provider doesn't work correctly on SLES 10.4 with install_options set
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4090 Zypper provider doesn't work correctly on SLES 10.4 with install_options set Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1628) Add mount provider for AIX
Title: Message Title Eric Thompson assigned an issue to Kurt Wall Puppet / PUP-1628 Add mount provider for AIX Change By: Eric Thompson Assignee: QA Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1628) Add mount provider for AIX
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1628 Add mount provider for AIX Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1628) Add mount provider for AIX
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1628 Add mount provider for AIX Change By: Eric Thompson Puppet does not provides a correct provider for the mount type on AIX.A new provider must be created.Mountpoints in AIX are managed by the commands: crfs, lsfs, rmfs, chfs (http://publib.boulder.ibm.com/infocenter/aix/v6r1/index.jsp?topic=/com.ibm.aix.cmds/doc/aixcmds1/crfs.htm). For nfs mountpoints the commands mknfsmnt, chnfsmnt, rmnfsmnt and chnfsmnt are provided, but they can partially be managed with former commands.The commands update the file /etc/filesystems that has following syntax:/usr: dev = /dev/hd2 vfs = jfs2 log = /dev/hd8 mount = automatic check = false type= bootfs vol = /usr free= false/var: dev = /dev/hd9var vfs = jfs2 log = /dev/hd8 mount = automatic check = false type= bootfs vol = /var free= false**IMPORTANT**: crfs (create) and rmfs (remove), if it is a local filesystem, will create and format (using jfs/jfs2) the needed Logical Volume, or directly remove the Logical Volume losing data. Two approaches: 1. Use command line tools and operate as expected by AIX commands: Operate on the LV. In that case type should be extended with new parameters (Volume Group, LV name, size...) 2. Modify directly /etc/filesystems files, and manage the Logical Volumes using a LVM type (as in other OS) risk: medium (manual validate) probability: medium (aix)severity: medium (can't manage aix mounts)test layer (no acceptance setup for aix) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (FACT-610) Change windows facter to return same hardware model as linux
Title: Message Title Michael Smith assigned an issue to QA Facter / FACT-610 Change windows facter to return same hardware model as linux Change By: Michael Smith Status: Ready for CI Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-956) Update puppet-agent#master to build facter#master, remove cfacter
Title: Message Title Michael Smith commented on FACT-956 Re: Update puppet-agent#master to build facter#master, remove cfacter Note that puppetversion should be fixed first or we'll likely end up breaking some modules. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4391) tag collecting is broken in 3.7
Title: Message Title Neil Prockter commented on PUP-4391 Re: tag collecting is broken in 3.7 Thanks, I prefixed my tags which solved the immediate issue and lets me upgrade puppet to 3.7 in a way I've just scoped the tags. My user/groups setup (which is what I was really working with) does not really give me what I want anyway so I'll give it more work and get rid of tag collection altogether I now see they are not stable enough to be realied upon. I think we all need to take a good look at tags as the current implementation and lack of agreed standard is a recipe for tags getting so widespread they cease to be of use for collecting and for strings == should mean ==, never contains. overloading == to be contains when the RHS is say IP and LHS is IP range makes som sense, but for strings is wrong How do I flag that up? Thanks, Neil Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4428) The 'err' logging function cannot be called as a statement
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-4428 The 'err' logging function cannot be called as a statement Issue Type: Bug Assignee: Unassigned Created: 2015/04/16 2:31 PM Fix Versions: PUP 4.1.0, PUP 3.8.1 Priority: Normal Reporter: Henrik Lindberg In the language specification: https://github.com/puppetlabs/puppet-specifications/blob/master/language/expressions.md#function-calls under the "statement style" subhead, there's a list like: # logging debug info
Jira (PUP-4429) Puppet command line tools accept partial matches for flags without altering behavior
Title: Message Title Charlie Sharpsteen created an issue Puppet / PUP-4429 Puppet command line tools accept partial matches for flags without altering behavior Issue Type: Bug Affects Versions: PUP 3.7.5, PUP 4.0.0 Assignee: Kylo Ginsberg Components: Client Created: 2015/04/16 2:35 PM Labels: redmine Priority: Normal Reporter: Charlie Sharpsteen The Puppet command line tools will accept partial matches for flags, but do not use the values provided. This causes unexpected behavior when a command accepts a flag or type but doesn't actually act upon it. Reproduction Case Install Puppet 3.7.x or 4.0.x. Execute config print commands with flags that affect settings, such as puppet agent - no-daemonize --configprint daemonize with various truncations of the -no-daemonize flag.
Jira (PUP-4421) Virtual resource collectors incorrectly collect exported resources from same node
Title: Message Title Henrik Lindberg commented on PUP-4421 Re: Virtual resource collectors incorrectly collect exported resources from same node Exported resource are in fact also virtual. What makes you think this is incorrect? Is this a regression you found? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1440) implement sum, avg, min, and max
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1440 implement sum, avg, min, and max Issue Type: New Feature Assignee: Unassigned Created: 2015/04/16 2:51 PM Priority: Normal Reporter: Wyatt Alt This is dependent on PDB-1181, but should be straightfoward when that work is done. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1436) PR (1354): (MAINT) Build pe-puppetdb from this repo. - waynr
Title: Message Title gepetto-bot commented on PDB-1436 Re: PR (1354): (MAINT) Build pe-puppetdb from this repo. - waynr waynr commented: @kbarber strange, I didn't see your comment show up in my inbox...gotta muck around with email filters some more I suppose. To test this, try `lein with-profile ezbake,pe ezbake build`. We could probably eliminate the need for the `ezbake` profile but I have been thinking of the `pe` profile as building on top of that. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3641) Changes to Puppet URL structure
Title: Message Title
Ruth Linehan updated an issue
Puppet / PUP-3641
Changes to Puppet URL structure
Change By:
Ruth Linehan
This is a roll-up ticket to capture the outcome of the scoping effort from PUP-3519. The t ickets tickets linked into this story represent the proposed changes to the URL structures. Updated Description:The result of this ticket is that for Puppet 4, we've split apart the Puppet master's API and the CA API. The master's API is now at {{/puppet/v3}} and the CA's API is now under {{/puppet-ca/v1}}. These version numbers will increasePuppet master's urls now look like {{/puppet/v3//?environment=}} and the CA urls look like {{/puppet-ca/v1//?environment=}}. All urls have a
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3645) allow configurable URL prefix for all routes
Title: Message Title
Ruth Linehan updated an issue
Puppet / PUP-3645
allow configurable URL prefix for all routes
Change By:
Ruth Linehan
Both the agent and the master should support a setting that configures a url prefix, e.g. "/puppet", that the web app could be mounted at. All the requests generated by the agent should honor this prefix. This will allow us to mount the Puppet HTTP endpoints in a namespaced URL space alongside other apps running on the same webserver. UPDATE: based on discussion (some of which is in PUP-3526), we decided not to allow these prefixes to be configurable. They are hardcoded as {{/puppet}} for the puppet master API and {{/puppet-ca}} for the CA API.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-1441) support nested extracts
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1441 support nested extracts Issue Type: New Feature Assignee: Unassigned Created: 2015/04/16 3:00 PM Priority: Normal Reporter: Wyatt Alt if we had nested extracts, we could replicate the existing functionality of aggregate-event-counts by using the group-by operator with a query like this: curl -X GET http://localhost:8080/v4/events -d 'query=["extract", [["function","count"],"status"], ["extract", [["function","count"],"status", "containing_class"], ["~","certname",".*], ["group_by", "status", "containing_class"]], ["group_by", "status"]] which would translate into something like: select status,count(1) from (select status,containing_class,count(1) from resource_events group by status,containing_class) ec group by status this would be more or less equalivalent to an aggregate-event-counts call with summarize_by=containing_class. Add Comment
Jira (PUP-3641) Changes to Puppet URL structure
Title: Message Title
Ruth Linehan updated an issue
Puppet / PUP-3641
Changes to Puppet URL structure
Change By:
Ruth Linehan
This is a roll-up ticket to capture the outcome of the scoping effort from PUP-3519. The tickets linked into this story represent the proposed changes to the URL structures.Updated Description:The result of this ticket is that for Puppet 4, we've split apart the Puppet master's API and the CA API. The master's API is now at {{/puppet/v3}} and the CA's API is now under {{/puppet-ca/v1}}. These version numbers will increasePuppet All non /puppet/v3 and /puppet-ca/v1 endpoints have been removed. The {{/puppet}} and {{/puppet-ca}} prefixes are hardcoded, not configurable. The environment name is no longer part of the path but is instead a query param.Thus, for Puppet 4 the Puppet master's urls now look like {{/puppet/v3//?environment=}} and the CA urls look like {{/puppet-ca/v1//?environment=}}. All urls have a For example, the Puppet 3 url {{http://localhost:8140/production/node/foo}} is now (in Puppet 4) {{http://localhost:8140/puppet/v3/node/foo?environment=production}}.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com
Jira (PUP-4428) The 'err' logging function cannot be called as a statement
Title: Message Title Nicholas Fagerlund commented on PUP-4428 Re: The 'err' logging function cannot be called as a statement This sounds legit to me. I'd forgotten those other log levels even existed. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-697) If NetworkManager is installed but not used facter throws a warning.
Title: Message Title
Kurt Wall commented on FACT-697
Re: If NetworkManager is installed but not used facter throws a warning.
Verified in pl-facter-b1c85e7b2fede74091875f3c2c38ccc55f94835e-el-7-x6_64. facter does not throw a warning when a non-running NetworkManager is installed:
# nmcli d
Error: NetworkManager is not running.
# facter | head -n10 2>&1
disks => {
fd0 => {
size => "4.00 KiB",
size_bytes => 4096
},
sda => {
model => "Virtu
Jira (PDB-1442) consider changing aggregate-event-counts and event-counts to PE-only
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1442 consider changing aggregate-event-counts and event-counts to PE-only Issue Type: New Feature Assignee: Unassigned Created: 2015/04/16 3:11 PM Priority: Normal Reporter: Wyatt Alt Once we have group-by (PDB-1181) and nested extracts (PDB-1441) the event-counts and aggregate-event-counts will not provide much utility above what is available through the events endpoint. We should consider moving the event-counts and aggregate-event-counts endpoint to the PE repo, and instructing FOSS users to just use group-by. If the various query parameters associated with event-counts and aggregate-event-counts are not important to the PE console, or can be expressed through regular query syntax, we should consider dropping the endpoints all together. Add Comment
Jira (FACT-697) If NetworkManager is installed but not used facter throws a warning.
Title: Message Title Kurt Wall updated an issue Facter / FACT-697 If NetworkManager is installed but not used facter throws a warning. Change By: Kurt Wall QA Contact: Kurt Wall Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-697) If NetworkManager is installed but not used facter throws a warning.
Title: Message Title Kurt Wall updated an issue Facter / FACT-697 If NetworkManager is installed but not used facter throws a warning. Change By: Kurt Wall QA Contact: Eric Thompson Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-697) If NetworkManager is installed but not used facter throws a warning.
Title: Message Title Kurt Wall assigned an issue to Unassigned Facter / FACT-697 If NetworkManager is installed but not used facter throws a warning. Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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 Kurt Wall assigned an issue to Kurt Wall Facter / FACT-610 Change windows facter to return same hardware model as linux Change By: Kurt Wall Assignee: QA Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4391) tag collecting is broken in 3.7
Title: Message Title Henrik Lindberg commented on PUP-4391 Re: tag collecting is broken in 3.7 There is really no need to flag the issue that tags stands on loose ground - we know that already. What we are planning on doing, now that "future parser" is released, is to start working on the compiler and catalog - we have an Epic with the project name "Biff the Catalog Builder" which ultimately also is about tags (but much more before we get to that) - as we are planning on changing the catalog to allow restating / merging resources the current way tags are assigned will be even more strange and needs to change (not to mention that they bloat catalogs with lots of redundant and quite useless information). There will be some time before this is done though... I am going to close this ticket with a "Won't fix". I am glad you found a solution that works for you for now. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4343) Add test(s) for the File resource links attribute
Title: Message Title Eric Thompson commented on PUP-4343 Re: Add test(s) for the File resource links attribute did the second PR clear CI? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1180) Status: (query) Ensure aggregated functionality is designed well in detail
Title: Message Title Wyatt Alt commented on PDB-1180 Re: Status: (query) Ensure aggregated functionality is designed well in detail I've created a draft for more general distribution here: https://docs.google.com/a/puppetlabs.com/document/d/1cgSE8DVne_H2iDLd4cLHso0eZDUc6oyu2N2Ch-pt9uQ/edit# Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4426) group resource doesn't work on Windows when members is an array and noop is used
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-4426 group resource doesn't work on Windows when members is an array and noop is used Change By: Owen Rodabaugh CS Priority: Needs Priority Major Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1421) PR (1347): (maint) add upgrading from v3 document to stable branch - wkalt
Title: Message Title gepetto-bot commented on PDB-1421 Re: PR (1347): (maint) add upgrading from v3 document to stable branch - wkalt wkalt commented: I added more emphasis on the fact that these changes don't all relate to released code. I left the 3.0 stuff in there though because I think some of it's pretty important and is set in stone, like dashes->underscores. If there are specific things we want to omit or qualify I'm open to it, but nothing pops out at me. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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
Kurt Wall commented on FACT-610
Re: Change windows facter to return same hardware model as linux
Verified in master at SHA=NN. Output format matches Linux:
C:\facter-2.4.3-1057-g40f60df-x86\bin> .\facter hardwaremodel os
2015-04-16 15:32:07.756875 WARN puppetlabs.facter - could not locate a ruby library: custom facts will not be resolved.
hardwaremodel => x86_64
os => {
architecture => "x64",
family => "windows",
hardware => "x86_64",
name => "windows",
release => {
Jira (FACT-610) Change windows facter to return same hardware model as linux
Title: Message Title Kurt Wall updated an issue Facter / FACT-610 Change windows facter to return same hardware model as linux Change By: Kurt Wall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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 Kurt Wall updated an issue Facter / FACT-610 Change windows facter to return same hardware model as linux Change By: Kurt Wall QA Contact: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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 Kurt Wall assigned an issue to Unassigned Facter / FACT-610 Change windows facter to return same hardware model as linux Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4390) Regression: Windows service provider fails to retrieve current state on 2003
Title: Message Title Ryan Gard updated an issue Puppet / PUP-4390 Regression: Windows service provider fails to retrieve current state on 2003 Change By: Ryan Gard QA Contact: Ryan Gard Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1419) PR (176): Enable the module to manage entries in $confdir/config.ini - buzzdeee
Title: Message Title gepetto-bot commented on PDB-1419 Re: PR (176): Enable the module to manage entries in $confdir/config.ini - buzzdeee wkalt commented: this looks good to me Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4343) Add test(s) for the File resource links attribute
Title: Message Title Kurt Wall commented on PUP-4343 Re: Add test(s) for the File resource links attribute Finally, yes![1] [1] This comment made with wasavi. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4390) Regression: Windows service provider fails to retrieve current state on 2003
Title: Message Title Ethan Brown commented on PUP-4390 Re: Regression: Windows service provider fails to retrieve current state on 2003 With the current AIO pipeline, it's not really possible to produce an AIO / Puppet 4 MSI from my fork for testing purposes. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4404) Spec tests on Windows expect environment setup
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-4404 Spec tests on Windows expect environment setup Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1421) PR (1347): (maint) add upgrading from v3 document to stable branch - wkalt
Title: Message Title gepetto-bot commented on PDB-1421 Re: PR (1347): (maint) add upgrading from v3 document to stable branch - wkalt pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1041/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4044) AIO acceptance tests copies multiple versions of repo configs to the SUT
Title: Message Title Eric Thompson assigned an issue to Josh Cooper Puppet / PUP-4044 AIO acceptance tests copies multiple versions of repo configs to the SUT Change By: Eric Thompson Assignee: Eric Thompson Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4044) AIO acceptance tests copies multiple versions of repo configs to the SUT
Title: Message Title Eric Thompson commented on PUP-4044 Re: AIO acceptance tests copies multiple versions of repo configs to the SUT Josh Cooper new PR against stable. it also removed the spurious curling of the rpm files and installs them directly... tested it against packages and aio method on many el platforms Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4359) puppetversion fact is missing
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-4359 puppetversion fact is missing Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
