Jira (FACT-1016) Repeated resolution of a facter fact causes never GC'd object references
Title: Message Title
E Salberg commented on FACT-1016
Re: Repeated resolution of a facter fact causes never GC'd object references
I ran into this also with the tests on razorsedge/puppet-network.
RuntimeError: fact "hostname" already has the maximum number of resolutions allowed (100).
Fixed with this in the spec_helper.rb file:
RSpec.configure do |config| config.before(:all) {Facter.clear}
end
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-1519) Package resource should allow ensure=>">1.0" or ensure=>"<0.10" as well as 'latest', 'installed' and specific version number
Title: Message Title E Salberg commented on PUP-1519 Re: Package resource should allow ensure=>">1.0" or ensure=>"<0.10" as well as 'latest', 'installed' and specific version number We ran into this issue when we were upgrading Puppet agents - existing nodes were at 1.5.3, but new ones were at 1.7.1. We had to create a new classifier node group so that the upgraded nodes didn't throw "trying to downgrade but can't" errors. Truthfully, this is a bigger issue for us on Windows, where the package resource doesn't handle "latest", than on RHEL, although we could have edge cases where this would be useful on RHEL as well. Greater is most useful to us. For Less Than, I'm more likely to hardcode a specific version. So for the bullets: 1. >= or > (either would be okay) 2. Upgrade package to latest would be fine for RHEL. Not sure what would happen for Windows - could there be an optional second variable that could specify what version to upgrade it to if it doesn't match the _expression_? 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-1084) Store variables set at classification along with facts in PuppetDB
Title: Message Title E Salberg commented on PDB-1084 Re: Store variables set at classification along with facts in PuppetDB Variables can act like facts in manifests, but aren't available (as far as I know) to custom 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 (PUP-1928) Using hostname as a unique key is not sufficient for /etc/hosts management
Title: Message Title E Salberg commented on PUP-1928 Re: Using hostname as a unique key is not sufficient for /etc/hosts management We use host6 module to handle the case where we need to clean up by IP instead of hostname, so while it would be nice to have that in the product itself, it's not necessary. However, I was wondering - does closing this ticket affect what is going to be done with https://tickets.puppetlabs.com/browse/PUP-3901 ? 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-283) Improve agent error reporting
Title: Message Title E Salberg commented on PUP-283 Re: Improve agent error reporting It looks like new reporting options cover what we need - I just verified that the classification issue shows up as "intended catalog failure" (the node run still reports a green checkmark despite throwing an error, but I can live with that). We also can pull the cached catalog results from PuppetDB, so I think we're all set. I have seen the dependency report issue recently, so I'll sign on as a watcher to that ticket. 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-6637) New attribute :manage_mountpoint for Mount type
Title: Message Title E Salberg commented on PUP-6637 Re: New attribute :manage_mountpoint for Mount type Raising a request for this to be applied to PE 2016.4.x (long term support) as well, once it's approved. 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-6895) pip provider does not work with perl pip (pip.bat) installed on windows
Title: Message Title E Salberg commented on PUP-6895 Re: pip provider does not work with perl pip (pip.bat) installed on windows As someone who also reported this... The issue isn't that we need Python support on Windows (which we don't currently). It's that the pip provider overreaches on Windows and assumes that the pip associated with perl is the same as that associated with python. This completely breaks "puppet resource package" - it errors out because it tries to run "pip freeze", which obviously doesn't work. So I would actually say on windows, the description (for us) would be: "puppet resource package" does not work with perl pip (pip.bat) installed on windows I'm working with Puppet support on workarounds (although I'm assuming removing perl from the system path is out of the question), and I'll look at the pull request option - I can easily put in something for the prepend (and test it), but I'm not sure about those latest methods that are mentioned - would people over there be able to help with that? 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-283) Improve agent error reporting
Title: Message Title E Salberg commented on PUP-283 Re: Improve agent error reporting Updating here even though this may need its own ticket (I already opened a case with Support): We're also seeing the same behavior (green checkmark / no alerts in the Console or Tagmail) in cases of Classifier conflicts (e.g. one node pinned to two different node groups that set the same variables to different values - myvariable=yes and myvariable=no). The node is not using a cached catalog and the run continues, so the node doesn't even enter Unresponsive state - conflicts could just be there forever. The only indications are on the Node page and a 400 error in the Puppet run log (which doesn't alert anywhere). It definitely seems to be related to the same logging functionality, so I wanted to make sure it was a known issue before the development is over. 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.
