节点第一次启动的时候报错；需要重启；image: eosiosg/dpos-pbft:bos-v0.9.9.2-Release

[zsq978663747]

场景：
节点从2.0.3版本启动，运行一段时间后，升级一半节点；升级系统合约，设置快高度升级；
在升级的过程中，用新的版本升级剩余的节点，发现报如下错误，重启后节点正常。

报错信息：

unknown key (chainbase::oid<eosio::chain::upgrade_property_object>): 0:
2019-06-01T03:27:35.117410137Z     {"what":"unknown key (chainbase::oid<eosio::chain::upgrade_property_object>): 0"}
2019-06-01T03:27:35.117413687Z     thread-0  controller.cpp:1558 apply_block
2019-06-01T03:27:35.117416623Z rethrow2019-06-01T03:27:35.117419521Z     {}
2019-06-01T03:27:35.117422481Z     thread-0  controller.cpp:1605 push_block
2019-06-01T03:27:36.067354160Z info  
2019-06-01T03:27:36.067 thread-0  net_plugin.cpp:1714           verify_catchup       ] got a catch_up notice while in in sync, fork head num = 4323 target LIB = 3943 next_expected = 1
2019-06-01T03:27:36.741107055Z warn  
2019-06-01T03:27:36.740 thread-0  controller.cpp:1605           push_block           ] 13 St9exception: unknown key (chainbase::oid<eosio::chain::upgrade_property_object>): 0
2019-06-01T03:27:36.741142411Z unknown key (chainbase::oid<eosio::chain::upgrade_property_object>): 0:
2019-06-01T03:27:36.741146029Z     {"what":"unknown key (chainbase::oid<eosio::chain::upgrade_property_object>): 0"}2019-06-01T03:27:36.741149035Z     thread-0  controller.cpp:1558 apply_block
2019-06-01T03:27:36.741153139Z error 2019-06-01T03:27:36.741 thread-0  producer_plugin.cpp:328       on_incoming_block    ] 13 St9exception: unknown key (chainbase::oid<eosio::chain::upgrade_property_object>): 0
2019-06-01T03:27:36.741157513Z unknown key (chainbase::oid<eosio::chain::upgrade_property_object>): 0:
2019-06-01T03:27:36.741160810Z     {"what":"unknown key (chainbase::oid<eosio::chain::upgrade_property_object>): 0"}2019-06-01T03:27:36.741165090Z     thread-0  controller.cpp:1558 apply_block
2019-06-01T03:27:36.741167544Z rethrow2019-06-01T03:27:36.741169824Z     {}
2019-06-01T03:27:36.741171971Z     thread-0  controller.cpp:1605 push_block

[oldcold]

Anlysis:
BP nodes with v2.0.3 continue producing after disconnection with other upgraded nodes, upo object together with the db was popped during the initial fork switch upon the first-time restart.

Workaround:
Check upo existence every time when trying to fetch upgrade status - ref tag bos-v0.9.10

[Frank-AFN]

当把至少2/3N+1个bp node 升级到pbft后. 没有升级的bp node 会继续produce block. 升级这些bp node后, 这些bp会pop出所有不能共识块, 并且undo升级过程中chainbase_db操作, upgrade_property_object在这些bp刚启动的head block创建并写入到chainbase_db, 由于切换分叉导致的 undo 操作, 导致在chainbase_db中找不到 upgrade_property_object.

Solution:
try to get the upgrade_property_obejct, It will be created when came across the exception. - ref tag bos-v0.9.10

[zsq978663747]

bos-v0.9.10经确认，这个版本已经解决