Make sure run_id is unique by using miliseconds instead of only seconds

[dahorak]

When the run_id is taken just from seconds timestamp, there is a possibility that two runs will get the same run_id:

• https://url.corp.redhat.com/209791b
• https://url.corp.redhat.com/6cc73a3

This situation breaks the reporting to Report Portal and might cause another issues.
To minimize this risk, we can use miliseconds as run_id.

[petr-balogh]

Suggested change

	run_id = int(time.time()) * 1000 + random.randint(0, 1000)
	run_id = int(time.time() * 1000)

As time.time() returns something like:
1746544165.797612

You can make it quite easy with milliseconds included instead of using random. Then the chance we hit the same millisecond is probably impossible

[ocs-ci]

PR validation

Cluster Name:
Cluster Configuration:
PR Test Suite: acceptance
PR Test Path: tests/
Additional Test Params:
OCP VERSION: 4.19
OCS VERSION: 4.19
tested against branch: master

Job FAILED (installation failed, tests not executed).

[ocs-ci]

Unknown PR validation

Cluster Name:
Cluster Configuration:
PR Test Suite: acceptance
PR Test Path: tests/
Additional Test Params:
OCP VERSION: 4.19
OCS VERSION: 4.19
tested against branch: master

Job state: ABORTED.

[ocs-ci]

PR validation

Cluster Name:
Cluster Configuration:
PR Test Suite: acceptance
PR Test Path: tests/
Additional Test Params:
OCP VERSION: 4.19
OCS VERSION: 4.19
tested against branch: master

Job FAILED (installation failed, tests not executed).

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dahorak, petr-balogh, vavuthu

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

Needs approval from an approver in each of these files:

• OWNERS

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

[petr-balogh]

/cherry-pick release-4.18

[openshift-cherrypick-robot]

@petr-balogh: new pull request created: #12089

In response to this:

/cherry-pick release-4.18

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[dahorak]

/cherry-pick release-4.17

[openshift-cherrypick-robot]

@dahorak: #12083 failed to apply on top of branch "release-4.17":

Applying: use miliseconds as run_id to make sure it is unique
Using index info to reconstruct a base tree...
A	ocs_ci/utility/framework/fusion_fdf_init.py
M	ocs_ci/utility/framework/initialization.py
Falling back to patching base and 3-way merge...
Auto-merging ocs_ci/utility/framework/initialization.py
CONFLICT (modify/delete): ocs_ci/utility/framework/fusion_fdf_init.py deleted in HEAD and modified in use miliseconds as run_id to make sure it is unique. Version use miliseconds as run_id to make sure it is unique of ocs_ci/utility/framework/fusion_fdf_init.py left in tree.
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 use miliseconds as run_id to make sure it is unique

In response to this:

/cherry-pick release-4.17

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[ocs-ci]

PR validation

Cluster Name:
Cluster Configuration:
PR Test Suite: acceptance
PR Test Path: tests/
Additional Test Params:
OCP VERSION: 4.19
OCS VERSION: 4.19
tested against branch: master

Job PASSED.