Jira (PUP-1606) Virtual classes are always realized
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1606 Virtual classes are always realized Change By: Henrik Lindberg Fix Version/s: PUP 4.10.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 (PUP-1606) Virtual classes are always realized
Title: Message Title Henrik Lindberg commented on PUP-1606 Re: Virtual classes are always realized Since there has been no new information on this since february 2016 and given that puppet has not supported virtual classes in its modern history (from 3.0.0 forwards), the right solution is to officially deprecate it, and make it an error in Puppet 6.0.0 (where the intent is to remove virtual resource all together). Suggest we implement this as an error if --strict is error and a warning otherwise, and that we update documentation. 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-1606) Virtual classes are always realized
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1606 Virtual classes are always realized Change By: Henrik Lindberg Component/s: Server Component/s: DSL Component/s: Language 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-1606) Virtual classes are always realized
Title: Message Title John Duarte updated an issue Puppet / PUP-1606 Virtual classes are always realized Change By: John Duarte Labels: needs_decision redmine triaged 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-1606) Virtual classes are always realized
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1606 Virtual classes are always realized Change By: Henrik Lindberg Team: Puppet Developer Support 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-1606) Virtual classes are always realized
Title: Message Title Eric Sorenson commented on PUP-1606 Re: Virtual classes are always realized So I don't understand what it means (from a semantic/intent standpoint) for a class to be virtual/realized but I've been opposed to virtual resources since 0.25 so I'm probably not the best person to decide this. So Adam T Backer can i come back to your original problem statement? I have a class that I wish to apply with a default set of parameters to all hosts, and a different set of parameters on a handful of management hosts (agents on all nodes, management bits on management nodes) and was hoping to provide it with the same class using virtualized class resources. [...] I will not entertain the idea of releasing my Nagios module in this state. I just wouldn't look to virtual resources to solve this problem; this pattern is super common and data lookups via hiera is the first-class solution, especially for published modules. If you're still involved in this issue at all, do you still think the approach you were trying should be made to work? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1606) Virtual classes are always realized
Title: Message Title Henrik Lindberg commented on PUP-1606 Re: Virtual classes are always realized Ping Eric Sorenson - this ticket has been around for a while. It needs a decision. Is it meaningful to support the concept of virtual for classes? If not then it should be an error to attempt to create one, and the documentation should state that it is no legal. If it is a valid concept then we have other work to do Since a class is not actually a resource type and we in other similar cases have turned down requests to make classes more like resources I suggest that we specify that it is illegal to specify a class as being virtual. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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-1606) Virtual classes are always realized
Title: Message Title Iain Buchanan commented on PUP-1606 Re: Virtual classes are always realized How about updating the documentation? 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 (PUP-1606) Virtual classes are always realized
Title: Message Title Henrik Lindberg commented on PUP-1606 Re: Virtual classes are always realized Verified that this still does not work on stable/master (just prior to 3.7.4/4.0.0 release). 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 (PUP-1606) Virtual classes are always realized
Title: Message Title Henrik Lindberg commented on PUP-1606 Re: Virtual classes are always realized ping Eric Sorenson what do you want to do with this issue? This feature (virtual classes) seems to have been broken a long time (since 2.6.7). IMO, it should either be accepted as a bug in a supported feature and fixed (or deprecated; in which case we want to do this asap to not having to wait until the next major release - hence this ping). 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 (PUP-1606) Virtual classes are always realized
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1606 Virtual classes are always realized Change By: Henrik Lindberg Affects Version/s: PUP2.7.25 Affects Version/s: PUP3.7.3 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 (PUP-1606) Virtual classes are always realized
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1606 Virtual classes are always realized Change By: Henrik Lindberg Scrum Team: Language 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 (PUP-1606) Virtual classes are always realized
Title: Message Title
Adam T Backer commented on an issue
Re: Virtual classes are always realized
Still present in puppet 3.4.3. I have a class that I wish to apply with a default set of parameters to all hosts, and a different set of parameters on a handful of management hosts (agents on all nodes, management bits on management nodes) and was hoping to provide it with the same class using virtualized class resources.
2 years and almost one full major version seem like a long time to be ignoring a regression of a core feature (virtualized resources). Should I expect this behavior to return at any point or begin architecting around this behavior as if it were now the intended functionality? Are there major obstacles (like large refactors that have happened since this was functional) to fix this regression?
Cheers,
abacker@mgt105:~$ puppet --version
3.4.3
abacker@mgt105:~$ vim iclass.pp
abacker@mgt105:~$ puppet apply --debug iclass.pp
Notice: Compiled catalog for mgt105 in environment production in 0.02 seconds
Debug: Creating default schedules
Debug: Failed to load library 'selinux' for feature 'selinux'
Debug: Using settings: adding file resource 'confdir': 'File[/home/abacker/.puppet]{:path=/home/abacker/.puppet, :ensure=:directory, :loglevel=:debug, :links=:follow, :backup=false}'
Jira (PUP-1606) Virtual classes are always realized
Title: Message Title Andy Parker updated an issue Puppet / PUP-1606 Virtual classes are always realized Change By: Andy Parker Component/s: DSL Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-1606) Virtual classes are always realized
Title: Message Title
Adam T Backer commented on an issue
Re: Virtual classes are always realized
I've created a workaround using this pattern, but it obviously has a required level of maintenance on the defined type that is undesirable. This will work in the interim, but I will not entertain the idea of releasing my Nagios module in this state.
Cheers,
1 class vclass ($var1 = 'blah', $var2 = 'blerf') {
2 notify {vclass:
3 message = I've been realized as ${title}: var1 = ${var1} - var2 = ${var2}
4 }
5 }
6
7 class iclass {
8 define idef (
9 $var1 = 'true',
10 $var2 = 'false') {
Jira (PUP-1606) Virtual classes are always realized
Title: Message Title
Adam T Backer commented on an issue
Re: Virtual classes are always realized
oh, for posterity's sake, the results were:
Notice: Compiled catalog for mgt105 in environment production in 0.04 seconds
Debug: Creating default schedules
Debug: Failed to load library 'selinux' for feature 'selinux'
Debug: Using settings: adding file resource 'confdir': 'File[/home/abacker/.puppet]{:path=/home/abacker/.puppet, :ensure=:directory, :loglevel=:debug, :links=:follow, :backup=false}'
Debug: Using settings: adding file resource 'vardir': 'File[/home/abacker/.puppet/var]{:path=/home/abacker/.puppet/var, :ensure=:directory, :loglevel=:debug, :links=:follow, :backup=false}'
Debug: Using settings: adding file resource 'logdir': 'File[/home/abacker/.puppet/var/log]{:path=/home/abacker/.puppet/var/log, :mode=750, :ensure=:directory, :loglevel=:debug, :links=:follow, :backup=false}'
Debug: Using settings: adding file resource 'statedir': 'File[/home/abacker/.puppet/var/state]{:path=/home/abacker/.puppet/var/state, :mode=1755, :ensure=:directory, :loglevel=:debug, :links=:follow, :backup=false}'
Debug: Using settings: adding file resource 'rundir': 'File[/home/abacker/.puppet/var/run]{:path=/home/abacker/.puppet/var/run, :mode=755, :ensure=:directory, :loglevel=:debug, :links=:follow, :backup=false}'
Jira (PUP-1606) Virtual classes are always realized
Title: Message Title
redmine.exporter created an issue
Puppet / PUP-1606
Virtual classes are always realized
Issue Type:
Bug
Assignee:
Eric Sorenson
Created:
06/Feb/14 6:38 PM
Labels:
redmine
Priority:
Normal
Reporter:
redmine.exporter
Declaring a virtual class should not instantiate it without being realized. This worked in puppet 2.6.1 but is broken in 2.6.7. I also tried it in 2.7.9 and it still seems to be broken. The code below is a very simple example. vclass and the notify should not happen because it is not realized.
pre class vclass { notify {vclass: message = I've been realized }
}
class iclass { @class {vclass: }
}
class {iclass:}
/pre
Puppet 2.7.9 output: pre puppet apply --debug iclass.pp debug: importing '/root/iclass.pp' in environment production debug: Creating default schedules debug: Failed to load library 'selinux' for feature 'selinux' debug: Failed to load library 'shadow' for feature 'libshadow' debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl does not exist debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not exist debug: Failed to load library 'ldap' for feature 'ldap' debug: Puppet::Type::User::ProviderLdap: feature ldap is missing debug: Puppet::Type::User::ProviderPw: file pw does not exist debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring File[/etc/puppet/ssl] debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring File[/etc/puppet/ssl] debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring
Jira (PUP-1606) Virtual classes are always realized
Title: Message Title
Kylo Ginsberg updated an issue
Puppet / PUP-1606
Virtual classes are always realized
Change By:
Kylo Ginsberg
Declaringavirtualclassshouldnotinstantiateitwithoutbeingrealized.Thisworkedinpuppet2.6.1butisbrokenin2.6.7.Ialsotrieditin2.7.9anditstillseemstobebroken.Thecodebelowisaverysimpleexample.vclassandthenotifyshouldnothappenbecauseitisnotrealized. pre {code} classvclass{notify{vclass:message=I'vebeenrealized}}classiclass{@class{vclass:}}class{iclass:} /pre {code} Puppet2.7.9output: pre {code} puppetapply--debugiclass.ppdebug:importing'/root/iclass.pp'inenvironmentproductiondebug:Creatingdefaultschedulesdebug:Failedtoloadlibrary'selinux'forfeature'selinux'debug:Failedtoloadlibrary'shadow'forfeature'libshadow'debug:Puppet::Type::User::ProviderDirectoryservice:file/usr/bin/dscldoesnotexistdebug:Puppet::Type::User::ProviderUser_role_add:fileroleadddoesnotexistdebug:Failedtoloadlibrary'ldap'forfeature'ldap'debug:Puppet::Type::User::ProviderLdap:featureldapismissingdebug:Puppet::Type::User::ProviderPw:filepwdoesnotexistdebug:/File[/etc/puppet/ssl/public_keys]:AutorequiringFile[/etc/puppet/ssl]debug:/File[/etc/puppet/ssl/certificate_requests]:AutorequiringFile[/etc/puppet/ssl]debug:/File[/var/lib/puppet/state/state.yaml]:AutorequiringFile[/var/lib/puppet/state]debug:/File[/var/lib/puppet/clientbucket]:AutorequiringFile[/var/lib/puppet]debug:/File[/var/lib/puppet/state/last_run_report.yaml]:AutorequiringFile[/var/lib/puppet/state]debug:/File[/var/lib/puppet/run]:AutorequiringFile[/var/lib/puppet]debug:/File[/etc/puppet/ssl/private_keys]:AutorequiringFile[/etc/puppet/ssl]debug:/File[/var/lib/puppet/state/graphs]:AutorequiringFile[/var/lib/puppet/state]debug:/File[/var/lib/puppet/client_data]:AutorequiringFile[/var/lib/puppet]debug:/File[/var/lib/puppet/log]:AutorequiringFile[/var/lib/puppet]debug:/File[/etc/puppet/ssl]:AutorequiringFile[/etc/puppet]debug:/File[/etc/puppet/ssl/private]:AutorequiringFile[/etc/puppet/ssl]debug:/File[/var/lib/puppet/lib]:AutorequiringFile[/var/lib/puppet]debug:/File[/var/lib/puppet/facts]:AutorequiringFile[/var/lib/puppet]debug:/File[/var/lib/puppet/state]:AutorequiringFile[/var/lib/puppet]debug:/File[/var/lib/puppet/state/last_run_summary.yaml]:AutorequiringFile[/var/lib/puppet/state]debug:/File[/var/lib/puppet/client_yaml]:AutorequiringFile[/var/lib/puppet]debug:/File[/etc/puppet/ssl/certs]:AutorequiringFile[/etc/puppet/ssl]debug:Finishingtransaction23948234472800debug:Loadedstatein0.00secondsdebug:Loadedstatein0.00secondsinfo:Applyingconfigurationversion'1327691293'debug:/Schedule[daily]:Skippingdeviceresourcesbecauserunningonahostdebug:/Schedule[monthly]:Skippingdeviceresourcesbecauserunningonahostnotice:I'vebeenrealizednotice:/Notify[vclass]/message:defined'message'as'I'vebeenrealized'debug:/Schedule[hourly]:Skippingdeviceresourcesbecauserunningonahostdebug:/Schedule[never]:Skippingdeviceresourcesbecauserunningonahostdebug:/Schedule[weekly]:Skippingdeviceresourcesbecauserunningonahostdebug:/Schedule[puppet]:Skippingdeviceresourcesbecauserunningonahostdebug:Finishingtransaction23948233321400debug:Storingstatedebug:Storedstatein0.00secondsnotice:Finishedcatalogrunin0.03secondsdebug:Finishingtransaction23948233059620 /pre {code} Puppet2.6.1: pre {code}
