Jira (PDB-1745) PR (1522): (maint) fix config migration - wkalt
Title: Message Title gepetto-bot commented on PDB-1745 Re: PR (1522): (maint) fix config migration - wkalt wkalt commented: @ajroetker that directory is the hsqldb data directory. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1746) PR (1523): (maint) revert project version - wkalt
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1746 PR (1523): (maint) revert project version - wkalt Issue Type: Task Assignee: Unassigned Created: 2015/07/09 9:35 AM Labels: github Priority: Normal Reporter: gepetto-bot (maint) revert project version Author: Wyatt Alt Company: Github ID: wkalt Pull Request 1523 Discussion Pull Request 1523 File Diff Pull Request Description This reverts our project version so we can smoke test without polluting nexus. (webhooks-id: 529b999389b472ff53e29d8c0232d138)
Jira (PDB-1745) PR (1522): (maint) fix config migration - wkalt
Title: Message Title gepetto-bot commented on PDB-1745 Re: PR (1522): (maint) fix config migration - wkalt Pull request (maint) fix config migration has been closed. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1746) PR (1523): (maint) revert project version - wkalt
Title: Message Title gepetto-bot commented on PDB-1746 Re: PR (1523): (maint) revert project version - wkalt Pull request (maint) revert project version has been closed. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4688) Ensure tests work correctly on OSX
Title: Message Title Michael Smith commented on PUP-4688 Re: Ensure tests work correctly on OSX Seems to have failed CI pre-suite. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1745) PR (1522): (maint) fix config migration - wkalt
Title: Message Title gepetto-bot commented on PDB-1745 Re: PR (1522): (maint) fix config migration - wkalt ajroetker commented: Without this we were parsing the subname to get the location of the hsqldb data directory so it can be migrated. In the default case though, this resides in the vardir, which is migrated a moment before. This patch changes things so that we only attempt to migrate that directory if Which is that directory? the original vardir still exists, which is a signal that the vardir is signal that the user had changed the vardir but not the hsqldb subname nonstandard, but the subname still points to the old one (since it's still the default value.) The commit message and PR message use a lot of pronouns that kind of made this hard to parse without a few rereads. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1111) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title Branan Riley commented on FACT- Re: deprecation of 'facter --puppet' removes critically necessary functionality Kylo Ginsberg Currently we reset libdir. If somebody had (for some reason) set both libdir and plugindest to the same value (even though plugindest defaults to libdir), we'd be causing breakages in the upgrade process. Given it's a one-liner to fix plugindest where we fixup libdir, it seems a worthwhile just in case... but def is unrelated to this ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1111) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title Michael Smith commented on FACT- Re: deprecation of 'facter --puppet' removes critically necessary functionality Facts that rely on things like Puppet::Util would work with facter -p, because Facter actually does require 'puppet'. So this still breaks some facts that would've worked with facter -p, but in a fairly trivial way. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1111) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title Branan Riley commented on FACT- Re: deprecation of 'facter --puppet' removes critically necessary functionality I'm fine with saying that those facts need to explicitly 'require puppet'. We probably do need to make sure that puppet is in our $LOAD_PATH, though. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1111) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title Kylo Ginsberg commented on FACT- Re: deprecation of 'facter --puppet' removes critically necessary functionality Agreed on gracefully handling failures to load custom facts. As for log level, I'd incline the other way, i.e. to making it a warning or error if custom facts fail to load - that is something that the admin should fix. Otoh, it may be that it's super common and we don't want to spam people who've been blithely living with custom fact load failures for years. Perhaps we should look at what facter 2 does as input to the log level question. As for resetting plugin*dest, IIRC Josh Cooper suggested that those two settings couldn't be productively or correctly set in puppet anyway, meaning maybe no one is doing so. Not sure if I got that right, or how to validate that though. So it couldn't hurt to reset those settings in puppet_agent. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1090) Custom facts not loaded when using puppet resource command
Title: Message Title Michael Smith commented on FACT-1090 Re: Custom facts not loaded when using puppet resource command So walking through the workflow again, here's what you could do with Ruby Facter: 1) Query an individual fact 2) Change $LOAD_PATH 3) Query an individual fact that is now available thanks to the change in $LOAD_PATH 4) Query all facts (as with to_hash) 5) Change $LOAD_PATH 6) Query all facts ignores the changed $LOAD_PATH 7) Query an individual fact will use the $LOAD_PATH, but only if the name matches the file it's defined in That behavior seems kind of confusing. You can individual facts that won't show up when you query all facts, because all facts is cached but individual facts aren't and check the $LOAD_PATH every time. Facter simplified that by ensuring that querying an individual fact would never find a fact that couldn't be found by querying all facts, but requires a Facter.reset to pick up any change in $LOAD_PATH. Requiring an explicit request to pick up a change in $LOAD_PATH seems sane compared to the set of circumstances I outlined above. The alternative that makes querying individual facts and to_hash consistent gets complicated: we have to check whether $LOAD_PATH has changed, if so search for new custom facts, if we load any re-evaluate all previous facts to see if they can now be resolved. Not much different than a Facter.reset. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1111) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title Peter Huene commented on FACT- Re: deprecation of 'facter --puppet' removes critically necessary functionality re: custom facts failing to load, currently we log an error in factor along with any exception message; --trace will cause the output to include the back trace, like we would have from Ruby Facter. I think that's sufficient and desirable. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1163) Smoke test packages
Title: Message Title Andrew Roetker commented on PDB-1163 Re: Smoke test packages Smoke tested upgrade and install on el7 puppetlabs nocm vagrant boxes. Worked great! Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2509) puppet resource service on Solaris needs -H flag
Title: Message Title
John Duarte commented on PUP-2509
Re: puppet resource service on Solaris needs -H flag
Running puppet at SHA e2fb8f3aa1797f675872c2761837d34aa14cd78f, this fails review.
PREVIEW is still captured as a service. The other headers do not appear in the found services.
root@t3mptnqng5dfnmy:/opt/puppet-git-repos/puppet# facter os
{name=Solaris, family=Solaris, release={major=11, minor=2, full=11.2}}
root@t3mptnqng5dfnmy:/opt/puppet-git-repos/puppet# git rev-parse HEAD
e2fb8f3aa1797f675872c2761837d34aa14cd78f
root@t3mptnqng5dfnmy:/opt/puppet-git-repos/puppet# puppet resource service | head -50
service { 'PRESERVE':
ensure = 'stopped',
}
service { 'acct':
ensure = 'stopped',
Jira (PDB-1746) PR (1523): (maint) revert project version - wkalt
Title: Message Title gepetto-bot commented on PDB-1746 Re: PR (1523): (maint) revert project version - wkalt 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/1634/ Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1084) Facter crashes on Windows when a network interface does not have a DHCP server assigned
Title: Message Title John Duarte commented on FACT-1084 Re: Facter crashes on Windows when a network interface does not have a DHCP server assigned Using puppet-agent SHA 698c32a6590009fa66beec549e18210b348ece01, this passes functional review. Steps to reproduce Using a Windows 8.1 x86_64 VM. Install loopback network adapter Open the Control Panel Search for Device Manager Open Device Manager Select Add legacy hardware from the Action menu. This will launch the Add Hardware Wizard Select the Install hardware I manually select option Select Network Adapters In the adapter select list, select Microsoft from the manufacturers pane and Microsoft KM-TEST Loopback Adapter from the network adapter pane. Continue to click Next to complete the install Install puppet-agent Run facter networking --debug Result C:\Program Files\Puppet Labs\Puppet\binfacter networking --debug 2015-07-09 11:45:40.122126 INFO puppetlabs.facter - executed with command line: networking --debug. 2015-07-09 11:45:40.122126 DEBUG puppetlabs.facter - no loaded libraries found matching pattern .*ruby(\d)?(\d)?(\d)?\.dll
Jira (PUP-4847) Custom facts not loaded when using puppet resource command
Title: Message Title Michael Smith updated an issue Puppet / PUP-4847 Custom facts not loaded when using puppet resource command Change By: Michael Smith
Jira (PDB-1747) PR (1524): (maint) Set version in project.clj to 3.0.0 - senior
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1747 PR (1524): (maint) Set version in project.clj to 3.0.0 - senior Issue Type: Task Assignee: Unassigned Created: 2015/07/09 11:53 AM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Set version in project.clj to 3.0.0 Author: Ryan Senior senior.r...@gmail.com Company: Github ID: senior Pull Request 1524 Discussion Pull Request 1524 File Diff Pull Request Description (webhooks-id: b387dc372b6b42658cb64080dda92065)
Jira (PDB-1747) PR (1524): (maint) Set version in project.clj to 3.0.0 - senior
Title: Message Title gepetto-bot commented on PDB-1747 Re: PR (1524): (maint) Set version in project.clj to 3.0.0 - senior Pull request (maint) Set version in project.clj to 3.0.0 has been closed. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1111) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title Josh Cooper commented on FACT- Re: deprecation of 'facter --puppet' removes critically necessary functionality re: plugindest, if plugindest is changed from the default, then puppet agent won't be able to load pluginsynced code: see https://projects.puppetlabs.com/issues/18459. The reason is because libdir is not also updated to reflect the new location, and the hook for that setting is what changes puppet's $LOAD_PATH. So tl; dr, puppet agent will not work if you change the default plugindest. The other thing to consider is pluginfactsdest for pluginsync'ed external facts. If that value was changed, I think puppet will still work (could tell facter to load those external facts). But I'm not sure if facter -p would have worked previously. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4847) Custom facts not loaded when using puppet resource command
Title: Message Title Michael Smith moved an issue Puppet / PUP-4847 Custom facts not loaded when using puppet resource command Change By: Michael Smith Fix Version/s: FACT3.0.2 Fix Version/s: PUP4.2.1 Key: FACT PUP - 1090 4847 Project: Facter Puppet Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1111) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title Josh Cooper commented on FACT- Re: deprecation of 'facter --puppet' removes critically necessary functionality re:pluginfactsdest, was ticketed as FACT-696 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1085) Facter should not redirect stderr to stdout
Title: Message Title John Duarte assigned an issue to John Duarte Facter / FACT-1085 Facter should not redirect stderr to stdout Change By: John Duarte Assignee: SeanGriffin JohnDuarte Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1111) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title Peter Huene commented on FACT- Re: deprecation of 'facter --puppet' removes critically necessary functionality From Michael's link, it doesn't look like Facter 2.x added pluginfactsdest to the external search paths, so I don't think pluginsync'd external facts worked even with -p in 2.x. Still, that's something we should get working in 3.0.2, even if it's for the default location only. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2509) puppet resource service on Solaris needs -H flag
Title: Message Title John Duarte assigned an issue to John Duarte Puppet / PUP-2509 puppet resource service on Solaris needs -H flag Change By: John Duarte Assignee: qa JohnDuarte Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1084) Facter crashes on Windows when a network interface does not have a DHCP server assigned
Title: Message Title John Duarte assigned an issue to John Duarte Facter / FACT-1084 Facter crashes on Windows when a network interface does not have a DHCP server assigned Change By: John Duarte Assignee: SeanGriffin JohnDuarte Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2509) puppet resource service on Solaris needs -H flag
Title: Message Title John Duarte assigned an issue to Kylo Ginsberg Puppet / PUP-2509 puppet resource service on Solaris needs -H flag Change By: John Duarte Assignee: JohnDuarte KyloGinsberg Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4819) Add service for obtaining class information per environment
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-4819 Add service for obtaining class information per environment Change By: Henrik Lindberg Assignee: HenrikLindberg Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4688) Ensure tests work correctly on OSX
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-4688 Ensure tests work correctly on OSX Change By: Josh Cooper Assignee: JoshCooper Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1750) PR (1525): (maint) Pin the module version we use in acceptance tests - ajroetker
Title: Message Title gepetto-bot commented on PDB-1750 Re: PR (1525): (maint) Pin the module version we use in acceptance tests - 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/1635/ Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1750) PR (1525): (maint) Pin the module version we use in acceptance tests - ajroetker
Title: Message Title gepetto-bot commented on PDB-1750 Re: PR (1525): (maint) Pin the module version we use in acceptance tests - ajroetker Pull request (maint) Pin the module version we use in acceptance tests has been closed. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4826) meaning of Integer[0] different in a ruby function
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4826 meaning of Integer[0] different in a ruby function Change By: Henrik Lindberg Sprint: Language2015-07-22 Scrum Team: Language Story Points: 1 Scope Change Reason: communityreported-inconsistencyintypesystembetweenpuppet/ruby Scope Change Category: Found Fix Version/s: PUP4.2.1 Fix Version/s: PUP3.8.2 Release Notes: BugFix Add Comment
Jira (PUP-4826) meaning of Integer[0] different in a ruby function
Title: Message Title Henrik Lindberg commented on PUP-4826 Re: meaning of Integer[0] different in a ruby function Merged to stable and master Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4848) Global parser = future with environment.conf parser = current gives an error in PE
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4848 Global parser = future with environment.conf parser = current gives an error in PE Change By: Henrik Lindberg Fix Version/s: PUP3.8.2 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1750) PR (1525): (maint) Pin the module version we use in acceptance tests - ajroetker
Title: Message Title gepetto-bot commented on PDB-1750 Re: PR (1525): (maint) Pin the module version we use in acceptance tests - ajroetker ajroetker commented: @mullr @senior we should merge this in while my other better fix is in flight Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1743) PR (61): (maint) Prep extensions for PuppetDB 3.0.0 release - ajroetker
Title: Message Title gepetto-bot commented on PDB-1743 Re: PR (61): (maint) Prep extensions for PuppetDB 3.0.0 release - ajroetker ajroetker commented: @senior looks like travis isn't running with the `test.sh` update Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4826) meaning of Integer[0] different in a ruby function
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-4826 meaning of Integer[0] different in a ruby function Change By: Thomas Hallgren Assignee: ThomasHallgren Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1745) PR (1522): (maint) fix config migration - wkalt
Title: Message Title gepetto-bot commented on PDB-1745 Re: PR (1522): (maint) fix config migration - wkalt 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/1633/ Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4826) meaning of Integer[0] different in a ruby function
Title: Message Title Thomas Hallgren commented on PUP-4826 Re: meaning of Integer[0] different in a ruby function Looking at the TypeParser, i see that Float[0] is handled the same way as Integer[0]. I'll change that too. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3788) Puppet Agent does not support Chained CRLs
Title: Message Title Andreas Paul commented on PUP-3788 Re: Puppet Agent does not support Chained CRLs I'm a bit surprised this doesn't just work. Puppet just hands off the file to openssl, and I thought openssl could handle a multi-crl pem file. Josh Cooper If that is indeed how the Puppet agent tries to validate a CRL file, then there is your root cause. openssl can not handle multiple CRLs in one file. $ curl -s https://tickets.puppetlabs.com/secure/attachment/17918/crl_bundle.pem | openssl crl -noout -text | grep Issuer Issuer: /C=US/ST=Oregon/O=Puppet Labs/OU=Engineering/CN=szxkjow4ae4a4zt.delivery.puppetlabs.net\x0A Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PUP-4810) Puppet caches parse results when environment_timeout is set to 0
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-4810 Puppet caches parse results when environment_timeout is set to 0 Change By: Thomas Hallgren Assignee: ThomasHallgren Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4810) Puppet caches parse results when environment_timeout is set to 0
Title: Message Title Thomas Hallgren commented on PUP-4810 Re: Puppet caches parse results when environment_timeout is set to 0 Merged to 3.x at 06d8d42, to stable at ff9b5a5, and to master at 9cda507. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4810) Puppet caches parse results when environment_timeout is set to 0
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-4810 Puppet caches parse results when environment_timeout is set to 0 Change By: Thomas Hallgren Assignee: ThomasHallgren Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4752) Uppercase letters in parameter variable names
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-4752 Uppercase letters in parameter variable names Change By: Thomas Hallgren Assignee: ThomasHallgren Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4752) Uppercase letters in parameter variable names
Title: Message Title Thomas Hallgren commented on PUP-4752 Re: Uppercase letters in parameter variable names Merged to 3.x at e6a2f62, to stable at 1bfeb51, and to master at e2fb8f3. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4752) Uppercase letters in parameter variable names
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-4752 Uppercase letters in parameter variable names Change By: Thomas Hallgren Assignee: ThomasHallgren Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1111) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title Jo Rhett commented on FACT- Re: deprecation of 'facter --puppet' removes critically necessary functionality Peter: that is completely untrue. Not only have I written dozens of modules which sync down facts that are used in bash scripts on the host, but I've found that dozens of community modules I depend on do similar things, pushing down facts to be used for cron jobs, etc. That is why I opened this issue. This did and does today work with Facter 2. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1163) Smoke test packages
Title: Message Title Ryan Senior commented on PDB-1163 Re: Smoke test packages Installed 2.3.5 on trusty, upgraded to 3.0.0, worked fine Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1111) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title Josh Cooper commented on FACT- Re: deprecation of 'facter --puppet' removes critically necessary functionality Jo Rhett you are confusing pluginsynced custom vs pluginsynced external facts. The former did work previously in 2.x, the latter did not (see FACT-696 ). Unfortunately we don't have great names for the three variations of facts: pluginsynced custom vs pluginsynced external vs non-pluginsynced external... Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4847) Custom facts not loaded when using puppet resource command
Title: Message Title Kylo Ginsberg commented on PUP-4847 Re: Custom facts not loaded when using puppet resource command Thanks for the analysis. Given the above, I agree with fixing this in puppet. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1085) Facter should not redirect stderr to stdout
Title: Message Title
John Duarte commented on FACT-1085
Re: Facter should not redirect stderr to stdout
Using puppet-agent at SHA 698c32a6590009fa66beec549e18210b348ece01, this passes functional review.
Steps to reproduce
Install puppet agent on Debian Wheezy device
Create custom fact on device
# cat my_facts/pe_razor_server_version.rb
Facter.add(pe_razor_server_version) do
confine :osfamily = Debian
setcode do
Facter::Core::Execution.exec(dpkg-query -W --showformat='${Version}' pe-razor-server | cut -f1 -d'-')
end
end
Jira (FACT-1111) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title Michael Smith commented on FACT- Re: deprecation of 'facter --puppet' removes critically necessary functionality To summarize a short in-person conversation with Branan Riley: To have Facter use Puppet's libdir for custom facts, we need to add libdir to the Ruby $LOAD_PATH when Facter initializes Ruby (before https://github.com/puppetlabs/facter/blob/stable/lib/src/ruby/module.cc#L756) Adding Puppet's pluginfactdest for external facts adds them to https://github.com/puppetlabs/facter/blob/stable/lib/src/facts/windows/collection.cc#L34 and https://github.com/puppetlabs/facter/blob/stable/lib/src/facts/posix/collection.cc#L19. In response to my own comment yesterday, we need to gracefully handle failures to load custom facts (pretty sure we already do, but worth verifying) and move people to modules to requiring Puppet explicitly if they need it and want to be usable. Tempted to make this an INFO level message, rather than a warning. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2509) puppet resource service on Solaris needs -H flag
Title: Message Title
William Hopper commented on PUP-2509
Re: puppet resource service on Solaris needs -H flag
PRESERVE and four other services are added to the top of the service list by the init service provider, rather than smf:
root@solaris12:~/puppet# bundle exec puppet resource service
DEBUG: acct
DEBUG: pppd
DEBUG: sendmail
DEBUG: dodatadm.udaplt
service { 'PRESERVE':
ensure = 'stopped',
}
service { 'acct':
ensure = 'stopped',
Jira (FACT-1083) fork/exec in Facter causes OOM in puppetserver
Title: Message Title Eric Thompson updated an issue Facter / FACT-1083 fork/exec in Facter causes OOM in puppetserver Change By: Eric Thompson QA Risk Assessment Reason: internalcodechanges,coveredbymanyacceptanceandunittestsanddownstreamservertests Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1083) fork/exec in Facter causes OOM in puppetserver
Title: Message Title Eric Thompson updated an issue Facter / FACT-1083 fork/exec in Facter causes OOM in puppetserver Change By: Eric Thompson QA Risk Assessment: Medium Low Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1083) fork/exec in Facter causes OOM in puppetserver
Title: Message Title Eric Thompson updated an issue Facter / FACT-1083 fork/exec in Facter causes OOM in puppetserver Change By: Eric Thompson QA Risk Probability: Medium Low Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2509) puppet resource service on Solaris needs -H flag
Title: Message Title William Hopper assigned an issue to William Hopper Puppet / PUP-2509 puppet resource service on Solaris needs -H flag Change By: William Hopper Assignee: KyloGinsberg WilliamHopper Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4810) Puppet caches parse results when environment_timeout is set to 0
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-4810 Puppet caches parse results when environment_timeout is set to 0 Change By: Owen Rodabaugh CS Priority: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3062) The default unit for `splaylimit` should not be seconds.
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-3062 The default unit for `splaylimit` should not be seconds. Change By: Owen Rodabaugh CS Priority: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2509) puppet resource service on Solaris needs -H flag
Title: Message Title William Hopper commented on PUP-2509 Re: puppet resource service on Solaris needs -H flag John Duarte Looking a bit further, I think we're actually seeing the right thing here. The original change was intended to remove the literal 'FMRI' header from appearing as a service, which it did. I don't believe PRESERVE or the other services reported by init were intended to be removed. The legacy_run services have always been stripped out of the smf service list, but have always come through the init provider (for reasons beyond my level of Solaris expertise ). Thoughts? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1749) Update Dujour
Title: Message Title Melissa Stone created an issue PuppetDB / PDB-1749 Update Dujour Issue Type: Sub-task Assignee: Unassigned Created: 2015/07/09 3:53 PM Priority: Normal Reporter: Melissa Stone Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4653) The filebucket client uses v1 API URLs internally
Title: Message Title
Shaigy Nixon commented on PUP-4653
Re: The filebucket client uses v1 API URLs internally
Validated with agent running on win2012r2-rubyx64: Manifest on master:
[root@xvexth0tmgidygv manifests]# cat site.pp
filebucket { main:
server = xvexth0tmgidygv.delivery.puppetlabs.net,
path = false }
File { backup = main }
node 'default' {
include test
}
Jira (FACT-867) Port xendomains fact to Facter 3
Title: Message Title Sean Griffin updated an issue Facter / FACT-867 Port xendomains fact to Facter 3 Change By: Sean Griffin QA Risk Severity: Medium Low QA Risk Probability: Medium Low QA Risk Assessment: Medium Low Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1111) deprecation of 'facter --puppet' removes critically necessary functionality
Title: Message Title Michael Smith commented on FACT- Re: deprecation of 'facter --puppet' removes critically necessary functionality Current modules that expect Puppet to be set puppetlabs-apache-0.3.0/spec/fixtures/modules/stdlib/lib/facter/puppet_vardir.rb puppetlabs-concat-1.0.0/lib/facter/concat_basedir.rb puppetlabs-concat-1.0.0-rc1/lib/facter/concat_basedir.rb puppetlabs-concat-1.0.1/lib/facter/concat_basedir.rb puppetlabs-concat-1.0.2/lib/facter/concat_basedir.rb puppetlabs-concat-1.0.3/lib/facter/concat_basedir.rb puppetlabs-concat-1.0.4/lib/facter/concat_basedir.rb puppetlabs-concat-1.1.0/lib/facter/concat_basedir.rb puppetlabs-concat-1.1.0-rc1/lib/facter/concat_basedir.rb puppetlabs-concat-1.1.1/lib/facter/concat_basedir.rb puppetlabs-concat-1.1.2/lib/facter/concat_basedir.rb puppetlabs-concat-1.2.0/lib/facter/concat_basedir.rb puppetlabs-concat-1.2.1/lib/facter/concat_basedir.rb puppetlabs-concat-1.2.2/lib/facter/concat_basedir.rb puppetlabs-firewall-1.4.0/lib/facter/iptables_persistent_version.rb puppetlabs-firewall-1.5.0/lib/facter/iptables_persistent_version.rb puppetlabs-keystone-2.1.0/spec/fixtures/modules/stdlib/lib/facter/puppet_vardir.rb puppetlabs-mysql-2.2.0/spec/fixtures/modules/stdlib/lib/facter/puppet_vardir.rb puppetlabs-nodejs-0.1.1/spec/fixtures/modules/stdlib/lib/facter/puppet_vardir.rb puppetlabs-nodejs-0.2.0/spec/fixtures/modules/stdlib/lib/facter/puppet_vardir.rb puppetlabs-pe_upgrade-1.0.0/spec/fixtures/modules/stdlib/lib/facter/puppet_vardir.rb puppetlabs-policy_engine-0.0.1/lib/facter/policy_engine.rb puppetlabs-policy_engine-0.0.1/lib/facter/puppet_vardir.rb puppetlabs-policy_engine-0.0.2/lib/facter/policy_engine.rb puppetlabs-policy_engine-0.0.2/lib/facter/puppet_vardir.rb puppetlabs-stdlib-2.3.0/lib/facter/puppet_vardir.rb puppetlabs-stdlib-2.3.1/lib/facter/puppet_vardir.rb puppetlabs-stdlib-2.3.2/lib/facter/puppet_vardir.rb puppetlabs-stdlib-2.3.3/lib/facter/puppet_vardir.rb puppetlabs-stdlib-2.4.0/lib/facter/facter_dot_d.rb puppetlabs-stdlib-2.4.0/lib/facter/puppet_vardir.rb puppetlabs-stdlib-2.5.0/lib/facter/facter_dot_d.rb puppetlabs-stdlib-2.5.0/lib/facter/puppet_vardir.rb puppetlabs-stdlib-2.5.1/lib/facter/facter_dot_d.rb puppetlabs-stdlib-2.5.1/lib/facter/puppet_vardir.rb puppetlabs-stdlib-2.6.0/lib/facter/facter_dot_d.rb puppetlabs-stdlib-2.6.0/lib/facter/puppet_vardir.rb puppetlabs-stdlib-3.0.0/lib/facter/puppet_vardir.rb puppetlabs-stdlib-3.0.1/lib/facter/puppet_vardir.rb puppetlabs-stdlib-3.1.0/lib/facter/puppet_vardir.rb puppetlabs-stdlib-3.1.1/lib/facter/puppet_vardir.rb puppetlabs-stdlib-3.2.0/lib/facter/puppet_vardir.rb puppetlabs-stdlib-3.2.1/lib/facter/puppet_vardir.rb puppetlabs-stdlib-3.2.2/lib/facter/puppet_vardir.rb puppetlabs-stdlib-4.1.0/lib/facter/puppet_vardir.rb puppetlabs-stdlib-4.2.0/lib/facter/puppet_vardir.rb puppetlabs-stdlib-4.2.1/lib/facter/puppet_vardir.rb puppetlabs-stdlib-4.2.2/lib/facter/puppet_vardir.rb puppetlabs-stdlib-4.3.0/lib/facter/puppet_vardir.rb puppetlabs-stdlib-4.3.2/lib/facter/puppet_vardir.rb puppetlabs-stdlib-4.4.0/lib/facter/puppet_vardir.rb puppetlabs-stdlib-4.5.0/lib/facter/puppet_vardir.rb puppetlabs-stdlib-4.5.1/lib/facter/facter_dot_d.rb puppetlabs-stdlib-4.5.1/lib/facter/puppet_vardir.rb puppetlabs-stdlib-4.6.0/lib/facter/facter_dot_d.rb puppetlabs-stdlib-4.6.0/lib/facter/puppet_vardir.rb Looks like just a few we'd have to patch up.
Jira (PDB-1748) document config-migration noise on 3.0.1 - 3.0.0 downgrade
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-1748 document config-migration noise on 3.0.1 - 3.0.0 downgrade Issue Type: Bug Assignee: Unassigned Created: 2015/07/09 3:33 PM Fix Versions: PDB 3.0.x Priority: Normal Reporter: Wyatt Alt users downgrading will see some junk related to running the config-migration script a second time. We need to document this in the release notes before 3.0.1 goes out. Add Comment
Jira (PDB-1750) PR (1525): (maint) Pin the module version we use in acceptance tests - ajroetker
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-1750 PR (1525): (maint) Pin the module version we use in acceptance tests - ajroetker Issue Type: Task Assignee: Unassigned Created: 2015/07/09 4:34 PM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Pin the module version we use in acceptance tests Author: Andrew Roetker Company: Puppet Labs Github ID: ajroetker Pull Request 1525 Discussion Pull Request 1525 File Diff Pull Request Description This commit pins the module version we use in acceptance tests as v5 of the module was released today and contained breaking changes. This commit is a temporary fix for the issue until we can upgrade to v5 of the puppetdb module.
Jira (PDB-1750) PR (1525): (maint) Pin the module version we use in acceptance tests - ajroetker
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-1750 PR (1525): (maint) Pin the module version we use in acceptance tests - ajroetker Change By: Andrew Roetker Sprint: PuppetDB2015-07-15 Story Points: 1 Scope Change Reason: Brokenacceptancetests Scope Change Category: Found Fix Version/s: PDB3.0.x Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To
Jira (FACT-1112) Move curl wrapper functions to Leatherman
Title: Message Title Maggie Dreyer assigned an issue to Maggie Dreyer Facter / FACT-1112 Move curl wrapper functions to Leatherman Change By: Maggie Dreyer Assignee: MaggieDreyer Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1742) PR (60): (maint) update versions in preparation for 3.0 release - wkalt
Title: Message Title gepetto-bot commented on PDB-1742 Re: PR (60): (maint) update versions in preparation for 3.0 release - wkalt ajroetker commented: added by https://github.com/puppetlabs/pe-puppetdb-extensions/pull/61 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1742) PR (60): (maint) update versions in preparation for 3.0 release - wkalt
Title: Message Title gepetto-bot commented on PDB-1742 Re: PR (60): (maint) update versions in preparation for 3.0 release - wkalt Pull request (maint) update versions in preparation for 3.0 release has been closed. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1620) Release Module 5.0.0
Title: Message Title Wyatt Alt commented on PDB-1620 Re: Release Module 5.0.0 removing fix version 3.0.0 for the moment Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1620) Release Module 5.0.0
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-1620 Release Module 5.0.0 Change By: Wyatt Alt Fix Version/s: PDB3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4826) meaning of Integer[0] different in a ruby function
Title: Message Title Henrik Lindberg commented on PUP-4826 Re: meaning of Integer[0] different in a ruby function Merged to 3.x at: 954f436 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4847) Custom facts not loaded when using puppet resource command
Title: Message Title Michael Smith commented on PUP-4847 Re: Custom facts not loaded when using puppet resource command This exposes a larger problem in how Facter is initialized for anything besides agent/apply/facts - namely puppet resource, where providers may care about facts. It doesn't go through the facter terminus initialization, so pluginsynced external facts don't resolve. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4822) Regression PMT cannot connect to forge on OSX
Title: Message Title Kylo Ginsberg commented on PUP-4822 Re: Regression PMT cannot connect to forge on OSX Michael Stahnke, Anderson Mills: how/where should we fix this? E.g. via pup-3450, or something in our openssl build, or ...? Also, Eric Sorenson, not sure if you're around but is this an SG blocker? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4848) Global parser = future with environment.conf parser = current gives an error in PE
Title: Message Title Jeremy Barlow moved an issue Puppet / PUP-4848 Global parser = future with environment.conf parser = current gives an error in PE Change By: Jeremy Barlow Fix Version/s: PE3.8.x Affects Version/s: PE3.8.1 Affects Version/s: PUP3.8.1 Key: PE PUP - 10643 4848 Project: Puppet Enterprise[Internal] Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To
Jira (PUP-4848) Global parser = future with environment.conf parser = current gives an error in PE
Title: Message Title Jeremy Barlow assigned an issue to Unassigned Puppet / PUP-4848 Global parser = future with environment.conf parser = current gives an error in PE Change By: Jeremy Barlow Sub-team: emerald Assignee: JeremyBarlow Sprint: ServerEmerald2015-07-22 Scrum Team: PuppetServer Language Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4848) Global parser = future with environment.conf parser = current gives an error in PE
Title: Message Title Jeremy Barlow commented on PUP-4848 Re: Global parser = future with environment.conf parser = current gives an error in PE Thanks, Henrik Lindberg. This ticket is now PUP-4848, and I assigned it to the Language scrum team. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
