Bug #744
closed
problems when 1.2.x configuration conversion
0%
Description
Not sure what the problem is, I've seen different symptoms and haven't dug into it a lot. It appears no 1.2.x configuration when restored onto a 2.0 install will upgrade and function correctly. Jim and I both have configs that will replicate. A similar scenario occurs when upgrading a 1.2.3 system to 2.0, the config upgrade then doesn't appear to do anything, leaving the entire system broken with the 1.2 config as /cf/conf/config.xml.
Updated by Chris Buechler over 14 years ago
- Subject changed from problems when 1.2.x configs restored to 2.0 installs to problems when 1.2.x configuration conversion
Updated by Jim Pingle over 14 years ago
- Status changed from New to Feedback
I committed a fix to the upgrade code that should handle dnsupdate settings correctly, which is what had been causing the known-bad upgrades to fail. Somehow people who had not ever configured RFC DNS updates had settings in their configurations, and the upgrade code for those settings was broken in a way that left the configuration in its original state.
I confirmed that the fixed worked by upgrade from a previously "broken" config with a new snapshot, and it worked properly without error.
We'll need more example configurations that break in order to investigate any other upgrade issues.