When upgrading to 11, I get "The configuration has not yet loaded" error

We found a number of issues that can cause the config not to migrate successfully from v10 (I'm also on 10.2.2) to v11. Hopefully this may again help someone else!

 

 

The issue you encountered is apparently caused by a change in the route domain configuration syntax - from "parent id" to "parent name". You might want to check you re-add the parent configuration to your route domain after the upgrade as simply removing it and loading means it will no longer have a parent set.

 

 

Other changes I am aware of from my upgrade to be wary of:

 

- If you refer to virtuals in iRules, instead of referring simply to the virtual name (e.g. Virtual1), you now need to change the iRule to refer to the partition as well as the virtual name i.e. /partitionname/Virtual1

 

- Logging behaviour has changed - so it no longer automatically logs APM session logs into syslog (now goes into a MySQL database). So if you refer to or use the /var/log/apm file at all you need to re-enable this using the command

 

tmsh modify sys db log.access.syslog enable

 

- If you did advanced customisation using advCustHelp to manually modify the inc files they are not moved over in the migration. Those customisations done in the Admin GUI are carried over.

 

 

I also got another weird error when I upgraded, after running the bigpipe daol command, not sure why, which was in the format of:

 

 

01070712:3: Caught configuration exception (0), Failed: name(/Common/ca-bundle.crt.preremoval) No copy in trash-bin to restore from. - sys/validation/FileObject.cpp, line 2899.

 

 

This was one error, there were a couple of different files with the same error - all seemed to refer to *.crt certificate files though.

 

I was able to get around this by copying the object to where it needed to be and then rerunning the bigpipe daol:

 

 

cp -pi /config/ssl/ssl.crt/ca-bundle.crt.preremoval /config/filestore/.file_object_upgrade_staging/

 

 

All the best!

 

Evan