roachtest: gossip/chaos/nodes=9 failed

[cockroach-teamcity]

Note: This build has runtime assertions enabled. If the same failure was hit in a run without assertions enabled, there should be a similar failure without this message. If there isn't one, then this failure is likely due to an assertion violation or (assertion) timeout.

roachtest.gossip/chaos/nodes=9 failed with artifacts on release-24.3.0-rc @ ef2ebe96f3a26fd6d6716e2ec4a0c8c6fe0fb567:

(gossip.go:78).2: gossip did not stabilize (dead node 6) in 27.7s
test artifacts and logs in: /artifacts/gossip/chaos/nodes=9/run_1

Parameters:

• ROACHTEST_arch=amd64
• ROACHTEST_cloud=gce
• ROACHTEST_coverageBuild=false
• ROACHTEST_cpu=4
• ROACHTEST_encrypted=false
• ROACHTEST_runtimeAssertionsBuild=true
• ROACHTEST_ssd=0
  Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

Same failure on other branches

- #135154 roachtest: gossip/chaos/nodes=9 failed [A-testing C-bug C-test-failure O-roachtest O-robot P-3 T-kv branch-master] - #135059 roachtest: gossip/chaos/nodes=9 failed [A-testing C-bug C-test-failure O-roachtest O-robot P-3 T-kv branch-release-24.2]

/cc @cockroachdb/kv-triage

This test on roachdash | Improve this report!

Jira issue: CRDB-44863

[andrewbaptist]

Dupe of #135154. Removing release blocker label and matching labels on that but leaving open.