Neil & All, Nope should be still be db4. I have not changed anything actually just took the source and updated my spec then built. So unless a default has changed no db changes.
So part of my update reroute is to just remove this key. At this point migration is going well have about 25 machines working on but need to touch my configs to make sure they are clean as the parser is catching more missing components like my version in some cases. I have seen another issue which could be related or not: I have grown these configs over the past 12+ months from the getting started guide. I use a large "main" bundle. In main I have a files promise for my test repo to get brought down. I noticed its not being touched. Ideally was going bridge the old package to the new one while troubleshooting and migration so not to interrupt tier one servers till they are scheduled. Anyhow the promise is not being seen in with verbose or debug 1 or debug 2. Currently pushing on debug 2 for output. Are there known issues around 3.1.2 with this? My update bundle works fine just my main has issues. Does not look like the variable expansion issue. I will keep plugging but though I would ask. Also on the discussion on how to better catalog templates, bundles, promises has there been thoughts to have a know issues section -- wiki like which ties to the bug reports? Regards -G On Wed, Jan 12, 2011 at 10:16 AM, <no-re...@cfengine.com> wrote: > Forum: Cfengine Help > Subject: Re: 3.0.5 -> 3.1.2 key issue? > Author: neilhwatson > Link to topic: https://cfengine.com/forum/read.php?3,20067,20089#msg-20089 > > Long shot follows. Have you changed back end databases? For example gone > from BDB to Tokyocabinet? > > _______________________________________________ > Help-cfengine mailing list > Help-cfengine@cfengine.org > https://cfengine.org/mailman/listinfo/help-cfengine > _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
