Adding shard to avoid ci job timeout

[gangwgr]

openshift/cluster-kube-apiserver-operator#1993 (comment)
e2e-gcp-operator-serial-ote-openshift-e2e-test took 4h10m16s, considering that tests adding shard ci job

[wangke19]

Better to exactly 2 commits following this structure:

1. Commit 1: Infrastructure code changes only
2. Commit 2: Automatically produced code/Dependency updates (go.mod, go.sum) and vendor/ directory changes

[wangke19]

/lgtm

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@gangwgr: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-openshift-cluster-kube-apiserver-operator-main-e2e-gcp-operator-serial-ote-1of2	openshift/cluster-kube-apiserver-operator	presubmit	Presubmit changed
pull-ci-openshift-cluster-kube-apiserver-operator-main-e2e-gcp-operator-serial-ote-2of2	openshift/cluster-kube-apiserver-operator	presubmit	Presubmit changed
pull-ci-openshift-cluster-kube-apiserver-operator-release-4.22-e2e-gcp-operator-serial-ote-1of2	openshift/cluster-kube-apiserver-operator	presubmit	Presubmit changed
pull-ci-openshift-cluster-kube-apiserver-operator-release-4.22-e2e-gcp-operator-serial-ote-2of2	openshift/cluster-kube-apiserver-operator	presubmit	Presubmit changed
pull-ci-openshift-cluster-kube-apiserver-operator-release-4.23-e2e-gcp-operator-serial-ote-1of2	openshift/cluster-kube-apiserver-operator	presubmit	Presubmit changed
pull-ci-openshift-cluster-kube-apiserver-operator-release-4.23-e2e-gcp-operator-serial-ote-2of2	openshift/cluster-kube-apiserver-operator	presubmit	Presubmit changed

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: gangwgr, wangke19
Once this PR has been reviewed and has the lgtm label, please assign benluddy for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• ci-operator/config/openshift/cluster-kube-apiserver-operator/OWNERS
• ci-operator/jobs/openshift/cluster-kube-apiserver-operator/OWNERS

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

[openshift-ci]

@gangwgr: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

[gangwgr]

/pj-rehearse ack

[openshift-ci-robot]

@gangwgr: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[p0lyn0mial]

this job used to work in the past just fine.

i suspect openshift/cluster-kube-apiserver-operator#1997 (review) might have cause it.

WaitForAPIServerToStabilizeOnTheSameRevision is very expensive in terms of time, for sure will delay any test that use it.

could you check if that method is absolutely required ? again in the past the operator tests just worked.