You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The test is running with force_gossip_topology_changes: true, so auth is not managed via raft and auth data is stored in system_auth keyspace with default replication factor 1. Test fails once per several runs.
It is doing rolling upgrade but sometimes the driver is not connected to some of the nodes after the rolling upgrade is finished (all nodes are up).
During the upgrade, the driver cannot authenticate if replica which owns the part of token ring holding user data (system_auth has RF=1) is down. But it isn't reconnected after the node gets up.
Observed in https://github.com/scylladb/scylla-enterprise/pull/4634#issuecomment-2333883650.
The test is running with
force_gossip_topology_changes: true
, so auth is not managed via raft and auth data is stored insystem_auth
keyspace with default replication factor 1. Test fails once per several runs.It is doing rolling upgrade but sometimes the driver is not connected to some of the nodes after the rolling upgrade is finished (all nodes are up).
Reproducer:
I was running the reproducer in
test/auth_cluster
suite (enabled authentication) https://github.com/scylladb/scylladb/blob/master/test/auth_cluster/suite.yamlDuring the upgrade, the driver cannot authenticate if replica which owns the part of token ring holding user data (
system_auth
has RF=1) is down. But it isn't reconnected after the node gets up.pytest.log
The text was updated successfully, but these errors were encountered: