Neil,
This is the same issue I had with my updates a few weeks back. I used
a tidy promise on the root-.pub file to clean it up which is a mess
but at least it gets past the constant failure for updates.
I slipped this into the update bundle and it at least takes care of
the key but I am not sure when the root-.pub is created, so it could
creep back in.
"$(sys.workdir)/ppkeys/root-.pub"
comment => "Clean up the bad ppkey",
handle => "ppkey_garbage",
delete => tidy,
classes => update_repaired("garbage_ppkey");
I would strongly suggest that you test your configs on the 3.1.4 and
pursue the update to that release. After 40 of 200 machines I waited
as this bug was something I did not wanted to live with.
All the best
Gusto
On Tue, Feb 1, 2011 at 1:51 PM, <[email protected]> wrote:
> Forum: Cfengine Help
> Subject: Upgrade 3.0.2 to 3.1.2 pains
> Author: neilhwatson
> Link to topic: https://cfengine.com/forum/read.php?3,20386,20386#msg-20386
>
> Getting this problem with more than a few hosts.
>
> cf3 -> Connect to configa01.example.com = 10.249.249.2 on port 5308
> cf3 -> Did not find new key format /var/cfengine/ppkeys/root-.pub
> cf3 -> Trying old style /var/cfengine/ppkeys/root-10.249.249.2.pub
> cf3 BAD: key could not be accepted on trust
>
>
> Even a two way trust does not work.
>
> Beware for others upgrading. Be sure to check that your newer cfengine std
> lib works with the older version. It's possible that they will coexist
> during the upgrade and newer syntax might through an error on the older
> cf-promises.
>
> _______________________________________________
> Help-cfengine mailing list
> [email protected]
> https://cfengine.org/mailman/listinfo/help-cfengine
>
_______________________________________________
Help-cfengine mailing list
[email protected]
https://cfengine.org/mailman/listinfo/help-cfengine
