WIP: OCPBUGS-52181: Add time component to the cluster id during force-new-cluster

[dusk125]

Ensures that the cluster id is different for each invocation of --force-new-cluster

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dusk125

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 [dusk125]

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

[openshift-ci-robot]

@dusk125: This pull request references Jira Issue OCPBUGS-52181, which is invalid:

• expected the bug to target the "4.20.0" version, but no target version was set
• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-52181 to depend on a bug targeting a version in 4.21.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Ensures that the cluster id is different for each invocation of --force-new-cluster

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@dusk125: This pull request references Jira Issue OCPBUGS-52181, which is invalid:

• expected the bug to target the "4.19.0" version, but no target version was set
• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-52181 to depend on a bug targeting a version in 4.20.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Ensures that the cluster id is different for each invocation of --force-new-cluster

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@dusk125: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-aws-ovn-serial	35776e8	link	true	/test e2e-aws-ovn-serial
ci/prow/e2e-aws-etcd-recovery	35776e8	link	false	/test e2e-aws-etcd-recovery
ci/prow/e2e-hypershift-conformance	35776e8	link	false	/test e2e-hypershift-conformance
ci/prow/e2e-hypershift	35776e8	link	false	/test e2e-hypershift
ci/prow/e2e-aws-ovn	35776e8	link	true	/test e2e-aws-ovn
ci/prow/e2e-aws-ovn-serial	35776e8	link	true	/test e2e-aws-ovn-serial
ci/prow/e2e-aws-etcd-recovery	35776e8	link	false	/test e2e-aws-etcd-recovery
ci/prow/configmap-scale	35776e8	link	true	/test configmap-scale
ci/prow/configmap-scale	35776e8	link	true	/test configmap-scale

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.