time_range fix

[msvinaykumar]

Description

The latest MVP code is encountering this issue: #1377.

The problem occurs because query_range is being called with start=0, end=0, and step=0 when the request payload is empty, resulting in a 400 error.

The proposed fix is to avoid using query_range in PromQL if the time_range is not provided. Instead, use the query parameter.

Fixes # (issue)

Type of change

• [x] Bug fix
• [ ] New feature
• [ ] Docs update
• [ ] Breaking change (What changes might users need to make in their application due to this PR?)
• [ ] Requires DB changes

How has this been tested?

Please describe the tests that were run to verify your changes and steps to reproduce. Please specify any test configuration required.

• [ ] New Test X
• [x] Functional testsuite

Test Configuration

• Kubernetes clusters tested on:

Checklist :dart:

• [x] Followed coding guidelines
• [x] Comments added
• [x] Dependent changes merged
• [x] Documentation updated
• [ ] Tests added or updated

Additional information

Include any additional information such as links, test results, screenshots here

[dinogun]

@msvinaykumar How has this been tested?

[msvinaykumar]

@msvinaykumar How has this been tested?

I used

./bulk_service_demo.sh -c openshift -i quay.io/vinakuma/autotune_operator:shk

it ran successfully