Jira (PUP-2023) Debian/Ubuntu service provider improvements
Title: Message Title Mathieu Parent commented on PUP-2023 Re: Debian/Ubuntu service provider improvements I proposed the related https://github.com/puppetlabs/puppet/pull/3900 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-1484) Memory leak when 'replace facts' failing
Title: Message Title Simon Oxwell commented on PDB-1484 Re: Memory leak when 'replace facts' failing Yes, two, but they're on the large size (~900M). 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-4503) systemd should be the default for Debian Jessie
Title: Message Title Mathieu Parent commented on PUP-4503 Re: systemd should be the default for Debian Jessie I proposed the related https://github.com/puppetlabs/puppet/pull/3900 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-4366) Test FOSS upgrade from 3.x to 4.0 using packages
Title: Message Title Kevin Imber commented on PUP-4366 Re: Test FOSS upgrade from 3.x to 4.0 using packages Eric Thompson is there a plan to add acceptance tests for this, such that Beaker support is required? Right now I'm trying to figure out what's required for BKR-254, and if the upgrade module is ready for me to be able to use it for that work. Thanks, Kevin 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-4540) Stock Puppet shipping with Ubuntu Vivid (3.7.2) has broken service type
Title: Message Title
Victor Danilchenko updated an issue
Puppet / PUP-4540
Stock Puppet shipping with Ubuntu Vivid (3.7.2) has broken service type
Change By:
Victor Danilchenko
Ifyou tun run apuppetmanifestonUbuntuVivid,certainservicesgetdetectedincorrectly,andPuppetattemptstotreatthemasUpstartservices.Forinstance,{{mysql}}worksthatway.ThefollowingPuppetmanifestexercisestheerror:{code:none}service{'mysql': ensure=running,}notify{test: notify=Service['mysql']}{code}Output:{code:none}$sudopuppetapplytest.ppNotice:Compiledcatalogforvdanilchenko-vivid.vistaprint.netinenvironmentproductionin0.33secondsNotice:testNotice:/Stage[main]/Main/Notify[test]/message:defined'message'as'test'Error:/Stage[main]/Main/Service[mysql]:Couldnotevaluate:Executionof'/sbin/statusmysql'returned1:status:UnabletoconnecttoUpstart:Failedtoconnecttosocket/com/ubuntu/upstart:ConnectionrefusedError:/Stage[main]/Main/Service[mysql]:Failedtocallrefresh:Executionof'/sbin/statusmysql'returned1:status:UnabletoconnecttoUpstart:Failedtoconnecttosocket/com/ubuntu/upstart:ConnectionrefusedError:/Stage[main]/Main/Service[mysql]:Executionof'/sbin/statusmysql'returned1:status:UnabletoconnecttoUpstart:Failedtoconnecttosocket/com/ubuntu/upstart:Connectionrefused{code}Nowthe{{apache2}}service,forinstance,getsdetectedcorrectly(it'salsonotanUpstartservice,andUpstartcommandsalsofail,butPuppettreatsitasInitserviceandmanagesitcorrectly);but{{mysql}}breaks.Ididn'ttestalltheservicesonthesystem,butthe{{cups}}service,forinstance,alsobreaksjustlike{{mysql}}.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4473) Extend file-based ENC spec tests to include Windows
Title: Message Title Michael Smith assigned an issue to Josh Cooper Puppet / PUP-4473 Extend file-based ENC spec tests to include Windows Change By: Michael Smith Assignee: JoshCooper 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 Branan Riley assigned an issue to Unassigned Puppet / PUP-735 Status unchanged when Could not apply complete catalog Change By: Branan Riley Assignee: BrananRiley 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-4477) Create a base agent upgrade module for rpm-based distro
Title: Message Title Michael Smith commented on PUP-4477 Re: Create a base agent upgrade module for rpm-based distro Prior script: https://github.com/puppetlabs/puppet/pull/3602 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-4481) Figure out steps to release the module
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4481 Figure out steps to release the module Change By: Kurt Wall QA Risk Assessment: Low 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-4481) Figure out steps to release the module
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4481 Figure out steps to release the module Change By: Kurt Wall QA Risk Assessment Reason: Release-relatedticket 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-4524) Rewrite spec/unit/provider/service/base_spec.rb to stub command execution
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4524 Rewrite spec/unit/provider/service/base_spec.rb to stub command execution 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 (PUP-4210) Support rename in the augeas resource type
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4210 Support rename in the augeas resource type 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 (PUP-4524) Rewrite spec/unit/provider/service/base_spec.rb to stub command execution
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4524 Rewrite spec/unit/provider/service/base_spec.rb to stub command execution Change By: Kurt Wall QA Risk Assessment Reason: Testingticket 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-4524) Rewrite spec/unit/provider/service/base_spec.rb to stub command execution
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4524 Rewrite spec/unit/provider/service/base_spec.rb to stub command execution Change By: Kurt Wall QA Risk Assessment: Low 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-981) Modules with facts cannot be tested with native facter
Title: Message Title
Peter Huene updated an issue
Facter / FACT-981
Modules with facts cannot be tested with native facter
Change By:
Peter Huene
Thereareanumberofmodulesontheforgewithfacts.ThosemoduleshavespecsthatattempttostubpartsofFactertoproperlytestthosefacts.Usersarefacingtwoissues:1.ThereisnowaytostubFactersuchthatitaltersthebehaviorofconfines.Previouslyaconfineof{{confine:osfamily=' bar foobar '}}couldbealteredinaspecbystubbing{{Facter#fact}}or{{Facter::Util::Fact#value}}becauseRubyFacterwouldcall{{Facter.fact(name).value}}togetthefact'svalueforcheckingintheconfine.TomakethisworkinFacter3,thenativecodethatimplementsconfinesneedstocallthroughtheRubyinterfacetoobtainthefact.Doingsowouldenablerspectoreturndifferentvaluestotheconfinelogic.2.WhennativeFacterwasoriginallywritten,theRubyAPIcreatedbynativeFacterwasmarkedasfrozentoeasilydetectattemptstomodifyFacterfromconsumerslikePuppet.However,thispreventsmoduleauthorsfromstubbing{{Facter::Util::Resolution#which}}and{{Facter::Util::Resolution#exec}}whichiscommonlydonetomockcommandexecutions.Weshouldunfreezethesemodules.
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-4427) Rake Spec tests fail due to missing dependencies
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4427 Rake Spec tests fail due to missing dependencies Change By: Kylo Ginsberg Sprint: Client2015- 05 06 - 27 10 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 Kylo Ginsberg updated an issue Puppet / PUP-4405 Ordering dependency exists between certificate_request_spec.rb and autosign_spec.rb Change By: Kylo Ginsberg Sprint: Client2015- 05 06 - 27 10 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-4492) Investigate: plan for module testing with puppet-agent
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4492 Investigate: plan for module testing with puppet-agent Change By: Kurt Wall QA Risk Assessment Reason: Testingticket 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-961) Windows binary sizes are huge
Title: Message Title Michael Smith updated an issue Facter / FACT-961 Windows binary sizes are huge Change By: Michael Smith Story Points: 0 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-956) Update puppet-agent#master to build facter#master, remove cfacter
Title: Message Title Kurt Wall updated an issue Facter / FACT-956 Update puppet-agent#master to build facter#master, remove cfacter Change By: Kurt Wall QA Risk Assessment Reason: Buildticket 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-4210) Support rename in the augeas resource type
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-4210 Support rename in the augeas resource type Change By: Eric Thompson 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 (PUP-4030) puppet module install does not consider no_proxy env var
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-4030 puppet module install does not consider no_proxy env var 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 (PDB-1479) Mark aggregate-event-counts event-counts API docs as experimental for the future
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1479 Mark aggregate-event-counts event-counts API docs as experimental for the future Change By: Kenneth Barber Fix Version/s: PDB3.0.0 Fix Version/s: PDB2.3.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-4492) Investigate: plan for module testing with puppet-agent
Title: Message Title Justin Stoller commented on PUP-4492 Re: Investigate: plan for module testing with puppet-agent For spec level testing currently module authors can continue to use Facter 2. And hopefully an SDK will provide that functionality later on. (Though there's been discussion about shipping compiled gems if the SDK isn't going to be until after Puppet 5, and I think that Eric Sorenson owns that convo) As far as acceptance testing goes there's a small amount of Beaker updates and a chain of module team work that culminates in testing the modules against AIO in PE: QENG-2371 (supported modules are only technically supported against PE releases). That chain AFAICT is roughly: Module team updates supported modules to include puppet 4 via gem in spec testing on travis (as a non-failing cell) Module team to triage failures, ticket issues Once the module team is ready to turn puppet 4 on in CI spec tests we'll do that (QENG-2374) (either when they've fixed the issues in an ad hoc way, or their ready for it to be their primary focus and have their board go red) Once specs are green we'll enable testing of the puppet-agent package in the FOSS.next stage of their pipelines (QENG-2372, requires BKR-195) The module team will fix any issues that arise with that Once FOSS.next is stable green, we'll migrate the puppet-agent to be the FOSS.stable step in their pipeline. We'll remove the FOSS.next step and replay it with a FOSS.legacy step that tests old puppet 3.x compat (QENG-2373 a CI maintenance task) After the FOSS issues have been ironed out and SG goes code complete we'll re-enable the PE.next step in the pipelines and make sure they point at SG (QENG-2371, BKR-252). Then the module team will fix any issues that shake out from SG integrations with puppet-agent. I've ticket the work that I think needs ticketing. I believe the module team is in the process of ticketing what work they can (though it may just be triage failures that this point). Either way I think FM-2657 is the place for the action.
Jira (PUP-4492) Investigate: plan for module testing with puppet-agent
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4492 Investigate: plan for module testing with puppet-agent Change By: Kurt Wall QA Risk Assessment: Low 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-981) Modules with facts cannot be tested with native facter
Title: Message Title
Peter Huene updated an issue
Facter / FACT-981
Modules with facts cannot be tested with native facter
Change By:
Peter Huene
Thereareanumberofmodulesontheforgewithfacts.ThosemoduleshavespecsthatattempttostubpartsofFactertoproperlytestthosefacts.Usersarefacingtwoissues:1.ThereisnowaytostubFactersuchthatitaltersthebehaviorofconfines.Previouslyaconfineof{{confine:osfamily='foobar'}}couldbealteredinaspecbystubbing{{Facter#fact}}or{{Facter::Util::Fact#value}}becauseRubyFacterwouldcall{{Facter.fact(name).value}}togetthefact'svalueforcheckingintheconfine.TomakethisworkinFacter3,thenativecodethatimplementsconfinesneedstocallthroughtheRubyinterfacetoobtainthefact.Doingsowouldenablerspectoreturndifferentvaluestotheconfinelogic.2.WhennativeFacterwasoriginallywritten,theRubyAPIcreatedbynativeFacterwasmarkedasfrozentoeasilydetectattemptstomodifyFacterfromconsumerslikePuppet.However,thispreventsmoduleauthorsfromstubbing{{Facter::Util::Resolution#which}}and{{Facter::Util::Resolution#exec}}whichiscommonlydonetomockcommandexecutions.Weshouldunfreezethesemodules. Here'sasimplereproforissue#1:{code:ruby}require'spec_helper'require'facter'describe'factermockissue'do before:eachdo Facter.fact(:osfamily).expects(:value).returns'foo' end it'shouldallowmockingconfines'do expect(Facter.fact(:osfamily).value).toeq('foo') Facter.add(:test)do confineosfamily:'foo' setcodedo 'bar' end end expect(Facter.value(:test)).toeq('bar') endend{code}
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 (FACT-981) Modules with facts cannot be tested with native facter
Title: Message Title
Peter Huene updated an issue
Facter / FACT-981
Modules with facts cannot be tested with native facter
Change By:
Peter Huene
Thereareanumberofmodulesontheforgewithfacts.ThosemoduleshavespecsthatattempttostubpartsofFactertoproperlytestthosefacts.Usersarefacingtwoissues:1.ThereisnowaytostubFactersuchthatitaltersthebehaviorofconfines.Previouslyaconfineof{{confine:osfamily='foobar'}}couldbealteredinaspecbystubbing{{Facter#fact}}or{{Facter::Util::Fact#value}}becauseRubyFacterwouldcall{{Facter.fact(name).value}}togetthefact'svalueforcheckingintheconfine.TomakethisworkinFacter3,thenativecodethatimplementsconfinesneedstocallthroughtheRubyinterfacetoobtainthefact.Doingsowouldenablerspectoreturndifferentvaluestotheconfinelogic.2.WhennativeFacterwasoriginallywritten,theRubyAPIcreatedbynativeFacterwasmarkedasfrozentoeasilydetectattemptstomodifyFacterfromconsumerslikePuppet.However,thispreventsmoduleauthorsfromstubbing{{Facter::Util::Resolution#which}}and{{Facter::Util::Resolution#exec}}whichiscommonlydonetomockcommandexecutions.Weshouldunfreezethesemodules.Here'sasimplereproforissue#1:{code:ruby}require'spec_helper'require'facter'describe'factermockissue'do before:eachdo Facter.fact(:osfamily).expects(:value).returns'foo' end it'shouldallowmockingconfines'do expect(Facter.fact(:osfamily).value).toeq('foo') Facter.add(:test)do confineosfamily:'foo' setcodedo 'bar' end end expect(Facter.value(:test)).toeq('bar') endend{code} Thiswillfailbecausethe:testfactdoesnotexist(confinenotsatisfied).
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1510) update dujour
Title: Message Title Melissa Stone created an issue PuppetDB / PDB-1510 update dujour Issue Type: Sub-task Assignee: Unassigned Created: 2015/05/07 1:06 PM Priority: Normal Reporter: Melissa Stone 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-4539) order dependent test warning
Title: Message Title Josh Cooper created an issue Puppet / PUP-4539 order dependent test warning Issue Type: Bug Assignee: Unassigned Created: 2015/05/07 10:37 AM Priority: Normal Reporter: Josh Cooper We are seeing lots of warnings like the following: C:/jenkins/workspace/platform_aio-puppet_unit-ruby_stable-windows/RUBY/ruby-2.1.5.2-x64/SLAVE/unit-win2012/lib/puppet/pops/loader/../../../puppet/functions/defined.rb:71: warning: already initialized constant Puppet::Pops::Loader::RubyFunctionInstantiator::ARG_TYPE in windows specs, https://jenkins.puppetlabs.com/view/All%20in%20One%20Agent/view/Stable/view/Puppet/job/platform_aio-puppet_unit-ruby_stable-windows/RUBY=ruby-2.1.5.2-x64,SLAVE=unit-win2012/71/console Seems to be an order dependent issue. I can reproduce on OSX with: $ bundle exec rspec spec/integration/parser/class_spec.rb
Jira (HI-46) Hiera should support alternate environments
Title: Message Title Trevor Vaughan commented on HI-46 Re: Hiera should support alternate environments I'm not a fan of the 'query across all envrionments' use case. I think that hiera data should match the way environments currently work. In other words, look in my environment, then look in $basemodulepath (or the equivalent for hiera). By default, what I would expect as a user would be for it to look in the environment, then go up to the default puppet/hiera.yaml for direction. 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 Michael Smith assigned an issue to Branan Riley Puppet / PUP-735 Status unchanged when Could not apply complete catalog Change By: Michael Smith Assignee: BrananRiley 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-4448) Create acceptance tests for non-root external facts
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4448 Create acceptance tests for non-root external facts Change By: Kylo Ginsberg Sprint: Client2015- 05 06 - 27 24 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-4492) Investigate: plan for module testing with puppet-agent
Title: Message Title Justin Stoller assigned an issue to Kylo Ginsberg Puppet / PUP-4492 Investigate: plan for module testing with puppet-agent Change By: Justin Stoller Assignee: JustinStoller KyloGinsberg 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-1499) Tag the release and create packages
Title: Message Title Melissa Stone commented on PDB-1499 Re: Tag the release and create packages tagged at [0] Melissa@melissa:puppetdb:(stable)$ git show 2.3.4 tag 2.3.4 Tagger: Melissa Stone meli...@puppetlabs.com Date: Thu May 7 12:52:39 2015 -0700 2.3.4 -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org iQIcBAABCgAGBQJVS8KHAAoJEBBUt6JL1uwwPCMP/RAsspBwi0ETBrJkTzeyKIDl
Jira (FACT-707) improve facter acceptance pre-suite for more platforms and git install
Title: Message Title Kylo Ginsberg commented on FACT-707 Re: improve facter acceptance pre-suite for more platforms and git install Eric Thompson can you estimate this ticket? Also does this effectively block anything else or is this a nice-to-have? 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-4540) Stock Puppet shipping with Ubuntu Vivid (3.7.2) has broken service type
Title: Message Title
Victor Danilchenko created an issue
Puppet / PUP-4540
Stock Puppet shipping with Ubuntu Vivid (3.7.2) has broken service type
Issue Type:
Bug
Assignee:
Unassigned
Created:
2015/05/07 11:00 AM
Priority:
Normal
Reporter:
Victor Danilchenko
If you tun a puppet manifest on Ubuntu Vivid, certain services get detected incorrectly, and Puppet attempts to treat them as Upstart services. For instance, mysql works that way. The following Puppet manifest exercises the error:
service{'mysql':
ensure = running,
}
Jira (FACT-981) Modules with facts cannot be tested with native facter
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-981 Modules with facts cannot be tested with native facter Change By: Kylo Ginsberg Sprint: Client2015-05-27 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-1500) Smoke test packages
Title: Message Title Melissa Stone commented on PDB-1500 Re: Smoke test packages packages available at http://builds.puppetlabs.lan/puppetdb/2.3.4/ 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-4230) File resources with ensure=absent do not have hashes logged after being filebucketed
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4230 File resources with ensure=absent do not have hashes logged after being filebucketed Change By: Kylo Ginsberg Sprint: Client2015-05-27 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-4230) File resources with ensure=absent do not have hashes logged after being filebucketed
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4230 File resources with ensure=absent do not have hashes logged after being filebucketed Change By: Kylo Ginsberg 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 (FACT-981) Modules with facts cannot be tested with native facter
Title: Message Title
Peter Huene updated an issue
Facter / FACT-981
Modules with facts cannot be tested with native facter
Change By:
Peter Huene
Thereareanumberofmodulesontheforgewithfacts.ThosemoduleshavespecsthatattempttostubpartsofFactertoproperlytestthosefacts.Usersarefacingtwoissues:1.ThereisnowaytostubFactersuchthatitaltersthebehaviorofconfines.Previouslyaconfineof{{confine:osfamily='foobar'}}couldbealteredinaspecbystubbing{{Facter#fact}}or{{Facter::Util::Fact#value}}becauseRubyFacterwouldcall{{Facter.fact(name).value}}togetthefact'svalueforcheckingintheconfine.TomakethisworkinFacter3,thenativecodethatimplementsconfinesneedstocallthroughtheRubyinterfacetoobtainthefact.Doingsowouldenablerspectoreturndifferentvaluestotheconfinelogic.2.WhennativeFacterwasoriginallywritten,theRubyAPIcreatedbynativeFacterwasmarkedasfrozentoeasilydetectattemptstomodifyFacterfromconsumerslikePuppet.However,thispreventsmoduleauthorsfromstubbing{{Facter::Util::Resolution#which}}and{{Facter::Util::Resolution#exec}}whichiscommonlydonetomockcommandexecutions.Weshouldunfreezethesemodules.Here'sasimplereproforissue#1:{code:ruby}require'spec_helper'require'facter'describe'factermockissue'do before:eachdo Facter.fact(:osfamily).expects(:value). at_least(1). returns'foo' end it'shouldallowmockingconfines'do expect(Facter.fact(:osfamily).value).toeq('foo') Facter.add(:test)do confineosfamily:'foo' setcodedo 'bar' end end expect(Facter.value(:test)).toeq('bar') endend{code}Thiswillfailbecausethe:testfactdoesnotexist(confinenotsatisfied).
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts
Title: Message Title Henrik Lindberg commented on PUP-2630 Re: Server-set global variables like $::environment get overwritten by client facts Merged to stable at 81684bd 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-1479) Mark aggregate-event-counts event-counts API docs as experimental for the future
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1479 Mark aggregate-event-counts event-counts API docs as experimental for the future Change By: Wyatt Alt Summary: Markaggregate-event-countsevent-countsAPIdocs asexperimental for removalin thefuture 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-965) facter doesn't run under jruby
Title: Message Title Eric Thompson commented on FACT-965 Re: facter doesn't run under jruby yep ^^ resolving... nice work 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-4030) puppet module install does not consider no_proxy env var
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4030 puppet module install does not consider no_proxy env var Change By: Kurt Wall QA Risk Assessment Reason: FairlynarrowreproductioncaserelativetoForgeusagevolume 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 Kurt Wall updated an issue Facter / FACT-956 Update puppet-agent#master to build facter#master, remove cfacter Change By: Kurt Wall QA Risk Assessment: Low 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-4030) puppet module install does not consider no_proxy env var
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4030 puppet module install does not consider no_proxy env var Change By: Kurt Wall QA Risk Severity: Low 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-4536) Investigate and document differences between Ruby 1.9 and 2.1
Title: Message Title Kylo Ginsberg commented on PUP-4536 Re: Investigate and document differences between Ruby 1.9 and 2.1 I've assigned it to 4.2.0 just so we don't lose track of it and I don't have a better hammer to ensure that. However, it should be a docs only change, so can be tackled after all the SG work is complete. (And we can yank the Fix Version once we have it in some team's sprint somewhere.) 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-4477) Create a base agent upgrade module for rpm-based distro
Title: Message Title Michael Smith commented on PUP-4477 Re: Create a base agent upgrade module for rpm-based distro Where should the upgrade module reside? New repo? 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-1500) Smoke test packages
Title: Message Title Wyatt Alt commented on PDB-1500 Re: Smoke test packages I'm testing wheezy on this box https://vagrantcloud.com/puppetlabs/boxes/debian-7.8-32-nocm with this process https://confluence.puppetlabs.com/display/PP/Smoke+Testing+Guide+for+PDB+Releases 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-4540) Stock Puppet shipping with Ubuntu Vivid (3.7.2) has broken service type
Title: Message Title
Victor Danilchenko updated an issue
Puppet / PUP-4540
Stock Puppet shipping with Ubuntu Vivid (3.7.2) has broken service type
Change By:
Victor Danilchenko
IfyourunapuppetmanifestonUbuntuVivid,certainservicesgetdetectedincorrectly,andPuppetattemptstotreatthemasUpstartservices ,usingthe/sbin/{start,stop,restart,reload,status}commands .Forinstance,{{mysql}}worksthatway.ThefollowingPuppetmanifestexercisestheerror:{code:none}service{'mysql': ensure=running,}notify{test: notify=Service['mysql']}{code}Output:{code:none}$sudopuppetapplytest.ppNotice:Compiledcatalogforvdanilchenko-vivid.vistaprint.netinenvironmentproductionin0.33secondsNotice:testNotice:/Stage[main]/Main/Notify[test]/message:defined'message'as'test'Error:/Stage[main]/Main/Service[mysql]:Couldnotevaluate:Executionof'/sbin/statusmysql'returned1:status:UnabletoconnecttoUpstart:Failedtoconnecttosocket/com/ubuntu/upstart:ConnectionrefusedError:/Stage[main]/Main/Service[mysql]:Failedtocallrefresh:Executionof'/sbin/statusmysql'returned1:status:UnabletoconnecttoUpstart:Failedtoconnecttosocket/com/ubuntu/upstart:ConnectionrefusedError:/Stage[main]/Main/Service[mysql]:Executionof'/sbin/statusmysql'returned1:status:UnabletoconnecttoUpstart:Failedtoconnecttosocket/com/ubuntu/upstart:Connectionrefused{code} Ofcourse,thisfailsbecauserunning{{/sbin/statusmysql}}fails.Thiscanbeverifiedbysimplyrunningitoncommandline. Nowthe{{apache2}}service,forinstance,getsdetectedcorrectly( it'salsonotan Upstart service,andUpstart commandsalsofail,butPuppettreats it apache2 asInitserviceandmanagesitcorrectly);but{{mysql}}breaks.Ididn'ttestalltheservicesonthesystem,butthe{{cups}}service,forinstance,alsobreaks , justlike{{mysql}}.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4030) puppet module install does not consider no_proxy env var
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4030 puppet module install does not consider no_proxy env var 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 (PUP-4210) Support rename in the augeas resource type
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4210 Support rename in the augeas resource type Change By: Kurt Wall QA Risk Probability: Low 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-4030) puppet module install does not consider no_proxy env var
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4030 puppet module install does not consider no_proxy env var Change By: Kurt Wall QA Risk Probability: Low 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-4536) Investigate and document differences between Ruby 1.9 and 2.1
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4536 Investigate and document differences between Ruby 1.9 and 2.1 Change By: Kylo Ginsberg Fix Version/s: PUP4.2.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-4477) Create a base agent upgrade module for rpm-based distro
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-4477 Create a base agent upgrade module for rpm-based distro 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 (FACT-981) Modules with facts cannot be tested with native facter
Title: Message Title Peter Huene created an issue Facter / FACT-981 Modules with facts cannot be tested with native facter Issue Type: Bug Affects Versions: FACT 3.0.0 Assignee: Peter Huene Created: 2015/05/07 12:16 PM Fix Versions: FACT 3.0.0 Priority: Normal Reporter: Peter Huene There are a number of modules on the forge with facts. Those modules have specs that attempt to stub parts of Facter to properly test those facts. Users are facing two issues: 1. There is no way to stub Facter such that it alters the behavior of confines. Previously a confine of confine :osfamily = 'bar' could be altered in a spec by stubbing Facter#fact or Facter::Util::Fact#value because Ruby Facter would call Facter.fact(name).value to get the fact's value for checking in the confine. To make this work in Facter 3, the native code that implements confines needs to call through the Ruby interface to obtain the fact. Doing so would enable rspec to return different values to the confine logic. 2. When native Facter was originally written, the Ruby API created by native Facter was marked as frozen to easily detect attempts to modify Facter from consumers like Puppet. However, this prevents module authors from stubbing Facter::Util::Resolution#which and
Jira (PUP-4210) Support rename in the augeas resource type
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4210 Support rename in the augeas resource type Change By: Kurt Wall QA Risk Assessment: Low 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-4210) Support rename in the augeas resource type
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4210 Support rename in the augeas resource type Change By: Kurt Wall QA Risk Severity: Low 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-4030) puppet module install does not consider no_proxy env var
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4030 puppet module install does not consider no_proxy env var Change By: Eric Thompson Assignee: QA 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-4030) puppet module install does not consider no_proxy env var
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4030 puppet module install does not consider no_proxy env var Change By: Kurt Wall QA Risk Assessment: Low 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-707) improve facter acceptance pre-suite for more platforms and git install
Title: Message Title Eric Thompson commented on FACT-707 Re: improve facter acceptance pre-suite for more platforms and git install it's a nice-to-have. i'm not sure why it's in a sprint. it may not really be applicable any more... 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-4520) Future parser is not correctly handling the default case of a case statement
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4520 Future parser is not correctly handling the default case of a case statement Change By: Kurt Wall QA Contact: 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-2576) Implement behavioral change in the crontab provider to allow more drastic purging
Title: Message Title Zee Alexander updated an issue Puppet / PUP-2576 Implement behavioral change in the crontab provider to allow more drastic purging Change By: Zee Alexander Comment: Cansomebodyclarifyformeexactlywhatthebehavioralchangeishere?It'snotcleartomefromreadingthetickets:( 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-3377) Puppet fails to manage file resources containing invalid UTF-8
Title: Message Title Josh Cooper commented on PUP-3377 Re: Puppet fails to manage file resources containing invalid UTF-8 This is a duplicate of PUP-1441. The - test argument implies -show_diff, and puppet will attempt to display the diff between the old file (containing binary data) and the new file. See comments in PUP-1441 for more detail. 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-1985) Allow class define parameters to reference earlier parameters
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-1985 Allow class define parameters to reference earlier parameters Change By: Owen Rodabaugh CS Priority: NeedsPriority Normal 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-4481) Figure out steps to release the module
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4481 Figure out steps to release the module Change By: Kylo Ginsberg Thiscanbedoneinparallelwith Resolvedby the moduledevelopment docthat[~alexander . Thismayberelevant johnson]puttogetherat : https://confluence.puppetlabs.com/display/DEL/ Supported+ Modules+Release+Process ButnotethatthatpageisforPEmodules,whichthisisn'tso...notsure. 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-4537) Transitory failure on rdoc specs in AppVeyor
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4537 Transitory failure on rdoc specs in AppVeyor Change By: Kylo Ginsberg 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-4531) create_resources() should deep merge the default parameters
Title: Message Title Henrik Lindberg commented on PUP-4531 Re: create_resources() should deep merge the default parameters We have extended the syntax for resources in the 3.x future parser that allows a lot more control over default values as well as the ability to set parameters from a hash. This was done to allow data transfomrations / merges etc. to be done prior to creating a resource. We think this is a better approach that turning every function into a swiss army knife of functionality. If you start doing merges and deep merges - how should they be done, what if it is an array inside, what if certain values should be kept or override, etc. (Sort of all the things the deep-merge gem does that is used with hiera and puppet lookup). I would rather add a general purpose hash deep merge function that adding deep merge functionality to the create_resources (if there is no such function already in stdlib). That would also be backwards compatible since it is up to users to call such functions and present the data the way the create_resources function (currently) expects them. 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-1300) Make acceptance tests compatible with Puppet 4.0
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1300 Make acceptance tests compatible with Puppet 4.0 putting the 2.3.x fix version back Change By: Wyatt Alt Fix Version/s: PDB2.3.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 (PDB-1471) Puppetdb 2.3.3 perfomance issue afer upgrading from 1.6
Title: Message Title Wyatt Alt commented on PDB-1471 Re: Puppetdb 2.3.3 perfomance issue afer upgrading from 1.6 Akos Hencz We released PDB 2.3.4 today to address PDB-1448 . Would you mind seeing if this issue still affects you? Wyatt 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-4540) Stock Puppet shipping with Ubuntu Vivid (3.7.2) has broken service type
Title: Message Title Victor Danilchenko commented on PUP-4540 Re: Stock Puppet shipping with Ubuntu Vivid (3.7.2) has broken service type I am not sure this is a duplicate, though it might be related. Is there a fix for PUP-4503 that I can grab and see if it fixes the problem? 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-4520) Future parser is not correctly handling the default case of a case statement
Title: Message Title Henrik Lindberg commented on PUP-4520 Re: Future parser is not correctly handling the default case of a case statement Kurt Wall regarding QA status - given that this has been broken for some time and not reported until now is an indication of people typically placing their default case last (probably because there historically was the very same problem in 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-4520) Future parser is not correctly handling the default case of a case statement
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4520 Future parser is not correctly handling the default case of a case statement Change By: Kurt Wall QA Risk Probability: High Low 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-4520) Future parser is not correctly handling the default case of a case statement
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4520 Future parser is not correctly handling the default case of a case statement Change By: Kurt Wall QA Risk Assessment: High Medium 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-4520) Future parser is not correctly handling the default case of a case statement
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4520 Future parser is not correctly handling the default case of a case statement Change By: Kurt Wall Sprint: Language2015-05- 13 27 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-4520) Future parser is not correctly handling the default case of a case statement
Title: Message Title Kurt Wall commented on PUP-4520 Re: Future parser is not correctly handling the default case of a case statement Henrik Lindberg Okay. I've dropped the risk level because it's been in the wild for some time. Thanks for the information! 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-4531) create_resources() should deep merge the default parameters
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4531 create_resources() should deep merge the default parameters 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-4520) Future parser is not correctly handling the default case of a case statement
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4520 Future parser is not correctly handling the default case of a case statement Change By: Henrik Lindberg Sprint: Language Client 2015-05- 27 13 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-1263) Round robin support for EC2 subnets
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1263 Round robin support for EC2 subnets replacing 2.3.x as the fix version. Change By: Wyatt Alt Fix Version/s: PDB2.3.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 (PDB-1448) 'replace facts' failing due to foreign key constraint issue
Title: Message Title Wyatt Alt commented on PDB-1448 Re: 'replace facts' failing due to foreign key constraint issue Simon Oxwell Duncan McNaught we released a fix today in PDB 2.3.4. Give it a shot when you can and let us know how it goes! Wyatt 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-4520) Future parser is not correctly handling the default case of a case statement
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4520 Future parser is not correctly handling the default case of a case statement Change By: Kurt Wall QA Risk Probability Reason: Unclearhowwidelyusedcase Thisbughasbeenpresentalongtimeandthis is thefirst(?)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 (PUP-4541) Create acceptance test for handling of default case in case statement in Puppet D
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4541 Create acceptance test for handling of default case in case statement in Puppet D Change By: Kurt Wall Summary: Createacceptancetestforhandlingofdefaultcaseincasestatement PP inPuppetD 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-4541) Create acceptance test for handling of default case in case statement in Puppet DSL
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4541 Create acceptance test for handling of default case in case statement in Puppet DSL Change By: Kurt Wall Summary: CreateacceptancetestforhandlingofdefaultcaseincasestatementinPuppet D DSL 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-1412) Update our gem dependencies, specifically rspec and company
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1412 Update our gem dependencies, specifically rspec and company adding 2.3.x back in Change By: Wyatt Alt Fix Version/s: PDB2.3.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-4541) Create acceptance test for handling of default case in case statement in Puppet DSL
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4541 Create acceptance test for handling of default case in case statement in Puppet DSL Change By: Kurt Wall Sprint: Language2015-05-27 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-4516) Agent does not stop with Ctrl-C
Title: Message Title Robert Schumann updated an issue Puppet / PUP-4516 Agent does not stop with Ctrl-C Change By: Robert Schumann Affects Version/s: PUP3.7.5 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-4534) Specify EPP templating language
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4534 Specify EPP templating language Change By: Kylo Ginsberg 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-4535) Node Classifier errors are not shown clearly to user
Title: Message Title Henrik Lindberg assigned an issue to Alex Jurkiewicz Puppet / PUP-4535 Node Classifier errors are not shown clearly to user Change By: Henrik Lindberg Assignee: AlexJurkiewicz 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-4535) Node Classifier errors are not shown clearly to user
Title: Message Title Henrik Lindberg commented on PUP-4535 Re: Node Classifier errors are not shown clearly to user Is this a regression from an earlier Puppet version? To me it looks like the API is that the command must return valid YAML as expected by the external NC terminus or exit with non 0 value to signal an error. When exit != 0, the error includes the exit status, and the output that was made to stdout. Does your external script exit with non 0 status? 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-1484) Memory leak when 'replace facts' failing
Title: Message Title Kenneth Barber commented on PDB-1484 Re: Memory leak when 'replace facts' failing Simon Oxwell actually, we're good - we did add a configuration item, I had just forgotten: http://docs.puppetlabs.com/puppetdb/2.3/configure.html#statements-cache-size Trying tuning that down, and seeing if that improves things memory-wise. 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-4347) Add test(s) for the File resource ignore attribute
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4347 Add test(s) for the File resource ignore attribute On Wed, May 6, 2015 at 11:04 AM, Eric Thompson (JIRA) !!! – Don't believe everything you think. 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-4347) Add test(s) for the File resource ignore attribute
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4347 Add test(s) for the File resource ignore attribute On Wed, May 6, 2015 at 11:04 AM, Eric Thompson (JIRA) !!! – Don't believe everything you think. 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-634) Facter emits Already evaluated... warnings
Title: Message Title Kurt Wall commented on FACT-634 Re: Facter emits Already evaluated... warnings Loic ANTOINE-GOMBEAUD You have two copies of facter installed in Ruby's lookup path. Remove one of them. 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-1508) Deprecate HSQLDB and change default database
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1508 Deprecate HSQLDB and change default database Issue Type: Task Assignee: Unassigned Created: 2015/05/07 5:20 AM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: Kenneth Barber Now we've announced the HSQLDB deprecation, time to do the necessary. This involes: a) Throwing deprecation messages when someone uses HSQLDB b) Changing documentation to reflect its deprecated status c) Changing the default to be postgresql in our shipped product - this requires some thought, new users might not understand the errors they get when there is no database setup yet. Add Comment
Jira (PUP-4540) Stock Puppet shipping with Ubuntu Vivid (3.7.2) has broken service type
Title: Message Title Melissa Stone commented on PUP-4540 Re: Stock Puppet shipping with Ubuntu Vivid (3.7.2) has broken service type If I'm wrong, I'm happy to reopen this ticket and evaluate further. I plan on starting work on PUP-4503 tomorrow, which includes evaluating a few fixes that community members have already put together. Those should all be linked in the other ticket if you're interested in trying them out 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-4542) mandatory attributes on defined resource types are not required for virtual/exported resources
Title: Message Title Geoff Williams created an issue Puppet / PUP-4542 mandatory attributes on defined resource types are not required for virtual/exported resources Issue Type: Bug Affects Versions: PUP 3.7.4 Assignee: Eric Sorenson Components: Language, UX Created: 2015/05/07 8:05 PM Environment: 3.7.4 (Puppet Enterprise 3.7.2) CentOS release 6.6 (Final) Priority: Normal Reporter: Geoff Williams Overview When declaring a virtual or exported resource using defined resource types, Puppet does not raise an error if mandatory attributes are not supplied. Testcase Create a single text file with the content below and run with puppet apply
Jira (PUP-4543) Document best practices for acceptance tests with puppet 4
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4543 Document best practices for acceptance tests with puppet 4 Issue Type: Task Assignee: Unassigned Created: 2015/05/07 10:37 PM Fix Versions: PUP 4.x Priority: Normal Reporter: Kylo Ginsberg In an AIO world https://github.com/puppetlabs/puppet/blob/master/docs/acceptance_tests.md may need updates for developer workflows, especially testing code from a developer branch. It sounds like William Hopper, Eric Thompson, and Josh Cooper may have relevant experience here. I'm giving this 3 story points and putting it out a few sprints so that we can dedicate appropriate attention to it. Also, it may make sense to spawn additional tickets for improvement as part of this task. Add Comment
Jira (PUP-4535) Node Classifier errors are not shown clearly to user
Title: Message Title Alex Jurkiewicz commented on PUP-4535 Re: Node Classifier errors are not shown clearly to user Sorry, I'm not sure if this a regression. The stdout is there, I opened this bug to cover: What's with the undefined method `inject' wrapping? I don't think stderr is captured, although I didn't try to replicate 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 (PUP-4536) Investigate and document differences between Ruby 1.9 and 2.1
Title: Message Title Christopher Price created an issue Puppet / PUP-4536 Investigate and document differences between Ruby 1.9 and 2.1 Issue Type: Task Assignee: Kylo Ginsberg Components: Client, Puppet Server Created: 2015/05/07 6:55 AM Priority: Normal Reporter: Christopher Price We have some documentation about the fact that we are (or soon will be) shipping MRI Ruby 2.1 in our AIO/PE packages. This Ruby interpreter is used to run all client side applications, but it is not used on the server. The current stable version of JRuby is (most) compatible with the MRI Ruby 1.9 API, and that is the mode we use for Puppet Server. JRuby 9000 will include 2.1 syntax compatibility, but we're at least 6 months out from that being stable enough to consider including in Puppet Server. Therefore, in the meantime, we probably need to do two things: 1. Go through our docs and make sure that where ever we are mentioning Ruby 2.1, we're making it very clear that that is for the client side only. 2. Have someone sift through the Ruby stdlib API changelog and see what kinds of things changed between 1.9 and 2.1. If there is anything significant, that is likely to be used in a custom user extension, we may need to document some guidelines about making sure the server-side parts of people's user extensions are written to be compatible with 1.9 syntax for now. We probably need to
