Fix storagecluster version in odfinfoconfig unit test

[Nikhil-Ladha]

Update storagcluster version in odfinfoconfig test to 4.17

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: iamniting, Nikhil-Ladha, raaizik

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [iamniting]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Nikhil-Ladha]

/retest

[raaizik]

Pasting relevant comment. @Nikhil-Ladha, I tend to agree as as mentioned in my first comment this data is better off as a dummy.

[malayparida2000]

The e2e is failing due to ocs-client-operator installation failing

[Nikhil-Ladha]

/retest

[Nikhil-Ladha]

Pasting relevant comment. @Nikhil-Ladha, I tend to agree as as mentioned in my first comment this data is better off as a dummy.

Technically, it is not a dummy value. But, a hardcoded value that would change in each release.

[raaizik]

Pasting relevant comment. @Nikhil-Ladha, I tend to agree as as mentioned in my first comment this data is better off as a dummy.

Technically, it is not a dummy value. But, a hardcoded value that would change in each release.

But IMO this type of data should be treated as a mock in tests and not in a way that stores its real value.

[Nikhil-Ladha]

Pasting relevant comment. @Nikhil-Ladha, I tend to agree as as mentioned in my first comment this data is better off as a dummy.

Technically, it is not a dummy value. But, a hardcoded value that would change in each release.

But IMO this type of data should be treated as a mock in tests and not in a way that stores its real value.

It should be, but in the part of code that this test is testing out, we can't set version to a mock value, since it is comparing the value with an actual storagecluster that is created in the test env.