Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

"Unexpected field 'storageDestructionPatchTimestamp' in config:" error after start skaled after update #1557

Closed
oleksandrSydorenkoJ opened this issue Jun 21, 2023 · 2 comments · Fixed by #1556
Closed

"Unexpected field 'storageDestructionPatchTimestamp' in config:" error after start skaled after update #1557

oleksandrSydorenkoJ opened this issue Jun 21, 2023 · 2 comments · Fixed by #1556
Assignees
@olehnikolaiev
Labels
bug Something isn't working release:2.2

Comments

@oleksandrSydorenkoJ
Copy link

Describe the bug
Schain config contains storageDestructionPatchTimestamp options, that should be read by skaled

Preconditions
Active schain medium type on 2.1.1. version skaled schain:3.16.1

Versions
schain:3.17.0-beta.1

To Reproduce

  1. Update Existing skaled from schain:3.16.1 to schain:3.17.0-beta.1
  2. Check skaled logs

Expected behavior
Skaled should be compatible with storageDestructionPatchTimestamp option in the schain config

Actual state:
Skaled crashes with the error in schain config

Logs:

2023-06-21 15:42:35.870885   /home/ubuntu/actions-runner/_work/skaled/skaled/libdevcore/JsonUtils.cpp(68): Throw in function void dev::requireJsonFields(const mObject&, const string&, const std::map<std::__cxx11::basic_string<char>, std::pair<std::set<json_spirit::Value_type>, dev::JsonFieldPresence> >&)
Dynamic exception type: boost::exception_detail::clone_impl<dev::UnknownField>
[dev::tag_comment*] = Unexpected field 'storageDestructionPatchTimestamp' in config: ChainParams::loadConfig::skaleConfig::sChain
@oleksandrSydorenkoJ oleksandrSydorenkoJ added bug Something isn't working release:2.2 labels Jun 21, 2023
@DmytroNazarenko DmytroNazarenko linked a pull request Jun 21, 2023 that will close this issue
1347 fix config validation #1556
Merged
@DmytroNazarenko DmytroNazarenko moved this to Merged To Release Candidate in SKALE Engineering 🚀 Jun 21, 2023
@DmytroNazarenko
Copy link
Collaborator

skaled: 3.17.0-beta.2

@github-project-automation github-project-automation bot moved this from Merged To Release Candidate to Ready For Release Candidate in SKALE Engineering 🚀 Jun 21, 2023
@DmytroNazarenko DmytroNazarenko moved this from Ready For Release Candidate to Merged To Release Candidate in SKALE Engineering 🚀 Jun 21, 2023
@DmytroNazarenko DmytroNazarenko moved this from Merged To Release Candidate to QA in SKALE Engineering 🚀 Jun 30, 2023
@oleksandrSydorenkoJ
Copy link
Author

Verified on 3.17.0-beta.7
no exceptions after creating skaled container

@EvgeniyZZ EvgeniyZZ moved this from QA to Done in SKALE Engineering 🚀 Sep 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@olehnikolaiev olehnikolaiev

Labels
bug Something isn't working release:2.2
Projects
SKALE Engineering 🚀
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

1347 fix config validation skalenetwork/skaled
3 participants
@DmytroNazarenko @olehnikolaiev @oleksandrSydorenkoJ