Skip to content

test: improve bulk operation status check

Type of change

  • Bug Fix
  • Feature
  • Pipeline
  • Test
  • Documentation

Does this introduce a change in the core logic?

  • No
  • Yes

Does this introduce a change in the cloud provider implementation, if so which cloud?

  • AWS
  • Anthos
  • Azure
  • GCP
  • IBM

Does this follow conventional commits spec?

  • No
  • Yes

Have you set the target Milestone?

  • No
  • Yes

Have you set the no-detached-pipeline label?

  • No
  • Yes

Updates description?

Improve the test behavior on 404 response code for bulk delete operation status verification:

  1. DATASET FILTER DELETE - accept 404 response and make 5 attempts with the 5 second interval to give sidecar time to get a message from the queue and put status information to Redis. The same logic is implemented if the status is not "completed".
  3. COMPUTE-SIZE DATASET GET - skip tests and make a retry if computed_size is undefined
Edited by Konstantin Khottchenkov

Merge request reports