Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts
Title: Message Title Boyan Tabakov updated an issue Puppet / PUP-2630 Server-set global variables like $::environment get overwritten by client facts Change By: Boyan Tabakov Affects Version/s: 3.6.2 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1471) Puppet Agent windows services accidentally comes of out Paused state
Title: Message Title Glenn Sarti commented on an issue Re: Puppet Agent windows services accidentally comes of out Paused state PR 2859 raised Add Comment Puppet / PUP-1471 Puppet Agent windows services accidentally comes of out Paused state The Windows Puppet Agent service will not stay in a paused stated, instead it will go back into a running state after a short period of time. This is an issue in the Win32-Service ruby code. Raised bug https://github.com/djberg96/win32-service/issues/11 and is fixed in version 0.8.3. Because the Pause feature is so rarely used, there is no point in... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2921) Wrong pagination urls on dashboard
Title: Message Title Victor Zhuravlyov created an issue Puppet / PUP-2921 Wrong pagination urls on dashboard Issue Type: Bug Assignee: Unassigned Created: 10/Jul/14 3:13 AM Environment: Debian 7.5 puppet 3.6.2 puppet-dashboard 1.2.23 Labels: puppet-dashboard puppet dashboard pagination Priority: Normal Reporter: Victor Zhuravlyov [ Previous 1 2 Next , [\Per page: \, \20\, \100\, \all\] , ] div class=actionbar[div class=\pagination\span class=\disabled prev_page\ Previous/span span class=\current\1/span a href="" rel=\next\2/a a href="" class=\next_page\ rel=\next\Next /a/div, div class=\pagination\[\spanPer page: /span\, \span class=\\\current\\\20/span\, \a href="" \a href="">/div, br class=\clear\ /]/div http://puppet.intranet:3000/%5C%22/reports?page=2#37;22 http://deb.msl.intranet:3000/%5C%5C%5C%22/reports?per_page=100\\\%22 http://deb.msl.intranet:3000/%5C%5C%5C%22/reports?per_page=all\\\%22
Jira (PUP-2921) Wrong pagination URLs on dashboard
Title: Message Title Victor Zhuravlyov updated an issue Puppet / PUP-2921 Wrong pagination URLs on dashboard Change By: Victor Zhuravlyov Summary: Wrongpagination urls URLs ondashboard Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts
Title: Message Title Henrik Lindberg commented on an issue Re: Server-set global variables like $::environment get overwritten by client facts Ah, got it now. So a solution would be to simply skip setting the facts as global variables that collide with those set by the server (the reserved variables), and instead only store those in the $facts hash. Add Comment Puppet / PUP-2630 Server-set global variables like $::environment get overwritten by client facts As per the docs (http://docs.puppetlabs.com/puppet/latest/reference/lang_facts_and_builtin_vars.html#variables-set-by-the-puppet-master) the puppet master sets the global $::environment variable to contain the name of the node's environment. However, if a node provides a fact with the name 'environment' that fact's value overrides the server-set environme... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com.
Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts
Title: Message Title Boyan Tabakov commented on an issue Re: Server-set global variables like $::environment get overwritten by client facts Yes, that would be one way to do it. It will break tons of old manifests that expect the facts as global variables though. So a temporary workaround might be to make sure the server-side variables have priority (e.g. are set after the facts). Add Comment Puppet / PUP-2630 Server-set global variables like $::environment get overwritten by client facts As per the docs (http://docs.puppetlabs.com/puppet/latest/reference/lang_facts_and_builtin_vars.html#variables-set-by-the-puppet-master) the puppet master sets the global $::environment variable to contain the name of the node's environment. However, if a node provides a fact with the name 'environment' that fact's value overrides the server-set environme... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PUP-2920) PMT should be able to authorize with forge and request extra modules
Title: Message Title Alex Dreyer updated an issue Puppet / PUP-2920 PMT should be able to authorize with forge and request extra modules Change By: Alex Dreyer Labels: PMT Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Brett Lentz commented on an issue Re: Not possible to manage SELinux file contexts via puppet in a sane way There's this module: https://github.com/blentz/puppet-selinux_types Add Comment Puppet / PUP-2169 Not possible to manage SELinux file contexts via puppet in a sane way There's currently no sane way to manage SELinux file contexts using puppet. The only way is to call 'semanage' via a 'exec' resource. But then the next issue comes up: Puppet seems to keep some file context rule cache, built once at startup. I wasn't able to find a way to invalidate this cache without restarting the whole puppet agent. Even when calling '... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2784) Run puppet specs against windows ruby 2.0 x64
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Puppet / PUP-2784 Run puppet specs against windows ruby 2.0 x64 Change By: Rob Reynolds Assignee: RobReynolds Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-569) Run Facter acceptance against ruby 2.0 x64
Title: Message Title Rob Reynolds assigned an issue to Rob Reynolds Facter / FACT-569 Run Facter acceptance against ruby 2.0 x64 Change By: Rob Reynolds Assignee: RobReynolds Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts
Title: Message Title Andy Parker commented on an issue Re: Server-set global variables like $::environment get overwritten by client facts Aha! I understand now. I tracked this through and it is happening because we don't keep these different sources of data separated. They all just get thrown together as parameters of the node: Unable to find source-code formatter for language: ruby. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml # Add any extra data necessary to the node. def add_node_data(node) # Merge in our server-side facts, so they can be used during compilation. node.merge(@server_facts) end In order to fix this we'll need to hold everything separate on the node object, which is the right thing to do, but might have consequences that I'm not seeing yet. Add Comment Puppet / PUP-2630 Server-set global variables like $::environment get overwritten by client facts As per the docs (http://docs.puppetlabs.com/puppet/latest/reference/lang_facts_and_builtin_vars.html#variables-set-by-the-puppet-master) the puppet master sets the global $::environment variable to contain the name of the node's environment. However, if a node provides a fact with the name 'environment' that fact's value overrides the server-set environme...
Jira (PUP-2922) Acceptance test is using an invalid regex
Title: Message Title Josh Cooper created an issue Puppet / PUP-2922 Acceptance test is using an invalid regex Issue Type: Bug Assignee: Kurt Wall Created: 10/Jul/14 9:41 AM Priority: Normal Reporter: Josh Cooper The following acceptance test: https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/resource/service/should_not_change_the_system.rb#L11 When executing acceptance tests, the following warning is printed, but is not fatal: tests/resource/service/should_not_change_the_system.rb:11: warning: regexp has invalid interval tests/resource/service/should_not_change_the_system.rb:22: warning: regexp has invalid interval I think the regex needs to escape the single quote [^\']. But it makes me wonder if this test is actually testing anything. For reasons unknown the error message is intermingled in beaker output: https://jenkins.puppetlabs.com/view/Puppet%20FOSS/view/puppet-4/job/Puppet-Package-Acceptance-4.0/label=acc-coord,platform=rhel7/151/consoleFull Puppet returns only resource package declaration when qtests/resource/service/should_not_change_the_system.rb:11: warning: regexp has invalid interval tests/resource/service/should_not_change_the_system.rb:22: warning: regexp has invalid interval uerying an uninstalled package
Jira (PUP-2630) Server-set global variables like $::environment get overwritten by client facts
Title: Message Title Henrik Lindberg commented on an issue Re: Server-set global variables like $::environment get overwritten by client facts Maybe add $server_facts as well to have one authoritative source, and then either leave it as is (node facts overwrite), or change it to overwrite the other way (enforce server facts). In any case a warning (or even error) should be issued. Add Comment Puppet / PUP-2630 Server-set global variables like $::environment get overwritten by client facts As per the docs (http://docs.puppetlabs.com/puppet/latest/reference/lang_facts_and_builtin_vars.html#variables-set-by-the-puppet-master) the puppet master sets the global $::environment variable to contain the name of the node's environment. However, if a node provides a fact with the name 'environment' that fact's value overrides the server-set environme... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to
Jira (PUP-2909) Incorporate linting and static verification with rubocop
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2909 Incorporate linting and static verification with rubocop Applying the Client tag for tracking purposes. Don't let that confuse anyone though - this support is puppet-wide. Change By: Kylo Ginsberg Component/s: Client Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2881) Upgrade win32-taskscheduler (or replace)
Title: Message Title Rob Reynolds commented on an issue Re: Upgrade win32-taskscheduler (or replace) Also, remove task scheduler from the vendored ruby gems. Add Comment Puppet / PUP-2881 Upgrade win32-taskscheduler (or replace) We need to either upgrade or replace the use of win32-taskscheduler. During some upgrading we found issues, which lead to this particular ticket out of PUP-392. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-547) Limit the output of prtdiag on Solaris
Title: Message Title Andy Parker commented on an issue Re: Limit the output of prtdiag on Solaris Tried this out on a solaris 11 box. It appeared to work fine. However, prtdiag runs very quickly on the box, so it is hard to tell if it really saves time. Add Comment Facter / FACT-547 Limit the output of prtdiag on Solaris prtdiag is used to determine manufacturer and productname on Solaris If you run it on a big box like a SPARC T5 it produces a lot of output, and might take some time. On a SPARC T5 this can cause timeouts. Will provide a PR This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2802) add slot support for packages in portage.rb
Title: Message Title Andy Parker commented on an issue Re: add slot support for packages in portage.rb There are still some open questions on the PR about specifying versions without a slot. Add Comment Puppet / PUP-2802 add slot support for packages in portage.rb This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1541) PR (2309): Separate out hold state into a separate property - lollipopman
Title: Message Title Andy Parker commented on an issue Re: PR (2309): Separate out hold state into a separate property - lollipopman There are a number of problems that Adrien Thebo identified in the PR. The functional problems are around how it interacts with puppet's handling of ensure and syncing of properties. Add Comment Puppet / PUP-1541 PR (2309): Separate out hold state into a separate property - lollipopman h2. Separate out hold state into a separate property * Author: * Company: * Github ID: [lollipopman|https://github.com/lollipopman] * [Pull Request 2309 Discussion|https://github.com/puppetlabs/puppet/pull/2309] * [Pull Request 2309 File Diff|https://github.com/puppetlabs/puppet/pull/2309/files] h2. Pull Request Description Currently hol... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-1541) PR (2309): Separate out hold state into a separate property - lollipopman
Title: Message Title Andy Parker assigned an issue to Jesse Hathaway Puppet / PUP-1541 PR (2309): Separate out hold state into a separate property - lollipopman Change By: Andy Parker Assignee: JesseHathaway Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-598) fqdn is concatenation of hostname -s and domainname instead of hostname -f
Title: Message Title Andy Parker assigned an issue to Adrien Thebo Facter / FACT-598 fqdn is concatenation of hostname -s and domainname instead of hostname -f Change By: Andy Parker Assignee: AdrienThebo Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2626) Accept module paths in Puppet::Parser::Functions.file()
Title: Message Title Andy Parker assigned an issue to Andy Parker Puppet / PUP-2626 Accept module paths in Puppet::Parser::Functions.file() Change By: Andy Parker Assignee: AndyParker Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1244) Yum provider using version-release to validate installation.
Title: Message Title Jason Antman assigned an issue to Jason Antman Puppet / PUP-1244 Yum provider using version-release to validate installation. Change By: Jason Antman Assignee: JasonAntman Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2881) Upgrade win32-taskscheduler (or replace)
Title: Message Title Moses Mendoza commented on an issue Re: Upgrade win32-taskscheduler (or replace) As far as our obligations with respect to licensing, the Artistic License differentiates between distributing modified versions and source vs in compiled form. It seems to me it would be safe to say that we distribute modified version as source (e.g. via github.com/puppetlabs/puppet), which means we'll also want to adhere to: Distribution of Modified Versions of the Package as Source (4) You may Distribute your Modified Version as Source (either gratis or for a Distributor Fee, and with or without a Compiled form of the Modified Version) provided that you clearly document how it differs from the Standard Version, including, but not limited to, documenting any non-standard features, executables, or modules, and provided that you do at least ONE of the following: (a) make the Modified Version available to the Copyright Holder of the Standard Version, under the Original License, so that the Copyright Holder may include your modifications in the Standard Version. (b) ensure that installation of your Modified Version does not prevent the user installing or running the Standard Version. In addition, the Modified Version must bear a name that is different from the name of the Standard Version. (c) allow anyone who receives a copy of the Modified Version to make the Source form of the Modified Version available to others under the Original License or (ii) a license that permits the licensee to freely copy, modify and redistribute the Modified Version using the same licensing terms that apply to the copy that the licensee received, and requires that the Source form of the Modified Version, and of any works derived from it, be made freely available in that license fees are prohibited but Distributor Fees are allowed. IMO by emailing the author with the patch set we satisfy (a), which means the only remaining obligation from that clause is to document how our version and the upstream version differ, which could be done in a README or some other file in the repo. Add Comment Puppet / PUP-2881 Upgrade win32-taskscheduler (or replace)
Jira (PUP-2922) Acceptance test is using an invalid regex
Title: Message Title
Kurt Wall commented on an issue
Re: Acceptance test is using an invalid regex
Josh Cooper Beaker's logging has other issues with logging, such as QENG-637, so it wouldn't surprise me if something odd was going on here.
Add Comment
Puppet / PUP-2922
Acceptance test is using an invalid regex
The following acceptance test: https://github.com/puppetlabs/puppet/blob/master/acceptance/tests/resource/service/should_not_change_the_system.rb#L11 When executing acceptance tests, the following warning is printed, but is not fatal: {noformat} tests/resource/service/should_not_change_the_system.rb:11: warning: regexp has invalid interval tests/r...
This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
--
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2885) Periodic timeouts when reading from master
Title: Message Title Joshua Partlow commented on an issue Re: Periodic timeouts when reading from master Merged to master in 30e1d28 Add Comment Puppet / PUP-2885 Periodic timeouts when reading from master Periodically, there are failures where the agent performs a pluginsync, a number of files are downloaded from the master, and eventually one of the files hangs, timeouts, and causes the pluginsync to abort. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2885) Periodic timeouts when reading from master
Title: Message Title Joshua Partlow commented on an issue Re: Periodic timeouts when reading from master Kurt Wall I think you can FR this by creating some variable amount of module lib files, and setting very small agent configtimeout values. Add Comment Puppet / PUP-2885 Periodic timeouts when reading from master Periodically, there are failures where the agent performs a pluginsync, a number of files are downloaded from the master, and eventually one of the files hangs, timeouts, and causes the pluginsync to abort. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2728) zypper should always be the default package provider for Suse osfamily
Title: Message Title Matteo Cerutti commented on an issue Re: zypper should always be the default package provider for Suse osfamily Adrien Thebo, you can download yum rpm for OpenSuSE/SLES at http://download.opensuse.org/repositories/system:/packagemanager. HTH, Matteo Add Comment Puppet / PUP-2728 zypper should always be the default package provider for Suse osfamily zypper package manager should always be the default package provider for Suse osfamily. Additionally, this prevents puppet agent from moaning about the presence of multiple package providers if others are also installed (e.g. Yum) along with zypper. In this case, Puppet will default to the first provider it finds, which does not happen to be the same... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-2040) Allow excluding content from Puppet module tool built packages
Title: Message Title Brandon High updated an issue Puppet / PUP-2040 Allow excluding content from Puppet module tool built packages Change By: Brandon High Sprint: Week2014-7-9 Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2923) Add assumeyes attribute to yumrepo
Title: Message Title Joseph Damato created an issue Puppet / PUP-2923 Add assumeyes attribute to yumrepo Issue Type: Improvement Assignee: Unassigned Created: 10/Jul/14 2:12 PM Priority: Major Reporter: Joseph Damato Original Estimate: 1 hour Remaining Estimate: 1 hour The yumrepo type appears to be missing the boolean assumeyes attribute. This attribute is necessary in the following condition, and possibly others: The gpgkey attribute is set to a URL The repo_gpgcheck attribute is set to 1 When the above two attributes are set, yum will prompt for user input asking the user whether the GPG key should be imported. During a puppet run, the user won't actually be prompted and so the key will not be imported and subsequent package install may also fail. Adding the assumeyes attribute resolves this because yum will not attempt to prompt for user input when importing the key and the key will just be imported.
Jira (FACT-621) Add OpenBSD support for 'partitions' fact
Title: Message Title Jasper Lievisse Adriaanse commented on an issue Re: Add OpenBSD support for 'partitions' fact Would it help functional testing if beaker were available on OpenBSD? Add Comment Facter / FACT-621 Add OpenBSD support for 'partitions' fact Currently the partitions fact only supports Linux, this PR adds support for OpenBSD too. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-621) Add OpenBSD support for 'partitions' fact
Title: Message Title Andy Parker commented on an issue Re: Add OpenBSD support for 'partitions' fact Jasper Lievisse Adriaanse, not directly. Our functional testing is manual exploratory testing of the feature and other related things. So getting beaker working on OpenBSD would only work in so far as it would increase the likelihood that we would run our automated tests on OpenBSD and therefore have OpenBSD VMs handy. Also, I figured that you had already reviewed it pretty well Add Comment Facter / FACT-621 Add OpenBSD support for 'partitions' fact Currently the partitions fact only supports Linux, this PR adds support for OpenBSD too. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2040) Allow excluding content from Puppet module tool built packages
Title: Message Title Brandon High assigned an issue to Brandon High Puppet / PUP-2040 Allow excluding content from Puppet module tool built packages Change By: Brandon High Assignee: PietervandeBruggen BrandonHigh Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2924) Puppet searches disk for whit classes
Title: Message Title Peter Bakkum created an issue Puppet / PUP-2924 Puppet searches disk for whit classes Issue Type: Bug Assignee: Unassigned Created: 10/Jul/14 5:12 PM Environment: SmartOS, Puppet 3.6.2 Priority: Normal Reporter: Peter Bakkum Our Puppet instance has been pretty slow lately so we traced a puppet agent run to see what it was doing. In the trace we see a bunch of lines like this: stat(/opt/local/lib/ruby/site_ruby/2.0.0/puppet/vendor/semantic/lib/puppet/type/completed_stage.rb, 0xFD7FFFDFE4A0) Err#2 ENOENT stat(/etc/puppet/modules/admin/lib/puppet/type/completed_stage.rb, 0xFD7FFFDFE4A0) Err#2 ENOENT stat(/etc/puppet/modules/percona/lib/puppet/type/completed_stage.rb, 0xFD7FFFDFE4A0) Err#2 ENOENT stat(/etc/puppet/shared/modules/apt/lib/puppet/type/completed_stage.rb, 0xFD7FFFDFE4A0) Err#2 ENOENT stat(/etc/puppet/shared/modules/puppetlabs-stdlib/lib/puppet/type/completed_stage.rb, 0xFD7FFFDFE4A0) Err#2 ENOENT stat(/etc/puppet/external/modules/python/lib/puppet/type/completed_stage.rb, 0xFD7FFFDFE4A0) Err#2 ENOENT stat(/etc/puppet/external/modules/yum_puppet_plugin/lib/puppet/type/completed_stage.rb, 0xFD7FFFDFE4A0) Err#2 ENOENT stat(/var/lib/puppet/lib/puppet/type/completed_stage.rb, 0xFD7FFFDFE4A0) Err#2 ENOENT stat(/opt/local/lib/ruby/gems/2.0.0/gems/bigdecimal-1.2.0/lib/puppet/type/completed_stage.rb, 0xFD7FFFDFE4A0) Err#2 ENOENT stat(/opt/local/lib/ruby/gems/2.0.0/gems/bundler-1.5.3/lib/puppet/type/completed_stage.rb, 0xFD7FFFDFE4A0) Err#2 ENOENT stat(/opt/local/lib/ruby/gems/2.0.0/gems/byebug-3.1.2/lib/puppet/type/completed_stage.rb, 0xFD7FFFDFE4A0) Err#2 ENOENT
