Skip to content
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

Merged
merged 3 commits into from
Jan 2, 2024

Conversation

fruch
Copy link
Contributor

@fruch fruch commented Dec 31, 2023

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)

Fixes: #6825

Testing

PR pre-checks (self review)

  • I added the relevant backport labels
  • I didn't leave commented-out/debugging code

Reminders

  • Add New configuration option and document them (in sdcm/sct_config.py)
  • Add unit tests to cover my changes (under unit-test/ folder)
  • Update the Readme/doc folder relevent to this change (if needed)

@fruch fruch added backport/5.4 Need backport to 5.4 backport/2024.1 Need backport to 2024.1 labels Dec 31, 2023
@fruch fruch marked this pull request as ready for review December 31, 2023 20:35
@fruch fruch force-pushed the flush_schema_before_KMS_check branch from 1d6ca4a to 936f336 Compare December 31, 2023 20:36
roydahan
roydahan previously approved these changes Jan 1, 2024
@fruch
Copy link
Contributor Author

fruch commented Jan 1, 2024

Flush helped, but still there are issues to address here, don't yet merge

@fruch fruch marked this pull request as draft January 1, 2024 06:25
@fruch fruch marked this pull request as ready for review January 1, 2024 17:05
@fruch fruch force-pushed the flush_schema_before_KMS_check branch from 9e37c87 to 94328ca Compare January 1, 2024 17:07
@fruch fruch requested a review from roydahan January 1, 2024 17:07
@fruch
Copy link
Contributor Author

fruch commented Jan 1, 2024

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

fruch added 3 commits January 2, 2024 15:30
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`
@fruch fruch force-pushed the flush_schema_before_KMS_check branch from 94328ca to 1aa751b Compare January 2, 2024 13:30
@fruch
Copy link
Contributor Author

fruch commented Jan 2, 2024

@vponomaryov I've fix those according to you comments

Copy link
Contributor

@vponomaryov vponomaryov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@fruch fruch merged commit 50b2255 into scylladb:master Jan 2, 2024
5 checks passed
@fruch fruch added backport/2024.1-done Commit backported to 2024.1 backport/5.4-done Commit backported to 5.4 labels Jan 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/5.4-done Commit backported to 5.4 backport/5.4 Need backport to 5.4 backport/2024.1-done Commit backported to 2024.1 backport/2024.1 Need backport to 2024.1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

KMS encryption check is failing
3 participants