On 15/06/12 16:20, Neil Watson wrote: > This is slightly similar to a bug I saw when using IPV6. The trouble > for me was skipidentify. If you have skipidentify => "true"; somewhere > in your policy try removing it.
It's set to true, in fact. One clarification though: are you suggesting to remove/comment out the directive, or to set it to false? >> cf3> -> !! Package "puppet" cannot be verified -- no match >> cf3> -> !! Package "puppetmaster" cannot be verified -- no match >> cf3> -> !! Package "puppet-common" cannot be verified -- no match >> cf3> -> R: puppet is NOT installed >> cf3> -> R: puppetmaster is NOT installed >> cf3> -> R: puppet-common is NOT installed > > I'd like to know the story of the above output. Eheh :-D When I'll put these policies in production, they'll have the grateful task to kick out the puppet installation currently running on them, and replace it with cfengine. That output is part of the kick-out procedure: if puppet is installed, the /var/lib/puppet/state/puppetdlock is created so that puppet doesn't run any more. And if a certain class is defined, puppet packages are removed. And I'll be able to drive the process remotely using cf-runagent. Sweet, isn't it? I am looking forward so much to that moment :) Ciao -- bronto _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
