forked from TrueCloudLab/xk6-frostfs
[#61] scenarios: Fix setObjectStatus
parameters
We were providing new status instead of old and expected it to exist in DB. Signed-off-by: Evgenii Stratonikov <e.stratonikov@yadro.com>
This commit is contained in:
parent
e71ac35c36
commit
5c26b4bad4
1 changed files with 1 additions and 1 deletions
|
@ -105,7 +105,7 @@ export function obj_verify() {
|
||||||
|
|
||||||
const obj_status = verify_object_with_retries(obj, 3);
|
const obj_status = verify_object_with_retries(obj, 3);
|
||||||
obj_counters[obj_status].add(1);
|
obj_counters[obj_status].add(1);
|
||||||
obj_registry.setObjectStatus(obj.id, obj_status);
|
obj_registry.setObjectStatus(obj.id, obj.status, obj_status);
|
||||||
}
|
}
|
||||||
|
|
||||||
function verify_object_with_retries(obj, attempts) {
|
function verify_object_with_retries(obj, attempts) {
|
||||||
|
|
Loading…
Reference in a new issue