Closed ShlomiBalalis closed 1 year ago
Hi @ShlomiBalalis, I double checked the default configuration of scylla we use in our docker environment. From 3.1-branch -> https://github.com/scylladb/scylla-manager/blob/bd349aa44d9bcd8352c15bfcf9c66a6ee5bb4534/testing/scylla/config/scylla.yaml#L222
authenticator: PasswordAuthenticator
is enabled and all our tests are executed against this configuration.
Makefile copying this config file https://github.com/scylladb/scylla-manager/blob/bd349aa44d9bcd8352c15bfcf9c66a6ee5bb4534/testing/Makefile#L33 ..and docker compose binding it to the container https://github.com/scylladb/scylla-manager/blob/bd349aa44d9bcd8352c15bfcf9c66a6ee5bb4534/testing/docker-compose.yaml#L35-L37
@ShlomiBalalis OK, I found the reason. Whenever SM wants to create the session, it calls scylla first to get any node_info. This call return the scylla.yaml configuration values.
One of the checks includes validating if the CQL password protection is enabled. https://github.com/scylladb/scylla-manager/blob/22d7e33905c3fd91514619a039f7f634bbc94616/pkg/scyllaclient/config_client.go#L153-L162
To be sure that the authentication is enabled we compare scylla endpoint payload to "PasswordAuthenticator" string. And this is perfectly fine according to https://opensource.docs.scylladb.com/stable/operating-scylla/security/authentication.html#procedure
authenticator: PasswordAuthenticator
I realized that in your test, you use
authenticator: org.apache.cassandra.auth.PasswordAuthenticator
(see db-cluster-f296d884.tar.gz /db-cluster-f296d884/longevity-200gb-48h-verify-limited--db-node-f296d884-1/scylla.yaml)
You must change it to just
authenticator: PasswordAuthenticator
... to make it working.
Feel free to check and close the issue if the config change solves it (I guess so).
@karol-kokoszka, I think we need to take care of it in s-m
, since we are referring to cassandra-style authenticator names in some of our doc https://github.com/scylladb/scylladb/blob/37ceef23a6877748379a76ac2c6462553275ab36/conf/scylla.yaml#L232C1-L243C39
Also some of our customers that have migrated from cassandra will face this issue too.
Issue description
First, we added the cluster to the manager
Afterwards, we tried to restore a (previously created) snapshot, and the restore command failed due to missing authentication:
Grepped rows from the log:
Impact
Users that have authentication enabled on their clusters could potentially be unable to use the restore ability.
How frequently does it reproduce?
Reproduce constantly over the last several runs.
Installation details
Kernel Version: 5.15.0-1039-aws Scylla version (or git commit hash):
2022.2.11-20230705.27d29485de90
with build-idf467a0ad8869d61384d8bbc8f20e4fb8fd281f4b
Client version: 3.1.2-0.20230704.bd349aa4 Server version: 3.1.2-0.20230704.bd349aa4Cluster size: 4 nodes (i3.4xlarge)
Scylla Nodes used in this run:
OS / Image:
ami-0e981bde054209883
(aws: eu-west-1)Test:
longevity-200gb-48h-test_restore-nemesis
Test id:f296d884-316b-41b4-9406-a9090ec196ea
Test name:scylla-staging/Shlomo/longevity-200gb-48h-test_restore-nemesis
Test config file(s):Logs and commands
- Restore Monitor Stack command: `$ hydra investigate show-monitor f296d884-316b-41b4-9406-a9090ec196ea` - Restore monitor on AWS instance using [Jenkins job](https://jenkins.scylladb.com/view/QA/job/QA-tools/job/hydra-show-monitor/parambuild/?test_id=f296d884-316b-41b4-9406-a9090ec196ea) - Show all stored logs command: `$ hydra investigate show-logs f296d884-316b-41b4-9406-a9090ec196ea` ## Logs: - **db-cluster-f296d884.tar.gz** - [https://cloudius-jenkins-test.s3.amazonaws.com/f296d884-316b-41b4-9406-a9090ec196ea/20230720_115224/db-cluster-f296d884.tar.gz](https://cloudius-jenkins-test.s3.amazonaws.com/f296d884-316b-41b4-9406-a9090ec196ea/20230720_115224/db-cluster-f296d884.tar.gz) - **sct-runner-events-f296d884.tar.gz** - [https://cloudius-jenkins-test.s3.amazonaws.com/f296d884-316b-41b4-9406-a9090ec196ea/20230720_115224/sct-runner-events-f296d884.tar.gz](https://cloudius-jenkins-test.s3.amazonaws.com/f296d884-316b-41b4-9406-a9090ec196ea/20230720_115224/sct-runner-events-f296d884.tar.gz) - **sct-f296d884.log.tar.gz** - [https://cloudius-jenkins-test.s3.amazonaws.com/f296d884-316b-41b4-9406-a9090ec196ea/20230720_115224/sct-f296d884.log.tar.gz](https://cloudius-jenkins-test.s3.amazonaws.com/f296d884-316b-41b4-9406-a9090ec196ea/20230720_115224/sct-f296d884.log.tar.gz) - **loader-set-f296d884.tar.gz** - [https://cloudius-jenkins-test.s3.amazonaws.com/f296d884-316b-41b4-9406-a9090ec196ea/20230720_115224/loader-set-f296d884.tar.gz](https://cloudius-jenkins-test.s3.amazonaws.com/f296d884-316b-41b4-9406-a9090ec196ea/20230720_115224/loader-set-f296d884.tar.gz) - **monitor-set-f296d884.tar.gz** - [https://cloudius-jenkins-test.s3.amazonaws.com/f296d884-316b-41b4-9406-a9090ec196ea/20230720_115224/monitor-set-f296d884.tar.gz](https://cloudius-jenkins-test.s3.amazonaws.com/f296d884-316b-41b4-9406-a9090ec196ea/20230720_115224/monitor-set-f296d884.tar.gz) [Jenkins job URL](https://jenkins.scylladb.com/job/scylla-staging/job/Shlomo/job/longevity-200gb-48h-test_restore-nemesis/11/) [Argus](https://argus.scylladb.com/test/226c0f08-de6f-4d69-8f77-b01161019748/runs?additionalRuns[]=f296d884-316b-41b4-9406-a9090ec196ea)