Jira (PUP-4910) Make `puppet module generate` compatible with strings
Title: Message Title Kylo Ginsberg moved an issue Puppet / PUP-4910 Make `puppet module generate` compatible with strings Change By: Kylo Ginsberg Fix Version/s: PDOC0.3.0 Fix Version/s: PUP4.2.1 Issue Type: Task Improvement Key: PDOC PUP - 16 4910 Project: Puppet Strings Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails
Jira (PUP-4910) Make `puppet module generate` compatible with strings
Title: Message Title Kylo Ginsberg commented on PUP-4910 Re: Make `puppet module generate` compatible with strings Note: this was worked on as PDOC-16 and the commit message references that ticket. I moved the ticket to PUP so that we could tag it with a puppet release version. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4889) Ankeny Direct Puppet
Title: Message Title Kylo Ginsberg commented on PUP-4889 Re: Ankeny Direct Puppet Steve Barlow this is the epics for Direct Puppet in Ankeny. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1136) Move Ruby API to Leatherman
Title: Message Title Maggie Dreyer created an issue Facter / FACT-1136 Move Ruby API to Leatherman Issue Type: Task Assignee: Maggie Dreyer Created: 2015/07/21 9:31 AM Priority: Normal Reporter: Maggie Dreyer The Ruby API has been extracted to Leatherman. Update Facter to use Leatherman's version. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (FACT-1137) facter productname fails on CentOS
Title: Message Title
Fabrice Bacchella updated an issue
Facter / FACT-1137
facter productname fails on CentOS
Change By:
Fabrice Bacchella
Environment:
{code}~#lsb_release-aLSBVersion: :core-4.0-amd64:core-4.0-ia32:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-ia32:printing-4.0-noarchDistributorID: CentOSDescription: CentOSrelease5.11(Final)Release: 5.11Codename: Final{code}
Idon'tgettheproductnameonaallmyCentos5:{code}~#dmidecode-ssystem-product-nameSUNFIREX4150~# echo$( /opt/puppetlabs/bin/facterproductname ) {code}or:{code}~#dmidecode-ssystem-product-nameProLiantDL140G3~#echo$(/opt/puppetlabs/bin/facterproductname){code} ButonaScientificLinux6:{code}~#/opt/puppetlabs/bin/facterproductnameProLiantDL140G3{code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-1817) PR (1552): (maint) rollup 2.3.x to stable - mullr
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1817 PR (1552): (maint) rollup 2.3.x to stable - mullr Change By: Kenneth Barber Fix Version/s: PDB2.3.x Fix Version/s: PDB3.0.x Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4909) Re-upload Puppet 4.2.0 to Rubygems
Title: Message Title Kylo Ginsberg commented on PUP-4909 Re: Re-upload Puppet 4.2.0 to Rubygems This was merged back to stable, so will be in the forthcoming 4.2.1. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1731) Disable dist upgrades on acceptance tests
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1731 Disable dist upgrades on acceptance tests Change By: Kenneth Barber Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4909) Re-upload Puppet 4.2.0 to Rubygems
Title: Message Title Daniele Sluijters created an issue Puppet / PUP-4909 Re-upload Puppet 4.2.0 to Rubygems Issue Type: Bug Affects Versions: PUP 4.2.0 Assignee: Unassigned Created: 2015/07/21 8:25 AM Priority: Normal Reporter: Daniele Sluijters When trying to install Puppet 4.2.0 and Hiera 3.0.0 from gems you get the following conflict: Bundler could not find compatible versions for gem hiera: In Gemfile: puppet (~ 4.2) ruby depends on
Jira (PUP-4911) Parameters on exported resources consiting of an array with a single element are de-arrayified
Title: Message Title
Reinhard Vicinus created an issue
Puppet / PUP-4911
Parameters on exported resources consiting of an array with a single element are de-arrayified
Issue Type:
Bug
Affects Versions:
PUP 3.8.1
Assignee:
Unassigned
Created:
2015/07/21 8:59 AM
Priority:
Normal
Reporter:
Reinhard Vicinus
If a exported resource with a parameter consisting of an array with a single value is defined on one puppet node and then collected on another puppet node the array with the single value is de-arrayified.
Example:
define profiles::vres ( $dummy, ) { if is_array($dummy) { notify { array_$title: message = join($dummy, '_'), }
} else { notify { nonarray_$title: message = NOT AN ARRAY: $dummy, }
} }
on one server:
@@profiles::vres { arraywithonevalue: dummy = [ a, ], }
on another server:
Profiles::Vres | |
result of collecting the resource:
Notice: NOT AN ARRAY: a Notice: /Stage[main]/Roles::Collectvres/Profiles::Vres[arraywithonevalue]/Notify[nonarray_arraywithonevalue]/message: defined 'message' as 'NOT AN ARRAY: a'
This is probably related to
PUP-1299
Jira (PUP-4910) Make `puppet module generate` compatible with strings
Title: Message Title Hailee Kenney updated an issue Puppet / PUP-4910 Make `puppet module generate` compatible with strings Change By: Hailee Kenney Release Notes Summary: Previously,thePMTgeneratedamodulethatdidn'tworkwithstringsoutofthebox.NowinPuppet4.2.1,itwillgenerateamodulethata)HascommentsinMarkdown(oursuggestedstyle)b)hasa.gitignorethatwillignorethe.yarddocdirectorywhichshouldnotbecommittedandc)addsa.yardoptsfilewhichtellsYARDtorunwiththeMarkdownoption Release Notes: NewFeature Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1137) facter productname fails on CentOS
Title: Message Title Fabrice Bacchella created an issue Facter / FACT-1137 facter productname fails on CentOS Issue Type: Bug Affects Versions: FACT 3.0.1 Assignee: Unassigned Created: 2015/07/21 9:37 AM Environment: ~# lsb_release -a LSB Version: :core-4.0-amd64:core-4.0-ia32:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-ia32:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-ia32:printing-4.0-noarch Distributor ID: CentOS Description: CentOS release 5.11 (Final) Release: 5.11
Jira (PUP-4837) Tag the release and create packages
Title: Message Title Melissa Stone commented on PUP-4837 Re: Tag the release and create packages tag 4.2.1 Tagger: Melissa Stone meli...@puppetlabs.com Date: Tue Jul 21 10:08:09 2015 -0700 4.2.1 -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org iQIcBAABCgAGBQJVrnx5AAoJEBBUt6JL1uww1WcP/04nK2QWxIw2n1xiR86e0Dnt b8vingncqAKe4zTqY7j0xYcisV9LTzqZlOKe8g0PfI21u/KPd/cIeagrCrPh216h
Jira (PUP-4837) Tag the release and create packages
Title: Message Title Melissa Stone commented on PUP-4837 Re: Tag the release and create packages gem and tar archives available at http://builds.puppetlabs.lan/puppet/4.2.1/ Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1100) Merge master into stable
Title: Message Title Kylo Ginsberg commented on FACT-1100 Re: Merge master into stable Not applicable to a Z release. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1114) add pre-suite for acceptance tests against PE-only platforms
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1114 add pre-suite for acceptance tests against PE-only platforms Change By: Kylo Ginsberg Release Notes: NotNeeded Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1097) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Kylo Ginsberg commented on FACT-1097 Re: Is there a JIRA ticket targeted at the release for every commit? COMMIT TOKENS NOT FOUND IN JIRA (OR NOT WITH FIX VERSION OF FACT 3.0.2) FACT-1114 ALL ISSUES WERE FOUND IN GIT FACT-1114 is WIP but acceptance only. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4912) Puppet on french version of windows
Title: Message Title Gabriel Veilleux created an issue Puppet / PUP-4912 Puppet on french version of windows Issue Type: Bug Affects Versions: PUP 3.4.3 Assignee: Unassigned Created: 2015/07/21 10:50 AM Environment: Windows XP Professional 32 bits Service Pack 3 Priority: Major Reporter: Gabriel Veilleux Original Estimate: 1 hour Remaining Estimate: 1 hour We have trouble with puppet under french version of windows XP. I want to manage users account and when I try to type puppet resource user, it give this error message: Error: Could not run: invalid byte sequence in US-ASCII
Jira (FACT-1137) facter productname fails on CentOS
Title: Message Title Fabrice Bacchella commented on FACT-1137 Re: facter productname fails on CentOS ~# /opt/puppetlabs/bin/facter -d productname 21 2015-07-21 20:09:00.986567 INFO puppetlabs.facter - executed with command line: -d productname. 2015-07-21 20:09:00.987506 INFO puppetlabs.facter - ruby loaded from /opt/puppetlabs/puppet/lib/libruby.so.2.1.0. 2015-07-21 20:09:00.994273 INFO puppetlabs.facter - using ruby version 2.1.6 to resolve custom facts. 2015-07-21 20:09:01.033352 INFO puppetlabs.facter - requested queries: productname. 2015-07-21 20:09:01.033631 DEBUG puppetlabs.facter - fact facterversion has resolved to 3.0.1. 2015-07-21 20:09:01.034212 DEBUG puppetlabs.facter - skipping external facts for /opt/puppetlabs/facter/facts.d: No such file or directory 2015-07-21 20:09:01.034329 DEBUG puppetlabs.facter - skipping external facts for /etc/facter/facts.d: No such file or directory 2015-07-21 20:09:01.034458 DEBUG puppetlabs.facter - skipping external facts for /etc/puppetlabs/facter/facts.d: No such file or directory
Jira (PUP-4834) Merge master into stable
Title: Message Title Kylo Ginsberg commented on PUP-4834 Re: Merge master into stable Doesn't apply to a Z release. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1074) acceptance: facter should honor defaults in addition to --external-dir
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1074 acceptance: facter should honor defaults in addition to --external-dir Change By: Kylo Ginsberg Fix Version/s: FACT3.0.2 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1074) acceptance: facter should honor defaults in addition to --external-dir
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1074 acceptance: facter should honor defaults in addition to --external-dir Change By: Kylo Ginsberg Release Notes: NotNeeded Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1137) facter productname fails on CentOS
Title: Message Title Peter Huene commented on FACT-1137 Re: facter productname fails on CentOS Fabrice Bacchella Thanks for reporting this. Would you mind attaching the output of facter -d productname? Perhaps the debug output has some insight to the problem. Also, could you cat /sys/class/dmi/id/product_name? This is the file that facter is using to retrieve the fact. Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1137) facter productname fails on CentOS
Title: Message Title Peter Huene assigned an issue to Peter Huene Facter / FACT-1137 facter productname fails on CentOS Change By: Peter Huene Assignee: PeterHuene Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1104) Smoke test packages
Title: Message Title Kylo Ginsberg commented on FACT-1104 Re: Smoke test packages We don't have standalone packages for facter 3. So nothing to do here. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1103) Tag the release and create packages
Title: Message Title Melissa Stone commented on FACT-1103 Re: Tag the release and create packages tar archive available at http://builds.puppetlabs.lan/facter/3.0.2/ tag 3.0.2 Tagger: Melissa Stone meli...@puppetlabs.com Date: Tue Jul 21 10:31:05 2015 -0700 3.0.2 -BEGIN PGP SIGNATURE- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org iQIcBAABCgAGBQJVroHZAAoJEBBUt6JL1uww8OoQALMkm42PV1SW3fY91ffRf3H2
Jira (PUP-4831) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Kylo Ginsberg commented on PUP-4831 Re: Is there a JIRA ticket targeted at the release for every commit? COMMIT TOKENS NOT FOUND IN JIRA (OR NOT WITH FIX VERSION OF PUP 4.2.1) PDOC-16 PUP-4848 RE-5087 ALL ISSUES WERE FOUND IN GIT Re those three: PDOC-16 was moved to PUP-4910 PUP-4848 was a 3.8 fix which was merged up to 4.x but is a no-op in 4.2.1 (zero code change) RE-5087 was a SLES 10 packaging change (PE platform)
Jira (PUP-4835) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Kylo Ginsberg commented on PUP-4835 Re: Is the Jira tidy-up done for this release and prepared for the next one? Puppet 4.2.2 and 4.3.0 both exist. Introduced in puppet 4.2.1: https://tickets.puppetlabs.com/issues/?filter=15116 Fixed for puppet 4.2.1: https://tickets.puppetlabs.com/issues/?filter=15117 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4837) Tag the release and create packages
Title: Message Title Kylo Ginsberg commented on PUP-4837 Re: Tag the release and create packages The SHA is 62f7876dc7225f901aa934524fe5003e228fc746. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4838) Smoke test packages
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4838 Smoke test packages Change By: Kylo Ginsberg Proceduremayvarybyprojectandpointinthereleasecycle.Askaround.Ingeneralthis We should happenonavarietyofplatforms,i.e.oneortwoeachofkindofpackagewecreate(i.e.,gem,dmg,msi,deb,rpm,etc).ForPuppet,ouracceptancesuitenowtestsservicescripts,andondebian,apassengermaster.Manualsmoketestingcanthereforebelimited onlyneed to otherpackageformatsthandebandrpm.LightertestingofZreleasesisacceptable.*AddalinktothePackagesrepositorythatyoureceivefromtheTagandcreatepackagessubtask*Pingfolksonyourteam testgems for helpwithdifferentplatforms.*Whenyoupickupaplatform,pleaseleaveacommentbelowthatyouaretestingit.Whenitlooksgood,leaveanothercomment,preferablywithacodesnippetshowingthecommandsexecutedandtheiroutput.*Whenallplatformspickedhavebeensmoketested,move this tickettodone release . IMPORTANT:PleaseeditthedescriptionofthisticketandremoveExample:below.Edittheplatformstosmoketeston,andthesmoketestprocedure.Example:Smoketestplatforms:*picksomeplatformssuchas*Windows2003/2008/2012(msi)*Solaris10/11(tarballorgem?)*OSX(dmg)*(NoteifyouaresmoketestingPuppetandpickanrpmordebbasedplatform,concentrateontestingagemortarball,sinceacceptanceshouldhaveadequatelysmoketestedthosepackages.)*RHEL/CentOS5/6/7*Fedora19/20*Debian6/7*Ubuntu10.04/12.04/14.04Smoketestprocedure:*Start/stop/restartamaster(iftheplatformsupportsthat)*Start/stop/restartanagent*Help/man*WriteandrunsomemanifestsDependencies:*Tagandcreatepackages*ForWindowsMSIs-Pushtag Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (FACT-1088) Validate on Ubuntu lucid
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1088 Validate on Ubuntu lucid Change By: Kylo Ginsberg Release Notes: NotNeeded Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1088) Validate on Ubuntu lucid
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1088 Validate on Ubuntu lucid Change By: Kylo Ginsberg Fix Version/s: FACT3.1.0 Fix Version/s: FACT3.0.2 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1087) Validate on sles
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1087 Validate on sles Change By: Kylo Ginsberg Release Notes: NotNeeded Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1087) Validate on sles
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1087 Validate on sles Change By: Kylo Ginsberg Fix Version/s: FACT3.1.0 Fix Version/s: FACT3.0.2 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1101) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Kylo Ginsberg commented on FACT-1101 Re: Is the Jira tidy-up done for this release and prepared for the next one? FACT 3.0.3 and FACT 3.1.0 already exist. Introduced in facter 3.0.2: https://tickets.puppetlabs.com/issues/?filter=15118 Fixes for facter 3.0.2: https://tickets.puppetlabs.com/issues/?filter=15119 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4002) Add mechanism for providers to store state during catalog application
Title: Message Title Michael Smith commented on PUP-4002 Re: Add mechanism for providers to store state during catalog application Kylo Ginsberg is this something we want to consider when we start working on clarifying the types and providers API? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3829) pip package provider is broken on EL (where osfamily is RedHat)
Title: Message Title Josh Samuelson commented on PUP-3829 Re: pip package provider is broken on EL (where osfamily is RedHat) Was this tested with CentOS 6.6 and 3.8.1? I just ran into the issue and had to use the symlink workaround. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1136) Move Ruby API to Leatherman
Title: Message Title Kylo Ginsberg commented on FACT-1136 Re: Move Ruby API to Leatherman This is in the AM 2015-07-22 sprint but should probably have been in Client 2015-07-22. I won't fix it now since the sprint is ending in a few hours, but (assuming there isn't some reason I'm missing) it should probably be pulled into the upcoming Client 2015-08-05 sprint. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4002) Add mechanism for providers to store state during catalog application
Title: Message Title Henrik Lindberg commented on PUP-4002 Re: Add mechanism for providers to store state during catalog application Michael Smith This is very much part of what a new types/handler/provider should be able to do. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4905) Add feature switch for appmgmt
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4905 Add feature switch for appmgmt Change By: Henrik Lindberg Summary: Feature Addfeature switchforappmgmt Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4905) Add feature switch for appmgmt
Title: Message Title Henrik Lindberg commented on PUP-4905 Re: Add feature switch for appmgmt So, the most difficult decision first: what is the name of the switch? - xnode=true or -app_management=true ? I like the shorter. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4813) Can't generate exit codes 4 or 6 with puppet agent -test
Title: Message Title Branan Riley commented on PUP-4813 Re: Can't generate exit codes 4 or 6 with puppet agent -test I've sent a couple of emails to puppet dev. Marking this blocked and leaving assigned to myself to follow-up. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4913) Unable to update authorized_keys on EL7
Title: Message Title Shawn LoPresto created an issue Puppet / PUP-4913 Unable to update authorized_keys on EL7 Issue Type: Bug Affects Versions: PUP 3.8.1 Assignee: Kylo Ginsberg Components: Client Created: 2015/07/21 12:09 PM Environment: CentOS 7 and RHEL7 x86_64 Priority: Normal Reporter: Shawn LoPresto Puppet is unable to update user authorized key files, but default on EL7. Same error encountered on each attempt. Workaround has been to cd into each users home directory and run puppet test from there. Doing this for each server becomes a bit tedious and even prevents access to a system which only received credentials via puppet. Notice: /Stage[main]/Tui_accounts::Web_deployment/Account[tui-deployment]/Ssh_authorized_key[tui-deployment]/ensure: created Error: Puppet::Util::FileType::FileTypeFlat could not write /home/tui-deployment/.ssh/authorized_keys: could not find a temporary directory Error:
Jira (FACT-1137) facter productname fails on CentOS
Title: Message Title Peter Huene commented on FACT-1137 Re: facter productname fails on CentOS It looks like Facter has a dependency on kernel versions 2.6.23 (CONFIG_DMIID = Y) for this to work. On my Vagrant VM with Centos 5.11, the kernel is 2.6.18. For Facter 2.x run as root, it correctly returns the product name because it spawns dmidecode, and that directly accesses the underlying SMBIOS table and therefore works. Facter 3.x works without root provided that the the kernel is at least 2.6.23 because it just reads from what the kernel provides it without a dmidecode dependency. Let me see if there's something we can do to support these older kernels. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4905) Add feature switch for appmgmt
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4905 Add feature switch for appmgmt Change By: Henrik Lindberg Issue Type: Task NewFeature Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4905) Add feature switch for appmgmt
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4905 Add feature switch for appmgmt Change By: Henrik Lindberg Fix Version/s: PUP4.3.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4905) Add feature switch for appmgmt
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4905 Add feature switch for appmgmt Change By: Henrik Lindberg Scrum Team: Language Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4901) puppet-splunk doesn't update spunk
Title: Message Title Kyle Decot updated an issue Puppet / PUP-4901 puppet-splunk doesn't update spunk Change By: Kyle Decot Priority: Normal Major Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4886) puppet_agent module doesn't touch puppet.conf settings outside an INI section
Title: Message Title Michael Smith updated an issue Puppet / PUP-4886 puppet_agent module doesn't touch puppet.conf settings outside an INI section Change By: Michael Smith Fix Version/s: puppet_agent1.0.0 Fix Version/s: puppet_agent0.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4478) Extend upgrade module to deb platforms
Title: Message Title Michael Smith updated an issue Puppet / PUP-4478 Extend upgrade module to deb platforms Change By: Michael Smith Fix Version/s: puppet_agent0.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4677) Prep for a how to upgrade doc
Title: Message Title Michael Smith updated an issue Puppet / PUP-4677 Prep for a how to upgrade doc Change By: Michael Smith Fix Version/s: puppet_agent0.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4677) Prep for a how to upgrade doc
Title: Message Title Michael Smith updated an issue Puppet / PUP-4677 Prep for a how to upgrade doc Change By: Michael Smith Fix Version/s: puppet_agent0.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4886) puppet_agent module doesn't touch puppet.conf settings outside an INI section
Title: Message Title Michael Smith commented on PUP-4886 Re: puppet_agent module doesn't touch puppet.conf settings outside an INI section To see a change in the file, you'd need to use one of the settings pruned by the puppet_agent module, listed in https://github.com/puppetlabs/puppetlabs-puppet_agent/blob/master/manifests/prepare/puppet_config.pp, such as modulepath. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4914) Puppet server throwing 'java.nio.channels.WritePendingException: null' intermittently
Title: Message Title Brian Rak created an issue Puppet / PUP-4914 Puppet server throwing 'java.nio.channels.WritePendingException: null' intermittently Issue Type: Bug Assignee: Unassigned Created: 2015/07/21 1:07 PM Environment: CentOS 6.6 x86_64 puppetserver-2.1.1-1.el6.noarch Priority: Normal Reporter: Brian Rak I'm running Puppet server with a large (1000) number of nodes, the puppet server software is intermittently throwing this error: pre 2015-07-21 16:00:52,904 WARN [o.e.j.s.HttpChannel] /production/catalog/x java.nio.channels.WritePendingException: null at org.eclipse.jetty.server.HttpConnection$SendCallback.reset(HttpConnection.java:624) ~[puppet-server-release.jar:na] at org.eclipse.jetty.server.HttpConnection$SendCallback.access$100(HttpConnection.java:594) ~[puppet-server-release.jar:na] at org.eclipse.jetty.server.HttpConnection.send(HttpConnection.java:479) [puppet-server-release.jar:na] at org.eclipse.jetty.server.HttpChannel.sendResponse(HttpChannel.java:768) ~[puppet-server-release.jar:na] at org.eclipse.jetty.server.HttpChannel.write(HttpChannel.java:801) ~[puppet-server-release.jar:na] at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:142) ~[puppet-server-release.jar:na] at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:135) ~[puppet-server-release.jar:na] at org.eclipse.jetty.server.HttpOutput.close(HttpOutput.java:166) ~[puppet-server-release.jar:na] at org.eclipse.jetty.server.HttpWriter.close(HttpWriter.java:49) ~[puppet-server-release.jar:na] at java.io.PrintWriter.close(PrintWriter.java:339) ~[na:1.8.0_51] at ring.util.servlet$set_body.invoke(servlet.clj:86) ~[na:na] at
Jira (FACT-1121) Move execution class to Leatherman
Title: Message Title Michael Smith updated an issue Facter / FACT-1121 Move execution class to Leatherman Change By: Michael Smith Fix Version/s: FACT3.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4690) Migrate privatedir, privatekeydir, and publickeydir
Title: Message Title Michael Smith updated an issue Puppet / PUP-4690 Migrate privatedir, privatekeydir, and publickeydir Change By: Michael Smith Fix Version/s: puppet_agent0.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4468) puppet_agent module
Title: Message Title Michael Smith updated an issue Puppet / PUP-4468 puppet_agent module Change By: Michael Smith Fix Version/s: puppet_agent1.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4808) Enable testing puppet_agent module with full build matrix in jenkins-modules
Title: Message Title Michael Smith updated an issue Puppet / PUP-4808 Enable testing puppet_agent module with full build matrix in jenkins-modules Change By: Michael Smith Fix Version/s: puppet_agent0.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4479) Extend upgrade module to windows
Title: Message Title Michael Smith updated an issue Puppet / PUP-4479 Extend upgrade module to windows Change By: Michael Smith Fix Version/s: puppet_agent0.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4658) Agent migration for mco configuration should prefer new plugin location
Title: Message Title Michael Smith updated an issue Puppet / PUP-4658 Agent migration for mco configuration should prefer new plugin location Change By: Michael Smith Fix Version/s: puppet_agent0.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.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 updated an issue Puppet / PUP-4477 Create a base agent upgrade module for rpm-based distro Change By: Michael Smith Fix Version/s: puppet_agent0.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4746) MCollective config files with multiple libdir or plugin.yaml definitions can be updated incorrectly
Title: Message Title Michael Smith updated an issue Puppet / PUP-4746 MCollective config files with multiple libdir or plugin.yaml definitions can be updated incorrectly Change By: Michael Smith Fix Version/s: puppet_agent0.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4055) Support DNF package manager (yum successor)
Title: Message Title Erik L. commented on PUP-4055 Re: Support DNF package manager (yum successor) Rick's patch does help to fix some of the error messages resulting from calling yum instead of dnf. However puppet is still trying to delete packages that are already deleted, so these errors remain: Error: Execution of '/bin/dnf -y erase NetworkManager' returned 1: No match for argument: NetworkManager Error: No packages marked for removal. Error: /Stage[main]/Profile::Base/Package[NetworkManager]/ensure: change from absent to purged failed: Execution of '/bin/dnf -y erase NetworkManager' returned 1: No match for argument: NetworkManager Error: No packages marked for removal. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4055) Support DNF package manager (yum successor)
Title: Message Title Erik L. commented on PUP-4055 Re: Support DNF package manager (yum successor) Please note that there is a subtle difference between yum and dnf here: yum remove -y nonexistingpackage No match for argument: nonexistingpackage Error: No packages marked for removal. echo $? 0 versus: dnf remove -y nonexistingpackage No match for argument: nonexistingpackage Error: No packages marked for removal. echo $? 1 Whoops, maybe puppet was used to calling yum remove without checking if the package was even installed or not, counting on the zero return value if it was a no-op. But dnf actually gives a non-zero return value in that same situation. Imho it would be best to actually check if the package is installed anyway, but with dnf this becomes more of a necessity. Either that or puppet has to ignore the non-zero return value, which seems worse. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. 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 (PDB-1813) Run the state-overview queries as a single query.
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-1813 Run the state-overview queries as a single query. Change By: Andrew Roetker Sprint: PuppetDB2015-08-12 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4914) Puppet server throwing 'java.nio.channels.WritePendingException: null' intermittently
Title: Message Title
Brian Rak updated an issue
Puppet / PUP-4914
Puppet server throwing 'java.nio.channels.WritePendingException: null' intermittently
Change By:
Brian Rak
I'mrunningPuppetserverwithalarge(1000)numberofnodes,thepuppetserversoftwareisintermittentlythrowingthiserror: pre {noformat}
Jira (PUP-4886) puppet_agent module doesn't touch puppet.conf settings outside an INI section
Title: Message Title John Duarte commented on PUP-4886 Re: puppet_agent module doesn't touch puppet.conf settings outside an INI section Nicholas Fagerlund can you provide a scenario for testing this behavior? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4780) enhance versioncmp() error checking as it only accepts strings
Title: Message Title Hailee Kenney updated an issue Puppet / PUP-4780 enhance versioncmp() error checking as it only accepts strings Change By: Hailee Kenney Fix Version/s: PUP5.0.0 Fix Version/s: PUP4.3.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4780) enhance versioncmp() error checking as it only accepts strings
Title: Message Title Hailee Kenney commented on PUP-4780 Re: enhance versioncmp() error checking as it only accepts strings Merged into master in 761b4f5 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1121) Move execution class to Leatherman
Title: Message Title Michael Smith assigned an issue to qa Facter / FACT-1121 Move execution class to Leatherman Change By: Michael Smith Status: Readyfor CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4886) puppet_agent module doesn't touch puppet.conf settings outside an INI section
Title: Message Title Nicholas Fagerlund commented on PUP-4886 Re: puppet_agent module doesn't touch puppet.conf settings outside an INI section Yeah, Michael Smith has it. ssldir = /var/lib/puppet/ssl \[main] server = qxbxjv9ocpn43mr.delivery.puppetlabs.net This will leave the old ssldir in place instead of scrubbing it. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4886) puppet_agent module doesn't touch puppet.conf settings outside an INI section
Title: Message Title Shaigy Nixon commented on PUP-4886 Re: puppet_agent module doesn't touch puppet.conf settings outside an INI section Validated on centos-7 on puppet_agent module SHA:29e776a1b64867f5dcf42dc34a0fd56d9cc2a873 Steps to reproduce: 1) Install 3.x on Master and Agent 2) Upgrade Master to 4.x 3) Install puppet_agent module on Master 4) On Agent, modify puppet.conf and add values for 'preview_outputdir' and 'modulepath' globally as well as inside 'main' section. 5) Classify the Agent node with puppet_agent module 6) After classification, 'preview_outputdir' and 'modulepath' values should be pruned from the new puppet.conf on Agent from both global and 'main' sections. (Before the fix, the global settings were left untouched and only settings under 'main' section were removed) puppet.conf on agent before applying puppet_agent module [root@a8bmd0kkpukbt4l ~]# cat /etc/puppet/puppet.conf preview_outputdir = /tmp/preview modulepath = /tmp/modules [main] server = xqh7ofj91ykp0yy.delivery.puppetlabs.net # The Puppet log directory.
Jira (PUP-4886) puppet_agent module doesn't touch puppet.conf settings outside an INI section
Title: Message Title Shaigy Nixon updated an issue Puppet / PUP-4886 puppet_agent module doesn't touch puppet.conf settings outside an INI section Change By: Shaigy Nixon QA Risk Severity: Medium QA Risk Probability: Medium QA Risk Assessment: Medium QA Highest Test Level: Acceptance QA Risk Assessment Reason: Affectsexistingconfigurationonupgrade QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (FACT-1111) Restore 'facter --puppet'
Title: Message Title Sean Griffin commented on FACT- Re: Restore 'facter --puppet' Additional test cases: 1. pluginsynced external fact 2. facter cmds in a system absent puppet 1. pluginsynced external fact: tested on centos-7-x86_64 On the Master root directory I (1) created a module: hellofact, containing an external fact, hellofact.rb, which return string Hello facter!, (2) built it with 'puppet module build hellofact', (3) installed it with install hellofact/pkg/sean-hellofact-0.1.0.tgz, (4) called 'puppet agent -t'. On the agent node I also called 'puppet agent -t'. On both agent and master, facter behaves the same way when fetching the external fact hellofact. When called with --puppet, the fact is displayed. When called without --puppet, the fact is not displayed. [root@t08kvwquaxnqa35 ~]# facter -p hellofact Hello facter! [root@t08kvwquaxnqa35 ~]# facter hellofact [root@t08kvwquaxnqa35 ~]# 2. facter cmds in a system absent puppet Running facter with no puppet. Tested on fedora-20-x86_64 stable branch 7/22/15 2200 3.0.1 (commit fe9df8a0719361c88fb3726dc535d04b80759871) In this test, I compiled facter on a Fedora vm and ran it without puppet installed. facter -p generated a the following warning to stderr but did not cause failure (very nice): 2015-07-20 22:30:31.402088 WARN puppetlabs.facter - Could not load puppet; some facts may be unavailable: cannot load such file – puppet Except for that, the output from invocations with and without the -p option are the same. Tested with --custom-dir, --external-dir
Jira (PUP-3501) upstart provider fails with non-ASCII characters in job conf file with a non-UTF8 locale
Title: Message Title Yama commented on PUP-3501 Re: upstart provider fails with non-ASCII characters in job conf file with a non-UTF8 locale OK, It seem that /etc/environment doesn't work then the system has rebooted. You need to manually restart puppet again to get it working. I think the only option is the puppet init script. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4188) Agent applies broken cached catalog when puppetserver dies mid-run
Title: Message Title Rmi commented on PUP-4188 Re: Agent applies broken cached catalog when puppetserver dies mid-run Hello, Do you have any updates on this bug ? It has just occured on 60 production servers on my infrastructure. Puppet servers : 3.7.3 Puppet clients : 3.7.2 to 3.7.5 Does usecacheonfailure = false is a working workarround for this issue ? Thanks, Regards. Example Jul 18 07:02:18 was06-prp puppet-agent[3985]: Could not retrieve catalog from remote server: execution expired Jul 18 07:02:19 was06-prp puppet-agent[3985]: Using cached catalog Jul 18 07:02:21 was06-prp puppet-agent[3985]: (/Stage[main]/Common_cloud::Package/File[/etc/cron-apt/action.d]) Failed to generate additional resources using 'eval_generate': Could not intern_multiple from text/pson: undefined method `collect' for #Puppet::Resource::Catalog:0x7f8fddcbbe38 Jul 18 07:03:33 was06-prp puppet-agent[3985]: (/Stage[main]/Common_cloud::Package/File[/etc/cron-apt/action.d]) Could not evaluate: Could not retrieve file metadata for puppet:///modules/common_cloud/cron-apt/action.d: Could not intern from text/pson: Paths must be fully qualified Jul 18 07:03:48 was06-prp puppet-agent[3985]: (/Stage[main]/Apt_mbs::Manage_repo/File[/etc/apt/sources.list]/ensure) ensure changed 'file' to 'directory' Jul 18 07:03:55 was06-prp puppet-agent[3985]: (/Stage[main]/Manage_ssh::Config/File[/etc/issue.net]) Could not evaluate: Could not retrieve file
Jira (PUP-3501) upstart provider fails with non-ASCII characters in job conf file with a non-UTF8 locale
Title: Message Title Yama commented on PUP-3501 Re: upstart provider fails with non-ASCII characters in job conf file with a non-UTF8 locale OK, I need to update this again. When I set this in my /etc/init.d/puppet and reboot the machine it doesn't work also. Restarting the puppet service makes it work again. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3501) upstart provider fails with non-ASCII characters in job conf file with a non-UTF8 locale
Title: Message Title Yama updated an issue Puppet / PUP-3501 upstart provider fails with non-ASCII characters in job conf file with a non-UTF8 locale Change By: Yama Priority: Minor Normal Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1817) PR (1552): (maint) rollup 2.3.x to stable - mullr
Title: Message Title gepetto-bot commented on PDB-1817 Re: PR (1552): (maint) rollup 2.3.x to stable - mullr Pull request (maint) rollup 2.3.x to stable has been closed. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-700) java.io.IOException: Frame size larger than max allowed 100 MB
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-700 java.io.IOException: Frame size larger than max allowed 100 MB Change By: Kenneth Barber Fix Version/s: PDB2.1.0 Fix Version/s: 2.3.x Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1790) Show that sync works in the face of node expiration
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1790 Show that sync works in the face of node expiration Change By: Kenneth Barber Fix Version/s: PDB3.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1731) Disable dist upgrades on acceptance tests
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1731 Disable dist upgrades on acceptance tests Change By: Kenneth Barber Fix Version/s: PDB2.3.x Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1812) Some tables (value_types at least) are never analyzed
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1812 Some tables (value_types at least) are never analyzed Change By: Kenneth Barber Affects Version/s: PDB3.0.1 Fix Version/s: PDB3.0.x Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1809) Slow response times to aggregate-event-counts endpoint queries
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1809 Slow response times to aggregate-event-counts endpoint queries Change By: Kenneth Barber Fix Version/s: PDB3.0.x Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1817) PR (1552): (maint) rollup 2.3.x to stable - mullr
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1817 PR (1552): (maint) rollup 2.3.x to stable - mullr Change By: Kenneth Barber Fix Version/s: PDB2.3.x Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4905) Feature switch for appmgmt
Title: Message Title David Lutterkort created an issue Puppet / PUP-4905 Feature switch for appmgmt Issue Type: Task Assignee: Unassigned Created: 2015/07/21 7:23 AM Priority: Normal Reporter: David Lutterkort Plumb a feature switch form the command line into the lexer that changes whether keywords application/produces/consumes are recognized as keywords. This can be a global flag, and can therefore change static structures in the compiler to avoid any runtime overhead. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PUP-4906) Update language spec with spec from xnode-spec
Title: Message Title David Lutterkort created an issue Puppet / PUP-4906 Update language spec with spec from xnode-spec Issue Type: Task Assignee: Unassigned Created: 2015/07/21 7:25 AM Priority: Normal Reporter: David Lutterkort Can be deferred until we have had some more experience with what's proposed in https://github.com/puppetlabs/xnode-spec Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PUP-4907) Finish prototype implementation of xnode-spec
Title: Message Title David Lutterkort created an issue Puppet / PUP-4907 Finish prototype implementation of xnode-spec Issue Type: Task Assignee: Unassigned Created: 2015/07/21 7:30 AM Priority: Normal Reporter: David Lutterkort The branch https://github.com/lutter/puppet/tree/dev/xnode has an incomplete first cut of an implementation of https://github.com/puppetlabs/xnode-spec Finish the prototype and get it reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PUP-4908) Add validation of appmgmt contructs
Title: Message Title David Lutterkort created an issue Puppet / PUP-4908 Add validation of appmgmt contructs Issue Type: Task Assignee: Unassigned Created: 2015/07/21 7:32 AM Priority: Normal Reporter: David Lutterkort Determine what language level validations we can perform based on the prototype https://github.com/lutter/puppet/tree/dev/xnode and add them to the compiler Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
