On 10/13/2012 11:17 PM, Stefan Schulte wrote: > If puppet has to sync ensure it will not sync any other property. That > means if your type defines "ensurable" or you have defined an ensure > property manually and your system is not yet present, your create method > is called and puppet expects the create method to create your system with > interfaces.
My understanding of the problem was along those lines too. Now I have confirmation... > Otherwise you will see the described behaviour: > > 1) First run: Puppet finds out ensure is out of sync (is absent, should > be present) and calls create > 2) Second run: Puppet finds out interfaces is out of sync and and calls > interfaces= (or whatever method you have defined for that) I am already detecting in my create method if 'system' is added to 'cobbler' (if it's present on the machine agent is running on), and if it is, I choose to edit it rather then to try to create it again. So, can I just call method "interface=", if I detect I have to create the 'system', or is there any way to solve this issue? Problem is that cobbler is used for provisioning (PXE+installation), so when you add new 'system' to cobbler, you are going to try to install the machine immediately afterwards (in 99% of cases), so two puppet runs in this case really stand in the way of usability of the whole idea of puppetizing Cobbler setup. So I would love to circumvent it somehow if possible. Thank you -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
