We upgraded 6.3 to SP 3.3.2. We have a custom rollout configuration that worked just fine in 6.3.1. Since moving to 3.3.2 we noticed that the rollout configs were not being inherited from their masters even though everything looked correct. I doubled back through the .msm. selector and couldn't find the issue - it was defaulting to no rollout configurations not being found so using just the default... by default.
If I replaced the msm-core from 6.3.1 and used it in 188.8.131.52, things went back to working. I noticed a new CF on May 9th that looked like it might be handling this issue. However, after installing it, it still does not behave correctly.