Jira (PDB-1848) Cannot parse value for max-frame-size in command-processing
Title: Message Title
John Duarte created an issue
PuppetDB / PDB-1848
Cannot parse value for max-frame-size in command-processing
Issue Type:
Bug
Affects Versions:
PDB 2.3.6
Assignee:
Unassigned
Created:
2015/08/03 4:03 PM
Priority:
Normal
Reporter:
John Duarte
After adding a numeric value for max-frame-size in /etc/puppetlabs/puppetdb/conf.d/config.ini the server fails with the following error stating that it is not a String
clojure.lang.ExceptionInfo: Value does not match schema: {:max-frame-size (not (instance? java.lang.String 2048))}
However, when quoting the value to pass it as a string, the server then fails with the following error showing that the wireFormat.maxFrameSize does not expect a quoted value.
Jira (PUP-4984) Prepare long form release notes and short form release story
Title: Message Title Nicholas Fagerlund assigned an issue to Jorie Tappa Puppet / PUP-4984 Prepare long form release notes and short form release story Change By: Nicholas Fagerlund Assignee: NicholasFagerlund JorieTappa Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4622) Add a diff command in Puppet filebucket
Title: Message Title Michael Smith assigned an issue to qa Puppet / PUP-4622 Add a diff command in Puppet filebucket Change By: Michael Smith Status: Readyfor CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3045) exec resource with timeout doesn't kill executed command that times out
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3045 exec resource with timeout doesn't kill executed command that times out Change By: Charlie Sharpsteen Labels: customersupport Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3045) exec resource with timeout doesn't kill executed command that times out
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-3045 exec resource with timeout doesn't kill executed command that times out Change By: Charlie Sharpsteen Affects Version/s: PUP3.7.5 Affects Version/s: PUP3.8.1 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4545) Too many restarts on interface changes for Fedora, RHEL, CentOS
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4545 Too many restarts on interface changes for Fedora, RHEL, CentOS Change By: Kylo Ginsberg Summary: Toomanyrestartson interaface interface changesforFedora,RHEL,CentOS Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1123) Facter explodes with invalid locales
Title: Message Title Michael Smith assigned an issue to Michael Smith Facter / FACT-1123 Facter explodes with invalid locales Change By: Michael Smith Assignee: MichaelSmith Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1123) Facter explodes with invalid locales
Title: Message Title Michael Smith assigned an issue to qa Facter / FACT-1123 Facter explodes with invalid locales Change By: Michael Smith Status: Readyfor CI Test Assignee: MichaelSmith qa Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4813) Can't generate exit codes 4 or 6 with puppet agent -test
Title: Message Title Erik Dasher commented on PUP-4813 Re: Can't generate exit codes 4 or 6 with puppet agent -test https://groups.google.com/forum/#!searchin/puppet-dev/PUP-4813|sort:relevance/puppet-dev/QMTJli2oabc/HJl_AVFaSnIJ https://groups.google.com/forum/?utm_medium=emailutm_source=footer#!msg/puppet-dev/yZ4lwtngoao/48d6ZcX8YPwJ Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1737) Change storage_utils to dispatch on driver class
Title: Message Title Andrew Roetker assigned an issue to Unassigned PuppetDB / PDB-1737 Change storage_utils to dispatch on driver class Change By: Andrew Roetker Assignee: AndrewRoetker Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4828) Scope out a HOCON port to C++
Title: Message Title Kylo Ginsberg commented on PUP-4828 Re: Scope out a HOCON port to C++ Great job on this - thanks Maggie Dreyer! Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1144) Memory resolver for OpenBSD
Title: Message Title Peter Huene updated an issue Facter / FACT-1144 Memory resolver for OpenBSD Change By: Peter Huene Story Points: 1 Sprint: Client2015-08-19 Scrum Team: ClientPlatform Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1144) Memory resolver for OpenBSD
Title: Message Title Peter Huene updated an issue Facter / FACT-1144 Memory resolver for OpenBSD Change By: Peter Huene Fix Version/s: FACT3.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1721) Possible Memory leak with PuppetDB?
Title: Message Title Wyatt Alt commented on PDB-1721 Re: Possible Memory leak with PuppetDB? Simon Oxwell Richard Chatterton To address this we've made some changes that will reduce the size of cached prepared statements in the case of large structured facts, and also flipped the default statement cache size to 0 from 1000, after having concluded that the cache size doesn't have much of an operational impact. We're shooting to release these changes tomorrow – looking forward to hearing if the issue is resolved. Wyatt Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4984) Prepare long form release notes and short form release story
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-4984 Prepare long form release notes and short form release story Jorie Tappa, I've attached a preliminary list sorted into what I think the categories are. [Here's a Jira query with the tickets sorted by Release Notes field.|https://tickets.puppetlabs.com/issues/?jql=fixVersion%20%3D%20%22PUP%203.8.2%22%20AND%20project%20%3D%20PUP%20ORDER%20BY%20cf[11100]%20ASC] I've asked Kylo Ginsberg to have engineers double check their descriptions; if they haven't set the release notes summary field to either a description of the fix or see summary, that ticket may still be incomplete. Change By: Nicholas Fagerlund Attachment: 2015.08.03(1052)Puppet3.8.2.txt Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4865) Package resources no longer fail with bad names on EL5
Title: Message Title Michael Smith assigned an issue to qa Puppet / PUP-4865 Package resources no longer fail with bad names on EL5 Change By: Michael Smith Status: Readyfor CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1153) Facter build includes libcrypto.so multiple times
Title: Message Title Matthaus Owens created an issue Facter / FACT-1153 Facter build includes libcrypto.so multiple times Issue Type: Bug Assignee: Unassigned Created: 2015/08/03 4:09 PM Priority: Normal Reporter: Matthaus Owens When building facter on solaris 10, I get the following warning from ld, ld: warning: file /opt/puppetlabs/puppet/lib/libcrypto.so: attempted multiple inclusion of file Because -Werror is passed to g++, this fails the build. An example command that fails is the following (from building libfacter_test): /opt/pl-build-tools/bin/i386-pc-solaris2.10-g++ -pthreads -fPIC -pthreads -fPIC -Wno-maybe-uninitialized -std=c++11 -Wall -Werror -Wno-unused-parameter -Wno-unused-local-typedefs -Wno-unknown-pragmas -Wno-missing-field-initializers -O3 -DNDEBUG -Wl,-rpath=/opt/pl-build-tools/lib:/opt/pl-build-tools/lib64 -Wl,-rpath=/opt/pl-build-tools/lib:/opt/pl-build-tools/lib64 CMakeFiles/libfacter_test.dir/facts/array_value.cc.o CMakeFiles/libfacter_test.dir/facts/boolean_value.cc.o CMakeFiles/libfacter_test.dir/facts/double_value.cc.o CMakeFiles/libfacter_test.dir/facts/external/json_resolver.cc.o CMakeFiles/libfacter_test.dir/facts/external/text_resolver.cc.o CMakeFiles/libfacter_test.dir/facts/external/yaml_resolver.cc.o CMakeFiles/libfacter_test.dir/facts/collection.cc.o CMakeFiles/libfacter_test.dir/facts/integer_value.cc.o CMakeFiles/libfacter_test.dir/facts/map_value.cc.o
Jira (PUP-4975) caching server certificate performed twice?
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4975 caching server certificate performed twice? Change By: Kylo Ginsberg Scrum Team: ClientPlatform Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4813) Can't generate exit codes 4 or 6 with puppet agent -test
Title: Message Title Kylo Ginsberg commented on PUP-4813 Re: Can't generate exit codes 4 or 6 with puppet agent -test Per the discussion in puppet-dev, this is going to fan out into several tickets. I think we're ready to define those tickets, and this one either needs to be renamed or perhaps discarded in favor of the more detailed tickets. Once we have those tickets broken out, we can think about what order to fix what in. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4994) Request for vcenter module to be supported
Title: Message Title CJ Toolseram created an issue Puppet / PUP-4994 Request for vcenter module to be supported Issue Type: New Feature Assignee: Unassigned Created: 2015/08/03 10:07 PM Priority: Trivial Reporter: CJ Toolseram Request to have vcenter module from puppetlabs to be supported. https://forge.puppetlabs.com/puppetlabs/vcenter Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (FACT-1154) $::rubysitedir pointing to wrong directory.
Title: Message Title Anandkumar Asokan created an issue Facter / FACT-1154 $::rubysitedir pointing to wrong directory. Issue Type: Bug Affects Versions: FACT 3.0.0 Assignee: Unassigned Components: PE Created: 2015/08/03 10:28 PM Priority: Normal Reporter: Anandkumar Asokan Facter `facter -p rubysitedir` in PE 2015.2 is pointing to the wrong directory. ls `facter -p rubysitedir` ls: cannot access /opt/puppetlabs/puppet/lib/ruby/site_ruby/2.1.0: No such file or directory Its referencing the right dir in later PE versions. [root@pe-381-master testing]# `facter -p rubysitedir`bash: /opt/puppet/lib/ruby/site_ruby/1.9.1: is a directory [root@pe-381-master testing]# facter -p rubysitedir /opt/puppet/lib/ruby/site_ruby/1.9.1 PE 2015.2 is linking to /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/ instead.
Jira (PUP-4959) Custom facts are missing when modules are shared between machines in VirtualBox
Title: Message Title
Juha Vainikka updated an issue
Puppet / PUP-4959
Custom facts are missing when modules are shared between machines in VirtualBox
Change By:
Juha Vainikka
Summary:
Customfactsaremissingwhenmodulesareshared using betweenmachinesin VirtualBox
Withfollowingsampleproject:{noformat}example├──environments│├──local││└──environment.conf│└──vagrant│└──environment.conf├──manifests│└──site.pp└──modules└──simplefact└──lib└──facter└──helloworld.rb$catexample/environments/local/environment.confmodulepath=c:/example/modulesmanifest=c:/example/manifests/site.pp$catexample/environments/vagrant/environment.confmodulepath=c:/vagrant/example/modulesmanifest=c:/vagrant/example/manifests/site.pp$catexample/manifests/site.ppnotify{$hello_world:}$catexample/modules/simplefact/lib/facter/helloworld.rbFacter.add(hello_world)dosetcodedofoobarendend{noformat}RunningPuppet4(puppet-agent-1.2.2-x64.msi)insideWindowsguestgivesfollowingoutput:puppetapply--environmentpathenvironments--environmentlocalmanifests\site.pp{noformat}Notice:Compiledcatalogforwin2008r2.fi.logica.cominenvironmentlocalin0.30secondsNotice:foobarNotice:/Stage[main]/Main/Notify[foobar]/message:defined'message'as'foobar'Notice:Appliedcatalogin0.03seconds{noformat}puppetapply--environmentpathenvironments--environmentvagrantmanifests\site.pp{noformat}Error:EvaluationError:Missingtitle.Thetitle_expression_resultedinundefatC:/example/manifests/site.pp:1:9onnodewin2008r2.fi.demobox.com{noformat}Bothenvironmentsworkwithpuppet-3.8.1-x64.msi. Fulldebugoutputforfailingrunisprovidedinattachment.HostisWindows7andVirtualBoxversionis5.0.0r101573 CurrentlythispreventsustomovetoPuppet4 .Fulldebugoutputforfailingrun becauseVagrant/VirtualBox is provided acriticalpiece in attachment ouracceptancetestingprocess .
Add Comment
Jira (PUP-4905) Add feature switch for appmgmt
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-4905 Add feature switch for appmgmt Change By: Thomas Hallgren Assignee: ThomasHallgren Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4905) Add feature switch for appmgmt
Title: Message Title Thomas Hallgren commented on PUP-4905 Re: Add feature switch for appmgmt Merged to master at 7766695 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1847) with-log-level-and-logging-to-atom test may fail
Title: Message Title
Rob Browning created an issue
PuppetDB / PDB-1847
with-log-level-and-logging-to-atom test may fail
Issue Type:
Bug
Assignee:
Unassigned
Created:
2015/08/03 9:34 AM
Priority:
Normal
Reporter:
Rob Browning
On current master, this:
lein test :only puppetlabs.puppetdb.command-test puppetlabs.puppetdb.testutils.services-test
sometimes fail like this:
FAIL in (with-log-level-and-logging-to-atom) (services_test.clj:22) expected: (some (fn* [p1__36896#] (= {:level INFO, :message wlta-test} p1__36896#)) (map event-map (clojure.core/deref log))) actual: (not (some #object[puppetlabs.puppetdb.testutils.services_test$fn__36897$fn__36918 0x3432573c puppetlabs.puppetdb.testutils.services_test$fn__36897$fn__36918@3432573c] ()))
PDB-1845 might be one way to fix the problem.
Add Comment
Jira (PDB-1739) Upgrade query namespaces to the new java.jdbc
Title: Message Title Rob Browning assigned an issue to Unassigned PuppetDB / PDB-1739 Upgrade query namespaces to the new java.jdbc Change By: Rob Browning Assignee: RobBrowning Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1739) Upgrade query namespaces to the new java.jdbc
Title: Message Title Rob Browning commented on PDB-1739 Re: Upgrade query namespaces to the new java.jdbc Removing from current sprint and replacing with https://tickets.puppetlabs.com/browse/PDB-1737, which needs to go first. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4941) Reserve keywords 'application', 'consumes', and 'produces'
Title: Message Title Hailee Kenney assigned an issue to qa Puppet / PUP-4941 Reserve keywords 'application', 'consumes', and 'produces' Change By: Hailee Kenney Status: Readyfor CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4813) Can't generate exit codes 4 or 6 with puppet agent -test
Title: Message Title Erik Dasher commented on PUP-4813 Re: Can't generate exit codes 4 or 6 with puppet agent -test It has been nearly two weeks since the last activity on this ticket. Can we have an update? We have a number of tests that are being skipped because we rely on the various exit codes from puppet agent. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4818 PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Change By: Kylo Ginsberg Summary: PUP-121(relativenamespacing)wasnever acutally actually resolvedin3.xfutureparser Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4760) Service type should not retrieve ensure status when not needed
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4760 Service type should not retrieve ensure status when not needed Change By: Kylo Ginsberg Sprint: Client2015-09-02 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4238) msgpack tries to read private key, complains about permissions
Title: Message Title Lindsey Smith updated an issue Puppet / PUP-4238 msgpack tries to read private key, complains about permissions Change By: Lindsey Smith CS Priority: Critical Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4988) Push tag
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4988 Push tag Issue Type: Sub-task Assignee: Melissa Stone Created: 2015/08/03 12:15 PM Priority: Normal Reporter: Kylo Ginsberg The development team is responsible for updating the stable/master branches as necessary. This will be done after the version bump in version.rb. Dependencies: Go / No Go meeting (except where it's required to push the tag to build packages - MSIs) Add Comment This message was sent by Atlassian JIRA
Jira (PUP-4619) fstab entries can be written in bad order
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4619 fstab entries can be written in bad order Change By: Kylo Ginsberg Sprint: Client2015-07-22,Client2015- 08 09 - 19 02 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4978) Is the code ready for release?
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4978 Is the code ready for release? Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/08/03 12:14 PM Priority: Normal Reporter: Kylo Ginsberg If there are any version dependencies expressed in the code base, make sure these are up to date. For Puppet, make sure the shas used to build the MSI are correct. For Puppet-Server, make sure all references to the puppet version are correct. All tests (spec, acceptance) should be passing on all platforms for both stable master. If a new platform has been added, make sure that platform has acceptance testing, new features have decent coverage, etc. etc. If the release is going to be cut from a sha, rather than the head of a branch, make sure that sha specifically has gone through spec/acceptance/etc. tests Move all items that should be moved from Ready for CI to Ready for Review Have all tickets been resolved (passed Functional Review)? If not please add any missing tickets to the current sprint's board. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PUP%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%223.8.2%22
Jira (PUP-4981) Update version number in source
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4981 Update version number in source Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/08/03 12:14 PM Priority: Normal Reporter: Kylo Ginsberg Bump VERSION in lib/PUP/version.rb or project.clj to correct version. Commit the updated version file. e.g) commit -m (packaging) Update FACTERVERSION to 1.7.3. If any merging needs to happen (i.e. master into stable/stable into master), it can now happen (different subtask). Once this is done, hand the SHA to be built to RelEng to be tagged. Dependencies: Is the code ready for release? Is there a commit for every JIRA ticket targeted at the release?
Jira (PUP-4977) puppet 3.8.2 2015-08-06 Release
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4977 puppet 3.8.2 2015-08-06 Release Issue Type: Task Assignee: Kylo Ginsberg Created: 2015/08/03 12:14 PM Priority: Normal Reporter: Kylo Ginsberg puppet 3.8.2 2015-08-06 Release When working through this ticket, add it to the board and then keep it in the Ready for Engineering column. Move the subtasks to In Progress when you are working on them and Resolved when you have completed them. In general subtasks should only be moved to Ready for Engineering when they are ready to be worked on. For some assignees this is their cue to start working on release-related items. The first set of tickets are assigned to the developer, those can all be converted to Ready for Engineering and you can start working through them. Only when those are done should you move the Prepare notes and Tag release/create packages tasks to Ready for Engineering. Ping those assigned to move forward. When you hear back for Tag Release/create packages, you should move Smoke test packages to Ready for Engineering or In Progress if you are ready.
Jira (PUP-4984) Prepare long form release notes and short form release story
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4984 Prepare long form release notes and short form release story Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2015/08/03 12:14 PM Priority: Normal Reporter: Kylo Ginsberg Collaborating with product for release story Dependencies: Is there a JIRA ticket targeted at the release for every commit? Is there a commit for every JIRA ticket targeted at the release? Add Comment
Jira (PUP-4987) Go/no-go meeting (before 4pm)
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4987 Go/no-go meeting (before 4pm) Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/08/03 12:15 PM Priority: Normal Reporter: Kylo Ginsberg This should happen Monday-Thursday, before 4pm. We should not be shipping anything after 4:00 PM or on a Friday both for our users, and because shipping takes time. Get a yes/no for the release from dev, docs, product, qa, releng. This meeting is informal, over chat, and usually happens right before packages are pushed. Keep in mind we typically do not ship releases in the evening and we don't ship on Friday if the release is a final release. Dependencies: Smoke testing Add Comment
Jira (PUP-4985) Tag the release and create packages
Title: Message Title
Kylo Ginsberg created an issue
Puppet / PUP-4985
Tag the release and create packages
Issue Type:
Sub-task
Assignee:
Melissa Stone
Created:
2015/08/03 12:15 PM
Priority:
Normal
Reporter:
Kylo Ginsberg
Tag and create packages
Developer provides the SHA - Kylo Ginsberg - Please add the SHA as a comment (this should be the commit which contains the newly updated version.rb)
checkout the sha
Make sure you are about to tag the correct thing
Create the tag e.g.) git tag -s -u {GPG key}
-m 1.7.3 1.7.3
You need to know the pass phrase for this to complete successfully. It's important that we make sure all releases are signed to verify authenticity.
DO NOT push the tag to the repo, keep it local only
`git describe` will show you the tag. Make sure you're building what you think you're building.
Jira (PUP-4983) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4983 Is the Jira tidy-up done for this release and prepared for the next one? Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/08/03 12:14 PM Priority: Normal Reporter: Kylo Ginsberg This happens on Jira - we need to clean up the current release and prepare for the next release. Mark the version that's going out as Released in the Project Admin - Versions panel. Create a version we can target future issues or issues that didn't make it into the current release. (e.g. if we're releasing Facter 1.7.4, make sure there's a 1.7.5 version (or at least 1.7.x if there's isn't another bug release planned for the near future) Create a public pair of queries for inclusion in the release notes/announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes slated for the next release (Paste their URLs into the Release story ticket): 'project = XX AND affectedVersion = 'X.Y.Y', Save as Introduced in X.Y.Y, click Details, add permission for Everyone 'project = XX AND fixVersion = 'X.Y.Z', Save as Fixes for X.Y.Z, click Details, add permission for Everyone
Jira (PUP-4982) Merge master into stable
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4982 Merge master into stable Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/08/03 12:14 PM Priority: Normal Reporter: Kylo Ginsberg For some releases, the code base will need to be merged down to stable. NOTE: This is usually only during a x.y.0 release, but even then it may have already been done. If it doesn't apply, close this ticket. Assuming you have origin (your remote) and upstream (puppetlabs remote), the commands will look something like this: git fetch upstream git rebase upstream/master git checkout stable
Jira (PUP-4986) Smoke test packages
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4986 Smoke test packages Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/08/03 12:15 PM Priority: Normal Reporter: Kylo Ginsberg Procedure may vary by project and point in the release cycle. Ask around. In general this should happen on a variety of platforms, i.e. one or two each of kind of package we create (i.e., gem, dmg, msi, deb, rpm, etc). For Puppet, our acceptance suite now tests service scripts, and on debian, a passenger master. Manual smoke testing can therefore be limited to other package formats than deb and rpm. Lighter testing of Z releases is acceptable. Add a link to the Packages repository that you receive from the Tag and create packages subtask Ping folks on your team for help with different platforms. When you pick up a platform, please leave a comment below that you are testing it. When it looks good, leave another comment, preferably with a code snippet showing the commands executed and their output. When all platforms picked have been smoke tested, move this ticket to done. IMPORTANT: Please edit the description of this ticket and remove Example: below. Edit the platforms to
Jira (PUP-4980) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4980 Is there a commit for every JIRA ticket targeted at the release? Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/08/03 12:14 PM Priority: Normal Reporter: Kylo Ginsberg Ensure all tickets targeted at the release have a corresponding commit git log old tag..new tag This time, look through tickets targeted at this release in JIRA, and compare it to the commit log, looking for the corresponding numbers ticketmatch.rb script is a ruby script that helps with Is there a JIRA ticket targeted at the release for every commit? and Is there a commit for every JIRA ticket targeted at the release? (it beats doing it manually, but requires manual steps and hacking the script for the specific release) There is also the release-inquisition, which also helps a lot with this task. Add Comment
Jira (PUP-4760) Service type should not retrieve ensure status when not needed
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4760 Service type should not retrieve ensure status when not needed Change By: Kylo Ginsberg Scrum Team: ClientPlatform Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4992) Close all resolved tickets in Jira
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4992 Close all resolved tickets in Jira Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/08/03 12:15 PM Priority: Normal Reporter: Kylo Ginsberg Close any tickets that have been resolved for the release. https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20PUP%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20%223.8.2%22%20AND%20status%20%3D%20Resolved There is a bulk edit at the top (a gear with the word Tools). Should you decide to take this route: Select Bulk Change - All # issues Step 1 - choose all relevant issues (likely all of them) Step 2 - Select Transition Issues Step 3 - Select Closed Step 4 - Select Fixed in Change Resolution. View what is about to change and confirm it. Then commit the change. Dependencies:
Jira (PUP-4989) Packages pushed
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4989 Packages pushed Issue Type: Sub-task Assignee: Melissa Stone Created: 2015/08/03 12:15 PM Priority: Normal Reporter: Kylo Ginsberg Push packages run `rake pl:jenkins:uber_ship` You will need the keys to the castle (aka the passphrase) for this to work. Don't forget to make sure everything looks like it's in the correct folder, the pkgs dir has been cleared out, and that you are shipping for all expected platforms. Get a second set of RelEng eyes on the packages that are about to be shipped to make sure everything looks a-okay. If you're shipping a gem you need to make sure you have a rubygems account, are an owner of that project, and have a gem config file. If you're shipping puppet you need to sign the MSI file for Windows. This is a manual process and the ship task doesn't ship or build the msi so talk to Moses or Haus for more details. This file also needs to be manually signed. Dependencies:
Jira (PUP-4991) Send out announcements
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4991 Send out announcements Issue Type: Sub-task Assignee: Eric Sorenson Created: 2015/08/03 12:15 PM Priority: Normal Reporter: Kylo Ginsberg Melissa Stone: update the release google spreadsheet. Update the MSI build targets in the Puppet repo in ext/build_defaults.yaml. This needs to be done for any projects that are to get into the MSI (facter and hiera as of 8/2014) Send the drafted release notes email. If final send to puppet-announce and specific distribution lists (e.g. puppet to puppet-users puppet-dev). If this release has security implications, also send the release announcement to puppet-security-announce Make a PSA on IRC letting those kiddos know about the new release. Something along the lines of PSA: facter 1.7.3 now available Dependencies:
Jira (PUP-4979) Is there a JIRA ticket targeted at the release for every commit?
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4979 Is there a JIRA ticket targeted at the release for every commit? Issue Type: Sub-task Assignee: Kylo Ginsberg Created: 2015/08/03 12:14 PM Priority: Normal Reporter: Kylo Ginsberg Ensure all tickets referenced in the commit log have a bug targeted at the release git log old tag..new tag look through, and make sure that if there is a JIRA ticket number referenced in any of the commits, that ticket is targeted at the release Also, make sure the code itself is sane, that you understand why the change was made, etc. etc. ticketmatch.rb script is a ruby script that helps with Is there a JIRA ticket targeted at the release for every commit? and Is there a commit for every JIRA ticket targeted at the release? (it beats doing it manually, but requires manual steps and hacking the script for the specific release). There is also the release-inquisition, which also helps a lot with this task.
Jira (PUP-4990) Docs pushed
Title: Message Title Kylo Ginsberg created an issue Puppet / PUP-4990 Docs pushed Issue Type: Sub-task Assignee: Nicholas Fagerlund Created: 2015/08/03 12:15 PM Priority: Normal Reporter: Kylo Ginsberg Push the documentation updates to docs.puppetlabs.com. Dependencies: Go / No Go meeting (Status - Ship it!) Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PUP-4196) agent command line options ignored running under systemd
Title: Message Title Kylo Ginsberg assigned an issue to qa Puppet / PUP-4196 agent command line options ignored running under systemd Change By: Kylo Ginsberg Status: Readyfor CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4196) agent command line options ignored running under systemd
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4196 agent command line options ignored running under systemd Change By: Kylo Ginsberg Fix Version/s: PUP3.8.2 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4980) Is there a commit for every JIRA ticket targeted at the release?
Title: Message Title Kylo Ginsberg commented on PUP-4980 Re: Is there a commit for every JIRA ticket targeted at the release? See PUP-4979 for the two way git-jira reconciliation. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1737) Change storage_utils to dispatch on driver class
Title: Message Title Andrew Roetker commented on PDB-1737 Re: Change storage_utils to dispatch on driver class See linked gists for possible solutions. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1739) Upgrade query namespaces to the new java.jdbc
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-1739 Upgrade query namespaces to the new java.jdbc Change By: Rob Browning Sprint: PuppetDB2015-08- 12 26 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4818 PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Change By: Kylo Ginsberg Fix Version/s: PUP3.8.2 Fix Version/s: PUP3.8.3 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1737) Change storage_utils to dispatch on driver class
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-1737 Change storage_utils to dispatch on driver class Our goal was just to continue making progress on the clojure/java.jdbc upgrade, and PDB-1739 needs to go first. Change By: Rob Browning Scope Change Category: Adopted Scope Change Reason: PulledintoreplacePDB-1739 Sprint: PuppetDB2015-08- 26 12 Scrum Team: PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PUP-4905) Add feature switch for appmgmt
Title: Message Title Hailee Kenney assigned an issue to qa Puppet / PUP-4905 Add feature switch for appmgmt Change By: Hailee Kenney Status: Readyfor CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4976) Purge users doesn't remove home directories
Title: Message Title
Eslam El Husseiny created an issue
Puppet / PUP-4976
Purge users doesn't remove home directories
Issue Type:
Bug
Affects Versions:
PUP 3.8.1
Assignee:
Unassigned
Created:
2015/08/03 4:28 AM
Environment:
Operating System = CentOS-7.1 Puppet version = 3.8.1
Priority:
Normal
Reporter:
Eslam El Husseiny
I've a resource in my puppet code that purges users they aren't managed through puppet as following : resources { 'user': purge = true, unless_system_user = true, }
but actually the behavior I got is that the users are deleted, but the home directories still exist, is it a normal behavior ?
Add Comment
Jira (PDB-1828) puppetdb 3.0.2 2015-08-03 Release
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1828 puppetdb 3.0.2 2015-08-03 Release Change By: Kenneth Barber Fix Version/s: PDB3.0.x Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1823) Move should be deactivated logic from process-command! down to deactivate-node!
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1823 Move should be deactivated logic from process-command! down to deactivate-node! Change By: Kenneth Barber Fix Version/s: PDB3.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1739) Upgrade query namespaces to the new java.jdbc
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1739 Upgrade query namespaces to the new java.jdbc Change By: Kenneth Barber Fix Version/s: PDB3.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1653) Implement the outcome of PDB-1312 (TBD)
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1653 Implement the outcome of PDB-1312 (TBD) Change By: Kenneth Barber Fix Version/s: PDB3.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1845) Treat the log config as a global resource
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1845 Treat the log config as a global resource Change By: Kenneth Barber Fix Version/s: PDB3.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1807) PR (1547): (maint) Add access to packaging repo - melissa
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1807 PR (1547): (maint) Add access to packaging repo - melissa Change By: Kenneth Barber Fix Version/s: PDB3.0.x Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1526) Provide test packages to ops for sync logging feedback
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1526 Provide test packages to ops for sync logging feedback Change By: Kenneth Barber Fix Version/s: PDB3.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1653) Implement the outcome of PDB-1312 (TBD)
Title: Message Title Andrew Roetker assigned an issue to Andrew Roetker PuppetDB / PDB-1653 Implement the outcome of PDB-1312 (TBD) Change By: Andrew Roetker Assignee: AndrewRoetker Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1737) Change storage_utils to dispatch on driver class
Title: Message Title Andrew Roetker assigned an issue to Andrew Roetker PuppetDB / PDB-1737 Change storage_utils to dispatch on driver class Change By: Andrew Roetker Assignee: AndrewRoetker Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1653) Implement the outcome of PDB-1312 (TBD)
Title: Message Title Andrew Roetker assigned an issue to Unassigned PuppetDB / PDB-1653 Implement the outcome of PDB-1312 (TBD) Change By: Andrew Roetker Assignee: AndrewRoetker Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4993) systemd thinks 'activating' services are 'stopped'
Title: Message Title Ryan Gordon created an issue Puppet / PUP-4993 systemd thinks 'activating' services are 'stopped' Issue Type: Bug Affects Versions: PUP 4.2.1 Assignee: Unassigned Created: 2015/08/03 12:29 PM Priority: Normal Reporter: Ryan Gordon /bin/systemctl is-active servicetest123 activating echo $? 3 Puppet run: Notice: /Stage[main]/Service[servicetest123]/ensure: ensure changed 'stopped' to 'running' Expected behavior: A return code of 3 from is-active, is also considered running in puppet Add Comment
Jira (PUP-4854) PMT fails to install modules on Windows that have long paths
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4854 PMT fails to install modules on Windows that have long paths Change By: Kylo Ginsberg Fix Version/s: PUP3.8.2 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4978) Is the code ready for release?
Title: Message Title Kylo Ginsberg commented on PUP-4978 Re: Is the code ready for release? Yep, CI is green. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
