GHA: Change label from s390x to s390x-large

[BbolroC]

Recently, an additional s390x runner was added to the organization. However, it is insufficient for running the operator e2e tests and will function as a supplementary builder.

This commit changes the label for the platform from s390x to s390x-large to differentiate the existing runner.

Signed-off-by: Hyounggyu Choi Hyounggyu.Choi@ibm.com

[stevenhorsman]

LGTM. Thanks!

[ldoktor]

lgtm and I can see the labels are also updated, let me merge this.

[ldoktor]

Actually the instance is used in RUNNING_INSTANCE so that part needs to be addressed. Sorry for acking this a bit too quickly...

Also I grepped for the s390x and couldn't find any other uses, where exactly will the pure s390x machine tag be used?

[BbolroC]

Also I grepped for the s390x and couldn't find any other uses, where exactly will the pure s390x machine tag be used?

Good catch, by the way. I appreciate it.

Let me explain in an easy way:

2 runners for s390x are registered to the organization like:

• s390x-runner-01 with a label s390x and s390x-large
• s390x-runner-02 with a label s390x

A runner (2 runners) labeled with s390x is used for building artifacts/running unit tests for trustee, cloud-api-adaptor and guest-components while a runner with s390x-large can only serve an operator e2e test plus other upcoming e2e tests (e.g. cloud-api-adaptor).

[ldoktor]

Also I grepped for the s390x and couldn't find any other uses, where exactly will the pure s390x machine tag be used?

A runner labeled with s390x is used for building artifacts/running unit tests for trustee, cloud-api-adaptor and guest-components.

Good catch, by the way. I appreciate it.

Thanks, so IIUC it's not used in this repository, but you want to keep the tags in sync with the other repositories under this organization? That sounds reasonable.

[ldoktor]

Thanks, this should treat all the places.