-
Notifications
You must be signed in to change notification settings - Fork 27
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
scylla_conifgure.py: skip construct data volume on dev_instance_type #552
scylla_conifgure.py: skip construct data volume on dev_instance_type #552
Conversation
there is a specific test for t3.micro and it seems to be running just fine, on master and on 2024.2: I would recommend checking out why it's not catching the issue encounter, and adapt the test to catch it. |
Since dev_instance_type does not have local SSD, we should skip running scylla_create_devices. Fixes scylladb#551
39213f9
to
25e13c4
Compare
I realized that extra disks may attached to the dev instance (at least SCT test does it), changed the code to handle it: https://github.com/scylladb/scylla-machine-image/compare/39213f94e52694846b218ff0ba6cf6c629bf60f9..25e13c4f217535ee9b60e7345aafb64137506c5a |
Test passed. |
Maybe there should be a test that shows scylla working with adding an extra disk ? As in the original failure in issue this PR is fixing ? |
@fruch IIUC the the artifact test we have in SCT, it must have an extra disk:
Which I assumed was a requirement for it to work. @syuu1228 |
Since dev_instance_type does not have local SSD, we should skip running scylla_create_devices.
Fixes #551