xk6 Deletes data created in preset #154

New issue

Closed

opened 2024-07-10 13:23:37 +00:00 by a-baranov · 4 comments

a-baranov commented

2024-07-10 13:23:37 +00:00

Expected behaviour:
object being created in preset and stored in json file deleted by xK6 delete job

Current behaviour:
only object created by xK6 and stored in bolt database are deleted by xK6 delete job.
json file only used to supply bucket list

Create preset:

scenarios/preset/preset_s3.py --size 128 --buckets 4 --out /home/service/opt/k6/s3_128kb.json --endpoint https://10.78.131.223 --preload_obj 5 --location default --workers 2 --no-verify-ssl

Run xK6 to Delete objects:

./k6 run -e DURATION=240 -e STREAM_TIMEOUT=60 -e SLEEP_READ=0.2 -e SLEEP_WRITE=0.2 -e WRITE_OBJ_SIZE=128 -e READERS=0 -e WRITERS=0 -e DELETERS=2 -e DELETE_AGE=1 -e S3_ENDPOINTS=https://10.78.131.223 -e REGISTRY_FILE=/home/service/opt/k6/s3_128k.bolt -e PREGEN_JSON=/home/service/opt/k6/s3_128kb.json -e NO_VERIFY_SSL=true ./scenarios/s3.js

Object created during preset at step 1 are not deleted:

(screenshot attached)

**Expected behaviour:** object being created in preset and stored in json file deleted by xK6 delete job **Current behaviour:** only object created by xK6 and stored in bolt database are deleted by xK6 delete job. json file only used to supply bucket list # Create preset: scenarios/preset/preset_s3.py --size 128 --buckets 4 --out /home/service/opt/k6/s3_128kb.json --endpoint https://10.78.131.223 --preload_obj 5 --location default --workers 2 --no-verify-ssl # Run xK6 to Delete objects: ./k6 run -e DURATION=240 -e STREAM_TIMEOUT=60 -e SLEEP_READ=0.2 -e SLEEP_WRITE=0.2 -e WRITE_OBJ_SIZE=128 -e READERS=0 -e WRITERS=0 -e DELETERS=2 -e DELETE_AGE=1 -e S3_ENDPOINTS=https://10.78.131.223 -e REGISTRY_FILE=/home/service/opt/k6/s3_128k.bolt -e PREGEN_JSON=/home/service/opt/k6/s3_128kb.json -e NO_VERIFY_SSL=true ./scenarios/s3.js # Object created during preset at step 1 are not deleted: (screenshot attached)

delete-preset.PNG

335 KiB

a-baranov commented

2024-07-10 13:27:04 +00:00

Author

Functionality is expected as a part of clean-up after tests on the customer system.

Cleanup of data in preset requires "--force" flag to allow mix of read / write / delete operations.

Functionality is expected as a part of clean-up after tests on the customer system. Cleanup of data in preset requires "--force" flag to allow mix of read / write / delete operations.

fyrchik commented

2024-07-10 13:28:31 +00:00

Owner

Let's delete from preset only if registry is not provided.

a-baranov commented

2024-07-10 13:33:39 +00:00

Author

That works.

elebedeva was assigned by fyrchik

2024-07-10 14:15:49 +00:00

elebedeva referenced this issue from a pull request that will close it,

2024-07-26 10:30:01 +00:00

Delete data created in preset #157

elebedeva commented

2024-08-09 08:57:49 +00:00

Member

I suggest introducing command line tool for importing into registry objects created in preset so that they can be deleted with existing delete scenarios.

elebedeva referenced this issue from a pull request that will close it,

2024-08-09 09:02:17 +00:00

Add registry import command line tool #160