Hi, while migrating vServers from 2.1.0 to 2.2.0 I see the following assertion that seems to have been introduced between 2.1.0 and 2.2.0 trigger on the destination. This happens in a serious amount of cases. In most cases it works flawlessly on the second attempt to migrate the vServer (same source and same destination).
Any hints how to debug the root cause? Thank you, Peter