You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During testing of Release 2.3 we found that if we have change IP function called before updating admin, after update we will have error in admin related to 'getLastChangeIpTime' was not found in this contract's abi. This was done before skale-manager contracts update to 1.10.0-beta.0. Skaled containers is not starting during this error.
Admin should have fallback mechanism to use old algorithm of dealing with change IP procedure.
'getLastChangeIpTime' was not found in this contract's abi.", ' Are you sure you provided the correct contract abi?')
Traceback (most recent call last):
File "/usr/src/admin/core/schains/task.py", line 24, in run
self.action()
File "/usr/src/admin/core/schains/monitor/main.py", line 81, in run_config_pipeline
current_nodes = get_current_nodes(skale, name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/admin/core/node.py", line 387, in get_current_nodes
node['ip_change_ts'] = skale.nodes.get_last_change_ip_time(node['id'])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/skale/contracts/manager/nodes.py", line 140, in get_last_change_ip_time
return self.contract.functions.getLastChangeIpTime(node_id).call()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/web3/contract/contract.py", line 419, in __getattr__
raise ABIFunctionNotFound(
web3.exceptions.ABIFunctionNotFound: ("The function 'getLastChangeIpTime' was not found in this contract's abi.", ' Are you sure you provided the correct contract abi?')
During testing of Release 2.3 we found that if we have
change IP
function called before updating admin, after update we will have error in admin related to'getLastChangeIpTime' was not found in this contract's abi
. This was done beforeskale-manager
contracts update to1.10.0-beta.0
. Skaled containers is not starting during this error.Admin should have fallback mechanism to use old algorithm of dealing with change IP procedure.
Versions:
admin: 2.6.0-beta.0
skale-manager: 1.9.4-stable.0
Short log:
Detailed log
The text was updated successfully, but these errors were encountered: