Jira (PUP-6464) Template search behavior changed from v3 to v4
Title: Message Title Henrik Lindberg commented on PUP-6464 Re: Template search behavior changed from v3 to v4 The change regarding hyphens is that "names cannot contain hyphens, irrespective of what they identify (modules, classes, variables, defines, etc.)". 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-6464) Template search behavior changed from v3 to v4
Title: Message Title R.I.Pienaar commented on PUP-6464 Re: Template search behavior changed from v3 to v4 Doc you linked to sends you to https://docs.puppet.com/puppet/latest/reference/upgrade_major_pre.html which links to a many lists of deprecated things and all the warnings you're likely to get etc. But given how massive the change set is there really is no hope for every little case to be listed. You can open a documentation bug I think as it doesnt seem to specifically call out that a module cant have a "-" in it's name, but if a class cant then its kind of obvious a module cant have either. 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-6464) Template search behavior changed from v3 to v4
Title: Message Title Brian Sipos commented on PUP-6464 Re: Template search behavior changed from v3 to v4 I understand, I had been using puppet 3.8.4 which is standard in CentOS 7 and I was not seeing any such deprecation warnings, so that did not help my confusion. As you have mentioned "the changelog", I think part of my problem was that my cursory search for 3->4 migration came up with the page I linked to, some various blog articles, but I did not come upon an official 'changelog' page for 3->4 or for 4.0 or however it would be stated. If there is such a thing, then can that document be linked-to from the upgrade guidelines? My frustration was really not being able to find "the official list" wherever that may be. This ticket can be closed, as my issue was my own misunderstanding. Hopefully this may be indexed as a help to anyone else who wound up in my same situation. 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-6464) Template search behavior changed from v3 to v4
Title: Message Title R.I.Pienaar commented on PUP-6464 Re: Template search behavior changed from v3 to v4 Glad that sorted it out - the guide you linked though is a outline of steps, the changelog for 3->4 is absolutely immense and there would be no point in trying to point out 1 or 2 issues since there are so many breaking changes However I believe puppet 3.latest would have given you a warning about this being deprecated to prepare you for 4..the pre steps in the guide you linked covers how to do that. 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-6464) Template search behavior changed from v3 to v4
Title: Message Title
Brian Sipos commented on PUP-6464
Re: Template search behavior changed from v3 to v4
Sorry to forget the actual error itself, from the agent side the error appears as:
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Evaluation Error: Error while evaluating a Function Call, Could not find template 'local-data/app/file.erb' at /etc/puppetlabs/code/environments/production/manifests/site.pp:599:16 on node {snip}
I read about dash being unavailable for class names, but I guess I did not realize also not available for module names. I did try to correct this and was able to successfully run puppet v4 on my test host. I suppose that this is more of a "get the message out" issue that I did not realize this change in module name restriction. Could the official docs at https://docs.puppet.com/puppet/latest/reference/upgrade_major_server.html be updated to somehow add a step to "Check all module names and class names conform to naming requirements described at ..." ?
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
Jira (PUP-6464) Template search behavior changed from v3 to v4
Title: Message Title R.I.Pienaar commented on PUP-6464 Re: Template search behavior changed from v3 to v4 How is it not working? What happens? One thing to note modules cannot have a "-" in their name. Might be that. 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-6464) Template search behavior changed from v3 to v4
Title: Message Title
Brian Sipos updated an issue
Puppet / PUP-6464
Template search behavior changed from v3 to v4
Change By:
Brian Sipos
I have been attempting to migrate a puppet server v3 configuration to v4 test host. I have been following the recommended steps at [https://docs.puppet.com/puppet/latest/reference/upgrade_major_server.html]. Most of the modules and classes seem to migrate okay, but I'm seeing a strange issue in the use of a templated file. I have defined a custom module which is simply a "files" and "templates" subdirectory tree, to which I reference files from my {{site.pp}} directly in the form of {{... content => template('local-data/app/file.erb') ... }}.This worked fine in v3 but appears to not work in v4. I have tried to troubleshoot how puppet is searching for template files, but I have hit a dead-end and my knowledge of Ruby is very limited. Is this kind of template use supported in v4? Defining the files from within a module and referencing them directly from {{site.pp}} rather than the module itself?
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-6464) Template search behavior changed from v3 to v4
Title: Message Title
Brian Sipos created an issue
Puppet / PUP-6464
Template search behavior changed from v3 to v4
Issue Type:
Bug
Affects Versions:
PUP 4.5.2
Assignee:
Unassigned
Components:
Puppet Server
Created:
2016/06/30 8:43 PM
Environment:
CentOS-7 x86_64
Priority:
Normal
Reporter:
Brian Sipos
I have been attempting to migrate a puppet server v3 configuration to v4 test host. I have been following the recommended steps at https://docs.puppet.com/puppet/latest/reference/upgrade_major_server.html. Most of the modules and classes seem to migrate okay, but I'm seeing a strange issue in the use of a templated file. I have defined a custom module which is simply a "files" and "templates" subdirectory tree, to which I reference files from my site.pp directly in the form of {{... content => template('local-data/app/file.erb') ... }}. This worked fine in v3 but appears to not work in v4. I have tried to troubleshoot how puppet is searching for template files, but I have hit a dead-end and my knowledge of Ruby is
