-
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: autoupgrade failed #51776
Comments
(roachtest).autoupgrade failed on master@b8a50cc4d062293915969cdc83e3ec4d057cede5:
More
Artifacts: /autoupgrade
See this test on roachdash |
(roachtest).autoupgrade failed on master@bfa6307c292ef4dfed4a53cb99f506e6dab26533:
More
Artifacts: /autoupgrade
See this test on roachdash |
Hm, is this me? |
I'm not entirely sure what's happening here. Running it locally I've occasionally run into the following:
Which, looking at the test, basically means the cluster has autoupgraded despite the test not expecting it to (because a non-decommissioned node is still down). But that's a different failure mode from the 10h0m0s timeout that originally created this issue. Hm, actually looking at the logs for those I see that under under 3.logs, we have ctx tags for n5, which tells me it's the same thing as #51497 (comment). |
n3 also plays a central role in this test, and so does n5. Crossing those wires seems bad, and should be fixed anyway. I'm going to go do that now, and not think too hard about how confusing the two nodes may have resulted in this failure. Given this started flaking only recently, it's probably the same fallout (introduced in #51329). |
..and the setting of cluster settings for single node clusters. `roachprod start --sequential` was broken in cockroachdb#51329, and the broken-ness outlined in TODOs in cockroachdb#51790. This PR just addresses those TODOs. Fixes cockroachdb#51497 Fixes cockroachdb#51721 Fixes cockroachdb#51738 Fixes cockroachdb#51768 Fixes cockroachdb#51769 Fixes cockroachdb#51776 Release note: None
51893: roachprod: fixup `roachprod --sequential` r=irfansharif a=irfansharif ..and the setting of cluster settings for single node clusters. `roachprod start --sequential` was broken in #51329, and the broken-ness outlined in TODOs in #51790. This PR just addresses those TODOs. Fixes #51497 Fixes #51721 Fixes #51738 Fixes #51768 Fixes #51769 Fixes #51776 Release note: None Co-authored-by: irfan sharif <[email protected]>
(roachtest).autoupgrade failed on master@e9a4f83e3eee59510f97db2c6e0df9b57cf6b944:
More
Artifacts: /autoupgrade
Related:
roachtest: autoupgrade failed #51771 roachtest: autoupgrade failed C-test-failure O-roachtest O-robot branch-provisional_202007220233_v20.2.0-alpha.2 release-blocker
roachtest: autoupgrade failed #50058 roachtest: autoupgrade failed C-test-failure O-roachtest O-robot branch-provisional_202006091546_v20.1.2 release-blocker
See this test on roachdash
powered by pkg/cmd/internal/issues
The text was updated successfully, but these errors were encountered: