At first I upgrade from 20.3.5 to 20.6.3 and the error happened. I think it might be the bug of 20.6 then I continue to upgrade to 20.8.1, the error is still happened. I dont know if it is because the version of vManage or sth else
Hi , 20.6.3 got some bug where we were facing issue too. Raise a TAC case and they can provide u a temporary patch which will fix your issue. We have testing this today with the support of TAC engineer. Cisco is yet to release new version 18.104.22.168 probably by end of this month.