MariaDB 10.2 upgrade 10.3 , Table does not exist in the InnoDB internal data dictionary?

Hi, all
Today , we upgrade MariaDB 10.2.19 to MariaDB 10.3.13,
when execute mysql_upgrade, prompt some table not exists:
12:07:57Error : Table 'db_vst.tb_notice_0' doesn't exist in engine
12:07:57status : Operation failed

after run mysql_upgrade, when open some table, prompt table 'db_vst.tb_notice_0' doesn't exist in engine.
if execue drop table db_vst.tb_notice_0 , Through prompt 'db_vst.tb_notice_0' doesn't exist in engine, but table tb_notice_0 could not seen.
if open datadir , tb_notice_0.ibd is exists and tb_notice_0.frm not exists.
after manual rm tb_notice_0.ibd , execute create table tb_notice_0,
prompt table '`db_vst`.`tb_notice_0`' already exists.

if drop database db_vst, recreate db_vst, when restore database from backup, it still prompt
table '`db_vst`.`tb_notice_0`' already exists.

before upgrade 10.3 , all tables could normal access.
please help confirm , it is mysql_upgrade quiestion or bug ? how to solve the problem ?Thanks.

in error log:
......
Version: '10.3.13-MariaDB-log' socket: '/tmp/mysql.sock' port: 3306 MariaDB Server
2019-03-21 13:03:39 0 [Note] InnoDB: Buffer pool(s) load completed at 190321 13:03:39
2019-03-21 13:16:58 254 [ERROR] InnoDB: Table `db_vst`.`tb_notice_0` does not exist in the InnoDB internal data dictionary though MariaDB is trying to drop it. Have you copied the .frm file of the table to the MariaDB database directory from another database? Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting.html for how to resolve the issue.
2019-03-21 13:26:09 254 [ERROR] InnoDB: Operating system error number 17 in a file operation.
2019-03-21 13:26:09 254 [ERROR] InnoDB: Error number 17 means 'File exists'
2019-03-21 13:26:09 254 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2019-03-21 13:26:09 254 [Note] InnoDB: The file './db_vst/tb_notice_0.ibd' already exists though the corresponding table did not exist in the InnoDB data
dictionary. You can resolve the problem by removing the file.