Hello,
I have also run into this issue. The problem was that the child profile was referencing the parent profile "http" which, by default, contains a width of "80". I had actually manually set the LWS width to 80 in the child profile to resolve that particular issue, but then the LTM started to complain about the parent profile "http" not being found.
The issue was that in the bigip.conf configuration file the parent profile "http" did not exist. Funny thing was that if I issued:
tmsh list ltm profile http http or tmsh list ltm profile http /Common/http
...the profile showed up. I actually had to failover the unit in standby and load the configuration again. Once I did that I was able to successfully sync the configuration since the parent profile "http" actually showed up in bigip.conf. I'm going to assume this is likely your issue as well.
I also had one other issue with the upgrade. The client SSL profiles got messed up. The LTM was complaining that it could not find the key/certificate applied to the profile. I had to delete the certificate, key and chain entries and re-apply them to the same profile. Just a heads up.