Jira (PUP-4741) Unattend installation of Windows puppet agent version 3.6.2 is failing with error code 0X643
Title: Message Title Sushil Rai commented on PUP-4741 Re: Unattend installation of Windows puppet agent version 3.6.2 is failing with error code 0X643 Surprisingly the same process was working with version puppet agent version 3.3.2. We have just updated the puppet agent file name in the command line. There is not much of information on the provided URL. Please suggest a work-around to install puppet agent version 3.6.2 using Windows unattend.xml Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1700) PR (200): fixed serval puppet-lint warnings - SimonHoenscheid
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1700 PR (200): fixed serval puppet-lint warnings - SimonHoenscheid Issue Type: Task Assignee: Unassigned Created: 2015/06/30 1:44 AM Labels: github module Priority: Normal Reporter: gepetto-bot fixed serval puppet-lint warnings Author: Simon Hönscheid <> Company: Github ID: SimonHoenscheid Pull Request 200 Discussion Pull Request 200 File Diff Pull Request Description Fixed serval puppet-lint warnings. selector inside resource block still remaining (webhooks-id: 244a9247921127e46ab6d7de756cd0dc)
Jira (FACT-1080) CFacter fails to link (libboost_log vs libboost_log-mt)
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-1080 CFacter fails to link (libboost_log vs libboost_log-mt) Issue Type: Bug Affects Versions: FACT 3.0.1 Assignee: Unassigned Created: 2015/06/30 2:58 AM Environment: OpenBSD 5.8, Boost 1.58, GCC 4.9.2 Labels: leatherman facter Priority: Normal Reporter: Jasper Lievisse Adriaanse I'm currently in the process of porting CFacter to OpenBSD however there appears to be a linking issue. For some reason I end up with undefined references to: /usr/obj/ports/facter-3.0.1/build-amd64/lib/libfacter.so.0.0: undefined reference to `boost::log::v2_st::aux::default_attribute_names::message()' /usr/obj/ports/facter-3.0.1/build-amd64/lib/libfacter.so.0.0: undefined reference to `void boost::log::v2_st::aux::parse_date_time_format(char const*, char const*, boost::log::v2_st::aux::date_time_format_parser_callback&)' [...] While I have -lboost_log-mt in the linker co
Jira (PDB-1700) PR (200): fixed serval puppet-lint warnings - SimonHoenscheid
Title: Message Title gepetto-bot commented on PDB-1700 Re: PR (200): fixed serval puppet-lint warnings - SimonHoenscheid kbarber commented: @SimonHoenscheid the unit tests are failing on this patch across the board, see the 'details' button above next to "travis ci build failed" ^^, at first glance it seems like the change to the params pattern has made the variables in the class declaration from params out of scope (or something like this). Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1700) PR (200): fixed serval puppet-lint warnings - SimonHoenscheid
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1700 PR (200): fixed serval puppet-lint warnings - SimonHoenscheid Change By: Kenneth Barber Sprint: PuppetDB 2015-07-01 Story Points: 0 Scope Change Reason: Module PR raised by community member Scope Change Category: Adopted Fix Version/s: PDB module-5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
Jira (PDB-1610) 2.3.x Deprecation message for PostgreSQL < 9.4
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1610 2.3.x Deprecation message for PostgreSQL < 9.4 Change By: Kenneth Barber Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1665) Hide aggregate-event log warnings from PE
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1665 Hide aggregate-event log warnings from PE Change By: Kenneth Barber Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1678) PR (1500): (maint) fix command test race - wkalt
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1678 PR (1500): (maint) fix command test race - wkalt Change By: Kenneth Barber Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1680) PuppetDB 2.3.6 Release
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1680 PuppetDB 2.3.6 Release Change By: Kenneth Barber Sprint: PuppetDB 2015-07-15 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1665) Hide aggregate-event log warnings from PE
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1665 Hide aggregate-event log warnings from PE Change By: Kenneth Barber Fix Version/s: PDB 3.0.0 Fix Version/s: PDB 2.3.x Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1671) PR (1497): Bump ezbake to 0.3.11 for improved service account handling - shrug
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1671 PR (1497): Bump ezbake to 0.3.11 for improved service account handling - shrug Change By: Kenneth Barber Affects Version/s: PDB 3.0.0 Sprint: PuppetDB 2015-07-01 Scrum Team: PuppetDB Story Points: 0 Scope Change Reason: Bug with usermod on upgrade case for 3.0.0 Scope Change Category: Found Fix Version/s: PDB 3.0.0 Issue Type: Task Bug Add Comment
Jira (PDB-1670) PR (1496): RE-4779) Create a script to migrate config files and any needed data - melissa
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1670 PR (1496): RE-4779) Create a script to migrate config files and any needed data - melissa Change By: Kenneth Barber Sprint: PuppetDB 2015-07-01 Scrum Team: PuppetDB Story Points: 0 Scope Change Reason: Work on upgrade path 'problem' by release team Scope Change Category: Adopted Fix Version/s: PDB 3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1679) PR (1501): (maint) remove ssl-setup references to AIO pathing - wkalt
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1679 PR (1501): (maint) remove ssl-setup references to AIO pathing - wkalt Change By: Kenneth Barber Affects Version/s: PDB 2.3.5 Fix Version/s: PDB 2.3.x Issue Type: Task Bug Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1675) PR (199): added local puppetdb_version variable to puppetdb::server class - SimonHoenscheid
Title: Message Title gepetto-bot commented on PDB-1675 Re: PR (199): added local puppetdb_version variable to puppetdb::server class - SimonHoenscheid kbarber commented: @SimonHoenscheid what is precisely outdated in that example? The example does work as it says doesn't it? I presume you mean you want an example that shows how to modify the globals version - which to me is a different example from the original 'basic' one. We do have a section for the globals class already, I guess it could be expanded with a small example as well there perhaps. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1670) PR (1496): RE-4779) Create a script to migrate config files and any needed data - melissa
Title: Message Title gepetto-bot commented on PDB-1670 Re: PR (1496): RE-4779) Create a script to migrate config files and any needed data - melissa kbarber commented: So the pending concerns (at this point in time) are: After upgrading both puppetserver & puppetdb need a second manual restart for this to work. We can probably fix the puppetdb case and we should probably go ahead and have a look at this now @melissa. But ... the puppetserver restart case is less obvious. Although we could always restart when the terminus is upgraded? This would be harder if we supported both Puppet 3 & Puppet 4 - which we might in the future, but right now it's not difficult to conceive, but there are no hooks in ezbake to allow the terminus to have postinst 'stuff' I believe today. Not sure how I feel about this, it is a barrier to the upgrade true, fairly easily fixed but the kind of thing I can imagine we'll get hounded on about on IRC & puppet-users (release notes could cover this). Old configuration gets left behind, we're concerned people will still try to modify this thinking it will work. We could keep the archive of this after migration perhaps, since the migration script might mess it up, or just cover it in release notes perhaps. There is a bug in the usermod code during upgrade @shrug because the process is still running, this was related to your work on ezbake I think, did you want me to raise a separate bug or something? @wkalt found a small typo in error reporting. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1670) PR (1496): RE-4779) Create a script to migrate config files and any needed data - melissa
Title: Message Title Kenneth Barber assigned an issue to Melissa Stone PuppetDB / PDB-1670 PR (1496): RE-4779) Create a script to migrate config files and any needed data - melissa Change By: Kenneth Barber Assignee: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1157) Update changelog/release notes
Title: Message Title Kenneth Barber assigned an issue to Kenneth Barber PuppetDB / PDB-1157 Update changelog/release notes Change By: Kenneth Barber Assignee: Kenneth Barber Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1081) Unable to build filesystem_resolver
Title: Message Title Jasper Lievisse Adriaanse created an issue Facter / FACT-1081 Unable to build filesystem_resolver Issue Type: Bug Affects Versions: FACT 3.0.1 Assignee: Unassigned Created: 2015/06/30 7:05 AM Environment: OpenBSD 5.8, GCC 4.9, Boost 1.58 Priority: Normal Reporter: Jasper Lievisse Adriaanse Compiling lib/src/facts/bsd/filesystem_resolver.cc (with a local modification to skip undefined flags) results in the following error: [1/18] /usr/local/bin/ccache eg++ -DBOOST_ALL_DYN_LINK -DBOOST_LOG_WITHOUT_WCHAR_T -DLEATHERMAN_LOGGING_NAMESPACE=\"puppetlabs.facter\" -DUSE_OPENSSL -DUSE_POSIX_FUNCTIONS -DUSE_YAMLCPP -O2 -pipe -Wno-maybe-uninitialized -std=c++11 -Wall -Werror -Wno-unused-parameter -Wno-unused-local-typedefs -Wno-unknown-pragmas -Wno-missing-field-initializers -Wextra -DNDEBUG -fPIC -I/usr/obj/ports/facter-3.0.1/facter-3.0.1/lib/inc -I/usr/obj/ports/facter-3.0.1/facter-3.0.1/vendor/rapidjson-0.11/include -I/usr/local/include -I/usr/obj/ports/facter-3.0.1/facter-3.0.1/vendor/leatherman/vendor/boost-nowide -I/usr/obj/ports/facter-3.0.1/facter-3.0.1/vendor/leatherman/locale/inc -I/usr/obj/ports/facter-3.0.1/facter-3.0.1/vendor/leatherman/logging/inc -MMD -MT lib/CMakeFiles/libfactersrc.dir/src/facts/bsd/filesystem_resolver.cc.o -MF lib/CMakeFiles/libfactersrc.dir/src/facts/b
Jira (PDB-1701) Reject older revisions of the current command revisions at the wire
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1701 Reject older revisions of the current command revisions at the wire Issue Type: Task Assignee: Unassigned Created: 2015/06/30 6:57 AM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: Kenneth Barber We have brought back support for the older versions, but we have no way today of saying in code these are 'deprecated' or 'retired' or anything, so users may still be able to use them. One idea Ryan Senior had was to just reject these at the wire, but still allow them internally to be processed. This seems like a sound idea, probably a good start anyway. Add Comment
Jira (PUP-4799) Documentation lacks puppet requirement in metadata.json
Title: Message Title Fabien Wernli created an issue Puppet / PUP-4799 Documentation lacks puppet requirement in metadata.json Issue Type: Improvement Affects Versions: PUP 3.7.5 Assignee: Unassigned Components: Modules Created: 2015/06/30 7:46 AM Priority: Normal Reporter: Fabien Wernli The module development documentation does not mention how to constrain puppet version requirements using the "requirement" key in metadata.json Add Comment
Jira (PUP-4797) The command "puppet help" should not list "preview" as an available subcommand.
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4797 The command "puppet help" should not list "preview" as an available subcommand. Change By: Kurt Wall Affects Version/s: PUP 4.2.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4797) The command "puppet help" should not list "preview" as an available subcommand.
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4797 The command "puppet help" should not list "preview" as an available subcommand. Change By: Kurt Wall Component/s: Language Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4789) hiera_include does not have access to variables from node scope when future parser is enabled
Title: Message Title
Nick Walker updated an issue
Puppet / PUP-4789
hiera_include does not have access to variables from node scope when future parser is enabled
Change By:
Nick Walker
The 4.x hiera include function does not propagate the correct scope to the include function and this screws up in which context/scope things are being looked up.WORKAROUNDInstead of {{hiera_include}} use {{include hiera_array('classes')}} as the problem is with the 'include' functionality inside of hiera_include. REPRODUCTION{noformat}[root@master381-centos-2 ~]# cat /etc/puppetlabs/puppet/environments/production/modules/test/manifests/init.ppclass test { notify { "my role is ${role}": }}[root@master381-centos-2 ~]# cat /etc/puppetlabs/puppet/environments/production/modules/test_wrapper/manifests/init.ppclass test_wrapper { notify { "in test_wrapper ${role}" : } include test}[root@master381-centos-2 ~]# cat /etc/puppetlabs/puppet/environments/production/manifests/site.ppnode default { #$role = 'my_test_role' hiera_include( 'classes' ) #include hiera_array('classes') notify { "${role}" : }}{noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/
Jira (PDB-1664) PR (1493): Rename ubuntu 12.04 image name to remove dot - wkalt
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1664 PR (1493): Rename ubuntu 12.04 image name to remove dot - wkalt Change By: Wyatt Alt Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4789) hiera_include does not have access to variables from node scope when future parser is enabled
Title: Message Title Sean Griffin assigned an issue to Sean Griffin Puppet / PUP-4789 hiera_include does not have access to variables from node scope when future parser is enabled Change By: Sean Griffin Assignee: Shaigy Nixon Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4758) RSpec 3.3 produces many warning messages during Puppet spec runs
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-4758 RSpec 3.3 produces many warning messages during Puppet spec runs Change By: William Hopper Status: Ready for CI Test Assignee: Josh Cooper qa Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1702) PR (1502): (maint) Remove one-handed `=` in unit test - ajroetker
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1702 PR (1502): (maint) Remove one-handed `=` in unit test - ajroetker Issue Type: Task Assignee: Unassigned Created: 2015/06/30 9:45 AM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Remove one-handed `=` in unit test Author: Andrew Roetker <> Company: Puppet Labs Github ID: ajroetker Pull Request 1502 Discussion Pull Request 1502 File Diff Pull Request Description This commit removes an `=` called on an `every?` in our tests, which cause human-test-output to fail with a one-handed equals failure. (webhooks-id: db5ada53b86f06eef557d
Jira (PDB-1702) PR (1502): (maint) Remove one-handed `=` in unit test - ajroetker
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-1702 PR (1502): (maint) Remove one-handed `=` in unit test - ajroetker Change By: Andrew Roetker Sprint: PuppetDB 2015-07-01 Story Points: 1 Scope Change Reason: three character change to fix tests Scope Change Category: Adopted Fix Version/s: PDB 3.1.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To u
Jira (PUP-4741) Unattend installation of Windows puppet agent version 3.6.2 is failing with error code 0X643
Title: Message Title Ethan Brown commented on PUP-4741 Re: Unattend installation of Windows puppet agent version 3.6.2 is failing with error code 0X643 Sushil Rai the ability to configure the service user for Windows wasn't added until Puppet 3.4, so specifying PUPPET_AGENT_ACCOUNT_USER=Administrator in 3.3.2 would have been ignored. If you look at a machine that has the Puppet 3.3.2 agent installed, it's service should be running as LocalSystem I suggest you do one of the following: PUPPET_AGENT_ACCOUNT_USER is optional, so you can remove it (along with PUPPET_AGENT_ACCOUNT_PASSWORD) if you don't have a compelling reason to reconfigure the service user. If you need to specify a PUPPET_AGENT_ACCOUNT_USER to configure the service user for your install, create and configure a new account or use an existing account like NetworkService The Technet link from my last comment contains a link under Download this Solution Accelerator to https://www.microsoft.com/en-us/download/details.aspx?id=5543, which is a 35 page PDF that goes into a lot of detail about how to configure an account for service use, should you choose to go that route. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1703) PR (1503): (maint) Bump to Clojure 1.7.0 - ajroetker
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1703 PR (1503): (maint) Bump to Clojure 1.7.0 - ajroetker Issue Type: Task Assignee: Unassigned Created: 2015/06/30 10:02 AM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Bump to Clojure 1.7.0 Author: Andrew Roetker <> Company: Puppet Labs Github ID: ajroetker Pull Request 1503 Discussion Pull Request 1503 File Diff Pull Request Description Clojure 1.7.0 was just released, this commit bumps this to this version. (webhooks-id: 0b3334bfc56b75f18e84649491959bd8)
Jira (PDB-1703) PR (1503): (maint) Bump to Clojure 1.7.0 - ajroetker
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-1703 PR (1503): (maint) Bump to Clojure 1.7.0 - ajroetker Change By: Andrew Roetker Sprint: PuppetDB 2015-07-01 Story Points: 1 Scope Change Reason: Update to latest clojure for release Scope Change Category: Found Fix Version/s: PDB 3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe fro
Jira (PUP-4800) Puppet::Util::IniConfig::PhysicalFile cannot parse file correctly
Title: Message Title Corey Osman created an issue Puppet / PUP-4800 Puppet::Util::IniConfig::PhysicalFile cannot parse file correctly Issue Type: Bug Assignee: Unassigned Created: 2015/06/30 10:12 AM Labels: windows Priority: Normal Reporter: Corey Osman I was creating a windows provider that consumed a ini file. I decided that I would use the Puppet::Util::IniConfig::PhysicalFile to parse my ini file however it seems one of the regex values is not able to parse my content. regex that has trouble with my ini content https://github.com/puppetlabs/puppet/blob/master/lib/puppet/util/inifile.rb#L151 The content that breaks this is found here and I have highlighted the line where it breaks: https://gist.github.com/logicminds/1d4bea2d5ac0285e3417#file-gistfile1-txt-L34 At a glance I think just using the split function to capture the right and left side of the equal sign would work, but I am sure its more complicated than that as I don't have any other inclination of what goes into an ini file. My provider code does something like this for reference and was hoping to utilize the work of the utility rather than reinventing the wheel. inffile = 'c:\\windows\\tempsecedit.inf' secedit(['/export', '/cfg', inffile, '/quiet']) inf = Puppet::Util::IniConfig::Physi
Jira (PDB-1679) PR (1501): (maint) remove ssl-setup references to AIO pathing - wkalt
Title: Message Title gepetto-bot commented on PDB-1679 Re: PR (1501): (maint) remove ssl-setup references to AIO pathing - wkalt ajroetker commented: :+1: tested and works for me Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1679) PR (1501): (maint) remove ssl-setup references to AIO pathing - wkalt
Title: Message Title gepetto-bot commented on PDB-1679 Re: PR (1501): (maint) remove ssl-setup references to AIO pathing - wkalt Pull request (maint) remove ssl-setup references to AIO pathing has been closed. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1679) PR (1501): (maint) remove ssl-setup references to AIO pathing - wkalt
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1679 PR (1501): (maint) remove ssl-setup references to AIO pathing - wkalt Change By: Kenneth Barber Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1157) Update changelog/release notes
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1157 Update changelog/release notes Change By: Kenneth Barber Fix Version/s: PDB 3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4789) hiera_include does not have access to variables from node scope when future parser is enabled
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4789 hiera_include does not have access to variables from node scope when future parser is enabled Change By: Kurt Wall QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4789) hiera_include does not have access to variables from node scope when future parser is enabled
Title: Message Title Kurt Wall updated an issue Puppet / PUP-4789 hiera_include does not have access to variables from node scope when future parser is enabled Change By: Kurt Wall QA Risk Assessment Reason: Regression or loss of functionality from 3.x Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4777) Puppet gem dependencies are out of date
Title: Message Title Shaigy Nixon assigned an issue to Shaigy Nixon Puppet / PUP-4777 Puppet gem dependencies are out of date Change By: Shaigy Nixon Assignee: qa Shaigy Nixon Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1702) PR (1502): (maint) Remove one-handed `=` in unit test - ajroetker
Title: Message Title gepetto-bot commented on PDB-1702 Re: PR (1502): (maint) Remove one-handed `=` in unit test - ajroetker pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1570/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1080) CFacter fails to link (libboost_log vs libboost_log-mt)
Title: Message Title Jasper Lievisse Adriaanse assigned an issue to Peter Huene Facter / FACT-1080 CFacter fails to link (libboost_log vs libboost_log-mt) Change By: Jasper Lievisse Adriaanse Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1081) Unable to build filesystem_resolver
Title: Message Title Jasper Lievisse Adriaanse assigned an issue to Peter Huene Facter / FACT-1081 Unable to build filesystem_resolver Change By: Jasper Lievisse Adriaanse Assignee: Peter Huene Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4653) The filebucket client uses v1 API URLs internally
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-4653
The filebucket client uses v1 API URLs internally
Change By:
Josh Cooper
Since the {{0.25}} days, the {{filebucket}} client in the form of {{Puppet::FileBucket::Dipper}} has interfaces with the indirector by constructing URLs in the following fashion:{code}@rest_path = "https://#{server}:#{port}/#{environment}/file_bucket_file/"# thendest_path = "#{@rest_path}#{file_bucket_file.name}/#{files_original_path}"{code}The indirector breaks this down into its fields in {{Puppet::Indirector::Request#set_uri_key}}.{code}env, indirector, @key = URI.unescape(uri.path.sub(/^\//, '')).split('/',3)@key ||= ''self.environment = env unless env == ''{code}All of this is quite unecessary because 1. the indirection implicitly follows from the indirected class 2. the environment is not significant for filebucket interactions(As an aside, the API does not construct URLs like this anymore, either - the environment is a parameter and not a part of the URI path. This is not important here, though, because these URLs never hit the wire. They are only for the benefit of the {{Indirector::Request}} class.)A consequence of this construct is that new indirector uses with URLs in keys will be misinterpreted by the {{Request}} class.It would be beneficial to transform these internally used URLs into a form that 1. confers only the necessary information to the indirector 2. does not clash with other possible URLs h3. SummaryAlthough this sounds like a network change, it's not. It only changes how the client internally manages the filebucket request, but doesn't affect how the client sends the request on the wire. It also doesn't change file manifests, e.g. filebucket resources, etc.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-2509) puppet resource service on Solaris needs -H flag
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2509 puppet resource service on Solaris needs -H flag Change By: Josh Cooper Fix Version/s: PUP 4.3.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2509) puppet resource service on Solaris needs -H flag
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-2509
puppet resource service on Solaris needs -H flag
Change By:
Josh Cooper
On Solaris 11.2, the following behavior happens when 'puppet resource service' runs: {noformat} root@solaris:~# puppet resource service service { 'FMRI': ensure => 'stopped', enable => 'false', } service { 'PRESERVE': ensure => 'stopped', } <...> {noformat} Those entries are due to the header output of /usr/bin/svcs: {noformat} $ /usr/bin/svcs | head -5STATE STIMEFMRIlegacy_run 8:33:43 lrc:/etc/rc2_d/S47pppdlegacy_run 8:33:44 lrc:/etc/rc2_d/S81dodatadm_udapltlegacy_run 8:33:44 lrc:/etc/rc2_d/S89PRESERVEdisabled8:33:05 svc:/platform/i86pc/acpihpd:default {noformat} A possible fix is to update puppet/provider/service/smf.rb like so: {code:ruby} --- a/puppet/provider/service/smf.rb 2014-05-07 09:46:19.159462784 -0600+++ b/puppet/provider/service/smf.rb 2014-05-07 09:45:28.532934391 -0600@@ -32,7 +32,7 @@ enddef self.instances- svcs.split("\n").select{|l| l !~ /^legacy_run/ }.collect do |line|+ svcs("-H").split("\n").select{|l| l !~ /^legacy_run/ }.collect do |line| state,stime,fmri = line.split(/\s+/) status = case statewhen /online/; :running {code} To remove the headers from the output before processing each line. h3. SummaryAs a result of this change, puppet will no longer report that {{FMRI}} is an installed service.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed
Jira (PUP-2573) Puppet::Agent::Locker#lock doesn't return whether it acquired the lock or not
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2573 Puppet::Agent::Locker#lock doesn't return whether it acquired the lock or not Change By: Josh Cooper Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1703) PR (1503): (maint) Bump to Clojure 1.7.0 - ajroetker
Title: Message Title gepetto-bot commented on PDB-1703 Re: PR (1503): (maint) Bump to Clojure 1.7.0 - ajroetker pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1571/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2509) puppet resource service on Solaris needs -H flag
Title: Message Title Josh Cooper updated an issue Puppet / PUP-2509 puppet resource service on Solaris needs -H flag Change By: Josh Cooper Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1703) PR (1503): (maint) Bump to Clojure 1.7.0 - ajroetker
Title: Message Title gepetto-bot commented on PDB-1703 Re: PR (1503): (maint) Bump to Clojure 1.7.0 - ajroetker kbarber commented: Those unit tests are taking forever today on travisci . Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4801) Custom facts not loaded when using puppet resource command
Title: Message Title Jonathan Tripathy created an issue Puppet / PUP-4801 Custom facts not loaded when using puppet resource command Issue Type: Bug Assignee: Unassigned Created: 2015/06/30 11:58 AM Priority: Critical Reporter: Jonathan Tripathy I'm seeing an issue where when running puppet resource, it does not load custom facts (puppet apply works ok). root@hkmjr2cbdmkpxh2:~# /opt/puppetlabs/bin/puppet module install puppetlabs-firewall Notice: Preparing to install into /etc/puppetlabs/code/environments/production/modules ... Notice: Downloading from https://forgeapi.puppetlabs.com ... Notice: Installing -- do not interrupt ...
Jira (PUP-4801) Custom facts not loaded when using puppet resource command
Title: Message Title
Jonathan Tripathy updated an issue
Puppet / PUP-4801
Custom facts not loaded when using puppet resource command
Change By:
Jonathan Tripathy
I'm seeing an issue where when running puppet resource, it does not load custom facts (puppet apply works ok). This is a masterless installation (i.e. no certs setup), so I don't believe this to be a pluginsync issue. {code}root@hkmjr2cbdmkpxh2:~# /opt/puppetlabs/bin/puppet module install puppetlabs-firewallNotice: Preparing to install into /etc/puppetlabs/code/environments/production/modules ...Notice: Downloading from https://forgeapi.puppetlabs.com ...Notice: Installing -- do not interrupt .../etc/puppetlabs/code/environments/production/modules└── puppetlabs-firewall (v1.6.0)root@hkmjr2cbdmkpxh2:/opt/puppetlabs/bin# ls /etc/puppetlabs/code/environments/production/modules/firewall/lib/facter/iptables_version.rb/etc/puppetlabs/code/environments/production/modules/firewall/lib/facter/iptables_version.rbroot@hkmjr2cbdmkpxh2:/opt/puppetlabs/bin# cat test.ppnotify {"$::iptables_version":}root@hkmjr2cbdmkpxh2:/opt/puppetlabs/bin# strace -efile -f ./puppet apply test.pp 2>&1 | grep iptables_version[pid 1817] stat("/etc/puppetlabs/code/environments/production/modules/firewall/lib/facter/iptables_version.rb", {st_mode=S_IFREG|0644, st_size=234, ...}) = 0[pid 1817] open("/etc/puppetlabs/code/environments/production/modules/firewall/lib/facter/iptables_version.rb", O_RDONLY|O_CLOEXEC) = 8[pid 1817] open("/etc/puppetlabs/code/environments/production/modules/firewall/lib/facter/iptables_version.rb", O_RDONLY|O_CLOEXEC) = 8[pid 1817] lstat("/etc/puppetlabs/code/environments/production/modules/firewall/lib/facter/iptables_version.rb", {st_mode=S_IFREG|0644, st_size=234, ...}) = 0[pid 1817] stat("/etc/puppetlabs/code/environments/production/modules/firewall/lib/facter/iptables_version.rb", {st_mode=S_IFREG|0644, st_size=234, ...}) = 0root@hkmjr2cbdmkpxh2:/opt/puppetlabs/bin# strace -efile -f ./puppet resource firewall 2>&1 | grep iptables_versionroot@hkmjr2cbdmkpxh2:/opt/puppetlabs/bin# ./puppet resource firewallError: Could not autoload puppet/provider/firewall/iptables: undefined method `value' for nil:NilClassError: Could not autoload puppet/type/firewall: Could not autoload puppet/provider/firewall/iptables: undefined method `value' for nil:NilClassError: Could not run: Could not autoload puppet/type/firewall: Could not autoload puppet/provider/firewall/iptables: undefined method `value' for nil:NilClassroot@hkmjr2cbdmkpxh2:/opt/puppetlabs/bin# ./puppet resource firewall --trace --debugDebug: Runtime environment: puppet_version=4.2.0, ruby_version=2.1.6, run_mode=user, default_encoding=UTF-8Debug: Facter: searching for custom fact "iptables_version".Debug: Facter: fact "facterversion" has resolved to "3.0.1".Debug: Facter: skipping external facts for "/opt/puppetlabs/facter/facts.d": No such file or directoryDebug: Facter: skipping external facts for "/etc/facter/facts.d": No such file or directoryDebug: Facter: skipping external facts for "/etc/puppetlabs/facter/facts.d": No such file or directoryDebug: Facter: no external facts were found.Debug: Facter: loading all custom facts.Debug: Facter: custom fact "iptables_version" was not found.Error: Could not autoload puppet/provider/firewall/iptable
Jira (PUP-4790) regsubst incompatibility between puppet 3.x and 4.x, escaping [ inside []
Title: Message Title Nicholas Fagerlund commented on PUP-4790 Re: regsubst incompatibility between puppet 3.x and 4.x, escaping [ inside [] Henrik Lindberg Okay, noted! Sounds to me like something that should be isolated to the "4.0 breaks" document that Jorie Tappa is integrating into the language docs. I'll add something to that WIP google doc she'll be working from. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4802) Windows 2008 "Failed to add access control entry" on a file
Title: Message Title Mark Cornmesser created an issue Puppet / PUP-4802 Windows 2008 "Failed to add access control entry" on a file Issue Type: Bug Assignee: Unassigned Created: 2015/06/30 12:41 PM Priority: Normal Reporter: Mark Cornmesser Mon Jun 01 09:52:38 -0700 2015 Puppet (err): Failed to set owner to 'S-1-5-21-3861705028-2700629737-4079167078-500': Failed to add access control entry: No more memory is available for security information updates. Mon Jun 01 09:52:38 -0700 2015 /Stage[main]/Puppet::Atboot/File[c:/etc/puppetmasters.txt]/owner (err): change from NT AUTHORITY\SYSTEM to B-2008-IX-0178\root failed: Failed to set owner to 'S-1-5-21-3861705028-2700629737-4079167078-500': Failed to add access control entry: No more memory is available for security information updates. It seems that if the owner of the file is changed, and then Puppet changes it back, it appends the account to the dacl. Instead of replacing an entry. It will then at some point reach its limit in dacl entries. I have worked around this by using an icacl command in an exec in the manifest. Add Comment
Jira (PDB-1670) PR (1496): RE-4779) Create a script to migrate config files and any needed data - melissa
Title: Message Title gepetto-bot commented on PDB-1670 Re: PR (1496): RE-4779) Create a script to migrate config files and any needed data - melissa melissa commented: @kbarber @wkalt I've updated the script to clean up the old config files if they are still around. They are archived in the new location, and a backup copy is made if any modifications happen in the script. That being said, this goes against what packaging systems do. As long as your okay with that, this should be fine. Testing now. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1704) PR (1504): PuppetDB hangs on shutdown when the database is down - senior
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1704 PR (1504): PuppetDB hangs on shutdown when the database is down - senior Issue Type: Task Assignee: Unassigned Created: 2015/06/30 1:16 PM Labels: github Priority: Normal Reporter: gepetto-bot PuppetDB hangs on shutdown when the database is down Author: Ryan Senior Company: Github ID: senior Pull Request 1504 Discussion Pull Request 1504 File Diff Pull Request Description This adds connection timeouts to the command processing and query connection pools. This fixes the problem where the ActiveMQ session can't be properly shutdown because the command connection pool can't get a connection to the database (i.e. the database is down)
Jira (PDB-1704) PR (1504): PuppetDB hangs on shutdown when the database is down - senior
Title: Message Title gepetto-bot commented on PDB-1704 Re: PR (1504): PuppetDB hangs on shutdown when the database is down - senior senior commented: This just needs docs for the new connection-timeout config Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-867) Port xendomains fact to Facter 3
Title: Message Title Michael Smith commented on FACT-867 Re: Port xendomains fact to Facter 3 A nightly build should be available tomorrow. It would be helpful to find a community member who can verify this fact. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-867) Port xendomains fact to Facter 3
Title: Message Title Michael Smith assigned an issue to qa Facter / FACT-867 Port xendomains fact to Facter 3 Change By: Michael Smith Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1075) Add flag to display legacy facts in default output
Title: Message Title Michael Smith assigned an issue to qa Facter / FACT-1075 Add flag to display legacy facts in default output Change By: Michael Smith Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1670) PR (1496): RE-4779) Create a script to migrate config files and any needed data - melissa
Title: Message Title gepetto-bot commented on PDB-1670 Re: PR (1496): RE-4779) Create a script to migrate config files and any needed data - melissa pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1572/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1705) Update dujour for PDB 2.3.6
Title: Message Title Melissa Stone created an issue PuppetDB / PDB-1705 Update dujour for PDB 2.3.6 Issue Type: Sub-task Assignee: Unassigned Created: 2015/06/30 1:40 PM Priority: Normal Reporter: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/op
Jira (PDB-1681) Is checklist current
Title: Message Title Melissa Stone commented on PDB-1681 Re: Is checklist current p.s., checklist isn't current, but I've updated it to reflect reality a little more. For the latest version of the script, run "rake package:implode package:bootstrap" in the repo you are running the task in. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4777) Puppet gem dependencies are out of date
Title: Message Title Shaigy Nixon commented on PUP-4777 Re: Puppet gem dependencies are out of date Validated on SHA:df66ab55dc9dff4fb0c69074485dd663aa2d4a20 [shaigynixon@puppetlabs452 ~/jun30-puppet]# git clone https://github.com/puppetlabs/puppet.git Cloning into 'puppet'... remote: Counting objects: 192859, done. remote: Compressing objects: 100% (137/137), done. remote: Total 192859 (delta 88), reused 14 (delta 14), pack-reused 192706 Receiving objects: 100% (192859/192859), 47.52 MiB | 1.80 MiB/s, done. Resolving deltas: 100% (139352/139352), done. Checking connectivity... done. [shaigynixon@puppetlabs452 ~/jun30-puppet]# cd puppet/ [shaigynixon@puppetlabs452 ~/jun30-puppet/puppet:master]# git checkout master
Jira (PDB-1706) PR (1505): (maint) Update specter dependency to remove `update` conflict - ajroetker
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1706 PR (1505): (maint) Update specter dependency to remove `update` conflict - ajroetker Issue Type: Task Assignee: Unassigned Created: 2015/06/30 2:18 PM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Update specter dependency to remove `update` conflict Author: Andrew Roetker <> Company: Puppet Labs Github ID: ajroetker Pull Request 1505 Discussion Pull Request 1505 File Diff Pull Request Description This commit updates `specter` to the laster version to remove the conflict with the name `update` in `clojure.core`. (webhooks-id: d
Jira (PDB-1706) PR (1505): (maint) Update specter dependency to remove `update` conflict - ajroetker
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-1706 PR (1505): (maint) Update specter dependency to remove `update` conflict - ajroetker Change By: Andrew Roetker Sprint: PuppetDB 2015-07-01 Story Points: 1 Scope Change Reason: easy fix and PE wanted this Scope Change Category: Adopted Fix Version/s: PDB 3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs"
Jira (FACT-1056) Operatingsystem major release not resolved in OSX
Title: Message Title
William Hopper commented on FACT-1056
Re: Operatingsystem major release not resolved in OSX
Pre-FR from: 97fcfb639. Looks good!
Native Facter:
{
architecture => "x86_64",
family => "Darwin",
hardware => "x86_64",
macosx => {
build => "13F34",
product => "Mac OS X",
version => {
full => "10.9.5",
major => "10.9",
minor => "5"
Jira (PDB-1670) PR (1496): RE-4779) Create a script to migrate config files and any needed data - melissa
Title: Message Title gepetto-bot commented on PDB-1670 Re: PR (1496): RE-4779) Create a script to migrate config files and any needed data - melissa pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1576/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1707) PR (1506): (maint) fix ssl setup rollup - wkalt
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1707 PR (1506): (maint) fix ssl setup rollup - wkalt Issue Type: Task Assignee: Unassigned Created: 2015/06/30 2:49 PM Labels: github Priority: Normal Reporter: gepetto-bot (maint) fix ssl setup rollup Author: Wyatt Alt <> Company: Github ID: wkalt Pull Request 1506 Discussion Pull Request 1506 File Diff Pull Request Description This should fix our ssl setup stuff to get the right confdir in a 3.0 scenario (webhooks-id: 1ee2e92d7f140a3adb332ba15f237385)
Jira (PDB-1706) PR (1505): (maint) Update specter dependency to remove `update` conflict - ajroetker
Title: Message Title gepetto-bot commented on PDB-1706 Re: PR (1505): (maint) Update specter dependency to remove `update` conflict - ajroetker pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1578/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1707) PR (1506): (maint) fix ssl setup rollup - wkalt
Title: Message Title gepetto-bot commented on PDB-1707 Re: PR (1506): (maint) fix ssl setup rollup - wkalt ajroetker commented: :+1:, @shrug sanity check? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1707) PR (1506): (maint) fix ssl setup rollup - wkalt
Title: Message Title gepetto-bot commented on PDB-1707 Re: PR (1506): (maint) fix ssl setup rollup - wkalt pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1582/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1707) PR (1506): (maint) fix ssl setup rollup - wkalt
Title: Message Title gepetto-bot commented on PDB-1707 Re: PR (1506): (maint) fix ssl setup rollup - wkalt wkalt commented: @pljenkinsro retest this please Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1707) PR (1506): (maint) fix ssl setup rollup - wkalt
Title: Message Title gepetto-bot commented on PDB-1707 Re: PR (1506): (maint) fix ssl setup rollup - wkalt pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1581/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1707) PR (1506): (maint) fix ssl setup rollup - wkalt
Title: Message Title gepetto-bot commented on PDB-1707 Re: PR (1506): (maint) fix ssl setup rollup - wkalt pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1583/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1707) PR (1506): (maint) fix ssl setup rollup - wkalt
Title: Message Title gepetto-bot commented on PDB-1707 Re: PR (1506): (maint) fix ssl setup rollup - wkalt melissa commented: :+1: Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1707) PR (1506): (maint) fix ssl setup rollup - wkalt
Title: Message Title gepetto-bot commented on PDB-1707 Re: PR (1506): (maint) fix ssl setup rollup - wkalt wkalt commented: @pljenkinsro retest this please Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1075) Add flag to display legacy facts in default output
Title: Message Title Eric Thompson updated an issue Facter / FACT-1075 Add flag to display legacy facts in default output Change By: Eric Thompson QA Risk Assessment: Medium QA Risk Assessment Reason: customer request, possibly temporary for deprecation purposes. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1707) PR (1506): (maint) fix ssl setup rollup - wkalt
Title: Message Title gepetto-bot commented on PDB-1707 Re: PR (1506): (maint) fix ssl setup rollup - wkalt wkalt commented: @pljenkinsro retest this please Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1707) PR (1506): (maint) fix ssl setup rollup - wkalt
Title: Message Title gepetto-bot commented on PDB-1707 Re: PR (1506): (maint) fix ssl setup rollup - wkalt pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1584/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1670) PR (1496): RE-4779) Create a script to migrate config files and any needed data - melissa
Title: Message Title gepetto-bot commented on PDB-1670 Re: PR (1496): RE-4779) Create a script to migrate config files and any needed data - melissa pljenkinsro commented: Test FAILed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1580/ Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4802) Windows 2008 "Failed to add access control entry" on a file
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4802 Windows 2008 "Failed to add access control entry" on a file Change By: Josh Cooper Scrum Team: Windows Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4802) Windows 2008 "Failed to add access control entry" on a file
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-4802
Windows 2008 "Failed to add access control entry" on a file
Change By:
Josh Cooper
{noformat} Mon Jun 01 09:52:38 -0700 2015 Puppet (err): Failed to set owner to 'S-1-5-21-3861705028-2700629737-4079167078-500': Failed to add access control entry: No more memory is available for security information updates. Mon Jun 01 09:52:38 -0700 2015 /Stage[main]/Puppet::Atboot/File[c:/etc/puppetmasters.txt]/owner (err): change from NT AUTHORITY\SYSTEM to B-2008-IX-0178\root failed: Failed to set owner to 'S-1-5-21-3861705028-2700629737-4079167078-500': Failed to add access control entry: No more memory is available for security information updates. {noformat} It seems that if the owner of the file is changed, and then Puppet changes it back, it appends the account to the dacl. Instead of replacing an entry. It will then at some point reach its limit in dacl entries. I have worked around this by using an icacl command in an exec in the manifest.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1075) Add flag to display legacy facts in default output
Title: Message Title Eric Thompson updated an issue Facter / FACT-1075 Add flag to display legacy facts in default output Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1075) Add flag to display legacy facts in default output
Title: Message Title Michael Smith commented on FACT-1075 Re: Add flag to display legacy facts in default output Some unit tests make sense, also an acceptance test. I'll add them. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-867) Port xendomains fact to Facter 3
Title: Message Title Eric Thompson updated an issue Facter / FACT-867 Port xendomains fact to Facter 3 Change By: Eric Thompson QA Risk Severity: Medium QA Risk Probability: Medium QA Risk Severity Reason: custom facts workaround QA Risk Assessment: Medium QA Risk Probability Reason: xen hypervisor users QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (FACT-1073) Operatingsystem release facts not properly resolved in Arch Linux
Title: Message Title Eric Thompson updated an issue Facter / FACT-1073 Operatingsystem release facts not properly resolved in Arch Linux Change By: Eric Thompson QA Risk Severity: Low QA Risk Probability: Medium QA Risk Severity Reason: work arounds exist and these version numbers are semi-sensical here QA Risk Assessment: Medium QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Gr
Jira (PUP-4801) Custom facts not loaded when using puppet resource command
Title: Message Title Josh Cooper commented on PUP-4801 Re: Custom facts not loaded when using puppet resource command I don't know that puppet resource has ever been able to load custom facts from the modulepath (as opposed to pluginsync). Can you try this with an earlier version and see if this is a regression or just long standing behavior. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1078) `facter fqdn` not returning the domain, only the hostname
Title: Message Title Eric Thompson updated an issue Facter / FACT-1078 `facter fqdn` not returning the domain, only the hostname Change By: Eric Thompson QA Highest Test Level Reason: no unit tests, depends upon networking, etc QA Risk Severity: Medium QA Risk Probability: Medium QA Risk Severity Reason: other facts as work arounds? QA Risk Assessment: Medium QA Risk Probability Reason: lots of use of this fact, but depends on some weird DNS results QA Highest Test Level: Acceptance QA Status: Reviewed Add Comment
Jira (FACT-1056) Operatingsystem major release not resolved in OSX
Title: Message Title Eric Thompson updated an issue Facter / FACT-1056 Operatingsystem major release not resolved in OSX Change By: Eric Thompson QA Risk Severity: Medium QA Risk Probability: Medium QA Risk Severity Reason: higher severity on osx where the OS *has* a version QA Risk Assessment: Medium QA Highest Test Level: Acceptance QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4790) regsubst incompatibility between puppet 3.x and 4.x, escaping [ inside []
Title: Message Title Artyom A. Konovalenko commented on PUP-4790 Re: regsubst incompatibility between puppet 3.x and 4.x, escaping [ inside [] OK, got it. Thank you for citation and for reference. I was not sure how much Java and how much Ruby is in the new DSL parser and who was responsible for that odd behavior. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1708) PR (1507): (maint) remove extraneous com namespace - wkalt
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1708 PR (1507): (maint) remove extraneous com namespace - wkalt Issue Type: Task Assignee: Unassigned Created: 2015/06/30 3:45 PM Labels: github Priority: Normal Reporter: gepetto-bot (maint) remove extraneous com namespace Author: Wyatt Alt <> Company: Github ID: wkalt Pull Request 1507 Discussion Pull Request 1507 File Diff Pull Request Description this snuck in during a rollup. The change that got rolled up in this namespace relates to deprecation of postgres < 9.4, which isn't relevant to 3.0 because postgres < 9.4 is retired in 3.0 for PE and FOSS.
Jira (PDB-1707) PR (1506): (maint) fix ssl setup rollup - wkalt
Title: Message Title gepetto-bot commented on PDB-1707 Re: PR (1506): (maint) fix ssl setup rollup - wkalt Pull request (maint) fix ssl setup rollup has been closed. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4740) Add missing query parameters to Puppet HTTPS API docs
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-4740 Add missing query parameters to Puppet HTTPS API docs Change By: Nicholas Fagerlund Scrum Team: Puppet Server Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4508) systemd provider should support manual
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-4508 systemd provider should support manual Change By: Nicholas Fagerlund Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4775) org.jruby.exceptions.RaiseException: (SystemStackError) stack level too deep
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4775 org.jruby.exceptions.RaiseException: (SystemStackError) stack level too deep Change By: Eric Thompson QA Highest Test Level Reason: PR has good coverage QA Risk Severity: High QA Risk Probability: Medium QA Risk Severity Reason: crash QA Risk Assessment: High QA Risk Probability Reason: requires certain modules which extend serialization stack needs QA Highest Test Level: Unit QA Risk Assessment Reason: escaped, reported by customer QA Status: Reviewed
Jira (PDB-1637) Not all PuppetDB tickets mentioned in release notes are available publicly
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-1637 Not all PuppetDB tickets mentioned in release notes are available publicly Change By: Kurt Wall QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1637) Not all PuppetDB tickets mentioned in release notes are available publicly
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-1637 Not all PuppetDB tickets mentioned in release notes are available publicly Change By: Kurt Wall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1637) Not all PuppetDB tickets mentioned in release notes are available publicly
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-1637 Not all PuppetDB tickets mentioned in release notes are available publicly Change By: Kurt Wall QA Risk Assessment Reason: Doc Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1647) Prepare branches/docs & jenkins for 3.0.0 release
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-1647 Prepare branches/docs & jenkins for 3.0.0 release Change By: Kurt Wall QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1647) Prepare branches/docs & jenkins for 3.0.0 release
Title: Message Title Kurt Wall updated an issue PuppetDB / PDB-1647 Prepare branches/docs & jenkins for 3.0.0 release Change By: Kurt Wall QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
