-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
roachtest: decommission/mixed-versions failed #58058
Comments
(roachtest).decommission/mixed-versions failed on release-20.2@cb9df011e6f1f365c03ab6a24a301fb8dcd8d708:
More
Artifacts: /decommission/mixed-versions See this test on roachdash |
(roachtest).decommission/mixed-versions failed on release-20.2@7274fe0d3c5ce963d2f50920670d7e6e4a2969de:
More
Artifacts: /decommission/mixed-versions See this test on roachdash |
(roachtest).decommission/mixed-versions failed on release-20.2@eb21aede5ceae7747d1392b66b61ec7799d5171c:
More
Artifacts: /decommission/mixed-versions
See this test on roachdash |
(roachtest).decommission/mixed-versions failed on release-20.2@b0012907c1bc9627ae2de83e6099c4930a32699e:
More
Artifacts: /decommission/mixed-versions
See this test on roachdash |
(roachtest).decommission/mixed-versions failed on release-20.2@6b701b545f1a50c8e9b2de216b0d8d02cd7d0d72:
More
Artifacts: /decommission/mixed-versions
See this test on roachdash |
(roachtest).decommission/mixed-versions failed on release-20.2@34ae57c277484ddc95e6f01137a75e0267c887b7:
More
Artifacts: /decommission/mixed-versions
See this test on roachdash |
This is a new failure mode:
Probably due to recent decommissioning protocol changes. cc @irfansharif @erikgrinaker for triage. |
These errors are from before the decommissioning changes were merged in #61356. It's probably just a race where the node moves past |
@tbg I suspect this (as well as #61692) is caused by or related to #56568 which wasn't backported to 20.2, as well as the follow-up self-decommissioning work in #61356. How do you feel about backporting this work? We'll hold off on the status entry removal, since that has more externally visible changes. |
Self decommission only got iffy in the 21.1 cycle, this is on the 20.2 branch. Could this be something else? Wouldn't be the first time these tests need to be deflaked. |
Ah ok. Will do a few local runs and see if I can reproduce. |
Have been running this for a few hours, and the only failures I see are:
This is an oldie but a goodie, which should be fixed on As for the missing |
From the error message, it looks as though version 20.1 is the one that didn't sync correctly. It doesn't look like we backported this all the way there. |
It has issues that come from its use of the v20.1 binary, and it is unlikely that we will introduce any mixed-version issues related to decommissioning that this test would catch. Closes #58058. Release note: None
(roachtest).decommission/mixed-versions failed on release-20.2@7f140b6fdc0c5086353a56016aafcdaa34ed6405:
More
Artifacts: /decommission/mixed-versions
See this test on roachdash
powered by pkg/cmd/internal/issues
The text was updated successfully, but these errors were encountered: