Jira (BOLT-191) Ability to upload directories or recursively upload files in plans
Title: Message Title Stephen Gelman commented on BOLT-191 Re: Ability to upload directories or recursively upload files in plans I tested this and as far as I can tell there's no downside to setting ":recursive => true" on the file upload. I still need to finish up writing tests for this but would anyone object to my finishing that then PRing it? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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-7770) Pip provider cannot manage any system python packages
Title: Message Title Stephen Gelman commented on PUP-7770 Re: Pip provider cannot manage any system python packages PR submitted at https://github.com/puppetlabs/puppet/pull/6059 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-7770) Pip provider cannot manage any system python packages
Title: Message Title Stephen Gelman created an issue Puppet / PUP-7770 Pip provider cannot manage any system python packages Issue Type: Bug Assignee: Unassigned Components: Types and Providers Created: 2017/07/11 3:17 PM Priority: Normal Reporter: Stephen Gelman The pip package provider cannot manage the installation of setuptools, distribute, or wheel as they are excluded from the output of "pip freeze". What happens is that puppet tries to install them on every run because it does not know they are installed. In versions of pip newer than 8.0.3 there is an "--all" flag that can be passed to pip to list them. PR is incoming to fix this, just wanted to have a jira ticket to reference . Add Comment
Jira (PUP-4045) Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket
Title: Message Title Stephen Gelman commented on PUP-4045 Re: Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket I couldn't use ignore because it only matches the filename, not the patch and the socket was a non-unique name. I worked around it locally by adding an empty "when socket" case here: https://github.com/puppetlabs/puppet/blob/3daa532/lib/puppet/file_serving/metadata.rb#L121 I don't think this is an acceptable solution long term so I am not going to PR it but i wanted to throw it out there in case it helps someone. One solution might be to change ignore to allow it to match on a path instead of just a filename. 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-1226) puppet breaking setuid bit on group change
Title: Message Title Stephen Gelman commented on PUP-1226 Re: puppet breaking setuid bit on group change We are running into the same issue under Debian. It seems to me like this is a legitimate bug that should be fixed. Leaving the permissions incorrect until the next puppet run does not seem to be an adequate solution. 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 (HI-537) Default value doesn't work correctly with an alias
Title: Message Title Stephen Gelman commented on HI-537 Re: Default value doesn't work correctly with an alias I understand. As an aside that actually seems very useful for us and I am glad to know it is an option. Another fix I considered would be to pass the default value from lookup down into the recursive lookup. I believe that would avoid breaking automatic parameter lookup but it would require changing a number of function signatures. I know in the past that was a concern in hiera. Do you think that is a workable solution? 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 (HI-537) Default value doesn't work correctly with an alias
Title: Message Title Stephen Gelman commented on HI-537 Re: Default value doesn't work correctly with an alias Could you explain a bit more what you mean by this? An actual nil value is supported in automatic data binding with the meaning set undef. In many versions of puppet that has not been working, but it does now. I don't believe that my proposed change will affect this - if a default value is not set a `nil` will continue to be returned. This will only have an effect if the default value is set. 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 (HI-537) Default value doesn't work correctly with an alias
Title: Message Title Stephen Gelman assigned an issue to Stephen Gelman Hiera / HI-537 Default value doesn't work correctly with an alias Change By: Stephen Gelman Assignee: Stephen Gelman 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 (HI-537) Default value doesn't work correctly with an alias
Title: Message Title Stephen Gelman commented on HI-537 Re: Default value doesn't work correctly with an alias After spending a while looking at the code I believe the best solution is to check if new_answer is nil in `lookup` and treat that as not found. From what I can tell an actual nil value is unsupported in hiera so I don't believe it will cause any issues. Henrik Lindberg Does that seem like a reasonable solution to you? 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 (HI-537) Default value doesn't work correctly with an alias
Title: Message Title
Stephen Gelman created an issue
Hiera / HI-537
Default value doesn't work correctly with an alias
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/09/10 2:53 PM
Priority:
Normal
Reporter:
Stephen Gelman
When doing a hiera lookup that points to an alias that doesn't exist, one would expect to get the default value passed into the lookup. Currently, that does not happen. Instead nil is always returned. In the case of puppet this raises an error that the hiera lookup failed. I have a PR incoming to fix this - just wanted to get a ticket open to reference in the commit. An example follows.
Hiera data:
value1: "%{alias('value2')}"
Running:
$ hiera value1 defaultanswer
Jira (FACT-1480) Statically Compile Facter
Title: Message Title Stephen Gelman created an issue Facter / FACT-1480 Statically Compile Facter Issue Type: Bug Assignee: Unassigned Created: 2016/08/09 7:37 AM Environment: Debian Jessie amd64 Priority: Normal Reporter: Stephen Gelman I am looking to statically compile facter (the exact reason is a bit of a long story but I am hoping to have a binary that is portable between debian wheezy and jessie). I have been trying on Debian Jessie and have made a fair amount of progress but I still am getting some errors when linking. Is this currently doable? The cmake command I am using is: cmake -DBOOST_STATIC=ON -DYAMLCPP_STATIC=ON -DCMAKE_EXE_LINKER_FLAGS="-static -fPIC" .. Looking at the code, it does seem like a statically compiled binary is possible at least on windows. Sorry if this is not an appropriate place to ask this question - if there is a better place please let me know!
Jira (PUP-1153) Incorrect ordering of group and user resource purging
Title: Message Title Stephen Gelman commented on PUP-1153 Re: Incorrect ordering of group and user resource purging Kylo Ginsberg: We just upgraded to puppet 4.5.2 and the issue is now worse. Before, the group removal errored but the user removal succeeded so the issue went away on subsequent puppet runs. Now, the group removal failing causes cascading dependency failures and the user removal gets skipped. This means the only way we are able to remove users on the box is doing so by hand. Is it possible for this to be prioritized more now that it is a huge breaking issue for us, and presumably anyone recursively managing users and groups in debian/ubuntu? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- 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-1153) Incorrect ordering of group and user resource purging
Title: Message Title Stephen Gelman commented on PUP-1153 Re: Incorrect ordering of group and user resource purging Well it now has 2 votes. Looking at PUP-1963 my gut feeling is that it is not the issue however I am going to test out the PR. I'll report back my findings. 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-1153) Incorrect ordering of group and user resource purging
Title: Message Title Stephen Gelman commented on PUP-1153 Re: Incorrect ordering of group and user resource purging Kylo Ginsberg: this ticket has been open since 2013 and affects us daily. Any chance of it getting prioritized to be fixed? AFAIK it would affect anyone running debian or ubuntu. 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-1153) Incorrect ordering of group and user resource purging
Title: Message Title Stephen Gelman commented on PUP-1153 Re: Incorrect ordering of group and user resource purging Kylo Ginsberg: any update on this? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-1153) Incorrect ordering of group and user resource purging
Title: Message Title Stephen Gelman commented on PUP-1153 Re: Incorrect ordering of group and user resource purging Kylo Ginsberg what is the hold up on this getting fixed? It's not necessarily a breaking issue but it does consistently cause errors in our puppet runs... Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-1153) Incorrect ordering of group and user resource purging
Title: Message Title Stephen Gelman commented on PUP-1153 Re: Incorrect ordering of group and user resource purging Kylo Ginsberg, sorry, I should have given more detail. The reason it doesn't work is that the problem in puppet is different from the problem that USERGROUPS_ENAB is intended to solve. The purpose of USERGROUPS_ENAB=no is that when a user is deleted their primary group is deleted also (if it had no other members). The problem in puppet is that it tries to delete the group before the user. This fails because groupdel does not allow a user's primary group to be deleted. From its man page: You may not remove the primary group of any existing user. You must remove the user before you remove the group. I believe the solution here is that puppet should always delete users before deleting groups. I don't think it necessarily makes a difference but we are running Debian wheezy. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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-1153) Incorrect ordering of group and user resource purging
Title: Message Title Stephen Gelman commented on PUP-1153 Re: Incorrect ordering of group and user resource purging We are running into this exact problem. It seems like the status is Needs Information but I'm not sure what that information is. If someone could point me in the right direction I'd be happy to try and find the required information to get the ball rolling on fixing this. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (HI-304) Override does not work with interpolation
Title: Message Title Stephen Gelman commented on HI-304 Re: Override does not work with interpolation Is that a change you would like me to make or will you? Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- 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 (HI-304) Override does not work with interpolation
Title: Message Title Stephen Gelman created an issue Hiera / HI-304 Override does not work with interpolation Issue Type: Bug Affects Versions: HI 1.3.4 Assignee: Unassigned Created: 2014/12/16 8:24 AM Priority: Normal Reporter: Stephen Gelman According to the documentation, hiera accepts a hierarchy override. It says: Override (optional): the name of an arbitrary hierarchy level to insert at the top of the hierarchy. This lets you use a temporary modified hierarchy for a single lookup. (E.g., instead of a hierarchy of $clientcert - $osfamily - common, a lookup would use specialvalues - $clientcert - $osfamily - common; you would need to be sure to have specialvalues.yaml or whatever in your Hiera data.) This does not work with interpolation. When the variable is interpolated the original hierarchy is used. We have fixed this and will be submitting a patch but I wanted to make sure a bug was filed first.
Jira (HI-304) Override does not work with interpolation
Title: Message Title Stephen Gelman updated an issue Hiera / HI-304 Override does not work with interpolation Change By: Stephen Gelman Affects Version/s: HI1.3.0 Affects Version/s: HI1.3.1 Affects Version/s: HI1.3.2 Affects Version/s: HI1.3.3 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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 (HI-304) Override does not work with interpolation
Title: Message Title
Stephen Gelman updated an issue
Hiera / HI-304
Override does not work with interpolation
Change By:
Stephen Gelman
Accordingtothedocumentation,hieraacceptsahierarchyoverride.Itsays:{quote}Override(optional):thenameofanarbitraryhierarchyleveltoinsertatthetopofthehierarchy.Thisletsyouuseatemporarymodifiedhierarchyforasinglelookup.(E.g.,insteadofahierarchyof$clientcert-$osfamily-common,alookupwouldusespecialvalues-$clientcert-$osfamily-common;youwouldneedtobesuretohavespecialvalues.yamlorwhateverinyourHieradata.){quote}Thisdoesnotworkwithinterpolation.Whenthevariableisinterpolatedtheoriginalhierarchyisused.WehavefixedthisandwillbesubmittingapatchbutIwantedtomakesureabugwasfiledfirst. ThebuggoesbackatleastasfarasHiera1.2.1.
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
--
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 (HI-304) Override does not work with interpolation
Title: Message Title Stephen Gelman commented on HI-304 Re: Override does not work with interpolation Patch submitted and ready for review at https://github.com/puppetlabs/hiera/pull/221. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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.
