-
Notifications
You must be signed in to change notification settings - Fork 96
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
fix(nemesis): flush system_schema before doing encryption check #7036
Conversation
1d6ca4a
to
936f336
Compare
Flush helped, but still there are issues to address here, don't yet merge |
9e37c87
to
94328ca
Compare
Now all issues were addressed. flush of the schema did helped, and we also need to take into account the fact tables are encrypted by default, so the check for clear, was wrong |
To avoid those errors, when checking a newly created table: ``` error processing arguments: could not load schema via schema-tables: std::runtime_error (Failed to find keyspace1.tmp_encrypted_table in schema tables) ```
since the data coming from `scylla sstable` might be with `Invalid control characters` which the default json parse doesn't allow
since we enabled `user_info_encryption` the `check_encryption_fact` in the end of the nemesis assumed it should be clear, but in fact it's still encrypeted cause of `user_info_encryption`
94328ca
to
1aa751b
Compare
@vponomaryov I've fix those according to you comments |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
To avoid those errors, when checking a newly created table:
Fixes: #6825
Testing
PR pre-checks (self review)
backport
labelsReminders
sdcm/sct_config.py
)unit-test/
folder)