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.

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

Paseo #1789153: Storage root mismatch #4182

Open
EclesioMeloJunior opened this issue Sep 13, 2024 · 1 comment
Open

Paseo #1789153: Storage root mismatch #4182

EclesioMeloJunior opened this issue Sep 13, 2024 · 1 comment
Assignees
Labels
P-critical this must be fixed immediately or contributors or users will be severely impacted. S-network issues related to the dot/network package. T-bug this issue covers unexpected and/or wrong behaviour. T-investigation this issue/pr is an investigation, probably related to some bug with unknown causes.

Comments

@EclesioMeloJunior
Copy link
Member

Describe the bug

Gossamer node running on Paseo failed to execute block #1789153, the problem is a storage root mismatch.

image

@EclesioMeloJunior EclesioMeloJunior added T-bug this issue covers unexpected and/or wrong behaviour. S-network issues related to the dot/network package. P-critical this must be fixed immediately or contributors or users will be severely impacted. labels Sep 13, 2024
@jimjbrettj
Copy link
Contributor

Updated context on this issue:

This failure is associated with the runtime upgrade that occurs on block 1789152, in which the spec is upgraded to 1002004. This is the PR associated with this upgrade. If you go to the logs listed in the comments from the test run, or by clicking here you will see that a new pallet "ImOnline" in created.

After the creation of this pallet, you can see the log "Removed 0 ImOnline keys 🧹" and after debugging gossamer we found that this was not consistent with our behavior and we were removing a key.

This meant one of two things: we were either removing a key we shouldn't or adding a key we shouldn't. I modified our code to avoid adding this problematic key and it resolved our problem, meaning the issue was this key should not be added.

Though we have a temporary fix, I am doing more investigations into the root cause of this to find a sustainable solution.

@P1sar P1sar added the T-investigation this issue/pr is an investigation, probably related to some bug with unknown causes. label Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P-critical this must be fixed immediately or contributors or users will be severely impacted. S-network issues related to the dot/network package. T-bug this issue covers unexpected and/or wrong behaviour. T-investigation this issue/pr is an investigation, probably related to some bug with unknown causes.
Projects
None yet
Development

No branches or pull requests

3 participants