ERROR args count differs from table column count in BuildDMLInsertQuery

After cut-over i get the error information `ERROR args count differs from table column count in BuildDMLInsertQuery` ,Is there any logical problems?

```2017-07-06 22:06:25 INFO Setting RENAME timeout as 3 seconds
2017-07-06 22:06:25 INFO Session renaming tables is 2696573
2017-07-06 22:06:25 INFO Issuing and expecting this to block: rename /* gh-ost */ table `ghostdb`.`test100g` to `ghostdb`.`_test100g_del`, `ghostdb`.`_test100g_gho` to `ghostdb`.`test100g`
2017-07-06 22:06:25 INFO Found atomic RENAME to be blocking, as expected. Double checking the lock is still in place (though I don't strictly have to)
2017-07-06 22:06:25 INFO Checking session lock: gh-ost.2696669.lock
2017-07-06 22:06:25 INFO Connection holding lock on original table still exists
2017-07-06 22:06:25 INFO Will now proceed to drop magic table and unlock tables
2017-07-06 22:06:25 INFO Dropping magic cut-over table
**2017-07-06 22:06:25 INFO Releasing lock from `ghostdb`.`test100g`, `ghostdb`.`_test100g_del`
2017-07-06 22:06:25 INFO Tables unlocked
2017-07-06 22:06:25 INFO Tables renamed**
2017-07-06 22:06:25 INFO Lock & rename duration: 1.082587024s. During this time, queries on `test100g` were blocked
2017-07-06 22:06:25 INFO Looking for magic cut-over table
**2017-07-06 22:06:26 ERROR args count differs from table column count in BuildDMLInsertQuery
2017-07-06 22:06:27 ERROR args count differs from table column count in BuildDMLInsertQuery
2017-07-06 22:06:28 ERROR args count differs from table column count in BuildDMLInsertQuery
2017-07-06 22:06:29 ERROR args count differs from table column count in BuildDMLInsertQuery**
2017-07-06 22:06:29 INFO Closed streamer connection. err=
2017-07-06 22:06:29 INFO Droppping table `ghostdb`.`_test100g_ghc`
2017-07-06 22:06:29 INFO Table dropped
2017-07-06 22:06:29 INFO Am not dropping old table because I want this operation to be as live as possible. If you insist I should do it, please add `--ok-to-drop-table` next time. But I prefer you do not. To drop the old table, issue:
2017-07-06 22:06:29 INFO -- drop table `ghostdb`.`_test100g_del`
2017-07-06 22:06:29 INFO executing gh-ost-on-success hook: /tmp/gh-ost-on-success.hook

2017-07-06 22:06:29 INFO Done migrating `ghostdb`.`test100g`
2017-07-06 22:06:29 INFO Removing socket file: /tmp/gh-ost.ghostdb.test100g.sock
# Done
```

Thank you!