Jira (PUP-3765) service providers not utilizing selinux
Title: Message Title eric gisse created an issue Puppet / PUP-3765 service providers not utilizing selinux Issue Type: Bug Affects Versions: PUP 3.7.3 Assignee: Unassigned Created: 2014/12/15 1:11 AM Environment: Any SELinux system Labels: selinux redhat gentoo Priority: Normal Reporter: eric gisse Puppet on SELinux enabled systems currently has an issue where the init provider does not start programs into their correct SELinux context. While this problem was first discovered with Gentoo's openrc provider, this applies for sure to redhat and probably debian as well. Though I don't have a test case for debian at the moment. The problem is setup like this. When you start a service under selinux, the program inherits the contexts of the current SELinux user/role/context unless there's a transition to move it to a more appropriate domain.
Jira (PUP-3765) service providers not utilizing selinux
Title: Message Title
eric gisse updated an issue
Puppet / PUP-3765
service providers not utilizing selinux
Change By:
eric gisse
PuppetonSELinuxenabledsystemscurrentlyhasanissuewheretheinitproviderdoesnotstartprogramsintotheircorrectSELinuxcontext.WhilethisproblemwasfirstdiscoveredwithGentoo'sopenrcprovider,thisappliesforsuretoredhatandprobablydebianaswell.ThoughIdon'thaveatestcasefordebianatthemoment.Theproblemissetuplikethis.Whenyoustartaserviceunderselinux,theprograminheritsthecontextsofthecurrentSELinuxuser/role/contextunlessthere'satransitiontomoveittoamoreappropriatedomain.Threisaselinuxuserspaceutilitycalledrun_inittohelpthisalongsothatinitscriptscanbecalledviauserspaceintotheirpropercontext.Theproblemillustrated:ThisishowsshdlikestorunonEL6: {quote} \ #psauxZ|grep/usr/sbin/sshdsystem_u:system_r:sshd_t:s0-s0:c0.c1023root19320.00.0666881252?SsDec140:00/usr/sbin/sshd {quote} Nowrestarttheserviceandseewhatcontextitrunsunder.This,bytheway,ishowpuppetwillrestartaservice.Eitherwithserviceordirectlycallingtheinitscript-eitherwaytheresultisthesame.#servicesshdrestartStoppingsshd:[OK]Startingsshd:[OK]#psauxZ|grep/usr/sbin/sshdunconfined_u:system_r:sshd_t:s0-s0:c0.c1023root39550.50.0666881220?Ss03:020:00/usr/sbin/sshdItshouldnotbetoosurprisingthattherootuser'sselinuxuserisunconfined_uunderEL6:#id-Zunconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023Nowwhensshdisrestartedwithrun_init:#run_initservicesshdrestartAuthenticatingroot.Stoppingsshd:[OK]Startingsshd:[OK]#psauxZ|grep/usr/sbin/sshdsystem_u:system_r:sshd_t:s0-s0:c0.c1023root39810.00.0666881228?Ss03:030:00/usr/sbin/sshdCorrectcontext!I'mreasonably*close*toasolution,butitrequirestweakingfornon-selinuxcasesandhasafewengineeringconcerns.Inshort:1)Droparun_initcommandintotheprovider:has_command(:run_init,'/usr/sbin/run_init')dois_optionalend2)Modifytheservicecallsaccordingly.Eg,statuscmdintheopenrc.rbprovidergoesfromthis:command(:rcservice),@resource[:name],:status...tothis:command(:run_init),command(:rcservice),@resource[:name],:statusThisworkshappilyintheopenrcexample,thoughitdoesnotworksowellinthenon-selinuxcaseduetoanadditionalspacebeingprependedtotherun_initcommandbeingnonexistent.I'mnotclearhowtosolvethat,butthat'sasolidstartingpointintofixingthis.Thisdoeshaveanadditionalissuewhereanycasewhererun_initisused,amodificationtopamneedstobemadesotheautomatictransitionispossible.I'mnotclearonthegeneralresolutionofthat.
Add Comment
Jira (PUP-3765) service providers not utilizing selinux
Title: Message Title
eric gisse updated an issue
Puppet / PUP-3765
service providers not utilizing selinux
Change By:
eric gisse
PuppetonSELinuxenabledsystemscurrentlyhasanissuewheretheinitproviderdoesnotstartprogramsintotheircorrectSELinuxcontext.WhilethisproblemwasfirstdiscoveredwithGentoo'sopenrcprovider,thisappliesforsuretoredhatandprobablydebianaswell.ThoughIdon'thaveatestcasefordebianatthemoment.Theproblemissetuplikethis.Whenyoustartaserviceunderselinux,theprograminheritsthecontextsofthecurrentSELinuxuser/role/contextunlessthere'satransitiontomoveittoamoreappropriatedomain.Threisaselinuxuserspaceutilitycalledrun_inittohelpthisalongsothatinitscriptscanbecalledviauserspaceintotheirpropercontext.Theproblemillustrated:ThisishowsshdlikestorunonEL6:{quote}\#psauxZ|grep/usr/sbin/sshdsystem_u:system_r:sshd_t:s0-s0:c0.c1023root19320.00.0666881252?SsDec140:00/usr/sbin/sshd{quote}Nowrestarttheserviceandseewhatcontextitrunsunder.This,bytheway,ishowpuppetwillrestartaservice.Eitherwithserviceordirectlycallingtheinitscript-eitherwaytheresultisthesame. {quote} \ #servicesshdrestartStoppingsshd:[OK]Startingsshd:[OK] \ #psauxZ|grep/usr/sbin/sshdunconfined_u:system_r:sshd_t:s0-s0:c0.c1023root39550.50.0666881220?Ss03:020:00/usr/sbin/sshd {quote} Itshouldnotbetoosurprisingthattherootuser'sselinuxuserisunconfined_uunderEL6: {quote} \ #id-Zunconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 {quote} Nowwhensshdisrestartedwithrun_init: {quote} \ #run_initservicesshdrestartAuthenticatingroot.Stoppingsshd:[OK]Startingsshd:[OK] \ #psauxZ|grep/usr/sbin/sshdsystem_u:system_r:sshd_t:s0-s0:c0.c1023root39810.00.0666881228?Ss03:030:00/usr/sbin/sshd {quote} Correctcontext!I'mreasonably*close*toasolution,butitrequirestweakingfornon-selinuxcasesandhasafewengineeringconcerns.Inshort:1)Droparun_initcommandintotheprovider: {quote} has_command(:run_init,'/usr/sbin/run_init')dois_optionalend {quote} 2)Modifytheservicecallsaccordingly.Eg,statuscmdintheopenrc.rbprovidergoesfromthis: {quote} command(:rcservice),@resource[:name],:status {quote} ...tothis: {quote} command(:run_init),command(:rcservice),@resource[:name],:status {quote} Thisworkshappilyintheopenrcexample,thoughitdoesnotworksowellinthenon-selinuxcaseduetoanadditionalspacebeingprependedtotherun_initcommandbeingnonexistent.I'mnotclearhowtosolvethat,butthat'sasolidstartingpointintofixingthis.Thisdoeshaveanadditionalissuewhereanycasewhererun_initisused,amodificationtopamneedstobemadesotheautomatictransitionispossible.I'mnotclearonthegeneralresolutionofthat.
Add Comment
Jira (PUP-3766) exec should set LC_ALL and LANG to C by default
Title: Message Title Daniele Sluijters created an issue Puppet / PUP-3766 exec should set LC_ALL and LANG to C by default Issue Type: Task Assignee: Unassigned Components: DSL Created: 2014/12/15 2:54 AM Priority: Normal Reporter: Daniele Sluijters Puppet::Util::Execution#execute already does this which is what most providers use. By setting these two variables to C by default you usually end up with US/English output in ASCII and byte-wise sorting/ordering. This means that no matter the locale of the user who runs Puppet you'll get consistent output from a command. Add Comment
Jira (PUP-3766) exec should set LC_ALL and LANG to C by default
Title: Message Title Daniele Sluijters commented on PUP-3766 Re: exec should set LC_ALL and LANG to C by default Related to this: https://github.com/puppetlabs/puppetlabs-apt/pull/394. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-659) Qualified variable lookups are very slow under Puppet 2.7+ unless prefixed with ::
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-659 Qualified variable lookups are very slow under Puppet 2.7+ unless prefixed with :: Change By: Hailee Kenney Assignee: HaileeKenney Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3766) exec should set LC_ALL and LANG to C by default
Title: Message Title Josh Cooper commented on PUP-3766 Re: exec should set LC_ALL and LANG to C by default Hi Daniele Sluijters, the base exec provider does call into Puppet::Util::Execution#execute, but it always sets override_locale = false. It looks that behavior was first introduced in commit https://github.com/puppetlabs/puppet/commit/2ea85ef38212ca9ebb79a6e1d57b54a759fbb76e for https://projects.puppetlabs.com/issues/11860. I think if we were to switch LANG, etc, it would bring back the issues mentioned in the old bug report. /cc Christopher Price Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3761) puppet agent --onetime not honored
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-3761
puppet agent --onetime not honored
Change By:
Josh Cooper
whenrunningthefollowingcommand: {noformat} puppetagent--nooppuppet-master.service.consul--test--onetime {noformat} (NOTE:--onetimeaddedforclarifyhere,itisalsopartofthe--testalias)Igetthefollowingerror: {noformat} Notice:SkippingrunofPuppetconfigurationclient;administrativelydisabled(Reason:'Disabledbydefaultonnewinstallations');Use'puppetagent--enable'tore-enable. {noformat} Afterreadingabout \ - \ -enable,itlookslikeIwouldnotwanttoenablethisoption(--onetimemeansthatIjustwanttorunpuppetonce,andIdon'tnecessarilywantittoruninthebackground.Itseemsasif--test,--onetime,and--no-daemonize,havebeenrenderedunsupportedbythisadminlock.AmImissingsomething,oraretheseoptionsnotgoingtobesupportedanymore?Thatwouldbeashameb/ctheywerereallyuseful:(
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@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-3761) puppet agent --onetime not honored
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3761 puppet agent --onetime not honored Change By: Josh Cooper Assignee: DanBode Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3761) puppet agent --onetime not honored
Title: Message Title Josh Cooper commented on PUP-3761 Re: puppet agent --onetime not honored Dan Bode If the agent is administratively disabled, then both foreground and background puppet agent runs are disabled. Are you asking that puppet agent when running in the foreground with onetime, should be allowed to run (ignoring the lock file)? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3761) puppet agent --onetime not honored
Title: Message Title Dan Bode commented on PUP-3761 Re: puppet agent --onetime not honored It appears that setting this flat to --enable means that the puppet agent will start running in the background (is that not true?) Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3761) puppet agent --onetime not honored
Title: Message Title Dan Bode commented on PUP-3761 Re: puppet agent --onetime not honored maybe --enable should just be added to the --test alias? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-659) Qualified variable lookups are very slow under Puppet 2.7+ unless prefixed with ::
Title: Message Title Hailee Kenney commented on PUP-659 Re: Qualified variable lookups are very slow under Puppet 2.7+ unless prefixed with :: I've opened a pull request to revert the revert: https://github.com/puppetlabs/puppet/pull/3414 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3761) puppet agent --onetime not honored
Title: Message Title Josh Cooper commented on PUP-3761 Re: puppet agent --onetime not honored I don't think we want - test/onetime to imply -enable, since that would introduce race conditions where the background agent could run between the time the lock is removed and when the foreground agent runs. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3761) puppet agent --onetime not honored
Title: Message Title Dan Bode commented on PUP-3761 Re: puppet agent --onetime not honored I need to look into this more. After looking at the code I can tell this isn't something new. I was a little confused b/c this message is what I see after a fresh Puppet install (ie: things are disabled by default). I may need to recreate and try to understand why I'm seeing it (b/c I didn't see any recent commits merged into 3.x that would cause this to be the default behavior) Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3767) PMT build action should warn when it encounters unrecognized keys in metadata.json
Title: Message Title Jesse Scott created an issue Puppet / PUP-3767 PMT build action should warn when it encounters unrecognized keys in metadata.json Issue Type: Improvement Assignee: Unassigned Components: PMT Created: 2014/12/15 11:33 AM Priority: Normal Reporter: Jesse Scott Some sort of indication during pmt build about unrecognized metadata.json keys would help module authors detect problems before publishing. For example, in a dependency: having a valid name but a typo in the version_requirement key will currently result an unbounded dependency. Add Comment
Jira (PDB-1059) PR (1172): (pdb-775) Retire old postgres versions - ajroetker
Title: Message Title gepetto-bot commented on PDB-1059 Re: PR (1172): (pdb-775) Retire old postgres versions - ajroetker pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/291/ Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-659) Qualified variable lookups are very slow under Puppet 2.7+ unless prefixed with ::
Title: Message Title Henrik Lindberg commented on PUP-659 Re: Qualified variable lookups are very slow under Puppet 2.7+ unless prefixed with :: Merged to master https://github.com/puppetlabs/puppet/commit/9129051acb1b069233cda6f6ee1ef6d315660691 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3768) scheduled_task keeps reapplying
Title: Message Title zack shahan created an issue Puppet / PUP-3768 scheduled_task keeps reapplying Issue Type: Bug Affects Versions: PUP 3.7.2 Assignee: Kylo Ginsberg Components: Client Created: 2014/12/15 1:26 PM Priority: Normal Reporter: zack shahan Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (PUP-3768) scheduled_task keeps reapplying
Title: Message Title zack shahan updated an issue Puppet / PUP-3768 scheduled_task keeps reapplying Change By: zack shahan EverypuppetrunIhaveascheduledtaskthatgetsre-appliedeventhoughtherewasnochange.Afterdoingsomedigging,itlookslikeitappliescorrectly,butonthenextrun,itisonlycomparingapartoftheargumentstringinsteadofthefullstring.Itlookslikewhendoingthe comparision comparison ,itisonlyreadinginthefirst256charactersinsteadoftheentirestring.argumentschanged'backup--ftp-username=empty--ftp-password=empty--max-upload-pr-second=500kb--thread-priority=BelowNormal--use-ssl--passphrase=empty--aes-encryption-dont-allow-fallback=true--full-if-older-than=1M--exclude=*.wma--exclude=*.mp3--exclu'to'backup--ftp-username=empty--ftp-password=empty--max-upload-pr-second=500kb--thread-priority=BelowNormal--use-ssl--passphrase=empty--aes-encryption-dont-allow-fallback=true--full-if-older-than=1M--exclude=*.wma--exclude=*.mp3--exclude=*.acc'--exclude=*.mp4--exclude=*.avi--exclude=*.3gp--exclude=*.mpg--exclude=*.mov Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3768) scheduled_task keeps reapplying
Title: Message Title zack shahan updated an issue Puppet / PUP-3768 scheduled_task keeps reapplying Change By: zack shahan EverypuppetrunIhaveascheduledtaskthatgetsre-appliedeventhoughtherewasnochange.Afterdoingsomedigging,itlookslikeitappliescorrectly,butonthenextrun,itisonlycomparingapartoftheargumentstringinsteadofthefullstring.Itlookslikewhendoingthecomparision,itisonlyreadinginthefirst256charactersinsteadoftheentirestring.argumentschanged'backup--ftp-username=empty--ftp-password=empty--max-upload-pr-second=500kb--thread-priority=BelowNormal--use-ssl--passphrase=empty--aes-encryption-dont-allow-fallback=true--full-if-older-than=1M--exclude=*.wma--exclude=*.mp3--exclu'to'backup--ftp-username=empty--ftp-password=empty--max-upload-pr-second=500kb--thread-priority=BelowNormal--use-ssl--passphrase=empty--aes-encryption-dont-allow-fallback=true--full-if-older-than=1M--exclude=*.wma--exclude=*.mp3--exclude=*.acc'--exclude=*.mp4--exclude=*.avi--exclude=*.3gp--exclude=*.mpg--exclude=*.mov Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3768) scheduled_task keeps reapplying
Title: Message Title
zack shahan updated an issue
Puppet / PUP-3768
scheduled_task keeps reapplying
Change By:
zack shahan
EverypuppetrunIhaveascheduledtaskthatgetsre-appliedeventhoughtherewasnochange.Afterdoingsomedigging,itlookslikeitappliescorrectly,butonthenextrun,itisonlycomparingapartoftheargumentstringinsteadofthefullstring.Itlookslikewhendoingthecomparison,itisonlyreadinginthefirst256charactersinsteadoftheentirestring. {quote} scheduled_task{'cloud_backup':ensure=present,command='C:\ProgramFiles\Duplicati\Duplicati.CommandLine.exe',arguments=template('fdlic/duplicati/backup.erb'),trigger={schedule=weekly,start_time='08:00:00',start_date='2014-05-08'},} {quote} argumentschanged'backup--ftp-username=empty--ftp-password=empty--max-upload-pr-second=500kb--thread-priority=BelowNormal--use-ssl--passphrase=empty--aes-encryption-dont-allow-fallback=true--full-if-older-than=1M--exclude=*.wma--exclude=*.mp3--exclu'to'backup--ftp-username=empty--ftp-password=empty--max-upload-pr-second=500kb--thread-priority=BelowNormal--use-ssl--passphrase=empty--aes-encryption-dont-allow-fallback=true--full-if-older-than=1M--exclude=*.wma--exclude=*.mp3--exclude=*.acc'--exclude=*.mp4--exclude=*.avi--exclude=*.3gp--exclude=*.mpg--exclude=*.mov
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to
Jira (PUP-3768) scheduled_task keeps reapplying
Title: Message Title
zack shahan updated an issue
Puppet / PUP-3768
scheduled_task keeps reapplying
Change By:
zack shahan
EverypuppetrunIhaveascheduledtaskthatgetsre-appliedeventhoughtherewasnochange.Afterdoingsomedigging,itlookslikeitappliescorrectly,butonthenextrun,itisonlycomparingapartoftheargumentstringinsteadofthefullstring.Itlookslikewhendoingthecomparison,itisonlyreadinginthefirst256charactersinsteadoftheentirestring.{quote}scheduled_task{'cloud_backup':ensure=present,command='C:\ProgramFiles\Duplicati\Duplicati.CommandLine.exe',arguments=template('fdlic/duplicati/backup.erb'),trigger={schedule=weekly,start_time='08:00:00',start_date='2014-05-08'} , }{quote}argumentschanged'backup--ftp-username=empty--ftp-password=empty--max-upload-pr-second=500kb--thread-priority=BelowNormal--use-ssl--passphrase=empty--aes-encryption-dont-allow-fallback=true--full-if-older-than=1M--exclude=*.wma--exclude=*.mp3--exclu'to'backup--ftp-username=empty--ftp-password=empty--max-upload-pr-second=500kb--thread-priority=BelowNormal--use-ssl--passphrase=empty--aes-encryption-dont-allow-fallback=true--full-if-older-than=1M--exclude=*.wma--exclude=*.mp3--exclude=*.acc'--exclude=*.mp4--exclude=*.avi--exclude=*.3gp--exclude=*.mpg--exclude=*.mov
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to
Jira (PUP-3768) scheduled_task keeps reapplying
Title: Message Title
zack shahan updated an issue
Puppet / PUP-3768
scheduled_task keeps reapplying
Change By:
zack shahan
EverypuppetrunIhaveascheduledtaskthatgetsre-appliedeventhoughtherewasnochange.Afterdoingsomedigging,itlookslikeitappliescorrectly,butonthenextrun,itisonlycomparingapartoftheargumentstringinsteadofthefullstring.Itlookslikewhendoingthecomparison,itisonlyreadinginthefirst256charactersinsteadoftheentirestring. {quote} scheduled_task{'cloud_backup':ensure=present,command='C:\ProgramFiles\Duplicati\Duplicati.CommandLine.exe',arguments=template('fdlic/duplicati/backup.erb'),trigger={schedule=weekly,start_time='08:00:00',start_date='2014-05-08'}} {quote} argumentschanged'backup--ftp-username=empty--ftp-password=empty--max-upload-pr-second=500kb--thread-priority=BelowNormal--use-ssl--passphrase=empty--aes-encryption-dont-allow-fallback=true--full-if-older-than=1M--exclude=*.wma--exclude=*.mp3--exclu'to'backup--ftp-username=empty--ftp-password=empty--max-upload-pr-second=500kb--thread-priority=BelowNormal--use-ssl--passphrase=empty--aes-encryption-dont-allow-fallback=true--full-if-older-than=1M--exclude=*.wma--exclude=*.mp3--exclude=*.acc'--exclude=*.mp4--exclude=*.avi--exclude=*.3gp--exclude=*.mpg--exclude=*.mov
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to
Jira (PDB-1059) PR (1172): (pdb-775) Retire old postgres versions - ajroetker
Title: Message Title gepetto-bot commented on PDB-1059 Re: PR (1172): (pdb-775) Retire old postgres versions - ajroetker ajroetker commented: @pljenkinsro retest this please Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3751) The installer should fail if the memory does not meet the minimum requirements.
Title: Message Title Celia Cottle updated an issue Puppet / PUP-3751 The installer should fail if the memory does not meet the minimum requirements. Change By: Celia Cottle Labels: support Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3768) scheduled_task keeps reapplying
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3768 scheduled_task keeps reapplying Change By: Josh Cooper Labels: windows Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3768) scheduled_task keeps reapplying
Title: Message Title Josh Cooper commented on PUP-3768 Re: scheduled_task keeps reapplying The windows APIs for retrieving task command, parameters, etc don't tell you how long the string is, instead you have to keep reading until you run into a wide null terminator. We enforce a maximum length of 256 to ensure we don't read off the end of the string: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/windows/taskscheduler.rb#L408. Looks like 256 is not large enough for scheduled task parameters. We should check the other task methods as well, e.g. working directory, trigger string, comment, creator, account info. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3761) puppet agent --onetime not honored
Title: Message Title Dan Bode commented on PUP-3761 Re: puppet agent --onetime not honored I had another look today, and by default puppet agent --test doesn't work (the main thing that I'm confused about) I remember this command always just working before, so it seems like a significant break in backwards compat. Also you mentioned race conditions related to running puppet from the foreground. What is the safe way to run it? service puppet stop puppet agent --enable puppet agent -t puppet agent --disable service puppet start Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1059) PR (1172): (pdb-775) Retire old postgres versions - ajroetker
Title: Message Title gepetto-bot commented on PDB-1059 Re: PR (1172): (pdb-775) Retire old postgres versions - ajroetker pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/292/ Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-303) Add optional dependency deep_merge to Gemfile
Title: Message Title Melissa Stone commented on HI-303 Re: Add optional dependency deep_merge to Gemfile Kylo Ginsberg fyi, we've updated the deep_merge gem dependency. I'm not entirely sure where this ticket needs to go next, I'm assuming ready for CI, but if that isn't correct, please feel free to correct it. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1059) PR (1172): (pdb-775) Retire old postgres versions - ajroetker
Title: Message Title gepetto-bot commented on PDB-1059 Re: PR (1172): (pdb-775) Retire old postgres versions - ajroetker ajroetker commented: @pljenkinsro retest this please Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-547) Allow the Hiera puppet backend to be used with DataBindings
Title: Message Title Henrik Lindberg commented on PUP-547 Re: Allow the Hiera puppet backend to be used with DataBindings Eric Sorenson Is this still relevant now that we added an agnostic mechanism for plugging in a provider of data in environment and modules ? IMO we can close this issue as a won't fix. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-548) Puppet hiera backend by default
Title: Message Title Henrik Lindberg commented on PUP-548 Re: Puppet hiera backend by default Eric Sorenson Is this still relevant now that we have an agnostic plugin mechanism for data in environment and modules? Suggest closing this as a won't fix, since the idea this ticket expresses was a stop-gap solution that we really did not want in the first place. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3657) Using create_resource or some other Ruby methodology for creating resources allows for invalid resource references
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3657 Using create_resource or some other Ruby methodology for creating resources allows for invalid resource references Change By: Henrik Lindberg Component/s: Server Component/s: DSL Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3657) Using create_resource or some other Ruby methodology for creating resources allows for invalid resource references
Title: Message Title Henrik Lindberg commented on PUP-3657 Re: Using create_resource or some other Ruby methodology for creating resources allows for invalid resource references The problem here is that the underlying logic uses a string as the datatype for the reference and the function simply relays what it got in the hash. If the example instead was written with a real reference (as in the working example), the parser would then give the same error. Fixing this in create_resources means that it must have special knowledge about certain parameters (their type) in order to enforce correct input. Alternatively fixing this can wait until types actually have proper typing. In 4.0, users should preferably use the new resource syntax (instead of create resources) and not specify relations by using strings that are encoded references. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3755) Catalogs are transformed to resources outside of node environments
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3755 Catalogs are transformed to resources outside of node environments Change By: Henrik Lindberg Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3656) Prefetch eats all exceptions, there is no way to fail out.
Title: Message Title Josh Cooper commented on PUP-3656 Re: Prefetch eats all exceptions, there is no way to fail out. Completely agree this is a problem, though puppet does not eat all exceptions in https://github.com/puppetlabs/puppet/blob/master/lib/puppet/transaction.rb#L306-L310, only those exceptions descending from StandardError, which excludes LoadError. On a side note, we made a pass through puppet eliminating places where we really were rescuing all Exceptions, see PUP-3521 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-1059) PR (1172): (pdb-775) Retire old postgres versions - ajroetker
Title: Message Title gepetto-bot commented on PDB-1059 Re: PR (1172): (pdb-775) Retire old postgres versions - ajroetker pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/293/ Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3769) resource/service/should_not_change_the_system should only run on agents
Title: Message Title Eric Thompson created an issue Puppet / PUP-3769 resource/service/should_not_change_the_system should only run on agents Issue Type: Bug Assignee: Eric Thompson Components: Client Created: 2014/12/15 4:38 PM Priority: Major Reporter: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the
Jira (PUP-1931) mount provider improvement when options property is not specified
Title: Message Title Peter Huene updated an issue Puppet / PUP-1931 mount provider improvement when options property is not specified Change By: Peter Huene Assignee: PeterHuene Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3665) future parser collector override with Resource reference does not work
Title: Message Title Eric Thompson commented on PUP-3665 Re: future parser collector override with Resource reference does not work some of the files printed out for posterity on how to setup puppetdb after install from acceptance... looks broken on fedora20 at puppet SHA: dd917cc; puppetdb SHA: 026a68a on the master: collect all exported Users with no query in | | [root@g85l6ml6iaat9sb puppetdb]# cat /etc/puppet/puppet.conf [agent] server=g85l6ml6iaat9sb.delivery.puppetlabs.net [master] storeconfigs = true storeconfigs_backend = puppetdb reports = puppetdb autosign = true
Jira (PUP-3665) future parser collector override with Resource reference does not work
Title: Message Title Eric Thompson commented on PUP-3665 Re: future parser collector override with Resource reference does not work second run, on master: [root@g85l6ml6iaat9sb puppetdb]# cat /etc/passwd root:x:0:0:root:/root:/bin/bash bin:x:1:1:bin:/bin:/sbin/nologin daemon:x:2:2:daemon:/sbin:/sbin/nologin adm:x:3:4:adm:/var/adm:/sbin/nologin lp:x:4:7:lp:/var/spool/lpd:/sbin/nologin sync:x:5:0:sync:/sbin:/bin/sync shutdown:x:6:0:shutdown:/sbin:/sbin/shutdown halt:x:7:0:halt:/sbin:/sbin/halt mail:x:8:12:mail:/var/spool/mail:/sbin/nologin
Jira (PUP-3665) future parser collector override with Resource reference does not work
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3665 future parser collector override with Resource reference does not work Change By: Eric Thompson QA Contact: KurtWall EricThompson Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3754) Better logging when fail to set ownership
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3754 Better logging when fail to set ownership Change By: Josh Cooper Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@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-3754) Better logging when fail to set ownership
Title: Message Title Josh Cooper updated an issue Puppet / PUP-3754 Better logging when fail to set ownership Change By: Josh Cooper Fix Version/s: PUP4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
