mirror of
https://github.com/scylladb/scylladb.git
synced 2026-04-20 00:20:47 +00:00
When an SSTable was encrypted with a KMS host that is not present in scylla.yaml, the error thrown was: std::invalid_argument (No such host: <host-name>) This message is very obscure in general, and especially confusing when encountered while using the scylla-sstable tool: it gives no indication that the SSTable is encrypted, that a KMS host lookup is involved, or what the user needs to do to fix the problem. Replace it with a message that names the missing host and points directly to the relevant scylla.yaml section: Encryption host "<host-name>" is not defined in scylla.yaml. Make sure it is listed under the "kmip_hosts" section. The wording is intentionally kept neutral (not framed as an SSTable tool problem) because the same code path is exercised by production ScyllaDB when a node's configuration no longer contains a host referenced by an existing data file (e.g. after a config rollback or when restoring data from a different cluster). The production use-case takes precedence, but the message is equally actionable from the tool. Closes scylladb/scylladb#29228