Jira (PUP-5082) When constructing the environment graph, correctly handle relationships
Title: Message Title David Lutterkort commented on PUP-5082 Re: When constructing the environment graph, correctly handle relationships Forgot: the format for the environment graph is documented here Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5082) When constructing the environment graph, correctly handle relationships
Title: Message Title
David Lutterkort commented on PUP-5082
Re: When constructing the environment graph, correctly handle relationships
Besides using export/consume, which the implementation covers, relationships can also be established with require (it's important that that works, and AFAIK it does), i.e. it's possible to say something like this
define web(...) { }
Web produces Http {
url ="" "http://${::fqdn}/"
}
# lb is a load balancer; it gets its members passed as an array of Http capabilities
define lb (members) { .. }
application app {
web {one: export => Http[one] }
web {two: export => Http[two] }
Jira (PUP-5077) CapabilityFinder needs to tolerate PuppetDB getting backed up
Title: Message Title David Lutterkort commented on PUP-5077 Re: CapabilityFinder needs to tolerate PuppetDB getting backed up If we can be sure that node catalog compiles are only kicked off when we know a node's prereqs have already been started, we could just retry the query with some reasonable but fairly generous timeout. With Direct Puppet, this is a safe assumption. For the time being though, that assumption requires that users configure agents a certain way, and we can't be sure that they did the for all of them. I initially thought that we could use the MQ Metrics endpoint but looking at it again, it doesn't seem feasible - the best we can do is wait for the QueueSize to drop to 0 but if we are unlucky that might not happen for a long time. For now, either just ignore this issue, or just keep retrying the query with some reasonable timeout (say 2 minutes) .. clearly not foolproof but probably good enough. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1245) Fix failing AIX tests - facter 3.1.0 (commit 1a39ed205c3c34cc66a73731c4d910a3fb3a42db)
Title: Message Title John Duarte created an issue Facter / FACT-1245 Fix failing AIX tests - facter 3.1.0 (commit 1a39ed205c3c34cc66a73731c4d910a3fb3a42db) Issue Type: Task Affects Versions: FACT 3.1.1 Assignee: Unassigned Created: 2015/09/28 8:11 PM Environment: AIX 5.3, 6.1, 7.3 Priority: Normal Reporter: John Duarte The following tests fail consistently on AIX 5.3, 6.1, 7.1. Test Case tests/ticket_1123_facter_with_invalid_locale.rb reported: # Test Case tests/facts/ruby.rb reported: #
Jira (FACT-1190) Get pre-suites working for AIX 6.1 (PowerPC) for Facter
Title: Message Title John Duarte assigned an issue to John Duarte Facter / FACT-1190 Get pre-suites working for AIX 6.1 (PowerPC) for Facter Change By: John Duarte Assignee: John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1192) Get pre-suites working for AIX 7.1 (PowerPC) for Facter
Title: Message Title John Duarte assigned an issue to John Duarte Facter / FACT-1192 Get pre-suites working for AIX 7.1 (PowerPC) for Facter Change By: John Duarte Assignee: John Duarte Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5276) User Purge on Windows
Title: Message Title Curtis Ruck commented on PUP-5276 Re: User Purge on Windows We extensively utilize resources/purge to ensure configuration drift is kept under control. To that end we manage users, groups, firewall rules, database users/roles/grants/tablespaces/objects/etc, packages, registry keys, files, etc... a large number of these types are custom, and running across linux and windows. At last count we had about 20 different resources types with purge=>true defined. I've historically found the resources type very frustrating as that it isn't extensible for type specific filters. I.e. you've baked user type details in the resources type, instead of in a provider. Short term, making unless_system_user=>false the default (for windows) would easily allow other Windows users to manage local users without incident. Long term, i'd prefer resources to be deprecated, and the implementation migrated into a new type that allows for extensible logic for managing purges. For example, in our databases (Oracle and SQL Server), we want to purge all users/roles that do not have a specific role granted, if not explicitly defined. I wouldn't care if custom type/providers just implemented a extended a base provider, that allows for custom logic for their types. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1244) xenu vs. xen0 difference not recognized by Puppet
Title: Message Title
Rachel Kelly updated an issue
Facter / FACT-1244
xenu vs. xen0 difference not recognized by Puppet
Change By:
Rachel Kelly
To manage hosts with the Xen hypervisor, customer tries to determine if it is xen0 or xenu, and Facter reports them just as "xen." Ideally for Xen, Puppet/Facter would detect whether you are a xen dom0 or a xen domU (reports xen0 and xenu respectively). Currently this is the report of the virtual fact when using the xen hypervisor.{code:bash}[root@herd-agent-06 ~]# facter virtualxen{code} Per our customer this worked, that is, multiple facts were present for multiple values (xen0, xenu) of Xen in Facter 2.x.
Add Comment
This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email 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-1244) xenu vs. xen0 difference not recognized by Puppet
Title: Message Title Rachel Kelly created an issue Facter / FACT-1244 xenu vs. xen0 difference not recognized by Puppet Issue Type: Bug Affects Versions: FACT 3.1.0 Assignee: Unassigned Created: 2015/09/28 4:51 PM Environment: xen, rhel 5.11/6.7, PE 2015.2.0/2015.2.1 Priority: Normal Reporter: Rachel Kelly To manage hosts with the Xen hypervisor, customer tries to determine if it is xen0 or xenu, and Facter reports them just as "xen." Ideally for Xen, Puppet/Facter would detect whether you are a xen dom0 or a xen domU (reports xen0 and xenu respectively). Currently this is the report of the virtual fact when using the xen hypervisor. [root@herd-agent-06 ~]# facter virtual
Jira (PUP-5264) Agent service status wrong on CentOS 6
Title: Message Title Matthaus Owens commented on PUP-5264 Re: Agent service status wrong on CentOS 6 Dirk Heinrichs I'm unable to reproduce this on a fresh centos 6 install. Can you add the output of `service puppet status` (as well as the return code) please? Also a run of `/opt/puppetlabs/bin/puppet resource service puppet ensure=running enable=true --verbose --trace --debug` would be helpful to see what's going on. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5040) Add agent-on-master configuration to Puppet AIO CI
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5040 Add agent-on-master configuration to Puppet AIO CI Change By: Josh Cooper Sprint: Client Triage Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5245) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Josh Cooper commented on PUP-5245 Re: Is the Jira tidy-up done for this release and prepared for the next one? puppet-agent 1.2.5 only includes an mcollective component fix ( MCO-728 ) and a packaging change on osx in puppet-agent. MCO release versions have been updated. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5240) puppet-agent 1.2.5 2015-09-16 Release
Title: Message Title Josh Cooper commented on PUP-5240 Re: puppet-agent 1.2.5 2015-09-16 Release MCO introduced in mco 2.8.6: https://tickets.puppetlabs.com/issues/?filter=15553 fixed in mco 2.8.6: https://tickets.puppetlabs.com/issues/?filter=15554 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5240) puppet-agent 1.2.5 2015-09-16 Release
Title: Message Title Josh Cooper commented on PUP-5240 Re: puppet-agent 1.2.5 2015-09-16 Release I moved the mcollective ticket to MCO-728 . Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5245) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-5245 Is the Jira tidy-up done for this release and prepared for the next one? Change By: Josh Cooper Assignee: Kylo Ginsberg Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5188) Close all resolved tickets in Jira
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5188 Close all resolved tickets in Jira Change By: Eric Thompson QA Status: Reviewed QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4932) Deprecate cfacter setting
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4932 Deprecate cfacter setting Change By: Eric Thompson QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4495) Puppet 3.5.0 introduced a regression in tag filtering for catalog runs
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4495 Puppet 3.5.0 introduced a regression in tag filtering for catalog runs Change By: Eric Thompson QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4932) Deprecate cfacter setting
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4932 Deprecate cfacter setting Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5059) Add support for --node in 'puppet lookup' command
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-5059 Add support for --node in 'puppet lookup' command Change By: Hailee Kenney Assignee: Hailee Kenney Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5059) Add support for --node in 'puppet lookup' command
Title: Message Title Hailee Kenney assigned an issue to Unassigned Puppet / PUP-5059 Add support for --node in 'puppet lookup' command Change By: Hailee Kenney Assignee: Hailee Kenney Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5061) Add support for --trusted in 'puppet lookup' command
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-5061 Add support for --trusted in 'puppet lookup' command Change By: Hailee Kenney Assignee: Hailee Kenney Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4495) Puppet 3.5.0 introduced a regression in tag filtering for catalog runs
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4495 Puppet 3.5.0 introduced a regression in tag filtering for catalog runs Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4890) Add code_id to catalog
Title: Message Title Josh Cooper assigned an issue to qa Puppet / PUP-4890 Add code_id to catalog Change By: Josh Cooper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5173) puppet 3.8.3 2015-09-21 Release
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5173 puppet 3.8.3 2015-09-21 Release Change By: Eric Thompson QA Status: Reviewed QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5254) Close all resolved tickets in Jira
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5254 Close all resolved tickets in Jira Change By: Eric Thompson QA Status: Reviewed QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5245) Is the Jira tidy-up done for this release and prepared for the next one?
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5245 Is the Jira tidy-up done for this release and prepared for the next one? Change By: Eric Thompson QA Status: Reviewed QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5249) Go/no-go meeting (before 4pm)
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5249 Go/no-go meeting (before 4pm) Change By: Eric Thompson QA Status: Reviewed QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5240) puppet-agent 1.2.5 2015-09-16 Release
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5240 puppet-agent 1.2.5 2015-09-16 Release Change By: Eric Thompson QA Status: Reviewed QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5248) Smoke test packages
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5248 Smoke test packages Change By: Eric Thompson QA Status: Reviewed QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5187) Send out announcements
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5187 Send out announcements Change By: Eric Thompson QA Status: Reviewed QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1243) el acceptance test does not support Scientific or Oracle
Title: Message Title Eric Thompson updated an issue Facter / FACT-1243 el acceptance test does not support Scientific or Oracle Change By: Eric Thompson QA Status: Reviewed QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5059) Add support for --node in 'puppet lookup' command
Title: Message Title Hailee Kenney commented on PUP-5059 Re: Add support for --node in 'puppet lookup' command I'm not sure if this ticket is actually resolved or not (cc: Henrik Lindberg Thomas Hallgren). We currently require a node to be passed in via the --node flag. But this was a decision I made because I didn't know how else to retrieve a scope and doesn't actually match the original description of that flag. Is this the desired behavior we want? Or do we need to do more work around that flag? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5061) Add support for --trusted in 'puppet lookup' command
Title: Message Title Hailee Kenney updated an issue Puppet / PUP-5061 Add support for --trusted in 'puppet lookup' command Change By: Hailee Kenney Sprint: Language 2015- 10 09 - 14 30 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5059) Add support for --node in 'puppet lookup' command
Title: Message Title Hailee Kenney assigned an issue to Unassigned Puppet / PUP-5059 Add support for --node in 'puppet lookup' command Change By: Hailee Kenney Assignee: Hailee Kenney Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4960) Runtime type does not treat ruby Module correctly.
Title: Message Title Henrik Lindberg commented on PUP-4960 Re: Runtime type does not treat ruby Module correctly. Merged to master at: 27bf246 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5059) Add support for --node in 'puppet lookup' command
Title: Message Title Hailee Kenney assigned an issue to Hailee Kenney Puppet / PUP-5059 Add support for --node in 'puppet lookup' command Change By: Hailee Kenney Assignee: Hailee Kenney Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5059) Add support for --node in 'puppet lookup' command
Title: Message Title Hailee Kenney updated an issue Puppet / PUP-5059 Add support for --node in 'puppet lookup' command Change By: Hailee Kenney Sprint: Language 2015- 10 09 - 14 30 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5288) acceptance: puppet ruby in windows should use the correct ssldir
Title: Message Title Eric Thompson created an issue Puppet / PUP-5288 acceptance: puppet ruby in windows should use the correct ssldir Issue Type: Task Assignee: Unassigned Components: QA Created: 2015/09/28 1:36 PM Priority: Normal Reporter: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message
Jira (PUP-5202) missing help for 'puppet lookup' command line option
Title: Message Title Henrik Lindberg commented on PUP-5202 Re: missing help for 'puppet lookup' command line option merged to master: 3f199b9 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5202) missing help for 'puppet lookup' command line option
Title: Message Title Henrik Lindberg assigned an issue to qa Puppet / PUP-5202 missing help for 'puppet lookup' command line option Change By: Henrik Lindberg Status: Ready for Merge Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5287) install_options capability on Solaris provider "sun" - clone
Title: Message Title Rachel Kelly moved an issue Puppet / PUP-5287 install_options capability on Solaris provider "sun" - clone Change By: Rachel Kelly Key: PE PUP - 12253 5287 Project: Puppet Enterprise [Internal] Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5276) User Purge on Windows
Title: Message Title Ethan Brown commented on PUP-5276 Re: User Purge on Windows Curtis Ruck Looking at the code for resources at https://github.com/puppetlabs/puppet/blob/master/lib/puppet/type/resources.rb, I don't think that that type is particularly designed to place nicely on Windows. Could you detail your use case to see if there's a better way of going about your desired behavior? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1430) puppetlabs-puppetdb should be able to manage /etc/sysconfig/puppetdb
Title: Message Title Wyatt Alt commented on PDB-1430 Re: puppetlabs-puppetdb should be able to manage /etc/sysconfig/puppetdb Trevor Vaughan We just merged in a patch to address this: https://github.com/puppetlabs/puppetlabs-puppetdb/pull/210 This introduces a merge_default_java_args setting that will allow you to toggle whether the java_args you provide are merged with the defaults or taken as the single source of truth. In order to manage the HeapDumpOnOutOfMemoryError setting you'll need to set merge_default_java_args to false, then explicitly manage the default settings you want to retain. Wyatt Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-2003) facts GC can exceed jdbc max message size if too many paths are deleted
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2003 facts GC can exceed jdbc max message size if too many paths are deleted Issue Type: Bug Affects Versions: PDB 3.0.2 Assignee: Unassigned Created: 2015/09/28 10:21 AM Priority: Normal Reporter: Wyatt Alt This was reported on the puppet-users list here: https://groups.google.com/forum/#!topic/puppet-users/o_4K-UcuTQQ I don't know the specific context in which the user is encountering it, but I'm able to reproduce this issue by creating and storing a very large array-valued structured fact with map-valued elements, then updating the fact by inserting an element at the front of the array to force recomputation of all the paths. This problem was encountered on 2.3.7, but it affects master/3.x as well. We'll need to coordinate with the user to figure out what's going on with his particular setup. If this relates to a large array-valued structured fact, reformulating the top-level structure as a map would likely fix the issue. Ultimately, if we want to support arbitrarily large structured facts we'll want to expose jdbc's max message size as a tunable. Alternatively we should document our limits.
Jira (PUP-4495) Puppet 3.5.0 introduced a regression in tag filtering for catalog runs
Title: Message Title Sean Griffin commented on PUP-4495 Re: Puppet 3.5.0 introduced a regression in tag filtering for catalog runs This is fixed in the 3.8.3 branch: [root@xec9kfbhtobzrf3 manifests]# puppet apply tag_test.pp --tags test::step1 Notice: Compiled catalog for xec9kfbhtobzrf3.delivery.puppetlabs.net in environment production in 0.21 seconds Notice: /Stage[main]/Test::Step1/File[/tmp/test1.txt]/ensure: created Notice: Finished catalog run in 0.01 seconds [root@xec9kfbhtobzrf3 manifests]# puppet --version 3.8.3 [root@xec9kfbhtobzrf3 manifests]# but not in master: root@s9ng40b9lw8stmc manifests]# puppet apply tag_test.pp --tags test::step1
Jira (FACT-1243) el acceptance test does not support Scientific or Oracle
Title: Message Title William Hopper assigned an issue to William Hopper Facter / FACT-1243 el acceptance test does not support Scientific or Oracle Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4495) Puppet 3.5.0 introduced a regression in tag filtering for catalog runs
Title: Message Title Sean Griffin assigned an issue to Sean Griffin Puppet / PUP-4495 Puppet 3.5.0 introduced a regression in tag filtering for catalog runs Change By: Sean Griffin Assignee: qa Sean Griffin Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1166) bug in RHEL's latest libblkid and facter partitions
Title: Message Title
Fabrice Bacchella commented on FACT-1166
Re: bug in RHEL's latest libblkid and facter partitions
Better but I'm still getting incomplete results:
{
/dev/sda1 => {
size => "1.00 MiB",
size_bytes => 1048576
},
/dev/sda2 => {
mount => "/",
size => "16.00 GiB",
size_bytes => 17179869184
},
/dev/sda3 => {
Jira (PUP-4960) Runtime type does not treat ruby Module correctly.
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-4960 Runtime type does not treat ruby Module correctly. Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-4960) Runtime type does not treat ruby Module correctly.
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-4960 Runtime type does not treat ruby Module correctly. Change By: Thomas Hallgren Sprint: Language 2015- 10 09 - 14 30 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-1165) facter partitions don't manage old HP SA
Title: Message Title Fabrice Bacchella commented on FACT-1165 Re: facter partitions don't manage old HP SA It works for me now. But the name for the partitions changed from /dev/cciss/c0d0p1 to /dev/cciss!c0d0p1 and this block device don't exist. It should be /dev/cciss/c0d0p1. $ ls -l '/dev/cciss!c0d0p1' '/dev/cciss/c0d0p1' ls: cannot access /dev/cciss!c0d0p1: No such file or directory brw-rw 1 root disk 104, 1 Aug 31 16:21 /dev/cciss/c0d0p1 Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-3238) puppet reports "end of file reached" if server closes HTTP connection
Title: Message Title Robert Scheer commented on PUP-3238 Re: puppet reports "end of file reached" if server closes HTTP connection Setting idle-timeout-milliseconds worked: the amount of failure reports dropped to 3 in the past 44 hours after doubling its value. What it is that causes our puppet clients to be so slow remains to be seen, but our immidiate problem is solved now. Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5077) CapabilityFinder needs to tolerate PuppetDB getting backed up
Title: Message Title Thomas Hallgren commented on PUP-5077 Re: CapabilityFinder needs to tolerate PuppetDB getting backed up How can the code can determine that a resource has been submitted but not yet processed? Should it always wait when the resource isn't found or is there some other way of determining this? What should the timeout should be when waiting? Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5077) CapabilityFinder needs to tolerate PuppetDB getting backed up
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5077 CapabilityFinder needs to tolerate PuppetDB getting backed up Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5077) CapabilityFinder needs to tolerate PuppetDB getting backed up
Title: Message Title Thomas Hallgren assigned an issue to David Lutterkort Puppet / PUP-5077 CapabilityFinder needs to tolerate PuppetDB getting backed up Change By: Thomas Hallgren Assignee: Thomas Hallgren David Lutterkort Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email 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-5082) When constructing the environment graph, correctly handle relationships
Title: Message Title
Thomas Hallgren commented on PUP-5082
Re: When constructing the environment graph, correctly handle relationships
David Lutterkort, you write that it's the :out part that is missing from the current implementation. I think it would help me a lot if given an example of expected output and how it differs from the current. AFAICS, the current implementation will provide things that I would consider part of :out such as 'produces'.
The current implementation, when given this manifest:
define prod($host) {
notify { "host ${host}":}
}
Prod produces Cap { }
define cons($host) {
notify { "host ${host}": }
}
