Jira (PUP-1200) [meta] please stop arbitrarily changing systemd service unit names
Title: Message Title Dominic Cleal commented on an issue Re: [meta] please stop arbitrarily changing systemd service unit names It appears the systemd behaviour is desired, they don't want to allow 'enable' to operate on symlinks: https://bugzilla.redhat.com/show_bug.cgi?id=955379 (c14 in particular) Add Comment Puppet / PUP-1200 [meta] please stop arbitrarily changing systemd service unit names In 3.4, what was previously puppetagent.service is now puppet.service. Now every person who was managing the puppet service and used systemd has to add a case statement based on version. I understand that puppet is a better (and more consistent) name, but the change seems unfounded. Instead of fixing any problem it just introduces yet another complexity i... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs.
Jira (PUP-1455) Puppet should utilize CFPropertyList to read/write plist files
Title: Message Title redmine.exporter created an issue Puppet / PUP-1455 Puppet should utilize CFPropertyList to read/write plist files Issue Type: New Feature Assignee: Unassigned Created: 16/Jan/14 2:19 AM Labels: redmine Priority: Normal Reporter: redmine.exporter Currently Puppet has to run `plutil -convert xml1` on EVERY plist it encounters because it has no way of supporting binary plist files. The CFPropertyList project is a Ruby library that allows direct access to read/write plist files WITHOUT using Apple's CoreFoundation libraries (which give Puppet problems due to green threading). Puppet should be able to utilize that library to read/write plist files as it would speed up service resource handling exponentially. Add Comment
Jira (MCO-158) MCollective service doesn't exit on Windows
Title: Message Title Pieter Loubser created an issue MCollective / MCO-158 MCollective service doesn't exit on Windows Issue Type: Bug Affects Versions: 2.4.0-rc1 Assignee: Unassigned Created: 16/Jan/14 3:11 AM Priority: Normal Reporter: Pieter Loubser Previous attempt at fixing http://projects.puppetlabs.com/issues/20467 was unsuccessful because of blocking threads. We need forcefully kill the threads so that we can exit cleanly. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (MCO-158) MCollective service doesn't exit on Windows
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-158 MCollective service doesn't exit on Windows Change By: Pieter Loubser Fix Version/s: 2.4.0-rc2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-158) MCollective service doesn't exit on Windows
Title: Message Title Pieter Loubser updated an issue MCollective / MCO-158 MCollective service doesn't exit on Windows Change By: Pieter Loubser Assignee: RichardClamp Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-158) MCollective service doesn't exit on Windows
Title: Message Title Pieter Loubser commented on an issue Re: MCollective service doesn't exit on Windows https://github.com/puppetlabs/marionette-collective/pull/152 Add Comment MCollective / MCO-158 MCollective service doesn't exit on Windows Previous attempt at fixing http://projects.puppetlabs.com/issues/20467 was unsuccessful because of blocking threads. We need forcefully kill the threads so that we can exit cleanly. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-159) PR (153): Revert maint - Add temp workaround for travis ruby 1.8.7 - richardc
Title: Message Title gepetto-bot created an issue MCollective / MCO-159 PR (153): Revert maint - Add temp workaround for travis ruby 1.8.7 - richardc Issue Type: Task Assignee: Unassigned Created: 16/Jan/14 3:36 AM Labels: github Priority: Normal Reporter: gepetto-bot Revert maint - Add temp workaround for travis ruby 1.8.7 Author: Richard Clamp richa...@unixbeard.net Company: Github ID: richardc Pull Request 153 Discussion Pull Request 153 File Diff Pull Request Description This reverts commit 34f10c9db724510ea584a6f44d989c60ae8ffe25. The underlying issue was was fixed in gem 2.2.1. (webhooks-id: e9c63723a2e560e6235c67937c62fff8)
Jira (MCO-159) PR (153): Revert maint - Add temp workaround for travis ruby 1.8.7 - richardc
Title: Message Title gepetto-bot commented on an issue Re: PR (153): Revert maint - Add temp workaround for travis ruby 1.8.7 - richardc Pull request Revert maint - Add temp workaround for travis ruby 1.8.7 has been closed. Add Comment MCollective / MCO-159 PR (153): Revert maint - Add temp workaround for travis ruby 1.8.7 - richardc h2. Revert maint - Add temp workaround for travis ruby 1.8.7 * Author: Richard Clamp richa...@unixbeard.net * Company: * Github ID: [richardc|https://github.com/richardc] * [Pull Request 153 Discussion|https://github.com/puppetlabs/marionette-collective/pull/153] * [Pull Request 153 File Diff|https://github.com/puppetlabs/marionette-collective/... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-330) Scope 2.0 epics
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-330 Scope 2.0 epics Change By: Kenneth Barber Wewanttodosomemoreforwardplanning.Ourproposalistofleshoutthescopeofalltheexpected2.0epicswhichshouldallowustoplanoutthefuturesprintstosomedegree,givingussomeideaofhowlikelywecanreachourtargets. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-331) PuppetDB el5 package via prerelease yum repo returns Package does not match intended download
Title: Message Title Kenneth Barber commented on an issue Re: PuppetDB el5 package via prerelease yum repo returns Package does not match intended download Ryan McKern and Matthaus Owens can you give some guidance on this ticket? Add Comment PuppetDB / PDB-331 PuppetDB el5 package via prerelease yum repo returns Package does not match intended download I'm having some trouble with el5 packaging for PuppetDB. Original failures are here: https://jenkins.puppetlabs.com/view/B_PuppetDB/job/PuppetDB%20Acceptance%20IN%20THE%20CLOUD/ I setup my own el5 box and tried to use that repo and got this error: https://gist.github.com/kbarber/8455081 It seems the metadata is not matching the package itself,... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PDB-331) PuppetDB el5 package via prerelease yum repo returns Package does not match intended download
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-331 PuppetDB el5 package via prerelease yum repo returns Package does not match intended download Change By: Kenneth Barber Sprint: 20140115to20140122 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-331) PuppetDB el5 package via prerelease yum repo returns Package does not match intended download
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-331 PuppetDB el5 package via prerelease yum repo returns Package does not match intended download Issue Type: Bug Assignee: Unassigned Created: 16/Jan/14 6:15 AM Priority: Blocker Reporter: Kenneth Barber I'm having some trouble with el5 packaging for PuppetDB. Original failures are here: https://jenkins.puppetlabs.com/view/B_PuppetDB/job/PuppetDB%20Acceptance%20IN%20THE%20CLOUD/ I setup my own el5 box and tried to use that repo and got this error: https://gist.github.com/kbarber/8455081 It seems the metadata is not matching the package itself, manual installation of the package directly works fine as far as I can tell. There was some mention in RE-691 of a potential el5 issue with checksums - not sure if its related. We might need to modify our packaging process to pass 'sha' for el5 potentially. Add Comment
Jira (MCO-160) Add standard packaging to mcollective-puppet-agent
Title: Message Title Richard Clamp created an issue MCollective / MCO-160 Add standard packaging to mcollective-puppet-agent Issue Type: Improvement Assignee: Richard Clamp Created: 16/Jan/14 6:29 AM Labels: plugin package Priority: Normal Reporter: Richard Clamp As a developer I want to add the standard packaging to mcollective-puppet-agent So that I can more easily release fixes Base this on https://github.com/puppetlabs/mcollective-package-agent/pull/6 Add Comment This message was sent by Atlassian JIRA
Jira (PDB-331) PuppetDB el5 package via prerelease yum repo returns Package does not match intended download
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-331 PuppetDB el5 package via prerelease yum repo returns Package does not match intended download Change By: Kenneth Barber Affects Version/s: 1.5.2 Fix Version/s: 1.5.X Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-161) Investigate possible loss of parity between standard Puppet Labs packaging and mco plugin package
Title: Message Title Pieter Loubser commented on an issue Re: Investigate possible loss of parity between standard Puppet Labs packaging and mco plugin package The change was merged in the package agent as https://github.com/puppetlabs/mcollective-package-agent/pull/6 Add Comment MCollective / MCO-161 Investigate possible loss of parity between standard Puppet Labs packaging and mco plugin package User feedback has brought up the fact that if plugin packaging moves to the standard Puppet Labs packaging methods mco plugin package becomes devalued. We need to have the discussion here if we should review moving forward with standardising packaging or move back to using mco plugin package. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (MCO-161) Investigate possible loss of parity between standard Puppet Labs packaging and mco plugin package
Title: Message Title Pieter Loubser created an issue MCollective / MCO-161 Investigate possible loss of parity between standard Puppet Labs packaging and mco plugin package Issue Type: Task Assignee: Unassigned Created: 16/Jan/14 7:51 AM Priority: Normal Reporter: Pieter Loubser User feedback has brought up the fact that if plugin packaging moves to the standard Puppet Labs packaging methods mco plugin package becomes devalued. We need to have the discussion here if we should review moving forward with standardising packaging or move back to using mco plugin package. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-331) PuppetDB el5 package via prerelease yum repo returns Package does not match intended download
Title: Message Title Matthaus Owens commented on an issue Re: PuppetDB el5 package via prerelease yum repo returns Package does not match intended download Kenneth Barber That may be related to an update to createrepo that went out yesterday, but our packaging tasks are passing '--checksum=sha' to the createrepo task. We can dig in more today. Add Comment PuppetDB / PDB-331 PuppetDB el5 package via prerelease yum repo returns Package does not match intended download I'm having some trouble with el5 packaging for PuppetDB. Original failures are here: https://jenkins.puppetlabs.com/view/B_PuppetDB/job/PuppetDB%20Acceptance%20IN%20THE%20CLOUD/ I setup my own el5 box and tried to use that repo and got this error: https://gist.github.com/kbarber/8455081 It seems the metadata is not matching the package itself,... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this 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-307) A change in rubygem 'mocha 1.0.0' has started causing rspec test failures
Title: Message Title
Kenneth Barber commented on an issue
Re: A change in rubygem 'mocha 1.0.0' has started causing rspec test failures
After much wrangling this seems to work, but I haven't been able to get a clean build from 1.5.x due to numerous other build/test related issues. Once I get a clean build, I'll merge this up to 1.6.x and master as well.
Add Comment
PuppetDB / PDB-307
A change in rubygem 'mocha 1.0.0' has started causing rspec test failures
So it seems that the change from mocha '0.14.0' to '1.0.0' has caused a new rspec test failure: {code} Failures: 1) Puppet::Reports::Puppetdb#report_to_hash should include the transaction uuid or nil Failure/Error: if subject.report_format = 4 NoMethodError: private method `report_format' called for #Puppet::Transaction::Rep...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at
Jira (MCO-161) Investigate possible loss of parity between standard Puppet Labs packaging and mco plugin package
Title: Message Title R.I.Pienaar commented on an issue Re: Investigate possible loss of parity between standard Puppet Labs packaging and mco plugin package Users who wants to write their own plugins and download some others from the internet - either from other users or puppetlabs - really want to have parity in the whole eco system. They should know a package for a given plugin is built using the same methods regardless of origin. They want to use the same deployment method like a puppet defined type and they want to know that they can use this process with a plugin from any source. They want to know that the versions, licensing information, choices of what files go into what packages, dependency information etc is from the same source and used in the same way. They want to know that updating this meta data in one place will result in all the output artifacts being updated. These artifacts include packages, docs, rpcutil#inventory and more - all served from a single bit of metadata. Today this is done with mco plugin package, it reads the DDL file for author information, versions, licence and more and produce packages. For a user there is no additional effort needed above writing a plugin. They cannot use a plugin without a valid DDL and as soon as a plugin have a valid DDL its packagable, documented and so forth. Going from basic working plugin to releasable artifact is at most 1 command and no duplication of information and manual syncing etc. It does not dictate what SCM they use and does not dictate how they tag or release or whatever workflow they wish to use. Puppet Labs packages are up till recently built using the same tooling and so users can have great confidence that the plugin eco system as a whole is a single known state. If the build method is changing at Puppet Labs we cannot have confidence that the plugins supplied via puppetlabs.com is going to behave the same was the ones we create in-house and so we will be forced to rebuild puppetlabs plugins before we can use them with the same level of confidence next to our own. Add Comment MCollective / MCO-161 Investigate possible loss of parity between standard Puppet Labs packaging and mco plugin
Jira (MCO-162) release MCollective 2.4.0-rc2
Title: Message Title Richard Clamp created an issue MCollective / MCO-162 release MCollective 2.4.0-rc2 Issue Type: Improvement Assignee: Pieter Loubser Created: 16/Jan/14 8:29 AM Fix Versions: 2.4.0-rc2 Priority: Normal Reporter: Richard Clamp Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-1456) Type exec is executed, although required type failed
Title: Message Title
Bjoern Lippert created an issue
Puppet / PUP-1456
Type exec is executed, although required type failed
Issue Type:
Bug
Affects Versions:
3.2.3, 3.4.2
Assignee:
Unassigned
Created:
16/Jan/14 8:42 AM
Environment:
master and agent running on Ubuntu 10.04.4 LTS 64bit
Priority:
Major
Reporter:
Bjoern Lippert
An exec-type is executed although a required type (an exec, too) has failed. The strange thing is, that when doing an agent run ,the output of puppet agent --test says Skipping because of failed dependency. The output is correct (as expected), but nevertheless the exec-type gets executed.
As I have problems in my productive code, that would be to complex to post it here, I use pseudo/abstract code to describe the problem. Mention that the strange behaving code is included in a separate puppet define (not a class) in a separate file.
module::path::to::the_strange_define { uniqueName: ... some parameters ... require = ... }
remark: When running puppet and the define is called, I see the output Scheduling refresh of Exec[...] for each puppet-type within the define.
Now the code of the_strange_define itself:
[...] $condition = a bash test condition used in all exec-types below # is always
Jira (PDB-306) Acceptance tests on CentOS 5 fail locally
Title: Message Title John Duarte updated an issue PuppetDB / PDB-306 Acceptance tests on CentOS 5 fail locally Change By: John Duarte Labels: qa-reviewed Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-162) release MCollective 2.4.0-rc2
Title: Message Title Richard Clamp commented on an issue Re: release MCollective 2.4.0-rc2 https://github.com/puppetlabs/marionette-collective/pull/154 Add Comment MCollective / MCO-162 release MCollective 2.4.0-rc2 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1456) Type exec is executed, although required type failed
Title: Message Title
Bjoern Lippert updated an issue
Puppet / PUP-1456
Type exec is executed, although required type failed
Change By:
Bjoern Lippert
Anexec-typeisexecutedalthougharequiredtype(anexec,too)hasfailed.Thestrangethingis,thatwhendoinganagentrun,theoutputofpuppetagent--testsaysSkippingbecauseoffaileddependency.Theoutputiscorrect(asexpected),butneverthelesstheexec-typegetsexecuted.AsIhaveproblemsinmyproductivecode,thatwouldbetocomplextopostithere,Iusepseudo/abstractcodetodescribetheproblem.Mentionthatthestrangebehavingcodeisincludedinaseparatepuppetdefine(notaclass)inaseparatefile. {code:title=thecallingdefine} module::path::to:: the_calling_define(...){ #...lotsofcode module::path::to:: the_strange_define{uniqueName: ...someparameters... require=... , } #...lotsofcode }{code} remark:Whenrunningpuppetandthedefineiscalled,Iseetheoutput {color:green} SchedulingrefreshofExec \ [... \ ] {color} foreachpuppet-typewithinthe called define. Nowthecodeofthe_strange_defineitself: {code:title=thecalleddefinewiththeexec-typeproblem} [...]$condition=abashtestconditionusedinallexec-typesbelow#isalwaystrueexec{e1:[...]onlyif=$condition,#conditionisok,e1commandgetsexecutedcommand=somebashscriptcallinggeneratingafile,#thatscriptFAILSreturning1(asaresultthefilewasn'tgenerated,too);Output frompuppet :...returned1insteadofoneof[0]}exec{e2:[...]onlyif=$condition,#conditionstillok,e2commandwouldbeexecuted,ifrequirewouldbeok,butitisnot:require= Exec[e1] ,#requirefails...leadstodebugoutputSkippingbecauseoffaileddependencycommand=anotherbashinstructionmovingawaytheine1createdfile,#isnotexecuted,becauserequirefailed}Herecomesthestrangething:exec{e6:[...]onlyif=$condition,#conditionstillok,e3commandwouldbeexecuted,ifrequirewouldbeok(isnot)require= Exec[e2] ,#requirefails...leadstodebugoutputSkippingbecauseoffaileddependency#require= [Exec[e1],Exec[e2]] ,#I'vetriedthis,butitmakesnodifferencetolinebeforecommand=againanotherbashcommandunzippingfiles,#shouldnotbeexecuted,becauserequirefailed,BUTitisexecuted} {code} Thedebugoutputsays(inorder): \ [... \ ]Notice:...Exec \ [e3 \ ]:DependencyExec \ [e1 \ ]hasfailures:true {color:red} Warning:...Exec \ [e3 \ ]:Skippingbecauseoffaileddependencies {color} Notice:...Exec \ [e3 \ ]:Triggered'refresh'from1events {color:green} Info:...Exec \ [e3 \ ]:SchedulingrefreshofExec \ [e7 \ ] {color} #Exec \ [e7 \ ]subscribesExec \ [e6 \ ].AsExec \ [e7 \ ]isscheduledforrefresh,thisisanindicatorthatExec \ [e6 \ ]wasexecutedsuccessfully \ [... \ ]Tosumitup:Exece1fails,that'swhye2isskipped(Icheckedthat).Allotherexecs(e3,e4,e5)requiree2andwereskipped,EXCEPTofe6althoughpuppetsaysskipping.Exece7subscribese6,andgetsscheduledforrefresh,butisdependency-skippedbecauserequirede6failed.I'veusemycodesincepuppet3.0.xandI'mquitesure,thatitwasworkingcorrectly.ThisissuewasreportedtomesinceI'vebeenusing3.2.xbutevenafterupgradingtodayto3.4.3(masterandagentintestenvironment)theissuestillpersists.MaybeIdidn'tconsideraverybasicpuppetbehaviour,butmaybeitisnot.TutorialsandGoogledidn'thelp.However,Ican'tfigureoutformysel,soIrequestassistance.ThankyouBjoern
Jira (PDB-112) Provide means to request events from latest report in timeframe
Title: Message Title
Joseph Wagner commented on an issue
Re: Provide means to request events from latest report in timeframe
Thanks for flagging this. I'd really like to get this in place so we can unblock the PE issue and get that resolved for 3.3. That PE fix will make event inspector far more useful.
On Thu, Jan 16, 2014 at 8:52 AM, Michelle Johansen (JIRA)
– Thanks,
-j
Add Comment
PuppetDB / PDB-112
Provide means to request events from latest report in timeframe
h2. Summary Implement something like a {{latest-report-before}} query for the Events endpoint. This is necessary in order to enable the user experience / feature request described in [PE-1906|https://jira.puppetlabs.com/browse/PE-1906?focusedCommentId=20630page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-20630]. h2. Des...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving
Jira (PDB-112) Provide means to request events from latest report in timeframe
Title: Message Title Michelle Johansen updated an issue PuppetDB / PDB-112 Provide means to request events from latest report in timeframe Change By: Michelle Johansen Assignee: DeepakGiridharagopal Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1456) Type exec is executed, although required type failed
Title: Message Title Bjoern Lippert updated an issue Puppet / PUP-1456 Type exec is executed, although required type failed Change By: Bjoern Lippert Environment: master (passenger) andagentrunningonUbuntu10.04.4LTS64bit Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-332) Tags not included in catalog hash
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-332 Tags not included in catalog hash Issue Type: Bug Affects Versions: 1.5.X Assignee: Unassigned Created: 16/Jan/14 9:28 AM Priority: Normal Reporter: Ryan Senior While working on PDB-313, I found that tags in the resource metadata are not being included in the catalog's hash. Talking with Kenneth Barber, it sounds like it would be pretty unlikely that a user could have a changed tag without something else changing along with it. If the user had a new explicit tag, the parameters would have changed too (causing the hash to change). If the user had a new implicit tag, there would have been other changes to that resource metadata (not just the tag), causing the hash change. Add Comment
Jira (PDB-333) Catalog wire format docs state aliases are required for resources
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-333 Catalog wire format docs state aliases are required for resources Issue Type: Bug Affects Versions: 1.5.X Assignee: Unassigned Created: 16/Jan/14 9:32 AM Priority: Normal Reporter: Ryan Senior Not sure where this came from, but we should chase it down. I didn't see any references to it in the Clojure side. Probably should check the terminus and if it's not there either remove it from the docs. Add Comment This message was sent by Atlassian JIRA
Jira (PDB-332) Tags not included in catalog hash
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-332 Tags not included in catalog hash Change By: Ryan Senior WhileworkingonPDB-313,Ifoundthattagsintheresourcemetadataarenotbeingincludedinthecatalog'shash.Talkingwith[~ken],itsoundslikeitwouldbeprettyunlikelythatausercouldhaveachangedtagwithoutsomethingelsechangingalongwithit.Iftheuserhadanewexplicittag,theparameterswouldhavechangedtoo(causingthehashtochange).Iftheuserhadanewimplicittag,therewouldhavebeenotherchangestothatresourcemetadata(notjustthetag),causingthehashchange. Looksliketheissuegoesbackto1.5,thecodeinquestionis[here|https://github.com/puppetlabs/puppetdb/blob/1.5.x/src/com/puppetlabs/puppetdb/scf/storage.clj#L429] Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-306) Acceptance tests on CentOS 5 fail locally
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-306 Acceptance tests on CentOS 5 fail locally Change By: Kenneth Barber Fix Version/s: 1.5.X Assignee: BrananPurvine-Riley KennethBarber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-306) Acceptance tests on CentOS 5 fail locally
Title: Message Title Kenneth Barber commented on an issue Re: Acceptance tests on CentOS 5 fail locally Ashley Penney and myself found the bug, and ash has fixed this in his new 5.10 image. I'm testing now to confirm, but this might be as simple as modifying our el5 definition for beaker to solve it. Patch pending. Add Comment PuppetDB / PDB-306 Acceptance tests on CentOS 5 fail locally There is a race condition type of issue, caused by a combination of private networking (setup via beaker/vagrant) and multiple ethernet devices on the machine. The solution is to remove the extra ethernet device eth1) from the image. This would match CentOS 6, which doesn't have this problem. Created a ticket for QA to update the image. Creating this ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more
Jira (PDB-306) Acceptance tests on CentOS 5 fail locally
Title: Message Title Kenneth Barber commented on an issue Re: Acceptance tests on CentOS 5 fail locally PR is here: https://github.com/puppetlabs/puppetdb/pull/805 Add Comment PuppetDB / PDB-306 Acceptance tests on CentOS 5 fail locally There is a race condition type of issue, caused by a combination of private networking (setup via beaker/vagrant) and multiple ethernet devices on the machine. The solution is to remove the extra ethernet device eth1) from the image. This would match CentOS 6, which doesn't have this problem. Created a ticket for QA to update the image. Creating this ... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-985) PR (204): Add default provider fact and make stdlib file_line default. - nanliu
Title: Message Title gepetto-bot commented on an issue Re: PR (204): Add default provider fact and make stdlib file_line default. - nanliu nanliu commented: @bodepd, a separate module won't resolve the problem since one of the change is in a resource in this module. We have forked stdlib to maintain for now. Add Comment Puppet / PUP-985 PR (204): Add default provider fact and make stdlib file_line default. - nanliu h2. Add default provider fact and make stdlib file_line default. * Author: Nan Liu * Company: VMware Inc. * Github ID: [nanliu|https://github.com/nanliu] * [Pull Request 204 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/204] * [Pull Request 204 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/204/files] h2. Pull R... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit
Jira (FACT-229) PR (605): Feature/facter 2/fact 65 aggregate resolutions - adrienthebo
Title: Message Title gepetto-bot created an issue Facter / FACT-229 PR (605): Feature/facter 2/fact 65 aggregate resolutions - adrienthebo Issue Type: Task Assignee: Eric Sorenson Components: Community Created: 16/Jan/14 10:54 AM Labels: github Priority: Normal Reporter: gepetto-bot Feature/facter 2/fact 65 aggregate resolutions Author: Adrien Thebo git+git...@somethingsinistral.net Company: Puppet Labs Github ID: adrienthebo Pull Request 605 Discussion Pull Request 605 File Diff Pull Request Description This
Jira (PDB-312) PR (802): Convert unit testing to use dynamic postgres instance - kbarber
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-312 PR (802): Convert unit testing to use dynamic postgres instance - kbarber Change By: Kenneth Barber Affects Version/s: 1.5.0 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-309) Update Schema config conversion logic for 2.0
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-309 Update Schema config conversion logic for 2.0 Change By: Kenneth Barber Affects Version/s: 1.6.0-rc1 Affects Version/s: 1.6.0-rc2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-310) Separate configuration conversion code into it's own library
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-310 Separate configuration conversion code into it's own library Change By: Kenneth Barber Affects Version/s: 1.6.0-rc1 Affects Version/s: 1.6.0-rc2 [~chris]hasaneedforthisintheTrapperKeepercodebasearoundtheJettyconfig thatwasaddedaspartof1 . 6.0. WeshouldmovethisoutintoaseparateJARsothatPuppetDBandTKcanbothuseit. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-13) Add acceptance tests for platforms with a default ruby of 1.9
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-13 Add acceptance tests for platforms with a default ruby of 1.9 Change By: Kenneth Barber Affects Version/s: 1.5.X Fix Version/s: 1.5.X Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-14) Add acceptance tests for platforms with a default ruby of 2.0
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-14 Add acceptance tests for platforms with a default ruby of 2.0 Change By: Kenneth Barber Affects Version/s: 1.5.X Fix Version/s: 1.5.X Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-331) PuppetDB el5 package via prerelease yum repo returns Package does not match intended download
Title: Message Title Matthaus Owens commented on an issue Re: PuppetDB el5 package via prerelease yum repo returns Package does not match intended download The debian createrepo package has an open bug, with a patch available. So Ryan McKern will be rolling out a patched version internally to get around this problem. Add Comment PuppetDB / PDB-331 PuppetDB el5 package via prerelease yum repo returns Package does not match intended download I'm having some trouble with el5 packaging for PuppetDB. Original failures are here: https://jenkins.puppetlabs.com/view/B_PuppetDB/job/PuppetDB%20Acceptance%20IN%20THE%20CLOUD/ I setup my own el5 box and tried to use that repo and got this error: https://gist.github.com/kbarber/8455081 It seems the metadata is not matching the package itself,... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PDB-331) PuppetDB el5 package via prerelease yum repo returns Package does not match intended download
Title: Message Title Matthaus Owens assigned an issue to Ryan McKern PuppetDB / PDB-331 PuppetDB el5 package via prerelease yum repo returns Package does not match intended download Change By: Matthaus Owens Assignee: RyanMcKern Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1438) puppet resource does not handle yum repo files with white space
Title: Message Title lee loucks updated an issue Puppet / PUP-1438 puppet resource does not handle yum repo files with white space Change By: lee loucks Summary: puppetresourcedoesnothandleyumrepofileswithwhite spaec space Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-331) PuppetDB el5 package via prerelease yum repo returns Package does not match intended download
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-331 PuppetDB el5 package via prerelease yum repo returns Package does not match intended download Change By: Kenneth Barber Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-223) Docs pushed
Title: Message Title Justin Holguin commented on an issue Re: Docs pushed Release summary Add Comment Facter / FACT-223 Docs pushed This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-128) Add JavaPackage versions of JDK to Debian/Ubuntu controlfile as a work-around for no JDK7 on squeeze/lucid
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-128 Add JavaPackage versions of JDK to Debian/Ubuntu controlfile as a work-around for no JDK7 on squeeze/lucid Change By: Kenneth Barber Assignee: KennethBarber Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-229) PR (605): Feature/facter 2/fact 65 aggregate resolutions - adrienthebo
Title: Message Title gepetto-bot commented on an issue Re: PR (605): Feature/facter 2/fact 65 aggregate resolutions - adrienthebo puppetcla commented: CLA signed by all contributors. Add Comment Facter / FACT-229 PR (605): Feature/facter 2/fact 65 aggregate resolutions - adrienthebo h2. Feature/facter 2/fact 65 aggregate resolutions * Author: Adrien Thebo git+git...@somethingsinistral.net * Company: Puppet Labs * Github ID: [adrienthebo|https://github.com/adrienthebo] * [Pull Request 605 Discussion|https://github.com/puppetlabs/facter/pull/605] * [Pull Request 605 File Diff|https://github.com/puppetlabs/facter/pull/605/files]... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-229) PR (605): Feature/facter 2/fact 65 aggregate resolutions - adrienthebo
Title: Message Title gepetto-bot commented on an issue Re: PR (605): Feature/facter 2/fact 65 aggregate resolutions - adrienthebo adrienthebo commented: When extracting the Resolvable mixin I got a bit tangled up in how we're validating the string normalization; I replaced it with an expectation that the normalization method was called since normalization isn't part of the resolvable behavior, but this could be argued against. Add Comment Facter / FACT-229 PR (605): Feature/facter 2/fact 65 aggregate resolutions - adrienthebo h2. Feature/facter 2/fact 65 aggregate resolutions * Author: Adrien Thebo git+git...@somethingsinistral.net * Company: Puppet Labs * Github ID: [adrienthebo|https://github.com/adrienthebo] * [Pull Request 605 Discussion|https://github.com/puppetlabs/facter/pull/605] * [Pull Request 605 File Diff|https://github.com/puppetlabs/facter/pull/605/files]... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-1457) fail should be usable in a selector
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1457
fail should be usable in a selector
Issue Type:
New Feature
Assignee:
Unassigned
Created:
16/Jan/14 1:07 PM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
It would be nice if this worked better: pre notify { test: message = $environment ? { production = http://blah/blah/prod, development = http://blah/blah/dev, default = fail(environment '$ {environment}
' is not yet supported), } } /pre
Desired result when the default branch of the selector is taken: Failure to compile the catalog, with the error message environment 'foo' is not supported.
Actual result when the default branch of the selector is taken: Failure to compile the catalog, with the error message Function 'fail' does not return a value.
Use case: Downloading an environment-dependent URL on the client.
Add Comment
Jira (PUP-1457) fail should be usable in a selector
Title: Message Title
Gavin Williams commented on an issue
Re: fail should be usable in a selector
Migrated this in case it's become easier to address with the future parser???
Add Comment
Puppet / PUP-1457
fail should be usable in a selector
It would be nice if this worked better: pre notify { test: message = $environment ? { production = http://blah/blah/prod, development = http://blah/blah/dev, default = fail(environment '${environment}' is not yet supported), } } /pre Desired result when the default branch of the selector is taken...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-985) PR (204): Add default provider fact and make stdlib file_line default. - nanliu
Title: Message Title gepetto-bot commented on an issue Re: PR (204): Add default provider fact and make stdlib file_line default. - nanliu zaphod42 commented: @nanliu @bodepd are you still interested in this change as it is in stdlib? Or are you two saying that in some specific situations it is ok, but there are problems with it in general? Add Comment Puppet / PUP-985 PR (204): Add default provider fact and make stdlib file_line default. - nanliu h2. Add default provider fact and make stdlib file_line default. * Author: Nan Liu * Company: VMware Inc. * Github ID: [nanliu|https://github.com/nanliu] * [Pull Request 204 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/204] * [Pull Request 204 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/204/files] h2. Pull R... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this 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 (HI-136) Is a new version created for the next version in the series?
Title: Message Title gepetto-bot created an issue Hiera / HI-136 Is a new version created for the next version in the series? Issue Type: Sub-task Assignee: Andrew Parker Created: 16/Jan/14 1:56 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-132) Is checklist current
Title: Message Title gepetto-bot created an issue Hiera / HI-132 Is checklist current Issue Type: Sub-task Assignee: Andrew Parker Created: 16/Jan/14 1:56 PM Priority: Normal Reporter: gepetto-bot Check against sub-tickets https://confluence.puppetlabs.com/display/DEL/FOSS+Release+Process Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from
Jira (HI-134) Is there a bug targeted at the release for every commit?
Title: Message Title gepetto-bot created an issue Hiera / HI-134 Is there a bug targeted at the release for every commit? Issue Type: Sub-task Assignee: Andrew Parker Created: 16/Jan/14 1:56 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-140) Smoke test packages
Title: Message Title gepetto-bot created an issue Hiera / HI-140 Smoke test packages Issue Type: Sub-task Assignee: Andrew Parker Created: 16/Jan/14 1:57 PM Priority: Normal Reporter: gepetto-bot Procedure may vary by project and point in the release cycle. Ask around. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop
Jira (HI-138) Tag the release
Title: Message Title gepetto-bot created an issue Hiera / HI-138 Tag the release Issue Type: Sub-task Assignee: Melissa Stone Created: 16/Jan/14 1:56 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-137) Prepare puppet-announcement
Title: Message Title gepetto-bot created an issue Hiera / HI-137 Prepare puppet-announcement Issue Type: Sub-task Assignee: Melissa Stone Created: 16/Jan/14 1:56 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-131) Hiera 1.3.1 Release
Title: Message Title Kylo Ginsberg updated an issue Hiera / HI-131 Hiera 1.3.1 Release Change By: Kylo Ginsberg Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-141) Go/no-go meeting
Title: Message Title gepetto-bot created an issue Hiera / HI-141 Go/no-go meeting Issue Type: Sub-task Assignee: Melissa Stone Created: 16/Jan/14 1:57 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-135) Is there a commit for every bug targeted at the release?
Title: Message Title gepetto-bot created an issue Hiera / HI-135 Is there a commit for every bug targeted at the release? Issue Type: Sub-task Assignee: Andrew Parker Created: 16/Jan/14 1:56 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-133) Ensure tests are passing
Title: Message Title gepetto-bot created an issue Hiera / HI-133 Ensure tests are passing Issue Type: Sub-task Assignee: Andrew Parker Created: 16/Jan/14 1:56 PM Priority: Normal Reporter: gepetto-bot All tests (spec, acceptance) should be passing on all platforms. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop
Jira (HI-131) Hiera 1.3.1 Release
Title: Message Title gepetto-bot created an issue Hiera / HI-131 Hiera 1.3.1 Release Issue Type: Task Assignee: Andrew Parker Created: 16/Jan/14 1:56 PM Priority: Normal Reporter: gepetto-bot See https://confluence.puppetlabs.com/display/DEL/FOSS+Release+Process Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving
Jira (HI-139) Create package
Title: Message Title gepetto-bot created an issue Hiera / HI-139 Create package Issue Type: Sub-task Assignee: Melissa Stone Created: 16/Jan/14 1:56 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-142) Docs pushed
Title: Message Title gepetto-bot created an issue Hiera / HI-142 Docs pushed Issue Type: Sub-task Assignee: Justin Holguin Created: 16/Jan/14 1:57 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-145) Merge into pe branch
Title: Message Title gepetto-bot created an issue Hiera / HI-145 Merge into pe branch Issue Type: Sub-task Assignee: Melissa Stone Created: 16/Jan/14 1:57 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-334) Epic Scoping
Title: Message Title Michelle Johansen created an issue PuppetDB / PDB-334 Epic Scoping Issue Type: Task Assignee: Unassigned Created: 16/Jan/14 1:57 PM Priority: Normal Reporter: Michelle Johansen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-334) Epic Scoping
Title: Message Title Michelle Johansen updated an issue PuppetDB / PDB-334 Epic Scoping Change By: Michelle Johansen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-330) Scope 2.0 epics
Title: Message Title Michelle Johansen updated an issue PuppetDB / PDB-330 Scope 2.0 epics Change By: Michelle Johansen Story Points: 13 5 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-143) Packages pushed
Title: Message Title gepetto-bot created an issue Hiera / HI-143 Packages pushed Issue Type: Sub-task Assignee: Melissa Stone Created: 16/Jan/14 1:57 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-147) Close all resolved tickets in Jira
Title: Message Title gepetto-bot created an issue Hiera / HI-147 Close all resolved tickets in Jira Issue Type: Sub-task Assignee: Melissa Stone Created: 16/Jan/14 1:57 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-131) Hiera 1.3.1 Release
Title: Message Title Kylo Ginsberg updated an issue Hiera / HI-131 Hiera 1.3.1 Release Change By: Kylo Ginsberg Sprint: Week2014-1-15to2014-1-21 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-146) Update the downloads page
Title: Message Title gepetto-bot created an issue Hiera / HI-146 Update the downloads page Issue Type: Sub-task Assignee: Melissa Stone Created: 16/Jan/14 1:57 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (HI-144) Update the branches
Title: Message Title gepetto-bot created an issue Hiera / HI-144 Update the branches Issue Type: Sub-task Assignee: Melissa Stone Created: 16/Jan/14 1:57 PM Priority: Normal Reporter: gepetto-bot Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-330) Scope 2.0 epics Round 1
Title: Message Title Michelle Johansen updated an issue PuppetDB / PDB-330 Scope 2.0 epics Round 1 Change By: Michelle Johansen Summary: Scope2.0epics Round1 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-335) Scope 2.0 epics Round 2
Title: Message Title Michelle Johansen updated an issue PuppetDB / PDB-335 Scope 2.0 epics Round 2 Change By: Michelle Johansen Sprint: 20140129 20140212 to 20140205 20140219 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-335) Scope 2.0 epics Round 2
Title: Message Title Deepak Giridharagopal created an issue PuppetDB / PDB-335 Scope 2.0 epics Round 2 Issue Type: Task Assignee: Unassigned Created: 16/Jan/14 1:59 PM Priority: Normal Reporter: Deepak Giridharagopal We want to do some more forward planning. Our proposal is to flesh out the scope of all the expected 2.0 epics which should allow us to plan out the future sprints to some degree, giving us some idea of how likely we can reach our targets. Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PDB-335) Scope 2.0 epics Round 2
Title: Message Title Michelle Johansen updated an issue PuppetDB / PDB-335 Scope 2.0 epics Round 2 Change By: Michelle Johansen Story Points: 5 3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-330) Scope 2.0 epics Round 1
Title: Message Title Michelle Johansen updated an issue PuppetDB / PDB-330 Scope 2.0 epics Round 1 Change By: Michelle Johansen Story Points: 5 8 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-985) PR (204): Add default provider fact and make stdlib file_line default. - nanliu
Title: Message Title gepetto-bot commented on an issue Re: PR (204): Add default provider fact and make stdlib file_line default. - nanliu nanliu commented: @zaphod42, I'm interested including it to stdlib if at all possible. If a user deploy the vmware vcenter module, they must deploy this patch. it's not optional because the module extended stdlib's file_line: https://github.com/vmware/vmware-vmware_lib/blob/master/lib/puppet/provider/file_line/ssh.rb Add Comment Puppet / PUP-985 PR (204): Add default provider fact and make stdlib file_line default. - nanliu h2. Add default provider fact and make stdlib file_line default. * Author: Nan Liu * Company: VMware Inc. * Github ID: [nanliu|https://github.com/nanliu] * [Pull Request 204 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/204] * [Pull Request 204 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/204/files] h2. Pull R... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving
Jira (PUP-1450) [Windows] Copying file resources from non-NTFS volumes causes Invalid DACL errors
Title: Message Title Ethan Brown assigned an issue to Ethan Brown Puppet / PUP-1450 [Windows] Copying file resources from non-NTFS volumes causes Invalid DACL errors Change By: Ethan Brown Assignee: EthanBrown Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-216) Is there a commit for every bug targeted at the release?
Title: Message Title Kylo Ginsberg commented on an issue Re: Is there a commit for every bug targeted at the release? Verified. Add Comment Facter / FACT-216 Is there a commit for every bug targeted at the release? This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-215) Is there a bug targeted at the release for every commit?
Title: Message Title Kylo Ginsberg commented on an issue Re: Is there a bug targeted at the release for every commit? Redmine #22107, aka FACT-82 Redmine #21868/21760/22005, aka FACT-182 Add Comment Facter / FACT-215 Is there a bug targeted at the release for every commit? This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (FACT-216) Is there a commit for every bug targeted at the release?
Title: Message Title Kylo Ginsberg commented on an issue Re: Is there a commit for every bug targeted at the release? https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20FACT%20AND%20fixVersion%20%3D%20%221.7.5%22%20ORDER%20BY%20status%20DESC%2C%20priority%20DESC Add Comment Facter / FACT-216 Is there a commit for every bug targeted at the release? This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1453) [Windows][Future] Running as non-Admin tries to create folders at C:/Users/Administrator/.puppet (no matter who the logged in user is)
Title: Message Title
Rob Reynolds commented on an issue
Re: [Windows][Future] Running as non-Admin tries to create folders at C:/Users/Administrator/.puppet (no matter who the logged in user is)
It's related to the fact that on the box - it goes with the SYSTEM environment variable for HOME, which is correctly set to C:\Users\Administrator. There should also be one in the USER env variables, but it isn't necessarily set on the creation of users.
One Reference: http://superuser.com/questions/375079/why-does-windows-xp-setting-environment-variable-to-userprofile-return-the-wro
Add Comment
Puppet / PUP-1453
[Windows][Future] Running as non-Admin tries to create folders at C:/Users/Administrator/.puppet (no matter who the logged in user is)
Who am I? {noformat} echo %USERNAME% {noformat} - bob From the codebase: {noformat} bundle exec puppet apply -e file {'c:/temp2':ensure=directory} --debug --trace --verbose {noformat} produces this: {noformat} Error: Could not set 'directory' on ensure: Permission denied - C:/Users/Administrator/.puppet C:/code/puppetlabs/puppet/lib/p...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-1458) Windows ACL support
Title: Message Title redmine.exporter created an issue Puppet / PUP-1458 Windows ACL support Issue Type: New Feature Assignee: Eric Sorenson Created: 16/Jan/14 2:44 PM Labels: redmine Priority: Normal Reporter: redmine.exporter Puppet's current implementation of mapping POSIX modes to Windows ACLs has some limitations. Puppet can only assign permissions to owner and group, but it's common practice on Windows systems to set full control to Administrators, LocalSystem, and Users, which is more than can be represented in our model, without creating a local group. Puppet doesn't support deny access control entries Puppet should support setting multiple access control entries, deny/allow aces, and inheritance. See http://technet.microsoft.com/en-us/library/bb727008.aspx for common permissions. Another option would be to express permissions in terms of SDDL, but that is likely overkill.
Jira (PUP-985) PR (204): Add default provider fact and make stdlib file_line default. - nanliu
Title: Message Title gepetto-bot commented on an issue Re: PR (204): Add default provider fact and make stdlib file_line default. - nanliu jhoblitt commented: @nanliu While it's not a fix for the odd provider selection issues your seeing, I very successfully manage sshd_config with the augeasproviders type: https://github.com/hercules-team/augeasproviders/blob/master/lib/puppet/type/sshd_config.rb Add Comment Puppet / PUP-985 PR (204): Add default provider fact and make stdlib file_line default. - nanliu h2. Add default provider fact and make stdlib file_line default. * Author: Nan Liu * Company: VMware Inc. * Github ID: [nanliu|https://github.com/nanliu] * [Pull Request 204 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/204] * [Pull Request 204 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/204/files] h2. Pull R... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-985) PR (204): Add default provider fact and make stdlib file_line default. - nanliu
Title: Message Title gepetto-bot commented on an issue Re: PR (204): Add default provider fact and make stdlib file_line default. - nanliu nanliu commented: @jhoblitt thanks for the suggestion, but I'm managing sshd configs on a esx server with no puppet agent installed. Add Comment Puppet / PUP-985 PR (204): Add default provider fact and make stdlib file_line default. - nanliu h2. Add default provider fact and make stdlib file_line default. * Author: Nan Liu * Company: VMware Inc. * Github ID: [nanliu|https://github.com/nanliu] * [Pull Request 204 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/204] * [Pull Request 204 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/204/files] h2. Pull R... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-985) PR (204): Add default provider fact and make stdlib file_line default. - nanliu
Title: Message Title gepetto-bot commented on an issue Re: PR (204): Add default provider fact and make stdlib file_line default. - nanliu jhoblitt commented: @nanliu Doh, for reason I thought you making some modification to how file_line was parsing ssh config files, not wedging the ssh transport layer in. Please excuse my pocket universe... Add Comment Puppet / PUP-985 PR (204): Add default provider fact and make stdlib file_line default. - nanliu h2. Add default provider fact and make stdlib file_line default. * Author: Nan Liu * Company: VMware Inc. * Github ID: [nanliu|https://github.com/nanliu] * [Pull Request 204 Discussion|https://github.com/puppetlabs/puppetlabs-stdlib/pull/204] * [Pull Request 204 File Diff|https://github.com/puppetlabs/puppetlabs-stdlib/pull/204/files] h2. Pull R... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this 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-1368) Puppet on Windows segfaulting
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1368 Puppet on Windows segfaulting Change By: Joshua Cooper Summary: WIndowsScheduledTaskcausesseg-fault PuppetonWindowssegfaulting Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1368) WIndows Scheduled Task causes seg-fault
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1368 WIndows Scheduled Task causes seg-fault Change By: Joshua Cooper UX Priority: Major Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1368) Puppet on Windows segfaulting
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1368 Puppet on Windows segfaulting Change By: Joshua Cooper Sprint: Week2014-1-15to2014-1-21 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-1368) Puppet on Windows segfaulting
Title: Message Title Joshua Cooper updated an issue Puppet / PUP-1368 Puppet on Windows segfaulting Change By: Joshua Cooper Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PDB-331) PuppetDB el5 package via prerelease yum repo returns Package does not match intended download
Title: Message Title Matthaus Owens assigned an issue to Ryan McKern PuppetDB / PDB-331 PuppetDB el5 package via prerelease yum repo returns Package does not match intended download Change By: Matthaus Owens Assignee: ReleaseEngineering RyanMcKern Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (MCO-143) Windows agents stop working when the mcollective service cannot be restarted
Title: Message Title Rob Reynolds commented on an issue Re: Windows agents stop working when the mcollective service cannot be restarted Does fixing MCO-158 fix this issue? Add Comment MCollective / MCO-143 Windows agents stop working when the mcollective service cannot be restarted The windows mcollective service fails to restart from puppet after multiple restarts in a row. The easiest way I found to reproduce the issue is the following: 1. Install PE3.1 with one windows agent 2. Run `puppet agent -t` on the windows agent and make sure the pe_mcollective module has been applied 3. Change `/etc/puppetlabs/mcollective/cr... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (MCO-161) Investigate possible loss of parity between standard Puppet Labs packaging and mco plugin package
Title: Message Title Simon Croome commented on an issue Re: Investigate possible loss of parity between standard Puppet Labs packaging and mco plugin package As PE customers we use mco plugin package. I agree with RI that there should be a single method for packaging. I don't know anything about the new method but am willing to give it a try given a pointer to some docs on how I need to setup my environment. In the meantime, I hope mco plugin package doesn't lose favour. Add Comment MCollective / MCO-161 Investigate possible loss of parity between standard Puppet Labs packaging and mco plugin package User feedback has brought up the fact that if plugin packaging moves to the standard Puppet Labs packaging methods mco plugin package becomes devalued. We need to have the discussion here if we should review moving forward with standardising packaging or move back to using mco plugin package. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it,
Jira (PUP-1048) PR (2161): (#21641) Windows puppet service should log to the eventlog - glennsarti
Title: Message Title gepetto-bot commented on an issue Re: PR (2161): (#21641) Windows puppet service should log to the eventlog - glennsarti peterhuene commented: Hi Glenn, Thanks for the pull request! The changes generally look good and I only have the three comments I made to the commit. It looks like we need to rebase your changes before we can merge the PR. Add Comment Puppet / PUP-1048 PR (2161): (#21641) Windows puppet service should log to the eventlog - glennsarti h2. (#21641) Windows puppet service should log to the eventlog * Author: * Company: * Github ID: [glennsarti|https://github.com/glennsarti] * [Pull Request 2161 Discussion|https://github.com/puppetlabs/puppet/pull/2161] * [Pull Request 2161 File Diff|https://github.com/puppetlabs/puppet/pull/2161/files] h2. Pull Request Description (#21... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (PUP-1048) PR (2161): (#21641) Windows puppet service should log to the eventlog - glennsarti
Title: Message Title Peter Huene assigned an issue to Peter Huene Puppet / PUP-1048 PR (2161): (#21641) Windows puppet service should log to the eventlog - glennsarti Change By: Peter Huene Assignee: PeterHuene Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
Jira (PUP-536) Create endpoint for enumerating environments
Title: Message Title Luke Kanies commented on an issue Re: Create endpoint for enumerating environments Will this be the single source of truth for environments, or meant more as a means of knowing what a given master sees? It seems difficult to make it a single source of truth, given that any master is likely to have a different list. Could/would we promote this to a separate service, like the node classifier? Add Comment Puppet / PUP-536 Create endpoint for enumerating environments Much of the Node Classifier and Continuous Delivery work is predicated on improved support for environments, and one significant gap is the absence of a way to enumerate the environments known to a puppet master. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-576) Add a fedora19 host to the platforms we are testing in ci.
Title: Message Title Joshua Cooper commented on an issue Re: Add a fedora19 host to the platforms we are testing in ci. f18 is EOL and will being phased out of the vsphere pool (QA-729). Once we have f19 in acceptance, we can remove f18 from the pool and our acceptance matrix. Add Comment Puppet / PUP-576 Add a fedora19 host to the platforms we are testing in ci. We are not currently testing on fedora19 because of two test failures we haven't had time to resolve. I believe fedora19 is the only platform currently available in our dynamic vcloud templates running Ruby 2.0, so it would be good to get this in. The two failures are: 1) helpful_error_message_when_hostname_not_match_server_certificate.rb 2) store... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-1048) PR (2161): (#21641) Windows puppet service should log to the eventlog - glennsarti
Title: Message Title gepetto-bot commented on an issue Re: PR (2161): (#21641) Windows puppet service should log to the eventlog - glennsarti glennsarti commented: Thanks Peter, yes I just had a look at the current daemon.rb file and it doesn't look like it will be too hard to merge the changes. I'll try doing a rebase soon. Add Comment Puppet / PUP-1048 PR (2161): (#21641) Windows puppet service should log to the eventlog - glennsarti h2. (#21641) Windows puppet service should log to the eventlog * Author: * Company: * Github ID: [glennsarti|https://github.com/glennsarti] * [Pull Request 2161 Discussion|https://github.com/puppetlabs/puppet/pull/2161] * [Pull Request 2161 File Diff|https://github.com/puppetlabs/puppet/pull/2161/files] h2. Pull Request Description (#21... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
