Jira (FACT-824) Reduce calls to 'ip link show' in Facter::Util::IP
Title: Message Title Kurt Wall assigned an issue to Unassigned Facter / FACT-824 Reduce calls to 'ip link show' in Facter::Util::IP Change By: Kurt Wall 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 (PDB-1426) PR (1348): Remove Fedora 19 from build targets - melissa
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1426 PR (1348): Remove Fedora 19 from build targets - melissa Issue Type: Task Assignee: Unassigned Created: 2015/04/13 11:39 AM Labels: github Priority: Normal Reporter: gepetto-bot Remove Fedora 19 from build targets Author: Melissa Company: Github ID: melissa Pull Request 1348 Discussion Pull Request 1348 File Diff Pull Request Description Fedora 19 went EOL on 2015-01-06. We should not longer be providing packages for this platform. (webhooks-id: 1b3dd9d2e1549254c512067c6749410c)
Jira (PDB-1427) PR (1349): (maint) Add knobs to logbook config under test - mullr
Title: Message Title gepetto-bot commented on PDB-1427 Re: PR (1349): (maint) Add knobs to logbook config under test - mullr pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1033/ 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-4233) Create node configs for puppet-passenger AIO acceptance tests
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4233 Create node configs for puppet-passenger AIO acceptance tests Change By: Steve Barlow Flagged: Impediment 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-4235) Create rake task for puppet-passenger AIO acceptance tests
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4235 Create rake task for puppet-passenger AIO acceptance tests Change By: Steve Barlow Flagged: Impediment 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-4234) Create pre-suites for puppet-passenger AIO acceptance tests
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4234 Create pre-suites for puppet-passenger AIO acceptance tests Change By: Steve Barlow Flagged: Impediment 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-585) Run spec tests for opened PR on Windows
Title: Message Title Michael Smith assigned an issue to Unassigned Puppet / PUP-585 Run spec tests for opened PR on Windows Change By: Michael Smith Assignee: MichaelSmith 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-585) Run spec tests for opened PR on Windows
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-585 Run spec tests for opened PR on Windows Change By: Michael Smith Assignee: MichaelSmith 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-585) Run spec tests for opened PR on Windows
Title: Message Title Michael Smith commented on PUP-585 Re: Run spec tests for opened PR on Windows Is https://github.com/puppetlabs/puppet/pull/3813 an acceptable solution to this ticket? 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-1246) Add V3 API deprecation message
Title: Message Title Michelle Johansen commented on PDB-1246 Re: Add V3 API deprecation message Ping Jason Cowley and Nathan Rawlins 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-1246) Add V3 API deprecation message
Title: Message Title Jason Cowley commented on PDB-1246 Re: Add V3 API deprecation message Thanks Moses Mendoza (and Michelle Johansen for the ping). Sounds like the removal of the V3 API was necessary. Good to have the context behind that decision. 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-1246) Add V3 API deprecation message
Title: Message Title Moses Mendoza commented on PDB-1246 Re: Add V3 API deprecation message Given the high cost and technical difficulty of maintaining both APIs (considering their dramatic divergence in behavior) the decision was made to retire the v3 api and focus on the v4 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 (FACT-951) Facter fails to run on Solaris due to implicit dependency of Boost.Log on Boost.Chrono
Title: Message Title Michael Smith assigned an issue to QA Facter / FACT-951 Facter fails to run on Solaris due to implicit dependency of Boost.Log on Boost.Chrono Change By: Michael Smith Status: Readyfor 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-947) Use GetUserProfileDirectory on Windows for more robust home directory lookup
Title: Message Title Michael Smith assigned an issue to QA Facter / FACT-947 Use GetUserProfileDirectory on Windows for more robust home directory lookup Change By: Michael Smith Status: Readyfor 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 (PDB-1426) PR (1348): Remove Fedora 19 from build targets - melissa
Title: Message Title gepetto-bot commented on PDB-1426 Re: PR (1348): Remove Fedora 19 from build targets - melissa 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/1032/ 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-926) Provide meaningful operating system fact values for Arista EOS
Title: Message Title Kurt Wall assigned an issue to Unassigned Facter / FACT-926 Provide meaningful operating system fact values for Arista EOS Change By: Kurt Wall Assignee: StanDuffy 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 gepetto-bot created an issue PuppetDB / PDB-1427 PR (1349): (maint) Add knobs to logbook config under test - mullr Issue Type: Task Assignee: Unassigned Created: 2015/04/13 12:01 PM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Add knobs to logbook config under test Author: Russell Mull Company: Github ID: mullr Pull Request 1349 Discussion Pull Request 1349 File Diff Pull Request Description (webhooks-id: b2afcc3023b8d9a65d5346ca21f3dc46)
Jira (FACT-951) Facter fails to run on Solaris due to implicit dependency of Boost.Log on Boost.Chrono
Title: Message Title Eric Thompson commented on FACT-951 Re: Facter fails to run on Solaris due to implicit dependency of Boost.Log on Boost.Chrono perhaps the title and description of this ticket needs updating? 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-4403) k5login should support setting selinux context and owner attributes
Title: Message Title Pat Riehecky created an issue Puppet / PUP-4403 k5login should support setting selinux context and owner attributes Issue Type: New Feature Affects Versions: PUP 3.7.5 Assignee: Kylo Ginsberg Components: Types and Providers Created: 2015/04/13 1:57 PM Labels: trivial Priority: Normal Reporter: Pat Riehecky Original Estimate: 3 hours Remaining Estimate: 3 hours When creating the .k5login
Jira (PUP-2080) Support functions written in pp
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2080 Support functions written in pp Change By: Henrik Lindberg Sprint: Week2014-4-02to2014-4-09,Week2014-4-09to2014-4-16 ,Language2015-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-2315) function call error message about mis-matched arguments is hard to understand
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2315 function call error message about mis-matched arguments is hard to understand Change By: Henrik Lindberg Sprint: Language2015-03-04,Language2015-03-18 ,Language2015-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-4398) Splat unfolding not supported in method call syntax
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4398 Splat unfolding not supported in method call syntax Change By: Henrik Lindberg Sprint: Language2015-04-29 Story Points: 1 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-951) Facter fails to run on Solaris due to implicit dependency of Boost.Log on Boost.Chrono
Title: Message Title Michael Smith updated an issue Facter / FACT-951 Facter fails to run on Solaris due to implicit dependency of Boost.Log on Boost.Chrono Change By: Michael Smith Boost.LoghasanimplicitdependencyonBoost.Chrono.ThisresultsinBoost.Chronobeingbuiltonallplatforms,andifFacterstaticallylinksinBoostorhasBoostontheLD_LIBRARY_PATH,alldependenciesareresolved.NeitherwasthecaseonSolaris,whichexposedtheimplicitdependencyonBoost.Chrono-whenweexplicitlylinkdynamiclibraries,libfacterhard-codestheirlocation,butsincelibboost_chronowasn'texplicitlylinkeditcouldn'tresolveitslocation.Toavoidthesekindsofissues,addanexplicitdependencyonchronosothestaticpathissetupcorrectly. 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: WilliamHopper 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-1428) Failure to contact updates.puppetlabs.com is logged at INFO
Title: Message Title
Deepak Giridharagopal created an issue
PuppetDB / PDB-1428
Failure to contact updates.puppetlabs.com is logged at INFO
Issue Type:
Bug
Affects Versions:
PDB 2.3.2
Assignee:
Unassigned
Created:
2015/04/13 2:38 PM
Fix Versions:
PDB 2.3.x
Priority:
Normal
Reporter:
Deepak Giridharagopal
Subject says it all. This is bad because what should be a harmless background process (the dujour ping-back) now looks weird and scary at INFO level.
The problem is due to an updated version of Apache's HTTP lib getting folded into PuppetDB. This newer version now logs things at INFO when there are connection problems.
Here is a sample of the output:
2015-04-13 15:22:41,339 INFO [o.a.h.i.c.DefaultHttpClient] I/O exception (java.net.NoRouteToHostException) caught when connecting to {}-http://updates.puppetlabs.com: No route to host 2015-04-13 15:22:41,339 INFO [o.a.h.i.c.DefaultHttpClient] Retrying connect to {}-http://updates.puppetlabs.com 2015-04-13 15:22:41,340 INFO [o.a.h.i.c.DefaultHttpClient] I/O exception (java.net.NoRouteToHostException) caught when connecting to {}-http://updates.puppetlabs.com: No route to host 2015-04-13 15:22:41,340 INFO [o.a.h.i.c.DefaultHttpClient] Retrying connect to
Jira (PUP-3895) EPP validator should error when specified template file does not exist
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3895 EPP validator should error when specified template file does not exist Change By: Henrik Lindberg Sprint: Language2015-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-2630) Server-set global variables like $::environment get overwritten by client facts
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2630 Server-set global variables like $::environment get overwritten by client facts Change By: Henrik Lindberg Sprint: Language2015-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-2862) Validate that default value expression for param does not define variable
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-2862 Validate that default value _expression_ for param does not define variable Change By: Henrik Lindberg Sprint: Language2015-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-3134) Decide on specification of Puppet Regexp
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3134 Decide on specification of Puppet Regexp Moving this from 4.1.0 to 4.x as this is not ready for engineering. Change By: Henrik Lindberg Fix Version/s: PUP4.1.0 Fix Version/s: PUP4.x 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-3146) Add support for provider specific attributes
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3146 Add support for provider specific attributes Because this is a cross-cutting concern, the fix version was changed from 4.1.0 to 4.x and the estimate of 5 points was removed. The entire feature will require a lot more work than just storing fully qualified names in the catalog. This should be an epic and coordinated across components/teams. Change By: Henrik Lindberg Story Points: 5 Fix Version/s: PUP4.1.0 Fix Version/s: PUP4.x 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
Jira (PDB-1426) PR (1348): Remove Fedora 19 from build targets - melissa
Title: Message Title gepetto-bot commented on PDB-1426 Re: PR (1348): Remove Fedora 19 from build targets - melissa Pull request Remove Fedora 19 from build targets 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 (FACT-951) Facter fails to run on Solaris due to implicit dependency of Boost.Log on Boost.Chrono
Title: Message Title Michael Smith commented on FACT-951 Re: Facter fails to run on Solaris due to implicit dependency of Boost.Log on Boost.Chrono Updated the description. The dependency didn't prevent building, but it caused runtime library resolution on Solaris - given the way cfacter-build works - because libboost_chrono couldn't be found. To resolve that I added the dependency on Boost.Chrono in the Facter project, which means we should explicitly build it everywhere we build boost. 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-2176) 4x function API for puppet function should require namespaced functions
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-2176
4x function API for puppet function should require namespaced functions
Change By:
Henrik Lindberg
TheabilitytowritefunctionsinthePuppetProgrammingLanguageisanewfeatureslatedforPuppet4.1.0.Thecurrentimplementationallowssuchfunctionstobeplacedintheglobalnamespace.Thissupportalsomeansthatfunctionsplacedunder{code}moduleroot/functions{code}areconsideredglobal,andfunctionsinthemodule'snamespacemustbeplacedunder:{code}moduleroot/functions/modulename{code}Whenreviewingthisitwasdecidedthatthismostlikelywillcausepeopletofollowthepathofleastresistanceresultinginlotsofglobalfunctions.Instead,wewanttomakethebestpracticealsobetheeasiesttoimplement.Hence,theAPIshouldtakeallentriesunder:{code}moduleroot/functions{code}Tobeinthemodule'sname-space,anditshouldnotbepossibletocreatepuppetfunctionsintheglobalnamespace.UPDATE---TheimplementationinPUP-2080isbasedonthat{{moduleroot/functions}}refertofunctionsinthemodule'snamespace.Nothingspecificwasneededforthisticket,andthetwoPRs forPUP-2176and
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-2176) 4x function API for puppet function should require namespaced functions
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-2176
4x function API for puppet function should require namespaced functions
Change By:
Henrik Lindberg
TheabilitytowritefunctionsinthePuppetProgrammingLanguageisanewfeatureslatedforPuppet4.1.0.Thecurrentimplementationallowssuchfunctionstobeplacedintheglobalnamespace.Thissupportalsomeansthatfunctionsplacedunder{code}moduleroot/functions{code}areconsideredglobal,andfunctionsinthemodule'snamespacemustbeplacedunder:{code}moduleroot/functions/modulename{code}Whenreviewingthisitwasdecidedthatthismostlikelywillcausepeopletofollowthepathofleastresistanceresultinginlotsofglobalfunctions.Instead,wewanttomakethebestpracticealsobetheeasiesttoimplement.Hence,theAPIshouldtakeallentriesunder:{code}moduleroot/functions{code}Tobeinthemodule'sname-space,anditshouldnotbepossibletocreatepuppetfunctionsintheglobalnamespace. UPDATE---TheimplementationinPUP-2080isbasedonthat{{moduleroot/functions}}refertofunctionsinthemodule'snamespace.Nothingspecificwasneededforthisticket,andthetwoPRs
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-3146) Add support for provider specific attributes
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-3146 Add support for provider specific attributes Change By: Henrik Lindberg Assignee: AndyParker 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-2176) 4x function API for puppet function should require namespaced functions
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-2176
4x function API for puppet function should require namespaced functions
Change By:
Henrik Lindberg
TheabilitytowritefunctionsinthePuppetProgrammingLanguageisanewfeatureslatedforPuppet 3 4 . 6 1 .0.Thecurrentimplementationallowssuchfunctionstobeplacedintheglobalnamespace.Thissupportalsomeansthatfunctionsplacedunder{code}moduleroot/functions{code}areconsideredglobal,andfunctionsinthemodule'snamespacemustbeplacedunder:{code}moduleroot/functions/modulename{code}Whenreviewingthisitwasdecidedthatthismostlikelywillcausepeopletofollowthepathofleastresistanceresultinginlotsofglobalfunctions.Instead,wewanttomakethebestpracticealsobetheeasiesttoimplement.Hence,theAPIshouldtakeallentriesunder:{code}moduleroot/functions{code}Tobeinthemodule'sname-space,anditshouldnotbepossibletocreatepuppetfunctionsintheglobalnamespace.
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-2176) 4x function API for puppet function should require namespaced functions
Title: Message Title Henrik Lindberg commented on PUP-2176 Re: 4x function API for puppet function should require namespaced functions The implementation in PUP-2080 is based on the decision that a module should not deliver functions in the global namespace. There is however nothing stopping users from defining non-namespaced puppet functions (just like there is nothing stopping users from creating defines, classes etc. in a foreign name-space, or the global namespace). Closing this issue as a Duplicate of PUP-2080, as the support for string name-spaces and similar issues with the global name space are covered by other tickets. 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-951) Facter fails to run on Solaris due to implicit dependency of Boost.Log on Boost.Chrono
Title: Message Title Eric Thompson commented on FACT-951 Re: Facter fails to run on Solaris due to implicit dependency of Boost.Log on Boost.Chrono so i suppose we can test this by just ensuring a facter package runs on windows? 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-3596) Ensure Language Specification specifies behavior of undef resource param
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3596 Ensure Language Specification specifies behavior of undef resource param Change By: Henrik Lindberg Sprint: Language2015-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-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 Sprint: Language2015-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-4111) The environment_scenario-* acceptance tests aren't asserting their success/failure and are therefore always 'passing'
Title: Message Title Eric Thompson commented on PUP-4111 Re: The environment_scenario-* acceptance tests aren't asserting their success/failure and are therefore always 'passing' ping Joshua Partlow, you might want to checkout what i had to do to fix scenario-bad. i think it was doing nothing in several ways before. it also required a bunch of changes to environment_utils, which should be benign to the other tests. 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-3134) Decide on specification of Puppet Regexp
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-3134
Decide on specification of Puppet Regexp
Change By:
Henrik Lindberg
ThespecificationcurrentlystatesthatPuppetsupportsRubyregexp.WeshouldconsiderspecifyingindetailwhatthePuppetregexphandles.ThisbecauseotherimplementationsofthePuppetLanguageareotherwiserequiredtobebasedonthenativeimplementationoftheRubyregexppackage. (Wehavealreadylimitedsomeescapesfrombeingusedinapuppetregexp-soPuppetisnot100%rubyregexp). Themainproblemisthatthecurrentpuppetruntime (whileitchecksforsomeescapes, allows other constructs ( suchas posixgroupse.g.{{[[:blank:]]}}tobeusedinRuby1.9.3 ). , The^and$areslightlydifferentthaninother regexp implementationsandtheuseofescapesAandZ/zarerequired (butthosearetheoneswefilterout!!??(unknownreasonwhy;inthespecitissimplystatedthattheyarenotsupported)) .Wealsodonotsupportanymodifierstotheregexp(whichinawayisgoodasitreducesthenumberofincompatibilitiesbecauseoptionsarequitedifferentbetweenimplementations) ,buttheycanbeenteredwithinlineflagsettingsinsidetheregexpdelimiters .Tobe100%accurateavalidatingregexpparserisrequiredthatisspecifictoPuppet-orweneedtotietheregexpimplementationtoaparticularimplementation(whichhasconsequences). Thisisalongtermconcernthatimpactstheabilitytohaveanagent/compilerimplementationinalanguageotherthanRuby.(ItmaybesolvableinCbysimplyusingthesameC-regexplibrarythatisusedbyRuby-butitisunknownhowRubyspecificitisandifitcanbeusedseparately.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to
Jira (PUP-2176) 4x function API for puppet function should require namespaced functions
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-2176
4x function API for puppet function should require namespaced functions
Change By:
Henrik Lindberg
TheabilitytowritefunctionsinthePuppetProgrammingLanguageisanewfeatureslatedforPuppet4.1.0.Thecurrentimplementationallowssuchfunctionstobeplacedintheglobalnamespace.Thissupportalsomeansthatfunctionsplacedunder{code}moduleroot/functions{code}areconsideredglobal,andfunctionsinthemodule'snamespacemustbeplacedunder:{code}moduleroot/functions/modulename{code}Whenreviewingthisitwasdecidedthatthismostlikelywillcausepeopletofollowthepathofleastresistanceresultinginlotsofglobalfunctions.Instead,wewanttomakethebestpracticealsobetheeasiesttoimplement.Hence,theAPIshouldtakeallentriesunder:{code}moduleroot/functions{code}Tobeinthemodule'sname-space,anditshouldnotbepossibletocreatepuppetfunctionsintheglobalnamespace.UPDATE---TheimplementationinPUP-2080isbasedonthat{{moduleroot/functions}}refertofunctionsinthemodule'snamespace.Nothingspecific was is neededforthisticket for4.1.0 , and as thetwoPRs for havebeenmergedinto3.xandwerereleasedearlier. PUP- 2176and 2035alsodealtwithotheraspectsofloaders.
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.
Jira (PUP-4402) Write acceptance test for puppetmaster-passenger on Debian
Title: Message Title Kurt Wall commented on PUP-4402 Re: Write acceptance test for puppetmaster-passenger on Debian John Duarte Do you recall what you were looking for in the original QA-415? Or is that lost in the mists of time and we should just quietly back away? 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-951) Facter fails to run on Solaris due to implicit dependency of Boost.Log on Boost.Chrono
Title: Message Title Michael Smith commented on FACT-951 Re: Facter fails to run on Solaris due to implicit dependency of Boost.Log on Boost.Chrono Yeah, that should be fine. contrib/facter.ps1 is used by the Facter#master Jenkins pipeline, so grab the latest package from there. 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-3988) remove logic for single feature hostname in 4.0 validator
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3988 remove logic for single feature hostname in 4.0 validator Change By: Henrik Lindberg Sprint: Language2015-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-521) allow classes to be treated differently by documentation and classification tools
Title: Message Title Henrik Lindberg commented on PUP-521 Re: allow classes to be treated differently by documentation and classification tools The functionality to load things privately and make them invisible to others exists in the new loaders that are currently used for 4.x function. The language changes are trivial, but the work on loading classes and defines via the new loaders is not yet specified and requires tickets. 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-3146) Add support for provider specific attributes
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3146 Add support for provider specific attributes Change By: Henrik Lindberg Itiscurrentlynotpossibleto(easily)provideextraattributevaluestoaproviderwithoutatypedirectlysupportingthis(itmustenumerateallofitsattributesandpassthemon).Thismeansthatsomeonethatwritesanewprovidercannotallowuserstotransparentlypassextraattributestosuchaproviderwithoutalsoupdatingthemaintypetheproviderisfor.Whilethiscanbedoneitalsoexposesthoseattributestoallotherproviders-thissometimescausesconflictovernames/conceptsorthattheattributehasdifferentmeaningtodifferentproviders.Theproposedsolutionistoallowfullyqualifiedattributenamesinaresource_expression_.(Theyarenowunqualfied).Thequalifiednameshouldreferencetheprovider,andthentheattributee.g,the'deluxe'providerhasa'golden'attributeanditisaddressedwith'deluxe::golden').Theproviderspecificattributesareonlyavailabletoaproviderofthestatedtype.Inordertovalidatethis,thecompilerlogicneedstobeabletofindthereferencedprovideranditssupportedresourceattributes. Thisfeatureisacross-cuttingconcernsinceittouchesonresource,thecatalog,agent,typesandproviders,andpuppet-db. 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
Jira (PUP-4378) Resource collectors can be assigned to variables by abusing chaining statements
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4378 Resource collectors can be assigned to variables by abusing chaining statements Change By: Henrik Lindberg Sprint: Language2015-04-29 Story Points: 1 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-3657) Using create_resource or some other Ruby methodology for creating resources allows for invalid resource references
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3657 Using create_resource or some other Ruby methodology for creating resources allows for invalid resource references Change By: Henrik Lindberg Fix Version/s: PUP4.1.0 Fix Version/s: PUP4.x 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-3493) Error: Could not retrieve catalog from remote server: Could not intern from
Title: Message Title Tim Spriggs commented on PUP-3493 Re: Error: Could not retrieve catalog from remote server: Could not intern from I started testing with parser = future and can reproduce this with a standalone puppet 3.7.4 master and 3.6.2 client. The catalog on the client parses as valid json. 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-3814) Duplicated error output
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3814 Duplicated error output Change By: Henrik Lindberg Sprint: Language2015-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-4329) Filebucket fails to update file resource if checksum doesn't match the configured checksum type
Title: Message Title Michael Smith commented on PUP-4329 Re: Filebucket fails to update file resource if checksum doesn't match the configured checksum type There's a (questionable) use-case for wanting to use different checksum types for large files than others. We haven't provided a better option, so it was worth fixing. See PUP-1208 for more back-story. 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 assigned an issue to Eric Thompson Puppet / PUP-4343 Add test(s) for the File resource links attribute Change By: Eric Thompson Assignee: EricThompson 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-4231) File resources with defined content don't output contents with ensure=present
Title: Message Title Michael Smith commented on PUP-4231 Re: File resources with defined content don't output contents with ensure=present We were writing binary, but not reading that way. Fixed with https://github.com/puppetlabs/puppet/commit/92f90a35fa9f10fafb2324b351936918f69e963a. 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-940) Add acceptance test with no ruby present
Title: Message Title Michael Smith commented on FACT-940 Re: Add acceptance test with no ruby present I'd be fine closing it. If we have platforms we release on that don't use Ruby, they'll cover testing it. 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 commented on PUP-4178 Re: defined() function returns true for undef and empty string, and false for main The ticket PUP-4331 is about warning/error when asking if an empty string is defined. 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 updated an issue Puppet / PUP-4178 defined() function returns true for undef and empty string, and false for main Change By: Henrik Lindberg Sprint: Language2015-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-4331) should warn on checking an empty string in defined()
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4331 should warn on checking an empty string in defined() Change By: Henrik Lindberg Sprint: Language2015-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-4329) Filebucket fails to update file resource if checksum doesn't match the configured checksum type
Title: Message Title Eli Young commented on PUP-4329 Re: Filebucket fails to update file resource if checksum doesn't match the configured checksum type Why is the checksum type for individual file resources configurable anyway? 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-4405) Ordering dependency exists between certificate_request_spec.rb and autosign_spec.rb
Title: Message Title Michael Smith created an issue Puppet / PUP-4405 Ordering dependency exists between certificate_request_spec.rb and autosign_spec.rb Issue Type: Bug Assignee: Unassigned Created: 2015/04/13 5:19 PM Fix Versions: PUP 4.1.0 Priority: Normal Reporter: Michael Smith If autosign_spec.rb isn't run first, certificate_request_spec.rb will fail. This blocks using the parallel:spec rake task to run spec tests faster on Windows. Specifically, it appears host.generate_certificate_request needs to be called before all the calls to Puppet::SSL::CertificateRequest.indirection.save(@csr). So far this has only been confirmed on Windows. Add Comment
Jira (PUP-4404) Spec tests on Windows expect environment setup
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-4404 Spec tests on Windows expect environment setup Change By: Michael Smith Assignee: MichaelSmith 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 Michael Smith created an issue Puppet / PUP-4404 Spec tests on Windows expect environment setup Issue Type: Bug Assignee: Unassigned Created: 2015/04/13 4:33 PM Fix Versions: PUP 4.1.0 Priority: Normal Reporter: Michael Smith There's no requirement that Windows installations have an Administrator user, but the Puppet spec tests expect one to exist. They also create and remove users, things that should be reserved for acceptance tests. This blocks using AppVeyor for CI, as those machines don't have Administrator users. Change the tests to use the current user if possible, or move them to acceptance tests. Add Comment
Jira (PUP-4231) File resources with defined content don't output contents with ensure=present
Title: Message Title Eli Young commented on PUP-4231 Re: File resources with defined content don't output contents with ensure=present Yup, that's caused by these changes. Looks like Ruby's doing some EOL normalization that Puppet isn't doing. 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 Michael Smith updated an issue Puppet / PUP-4404 Spec tests on Windows expect environment setup Change By: Michael Smith There'snorequirementthatWindowsinstallationshaveanAdministratoruser,butthePuppetspectestsexpectonetoexist. Theyalsocreateandremoveusers,thingsthatshouldbereservedforacceptance Changethe tests tousethecurrentuser .ThisblocksusingAppVeyorforCI,asthosemachinesdon'thaveAdministratorusers. Changetheteststousethecurrentuserifpossible,ormovethemtoacceptancetests. 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-4231) File resources with defined content don't output contents with ensure=present
Title: Message Title Michael Smith commented on PUP-4231 Re: File resources with defined content don't output contents with ensure=present All the test failures have been fixed, see https://jenkins.puppetlabs.com/view/All%20in%20One%20Agent/view/Master/view/Puppet/job/platform_aio-puppet_unit-ruby_master-windows/3/. 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-2754) Exit status is 0, even in the presence of errors, without --detailed-exitcodes
Title: Message Title Josh Cooper commented on PUP-2754 Re: Exit status is 0, even in the presence of errors, without --detailed-exitcodes PUP-735 has been fixed, but only addresses fatal errors in catalog application, e.g. dependency cycles. If an individual resource fails to apply, as in this ticket, puppet will exit with 0 or 4 (if --detailed-exitcodes is specified). The actual behavior is not well specified, if at all, and has lead to a number of issues. See PUP-3460. 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-735) Status unchanged when Could not apply complete catalog
Title: Message Title Josh Cooper commented on PUP-735 Re: Status unchanged when Could not apply complete catalog I think there is an issue with the original fix d0e4efa3fc. If a cycle is detected, Puppet::Configurer no longer calls Puppet::Transaction::Report#finalize_report prior to sending the report. I think this means the report summary metrics are incorrect. It would probably be more correct to do: def apply_catalog(catalog, options) report = options[:report] begin report.configuration_version = catalog.version benchmark(:notice, Applied catalog) do catalog.apply(options) end ensure report.finalize_report
Jira (PUP-735) Status unchanged when Could not apply complete catalog
Title: Message Title Kylo Ginsberg commented on PUP-735 Re: Status unchanged when Could not apply complete catalog Acceptance tests are failing like so: https://jenkins.puppetlabs.com/view/All%20in%20One%20Agent/view/Master/view/Puppet/job/platform_aio-puppet_intn-sys_master/SLAVE_LABEL=beaker,TEST_TARGET=win2012r2-rubyx86/2/testReport/junit/(root)/tests/cycle_detection_rb/ It looks like these two lines: https://github.com/puppetlabs/puppet/blob/b1274f42f468656193ecbf72144c021078e13a78/acceptance/tests/cycle_detection.rb#L9 https://github.com/puppetlabs/puppet/blob/b1274f42f468656193ecbf72144c021078e13a78/acceptance/tests/cycle_detection.rb#L23 need to be updated to expect an exit code of 1. 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-735) Status unchanged when Could not apply complete catalog
Title: Message Title Josh Cooper commented on PUP-735 Re: Status unchanged when Could not apply complete catalog PR for acceptance test: https://github.com/puppetlabs/puppet/pull/3817 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-1929) puppet apply should not return 0 if catalog compilation fails
Title: Message Title
Josh Cooper commented on PUP-1929
Re: puppet apply should not return 0 if catalog compilation fails
The case where the catalog has a dependency cycle, but puppet exits with 0 is PUP-735, and is now fixed in puppet's master branch:
$ cat cycle.pp
notify { a1: require = Notify[a2] }
notify { a2: require = Notify[a1] }
$ be puppet apply cycle.pp
Notice: Compiled catalog for XXX.local in environment production in 0.33 seconds
Error: Failed to apply catalog: Found 1 dependency cycle:
(Notify[a1] = Notify[a2] = Notify[a1])
Try the '--graph' option and opening the resulting '.dot' file in OmniGraffle or GraphViz
$ echo $?
1
Jira (FACT-940) Add acceptance test with no ruby present
Title: Message Title Kylo Ginsberg commented on FACT-940 Re: Add acceptance test with no ruby present Yep, makes sense. Closing as won't fix. (We can resurrect this when we have non-ruby-based packages.) 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-735) Status unchanged when Could not apply complete catalog
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-735 Status unchanged when Could not apply complete catalog Change By: Kylo Ginsberg Sprint: Client2015-04-15 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-914) Facter complains if locale is any thing other than LANG=C in Solaris
Title: Message Title Kurt Wall assigned an issue to Unassigned Facter / FACT-914 Facter complains if locale is any thing other than LANG=C in Solaris Change By: Kurt Wall Assignee: KurtWall 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-1246) Add V3 API deprecation message
Title: Message Title Moses Mendoza commented on PDB-1246 Re: Add V3 API deprecation message I reached out to Kenneth Barber for further clarification on the cost of maintaining the V3 API and why we chose to retire (rather than deprecate it). These are notes from that conversation (primarily Kenneth Barber's input): The main reasoning here is that the code behind v1/v2/v3 ... and the code behind v4 is very different the old code is as old as pdb basically and its convergence is very hard to maintain v3/v4 they aren't just 'translations' late in the game, the way they query is very different There are large hurdles to maintaining the v3 API from a maintenance perspective with the old query engine code was full of inconsistencies because of how it was written with the old code, making changes was a painful set of per endpoint changes for any cross-endpoint change for example an example of the failure state this introduced was that each dev would create a feature for 1 endpoint, and not carry it across all the endpoints, or, it would be poorly copied, and not work exactly the same The options with respect to the v3 api were: a) copy all v4 features into 2.x, however this would be working on stable, which we thought by now that work would be done - but the SG delays have caused us hassles. b) create a translation layer for v3 into 3.x ... but that would be all new work to 'replicate' how v3 worked using the new query engine. Add Comment
Jira (PUP-4402) Write acceptance test for puppetmaster-passenger on Debian
Title: Message Title Eric Thompson commented on PUP-4402 Re: Write acceptance test for puppetmaster-passenger on Debian Kurt Wall can you elaborate on this ticket description a bit? what's the problem it's trying to solve? is it intended for a scrum-team and/or sprint? 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-922) Add timeout for call to prtdiag on Solaris
Title: Message Title Eric Thompson updated an issue Facter / FACT-922 Add timeout for call to prtdiag on Solaris Change By: Eric Thompson Facter 2.x includesatimeoutoptionforcallstoprtdiagonSolaris,apparentlybecauseitcanhang.Thisisafeatureweprobablyneedtocarryover tonativefacter . 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-4384) PMT includes `._*` files when `puppet module build`ing in the `.tar.gz`
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-4384 PMT includes `._*` files when `puppet module build`ing in the `.tar.gz` Change By: Eric Thompson Assignee: EricThompson 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-922) Add timeout for call to prtdiag on Solaris
Title: Message Title
Eric Thompson commented on FACT-922
Re: Add timeout for call to prtdiag on Solaris
verified on sol11 at SHA:
root@i4338yojlv7r2v4:/opt/puppet-git-repos/cfacter-build# time ./build/i386/facter-0/bin/facter
2015-04-13 10:17:56.773275 WARN puppetlabs.facter - execution of prtdiag has timed out after 20 seconds.
disks = {
sd0 = {
product = VMware IDE CDR10Revision,
size = 0 bytes,
size_bytes = 0,
vendor = NECVMWar
},
[trimmed...]
Jira (FACT-895) Solaris: 'getloadavg' was not declared in this scope when building Facter
Title: Message Title Eric Thompson commented on FACT-895 Re: Solaris: 'getloadavg' was not declared in this scope when building Facter builds using cfacter-build on sol11 at SHA: ed622e9 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-914) Facter complains if locale is any thing other than LANG=C in Solaris
Title: Message Title
Kurt Wall commented on FACT-914
Re: Facter complains if locale is any thing other than LANG=C in Solaris
Validated at SHA=ed622e9ae43181eb742f8e3d885bc4c62484c662. The two warning messages are unrelated to this bug.
# ./facter-0
/bin/facter -j facterversion operatingsystem os
2015-04-13 10:30:32.753894 WARN puppetlabs.facter - ruby failed to run:
2015-04-13 10:30:32.755047 WARN puppetlabs.facter - could not locate a ruby library: custom facts will not be resolved.
{
facterversion: 2.9.0,
operatingsystem: Solaris,
os: {
architecture: i86pc,
family: Solaris,
Jira (FACT-914) Facter complains if locale is any thing other than LANG=C in Solaris
Title: Message Title Kurt Wall updated an issue Facter / FACT-914 Facter complains if locale is any thing other than LANG=C in Solaris Test Rail triage not necessary. Covered in unit tests with make test or crest. Change By: Kurt Wall QA Contact: KurtWall 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-4400) resource user no longer returns password hash
Title: Message Title Jo Rhett created an issue Puppet / PUP-4400 resource user no longer returns password hash Issue Type: Bug Affects Versions: PUP 4.x Assignee: Unassigned Created: 2015/04/13 12:00 AM Environment: Linux client.example.com 3.10.0-123.20.1.el7.x86_64 #1 SMP Thu Jan 29 18:05:33 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux CentOS Linux release 7.0.1406 (Core) (on the vagrant image provided by Puppet Labs, no less) Priority: Normal Reporter: Jo Rhett # puppet resource user vagrant Warning: ruby-shadow doesn't support sp_loginclass
Jira (PUP-2156) file provider silent behaviour change for mode
Title: Message Title Henrik Lindberg commented on PUP-2156 Re: file provider silent behaviour change for mode This bug was opened because it didn't validate the value. It validates now. Why use a distinct validation separate from the number validation performed on every other number? Because strictly speaking mode is not a number, it is a string with octal digits that does not have to start with a 0. Before file mode change to require a string, there were many that were bit by decimal numbers entered as bare words e.g. 777, which earlier was the same as '777' since there was no difference between literal numbers and strings, but now becomes the string '511' when converted to octal representation, which is a very different mode than '777'. We believe it is better to be told that a String must be used, than silently accepting numbers that due to representation has the potential to cause serious security consequences. As the mode String with octal digits is now validated by the file type, there is no possibility of entering an illegal mode. Earlier it just accept a numeric value which could be a different value than the intended due to representation issues - and it is just simply impossible to validate if a user intended '777' when the value 511 is seen in File mode. Remember that numbers have no representation by themselves, a value such as 0776 + 1 has no memory that one of the operands was an octal value - it is simply a numeric value. If you prefer to use numbers, and possibly perform arithmetic, for mode you must then convert it to an octal string using the sprintf function. We believe almost everyone uses literal mode values everywhere and thus it is simply a matter of quoting the octal digits - which has the additional benefit that modes that do not start with '0' works. Also, the training inconsistently. If you want an octal number validated to ensure it's good, use an unquoted string. Except when it's a File resource, then use a string. I think users should learn that File mode is a String and that it validates what is entered. Add Comment
Jira (PUP-4401) ssh_key purge on a authorized_key file belonging to different user
Title: Message Title Timo Bergemann created an issue Puppet / PUP-4401 ssh_key purge on a authorized_key file belonging to different user Issue Type: Bug Affects Versions: PUP 3.7.4 Assignee: Unassigned Created: 2015/04/13 3:16 AM Priority: Major Reporter: Timo Bergemann Hello, I am useing a modified version of the module sshkeys from sudorenko to manage my users and ssh_keys. In favor to our SLAs I modified it in that way that I can change the target and ownerchips and permissions. All works fine so far - purgeing ssh_keys, readding them and so on. However as soon as I change the ownerchip of the authorized_keys (/etc/keys/$USERNAME/authorized_keys) and try to remove a key from the file i get: Error: Puppet::Util::FileType::FileTypeFlat could not write /etc/keys/puppettest1/test_keys: Permission denied - /etc/keys/puppettest1/test_keys Error: /Stage[main]/Sshkeys/Sshkeys::User[puppettest1]/Ssh_authorized_key[hesemeyert_at_puppette...@template-centos-5.onet.itenos.de]: Could not evaluate: Puppet::Util::FileType::FileTypeFlat could not write /etc/keys/puppettest1/test_keys: Permission denied - /etc/keys/puppettest1/test_keys The reason for that is to me clear. Puppet runs as root but tries to remove the key as user puppettest1 which is not possible as the file belongs to root. For SLA reasons my authorized_keys MUST not belong to the user nor does the user to have writepermissions Is there a way of telling the tell the refference user to run as root rather then as user.
Jira (PUP-4400) resource user no longer returns password hash
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4400 resource user no longer returns password hash Change By: Henrik Lindberg Scrum Team: ClientPlatform 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-4344) Add test(s) for the File resource manage_symlinks attribute
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-4344 Add test(s) for the File resource manage_symlinks attribute Change By: Kurt Wall Assignee: QA KurtWall 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-1422) The DB migration in 2.3.1 doesn't clean out orphaned fact_values
Title: Message Title Erik Daln created an issue PuppetDB / PDB-1422 The DB migration in 2.3.1 doesn't clean out orphaned fact_values Issue Type: Bug Affects Versions: PDB 2.3.3 Assignee: Unassigned Created: 2015/04/13 6:19 AM Priority: Normal Reporter: Erik Daln After upgrade from puppetdb 2.3.0 to 2.3.3 I get this: puppetdb=# select count(*) from fact_values where id not in (select distinct fact_value_id from facts); count ---
Jira (PDB-46) Storing historical facts and catalogs
Title: Message Title Beth Cornils updated an issue PuppetDB / PDB-46 Storing historical facts and catalogs Change By: Beth Cornils Thisepiccoversthetasksrequiredtoprovidehistoricalstorageandretrievalofhistoricalfactsandcatalogs. Phase1forthiswillbetoimplementRyanSenior'splanforUnchangedResources. 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-1424) ConsoleDB: Create PE only endpoint for status overview
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1424 ConsoleDB: Create PE only endpoint for status overview Issue Type: New Feature Assignee: Unassigned Components: PE Created: 2015/04/13 9:48 AM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: Kenneth Barber Once we have aggregation capabilities for count in the core product, we need to fix the endpoint here: https://github.com/puppetlabs/puppetdb-sync/blob/master/src/puppetlabs/puppetdb/extensions/state_overview.clj to use this properly. Add Comment
Jira (PDB-1425) ConsoleDB: Create PE only endpoint for status overview
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1425 ConsoleDB: Create PE only endpoint for status overview Issue Type: New Feature Assignee: Unassigned Components: PE Created: 2015/04/13 9:54 AM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: Kenneth Barber Once we have aggregation capabilities for count in the core product, we need to fix the endpoint here: https://github.com/puppetlabs/puppetdb-sync/blob/master/src/puppetlabs/puppetdb/extensions/state_overview.clj to use this properly. Add Comment
Jira (PDB-1422) The DB migration in 2.3.1 doesn't clean out orphaned fact_values
Title: Message Title Rob Browning commented on PDB-1422 Re: The DB migration in 2.3.1 doesn't clean out orphaned fact_values Hey Erik - so the migration doesn't actually do anything about fact_value orphans, but the GC should handle them incrementally later (200 at a time). Can you see that happening in your database? Thanks for the report. 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-926) Provide meaningful operating system fact values for Arista EOS
Title: Message Title
Stan Duffy commented on FACT-926
Re: Provide meaningful operating system fact values for Arista EOS
We now get meaningful facts:
operatingsystem = AristaEOS
operatingsystemmajrelease = 4
operatingsystemrelease = 4.14.5F
os = {name=AristaEOS, family=Linux, release={major=4, minor=14, full=4.14.5F}}
osfamily = Linux
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (FACT-896) Solaris: undefined reference to symbol 'inet_ntop@@SUNW_1.7' when building Facter
Title: Message Title Eric Thompson commented on FACT-896 Re: Solaris: undefined reference to symbol 'inet_ntop@@SUNW_1.7' when building Facter builds from cfacter-build on sol11 at SHA: ed622e9 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-896) Solaris: undefined reference to symbol 'inet_ntop@@SUNW_1.7' when building Facter
Title: Message Title Eric Thompson updated an issue Facter / FACT-896 Solaris: undefined reference to symbol 'inet_ntop@@SUNW_1.7' when building Facter 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-926) Provide meaningful operating system fact values for Arista EOS
Title: Message Title Kurt Wall commented on FACT-926 Re: Provide meaningful operating system fact values for Arista EOS Stan Duffy will FR this. Thanks Stan! 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-4402) Write acceptance test for puppetmaster-passenger on Debian
Title: Message Title Kurt Wall assigned an issue to QA Puppet / PUP-4402 Write acceptance test for puppetmaster-passenger on Debian Change By: Kurt Wall Assignee: EricSorenson 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 (PUP-4402) Write acceptance test for puppetmaster-passenger on Debian
Title: Message Title Kurt Wall created an issue Puppet / PUP-4402 Write acceptance test for puppetmaster-passenger on Debian Issue Type: Improvement Assignee: Eric Sorenson Components: QA Created: 2015/04/13 9:29 AM Priority: Normal Reporter: Kurt Wall Write acceptance test for puppetmaster-passenger on Debian Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (FACT-914) Facter complains if locale is any thing other than LANG=C in Solaris
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Facter / FACT-914 Facter complains if locale is any thing other than LANG=C in Solaris Change By: Kurt Wall Assignee: QA KurtWall 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-4231) File resources with defined content don't output contents with ensure=present
Title: Message Title Kylo Ginsberg commented on PUP-4231 Re: File resources with defined content don't output contents with ensure=present Note that we now have CI again on puppet#master and all Windows cells are failing, e.g.: https://jenkins.puppetlabs.com/job/platform_aio-puppet_unit-ruby_master-windows/1/RUBY=ruby-2.1.5.2-x64,SLAVE=unit-win2008/consoleFull I actually don't know if these changes are the culprit or not, but it seemed more likely it was this than the one other RFI ticket so dropping the comment here. 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.
