Shard Azure MAPI regression job

[mdbooth]

This job is currently running for 7 hours.

[mdbooth]

/pj-rehearse

[openshift-ci-robot]

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

[openshift-ci-robot]

[REHEARSALNOTIFIER]
@mdbooth: 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-machine-api-provider-azure-main-regression-clusterinfra-azure-ipi-mapi-1of3	openshift/machine-api-provider-azure	presubmit	Presubmit changed
pull-ci-openshift-machine-api-provider-azure-main-regression-clusterinfra-azure-ipi-mapi-2of3	openshift/machine-api-provider-azure	presubmit	Presubmit changed
pull-ci-openshift-machine-api-provider-azure-main-regression-clusterinfra-azure-ipi-mapi-3of3	openshift/machine-api-provider-azure	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.

[mdbooth]

/pj-rehearse

[openshift-ci-robot]

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

[damdo]

/approve
/lgtm

Feel free to ack the pj once happy

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: damdo, mdbooth

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:

• ci-operator/config/openshift/machine-api-provider-azure/OWNERS [damdo]
• ci-operator/jobs/openshift/machine-api-provider-azure/OWNERS [damdo]

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

[mdbooth]

/hold

Given that the 3 shards are all still running after 4 hours, I assume this doesn't work on this job.

[theobarberbany]

It looks like the contents of the job (regression tests?) aren't configured to shard - this has run the whole regression 3 times in parallel

release/ci-operator/config/openshift/machine-api-provider-azure/openshift-machine-api-provider-azure-main.yaml

Lines 92 to 106 in 1b4affc

	- as: regression-clusterinfra-azure-ipi-mapi
	optional: true
	run_if_changed: ^(go\.mod|go\.sum)$
	steps:
	cluster_profile: azure4
	env:
	E2E_RUN_TAGS: '@mapi'
	TEST_FILTERS: NonHyperShiftHOST
	TEST_FILTERS_CLUSTERINFRASTRUCTURE: periodic&&!qe-only&&mapi
	TEST_SCENARIOS: Cluster_Infrastructure MAPI
	TEST_TIMEOUT: "35"
	test:
	- chain: openshift-e2e-test-clusterinfra-qe-regression
	workflow: cucushift-installer-rehearse-azure-ipi
	timeout: 7h0m0s

defines the actual job which is run, which looks like it uses the cucushift-installer-rehearse-azure-ipi workflow.

  test:
    - chain: openshift-e2e-test-clusterinfra-qe-regression
    workflow: cucushift-installer-rehearse-azure-ipi

I'm not sure what chain does.

edit: here's the chain definition, it's a chain of workflows? it breaks down how the test is run: https://steps.ci.openshift.org/chain/openshift-e2e-test-clusterinfra-qe-regression

I think this is what would need to support sharding.

https://steps.ci.openshift.org/reference/openshift-e2e-test supports sharding (takes SHARD_ARGS) maybe we can do something similar

[shellyyang1989]

cc @sunzhaohua2 for awareness

[miyadav]

/pj-rehearse

[openshift-ci-robot]

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

[miyadav]

not sure if it picked up changes when i triggered, still seeing it taking time 🤔

[miyadav]

/pj-rehearse

[openshift-ci-robot]

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

[miyadav]

doing more testing in separate PR (using a step other than the chain used in this PR as the chain contains other repos test as well ) , doesn't look like it worked at the moment.

[miyadav]

from the running logs of the test pods, here , sharding looking good .. once tests end we can confirm that.

[openshift-ci]

@mdbooth: 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/rehearse/openshift/machine-api-provider-azure/main/regression-clusterinfra-azure-ipi-mapi-1of3	68603f2	link	unknown	/pj-rehearse pull-ci-openshift-machine-api-provider-azure-main-regression-clusterinfra-azure-ipi-mapi-1of3
ci/rehearse/openshift/machine-api-provider-azure/main/regression-clusterinfra-azure-ipi-mapi-2of3	68603f2	link	unknown	/pj-rehearse pull-ci-openshift-machine-api-provider-azure-main-regression-clusterinfra-azure-ipi-mapi-2of3
ci/rehearse/openshift/machine-api-provider-azure/main/regression-clusterinfra-azure-ipi-mapi-3of3	68603f2	link	unknown	/pj-rehearse pull-ci-openshift-machine-api-provider-azure-main-regression-clusterinfra-azure-ipi-mapi-3of3

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.