Jira (PDB-3153) (maint) Fix some bootstrap.cfg issues
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3153 (maint) Fix some bootstrap.cfg issues Issue Type: Bug Assignee: Unassigned Created: 2016/10/28 5:02 PM Priority: Normal Reporter: gepetto-bot The bootstrap.cfg file used by the `lein pdb` alias erroneously listed two implementations of PDB's DefaultedConfig TK service protocol. Remove one of them. Delete `test-resources/bootstrap.cfg` as it appears unused (not referenced anywhere, and removing it doesn't break tests). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3152) (maint) remove mq listener service
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-3152 (maint) remove mq listener service Issue Type: Bug Assignee: Unassigned Created: 2016/10/28 4:18 PM Priority: Normal Reporter: gepetto-bot This doesn't exist anymore. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6853) Specification of closure_scope method is false
Title: Message Title
Nicholas Fagerlund created an issue
Puppet / PUP-6853
Specification of closure_scope method is false
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/10/28 3:43 PM
Priority:
Normal
Reporter:
Nicholas Fagerlund
I'm trying to document this, and:
https://github.com/puppetlabs/puppet-specifications/blob/master/language/func-api.md#closure_scope
closure_scope
Returns the scope where the function was defined. This is the scope a function should use if it needs to lookup top-scope variables like $facts. This scope does not provide access to the local scope the call originates from.
Puppet::Functions.create_function("functionbucket::scope_access") do
# Var name dispatch
dispatch(:var_name) do
Jira (PUP-6188) Puppet::FileSystem.open / exclusive_open does not support passing an encoding like UTF-8
Title: Message Title Moses Mendoza commented on PUP-6188 Re: Puppet::FileSystem.open / exclusive_open does not support passing an encoding like UTF-8 Initial PR raised here: https://github.com/puppetlabs/puppet/pull/5354 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3150) Investigate and estimate solutions to the "big structure fact" problem
Title: Message Title Wyatt Alt commented on PDB-3150 Re: Investigate and estimate solutions to the "big structure fact" problem yeah, something like that probably. If we weren't deduplicating we'd probably just need one table. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3150) Investigate and estimate solutions to the "big structure fact" problem
Title: Message Title Nick Walker commented on PDB-3150 Re: Investigate and estimate solutions to the "big structure fact" problem Wyatt Alt by de-duplicating do you mean just store the fact_paths columns directly in facts and potentially fact_values as well? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6852) Unable to install puppet-server on Centos-7
Title: Message Title phanikumar created an issue Puppet / PUP-6852 Unable to install puppet-server on Centos-7 Issue Type: Bug Affects Versions: PUP 3.8.8 Assignee: Unassigned Components: Puppet Server Created: 2016/10/28 2:01 PM Priority: Critical Reporter: phanikumar Hello team, I am trying to install puppet server on Centos-7 and I got the following error Error: Package: 1:ruby-shadow-2.2.0-2.el6.x86_64 (puppetlabs-deps) Requires: libruby.so.1.8()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Could you please help me out on resolving this.
Jira (PDB-3151) Increase admin-clean test wait
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-3151 Increase admin-clean test wait Change By: Rob Browning Summary: Increase admin-clean test delay wait Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3151) Increase admin-clean test delay
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3151 Increase admin-clean test delay Issue Type: Bug Assignee: Rob Browning Created: 2016/10/28 1:31 PM Labels: maintenance Priority: Normal Reporter: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To
Jira (PUP-5000) acceptance: test agent_specified environment, ENC, and related facts
Title: Message Title Eric Thompson commented on PUP-5000 Re: acceptance: test agent_specified environment, ENC, and related facts enc's don't automatically get facts sent to them (they get the node name as an argument). so this test will just ensure the existence and value of $::agent_specified_environment Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6851) Update AIX config files with FQDN
Title: Message Title Stan Duffy created an issue Puppet / PUP-6851 Update AIX config files with FQDN Issue Type: Task Assignee: Stan Duffy Created: 2016/10/28 12:46 PM Environment: Puppet Agent Manual CI Pipelines Priority: Normal Reporter: Stan Duffy There are some tests that require that beaker know the FQDN of the node. Beaker can pick this up either with the node name being set to the full FQDN or using the vmhostname setting. For consistency we will add the vmhostname setting to the AIX config files Add Comment
Jira (PDB-3150) Investigate and estimate solutions to the "big structure fact" problem
Title: Message Title
Wyatt Alt commented on PDB-3150
Re: Investigate and estimate solutions to the "big structure fact" problem
For a little more background, suppose you're trying to store the fact
"foo": {"foo": "bar", "spam": ["eggs"]}
today.
PDB will store this as three rows in the fact_values and fact_names table.
the full structure is stored in a jsonb column and associated with the path "foo"
"bar" is stored in a text column and associated with the path "foo#~foo"
"eggs" is stored in a text column and associated with the path "foo#~spam#~0"
This means all data is stored twice, though all values (leafs and large structures) are deduplicated across nodes when dupes occur. We store the JSONB blobs because it's much cheaper to pull the full blob out of the database than to reconstitute it from the leaves. We store the leaf values in their own rows to enable type-specific comparisons. If we only stored the jsonb column there are a couple issues we'll need to figure out
doing coercions on leaf values inside a jsonb for typed comparisons will prevent indexes from being used
postgres jsonb has no equivalent to our "regex path operator", which allows you to query for stuff like "mountpoints.*.available_bytes < 100" or whatever You can index jsonb to check for key containment, so it's possible that a containment check would cut down the results enough that lack of an index on the leaf wouldn't matter that much – I have no clue. I don't know how to get around the second issue.
I think the first thing I'd look into related to this would be whether we could afford to just stop deduplicating fact values altogether. This would significantly reduce the churn associated with an update to a large structured fact. We have some pretty good user data from support tickets that could inform that analysis.
Jira (PDB-3149) Update command :discards metric, assuming it's still desired
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3149 Update command :discards metric, assuming it's still desired Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3150) Investigate and estimate solutions to the "big structure fact" problem
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-3150 Investigate and estimate solutions to the "big structure fact" problem Change By: Karen Van der Veer Sprint: SE 2016-11-30 Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2631) PDB is incapable of efficiently storing large dynamic structured facter facts
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-2631 PDB is incapable of efficiently storing large dynamic structured facter facts Change By: Karen Van der Veer Sprint: SE Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3150) Investigate and estimate solutions to the "big structure fact" problem
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-3150 Investigate and estimate solutions to the "big structure fact" problem Change By: Karen Van der Veer Sprint: SE 2016-11- 16 30 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3150) Investigate and estimate solutions to the "big structure fact" problem
Title: Message Title Ryan Senior created an issue PuppetDB / PDB-3150 Investigate and estimate solutions to the "big structure fact" problem Issue Type: Task Assignee: Unassigned Created: 2016/10/28 11:00 AM Priority: Normal Reporter: Ryan Senior Before we decide whether we want to invest in "the real fix" for the big structured fact problem discussed in PDB-2631, we need to understand the rough size of potential fixes. The goal of this ticket is to give Deepak Giridharagopal and Alexander Johnson some options with rough estimates, so a decision can be made. Talking with Alexander Johnson, it is not acceptable to drop the large facts. So given that we need to store them, we need to look into our options. One solution could be to put them in a JSONB column, that would have one set of implications. Another would be to find a better way to fit it in our current setup. Nick Walker has some background in this and would be a good resource to bounce potential solutions off of. Ken Barber and Wyatt Alt are good resources for how facts are stored today. Add Comment
Jira (FACT-1528) Custom Ruby facts with additional resolutions instead replace core facts
Title: Message Title Michael Smith updated an issue Facter / FACT-1528 Custom Ruby facts with additional resolutions instead replace core facts Change By: Michael Smith Sprint: Facter Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1528) Custom Ruby facts with additional resolutions instead replace core facts
Title: Message Title Michael Smith updated an issue Facter / FACT-1528 Custom Ruby facts with additional resolutions instead replace core facts Change By: Michael Smith Labels: maintenance Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6846) Obscure error messages caused by error in metadata.json of a module.
Title: Message Title Michael Smith updated an issue Puppet / PUP-6846 Obscure error messages caused by error in metadata.json of a module. Change By: Michael Smith Sprint: Bug Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6846) Obscure error messages caused by error in metadata.json of a module.
Title: Message Title Michael Smith updated an issue Puppet / PUP-6846 Obscure error messages caused by error in metadata.json of a module. Change By: Michael Smith Labels: maintenance metadata module Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1271) puppet ca list --all fails with "Error: The certificate retrieved from the master does not match the agent's private key."
Title: Message Title Steve Snodgrass commented on PUP-1271 Re: puppet ca list --all fails with "Error: The certificate retrieved from the master does not match the agent's private key." I have this issue with puppet 3.7.5 running on RHEL6. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6789) Prefer but don't require capabilities matching the node environment
Title: Message Title Zach Reichert commented on PUP-6789 Re: Prefer but don't require capabilities matching the node environment Kenn Hussey Susan McNerney I don't think I will have bandwidth to author the automation this sprint. After talking with Alex Dreyer the cases do seem straight forward. I have documented the case in TestRail and created https://tickets.puppetlabs.com/browse/ORCH-1561 to track the automation of this acceptance test. I'll be able to commit to this work in the next Foundational Features sprint. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1413) External facts do not override custom Ruby facts that have confines or a non-default weight
Title: Message Title Michael Smith updated an issue Facter / FACT-1413 External facts do not override custom Ruby facts that have confines or a non-default weight Change By: Michael Smith Fix Version/s: FACT 3.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1482) mountpoints fact does not show mounts on tmpfs
Title: Message Title Michael Smith updated an issue Facter / FACT-1482 mountpoints fact does not show mounts on tmpfs Change By: Michael Smith Fix Version/s: FACT 3.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1527) os release fact doesn't work correctly on Gentoo
Title: Message Title Michael Smith updated an issue Facter / FACT-1527 os release fact doesn't work correctly on Gentoo Change By: Michael Smith Release Notes Summary: Previously the Gentoo os::release fact was incorrectly reporting kernel version. Switch to reporting the release version from /etc/gentoo-release. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1527) os release fact doesn't work correctly on Gentoo
Title: Message Title Michael Smith updated an issue Facter / FACT-1527 os release fact doesn't work correctly on Gentoo Change By: Michael Smith Fix Version/s: FACT 3.6.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2631) PDB is incapable of efficiently storing large dynamic structured facter facts
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-2631 PDB is incapable of efficiently storing large dynamic structured facter facts Change By: Karen Van der Veer Sprint: Server Maint - Next Up SE Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6850) Make commit formatting check robust
Title: Message Title Moses Mendoza commented on PUP-6850 Re: Make commit formatting check robust Shawn Ferry seems reasonable - i'm not as familiar with that behavior - I'll take a look. Generally speaking I think I'm inclined to avoid having something in there we know doesn't work well rather than keep it and possibly mask the failures, but I'm happy with whatever cuts down on the noise in the short term. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1527) os release fact doesn't work correctly on Gentoo
Title: Message Title Alexander Olofsson commented on FACT-1527 Re: os release fact doesn't work correctly on Gentoo Pull request is up at https://github.com/puppetlabs/facter/pull/1462 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1528) Custom Ruby facts with additional resolutions instead replace core facts
Title: Message Title Michael Smith updated an issue Facter / FACT-1528 Custom Ruby facts with additional resolutions instead replace core facts Change By: Michael Smith Summary: Custom Ruby facts with additional resolutions instead replace core facts Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1527) os release fact doesn't work correctly on Gentoo
Title: Message Title Alexander Olofsson assigned an issue to Unassigned Facter / FACT-1527 os release fact doesn't work correctly on Gentoo Change By: Alexander Olofsson Assignee: Alexander Olofsson Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1527) os release fact doesn't work correctly on Gentoo
Title: Message Title Alexander Olofsson assigned an issue to Alexander Olofsson Facter / FACT-1527 os release fact doesn't work correctly on Gentoo Change By: Alexander Olofsson Assignee: Alexander Olofsson Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1528) Custom Ruby facts replace core facts
Title: Message Title Alexander Olofsson commented on FACT-1528 Re: Custom Ruby facts replace core facts Here's an example from a Puppet 3 / Facter 2.4.6 client; $ cat /var/lib/puppet/lib/facter/hostname.rb Facter.add(:hostname) do confine fqdn: 'not-a-server' has_weight 100 setcode do 'NotGoingToHappen' end end $ facter hostname jenkins
Jira (PUP-6850) Make commit formatting check robust
Title: Message Title Shawn Ferry commented on PUP-6850 Re: Make commit formatting check robust Moses Mendoza Allow the commits check to fail without breaking everything? It's not optimal but maybe it's a bit better than removing it entirely. .travis.yaml: matrix: allow_failures: env: "CHECK=commits" Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3042) If a catalog has a dependency cycle, it does not count as failed
Title: Message Title Verne Lindner commented on PUP-3042 Re: If a catalog has a dependency cycle, it does not count as failed Steve Quin Scott Walker Can we create a ticket for our team to address the reporting issue? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6850) Make commit formatting check robust
Title: Message Title Moses Mendoza created an issue Puppet / PUP-6850 Make commit formatting check robust Issue Type: Bug Assignee: Unassigned Created: 2016/10/28 9:50 AM Labels: maintenance Priority: Normal Reporter: Moses Mendoza PUP-6849 proposes removal of the commit format check, as it is failing consistently on PRs due to commits unrelated to those PRs. Unfortunately, despite a range of attempts to make this work correctly/completely, including: e1efdebf 4d5afd57 1ed7c7ce ...we still haven't gotten it quite right. The most challenging aspect is to accurately get a list of commits that exist only in the pull request and check those. Failure to do so was causing consistent CI failures for many PRs, as commits unrelated to this PR would trigger failure. This then meant lost time investigating and spurious red in hipchat rooms - more effort than the check is worth in IMO. We need to make the check more robust so that it can correctly detect only the commits in a PR.
Jira (PUP-6849) Remove "commit" check task from travis ci
Title: Message Title Moses Mendoza created an issue Puppet / PUP-6849 Remove "commit" check task from travis ci Issue Type: Bug Assignee: Unassigned Created: 2016/10/28 9:37 AM Labels: maintenance Priority: Normal Reporter: Moses Mendoza CI now routinely fails against pull requests, because we haven't figured out a fully accurate way to only get the commit listing in a PR and check the commit format. Strictly speaking, having this check hasn't prevented commits that are incorrectly formatted from being added to the repo anyway, ie: 6e79498 Delete file commited to wrong repo 80af5ac ;lkajsd 35dd8ef Update MAINTAINERS
Jira (FACT-1528) Custom Ruby facts replace core facts
Title: Message Title Michael Smith commented on FACT-1528 Re: Custom Ruby facts replace core facts This might be expected behavior, but I've heard of requests for something like this before. Just to check, does Facter 2 behave differently? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1527) os release fact doesn't work correctly on Gentoo
Title: Message Title Michael Smith commented on FACT-1527 Re: os release fact doesn't work correctly on Gentoo Thanks for filing this! The current code doesn't appear to try to read the Gentoo release file. A pr fixing that would be welcome. It would probably belong somewhere in https://github.com/puppetlabs/facter/blob/3.5.0/lib/src/facts/linux/os_linux.cc#L250. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1527) os release fact doesn't work correctly on Gentoo
Title: Message Title Michael Smith updated an issue Facter / FACT-1527 os release fact doesn't work correctly on Gentoo Change By: Michael Smith Labels: maintenance Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1452) facter 3.1.7/3.1.8 releases on github are versioned as 3.2.0
Title: Message Title Clay Caviness commented on FACT-1452 Re: facter 3.1.7/3.1.8 releases on github are versioned as 3.2.0 Ah, this is https://tickets.puppetlabs.com/browse/FACT-1425 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6803) puppet run status should be "failed" if there are failed generated resources
Title: Message Title Moses Mendoza commented on PUP-6803 Re: puppet run status should be "failed" if there are failed generated resources Geoff Nichols yes - added. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6803) puppet run status should be "failed" if there are failed generated resources
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6803 puppet run status should be "failed" if there are failed generated resources Change By: Moses Mendoza Release Notes Summary: Some puppet types (notably "file" and "user") are capable of "generating" resources. For example, a managed directory file resource with `recurse => true` will "generate" resources of any subdirectories/files in that directory so that Puppet can apply management to them.Prior to this bug fix, if for some reason Puppet encountered an exception/issue while "generating" these resources (ie, if an unmanageable file such as a socket exists in a managed directory with recurse => true), this failure would be logged in the run report, but run report's overall status would still be considered successful (ie, a status of either `changed` or `unchanged`).In Puppet 4.8.0 and later, if Puppet fails to generate resources for any managed resource, this will result in a report status of `failed`. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6803) puppet run status should be "failed" if there are failed generated resources
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6803 puppet run status should be "failed" if there are failed generated resources Change By: Moses Mendoza Affects Version/s: PUP 3.8.7 Affects Version/s: PUP 4.6.2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3107) new-command-schema validation prevents PDB/NewRelic integration
Title: Message Title Susan McNerney commented on PDB-3107 Re: new-command-schema validation prevents PDB/NewRelic integration Ryan Senior I was looking at the note above where he said it required a PE release; I misinterpreted that to me it was a pe only thing. You are correct, Everett is out of the question at this point. So your options are: 2016.4.2 in Feb to get into the LTS, if it is in fact a critical bug. Flanders (Feb/March, dates are still finalizing). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6848) Throw a warning when fileserver can't read directory
Title: Message Title Tim Purkerson created an issue Puppet / PUP-6848 Throw a warning when fileserver can't read directory Issue Type: Improvement Affects Versions: PUP 4.5.2 Assignee: Unassigned Created: 2016/10/28 8:14 AM Priority: Normal Reporter: Tim Purkerson We use the Puppet fileserver to recursively manage a directory of node certificates for specific nodes. Our fileserver configuration looks like this: [SSL] path /data/SSL/certs/%H allow * We just run into an issue where the subdirectories of /data/SSL/certs were mistakenly chowned to root:root, meaning that the puppetserver couldn't read or traverse them anymore. Rather than throwing a warning, the Puppet run exits cleanly ignoring the directory silently. I'd like to make a feature request: make it possible to throw a warning if the directory the fileserver should be serving does exist but isn't readable by the fileserver. Currently, the fileserver will only warn you (error out, actually) if the directory it needs to serve doesn't exist.
Jira (PDB-3149) Update command :discards metric, assuming it's still desired
Title: Message Title Rob Browning created an issue PuppetDB / PDB-3149 Update command :discards metric, assuming it's still desired Issue Type: Bug Assignee: Unassigned Created: 2016/10/28 8:02 AM Priority: Normal Reporter: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-3042) If a catalog has a dependency cycle, it does not count as failed
Title: Message Title Scott Walker commented on PUP-3042 Re: If a catalog has a dependency cycle, it does not count as failed The root cause of PE-17901 is PUP-6803 . It's hard to be sure but that seems like a distinct issue to me. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5777) Whits don't copy tags from the containers they replace
Title: Message Title Laletin Michael commented on PUP-5777 Re: Whits don't copy tags from the containers they replace The case is still reproducible in puppet 4.7 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3107) new-command-schema validation prevents PDB/NewRelic integration
Title: Message Title Ryan Senior commented on PDB-3107 Re: new-command-schema validation prevents PDB/NewRelic integration If you feel Everett is ok, then they just need to get the bug into a PE build by the Everett deadline, which is Nov 2. The PuppetDB release for Everett is PDB 4.2.4 which was released yesterday. We were told the Everett deadline for PDB was 10/21 by the Everett release team. We weren't able to make that date, so we shipped yesterday. Has there been more changes to the Z release policy? This doesn't appear to meet our criteria for a Z release. PuppetDB 4.3.0 only uses ActiveMQ to migrate from older PDB to the new version. Since it's not using ActiveMQ, it wouldn't have this problem. We are currently targeting a FOSS release for 4.3.0 next week. We are hoping to ship that change with Flanders. /cc Karen Van der Veer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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 https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1528) Custom Ruby facts replace core facts
Title: Message Title Alexander Olofsson created an issue Facter / FACT-1528 Custom Ruby facts replace core facts Issue Type: Bug Affects Versions: FACT 3.4.1, FACT 3.3.0 Assignee: Unassigned Created: 2016/10/28 3:29 AM Priority: Major Reporter: Alexander Olofsson It seems that any facts that try to add additional resolutions to core facts are instead completely replacing said core facts. $ facter hostname Computer $ cat /opt/puppetlabs/puppet/cache/lib/facter/testfact.rb
Jira (FACT-1527) os release fact doesn't work correctly on Gentoo
Title: Message Title
Alexander Olofsson created an issue
Facter / FACT-1527
os release fact doesn't work correctly on Gentoo
Issue Type:
Bug
Affects Versions:
FACT 3.3.0, FACT 3.1.8
Assignee:
Unassigned
Created:
2016/10/28 1:19 AM
Priority:
Normal
Reporter:
Alexander Olofsson
It seems that Facter doesn't read the gentoo-release file correctly, instead providing the kernel version as os release data.
$ facter os
{
architecture => "amd64",
