Revert "Restore --parallel=30 for ppc64le slow e2e job"

[kishen-v]

Reverts commit c3c1ae8 through #37053

Reason: Mitigates flakiness in ci-kubernetes-ppc64le-e2e-slow-kubetest2.

The test suite performs better and has fewer flakes running with --parallel=15 , specifically regarding the test:
CSI Mock volume attach When CSIDriver AttachRequired changes from true to false should cleanup VolumeAttachment properly [Slow]

The parallelism can be increased once when the the root cause is identified.

[mkumatag]

@kishen-v please add more information in the description for the reason to revert this commit

[kishen-v]

I've updated the PR description with the related information. Thanks!

[mkumatag]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kishen-v, mkumatag

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• config/jobs/kubernetes/cloud-provider-ibmcloud/OWNERS [kishen-v,mkumatag]

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

[k8s-ci-robot]

@kishen-v: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key cloud-provider-ibmcloud-ppc64le-periodics.yaml using file config/jobs/kubernetes/cloud-provider-ibmcloud/cloud-provider-ibmcloud-ppc64le-periodics.yaml

Details

In response to this:

Reverts commit c3c1ae8 through #37053

Reason: Mitigates flakiness in ci-kubernetes-ppc64le-e2e-slow-kubetest2.

The test suite performs better and has fewer flakes running with --parallel=15 , specifically regarding the test:
CSI Mock volume attach When CSIDriver AttachRequired changes from true to false should cleanup VolumeAttachment properly [Slow]

The parallelism can be increased once when the the root cause is identified.

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.