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
Describe the bug
In case of node rotation, reload_ts is set to None (Setting reload_ts to None) because new node comes to the group (and new node IP "change IP"). It's necessary to compare rotation ID in skaled and upstream configs, and if they are different (which means node rotation is in progress), just don't set reload_ts.
To Reproduce
Steps to reproduce the behavior:
Start node rotation procedure
Go skale_admin logs
See Setting reload_ts to None for the rotating schain
Expected behavior reload_ts is set only in case of change IP procedure.
The text was updated successfully, but these errors were encountered:
Describe the bug
In case of node rotation,
reload_ts
is set to None (Setting reload_ts to None
) because new node comes to the group (and new node IP "change IP"). It's necessary to compare rotation ID in skaled and upstream configs, and if they are different (which means node rotation is in progress), just don't setreload_ts
.To Reproduce
Steps to reproduce the behavior:
Setting reload_ts to None
for the rotating schainExpected behavior
reload_ts
is set only in case of change IP procedure.The text was updated successfully, but these errors were encountered: