NO-JIRA: ote: fix duplicated topology label on SingleReplica

[mtulio]

Previously the SingleReplica job was setting duplicated topology label:

topology="[SingleReplica SingleReplica]"

https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/logs/openshift-origin-30747-ci-4.22-e2e-aws-upgrade-ovn-single-node/2018312069375332352/artifacts/e2e-aws-upgrade-ovn-single-node/single-node-e2e-test/build-log.txt

This fix skips re-adding the label when running in a SingleReplica cluster.

Issue observed while investigating:
#30747
https://issues.redhat.com//browse/TRT-2536

[openshift-ci-robot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

[openshift-ci-robot]

@mtulio: This pull request explicitly references no jira issue.

Details

In response to this:

Previously the SingleReplica job was setting duplicated topology label:

topology="[SingleReplica SingleReplica]"

https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/test-platform-results/logs/openshift-origin-30747-ci-4.22-e2e-aws-upgrade-ovn-single-node/2018312069375332352/artifacts/e2e-aws-upgrade-ovn-single-node/single-node-e2e-test/build-log.txt

This fix skips re-adding the label when running in a SingleReplica cluster.

Issue observed while investigating:
#30747
https://issues.redhat.com//browse/TRT-2536

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.

[mtulio]

/assign @neisw

[mtulio]

/test ?

[mtulio]

/payload-job periodic-ci-openshift-release-master-ci-4.22-e2e-aws-ovn

[openshift-ci]

@mtulio: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-ci-4.22-e2e-aws-ovn

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/b3a6b9a0-020b-11f1-9626-7a5ec4ffd2f3-0

[openshift-ci-robot]

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

[neisw]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mtulio, neisw

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:

• OWNERS [neisw]

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

[mtulio]

I can see the topology="[SingleReplica]" (no duplicated entry) in the microshift job.

[mtulio]

/verified by @mtulio #30759 (comment)

[openshift-ci-robot]

@mtulio: This PR has been marked as verified by @mtulio https://github.com/openshift/origin/pull/30759#issuecomment-3860847683.

Details

In response to this:

/verified by @mtulio #30759 (comment)

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]

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

[openshift-ci]

@mtulio: 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-microshift	2926066	link	true	/test e2e-aws-ovn-microshift
ci/prow/e2e-aws-ovn-serial-2of2	2926066	link	true	/test e2e-aws-ovn-serial-2of2
ci/prow/e2e-metal-ipi-ovn-ipv6	2926066	link	true	/test e2e-metal-ipi-ovn-ipv6

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.

[openshift-trt]

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New Test Risks for sha: 2926066

Job Name	New Test Risk
pull-ci-openshift-origin-main-e2e-vsphere-ovn	High - "[Monitor:audit-log-analyzer][Jira:"Test Framework"] operator service account vmware-vsphere-csi-driver-operator should not create excessive watch requests" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-vsphere-ovn	High - "[Monitor:audit-log-analyzer][Jira:"Test Framework"] operator service account vsphere-problem-detector-operator should not create excessive watch requests" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-vsphere-ovn-upi	High - "[Monitor:audit-log-analyzer][Jira:"Test Framework"] operator service account vmware-vsphere-csi-driver-operator should not create excessive watch requests" is a new test that was not present in all runs against the current commit.
pull-ci-openshift-origin-main-e2e-vsphere-ovn-upi	High - "[Monitor:audit-log-analyzer][Jira:"Test Framework"] operator service account vsphere-problem-detector-operator should not create excessive watch requests" is a new test that was not present in all runs against the current commit.

New tests seen in this PR at sha: 2926066

• "[Monitor:audit-log-analyzer][Jira:"Test Framework"] operator service account vmware-vsphere-csi-driver-operator should not create excessive watch requests" [Total: 4, Pass: 4, Fail: 0, Flake: 0]
• "[Monitor:audit-log-analyzer][Jira:"Test Framework"] operator service account vsphere-problem-detector-operator should not create excessive watch requests" [Total: 4, Pass: 4, Fail: 0, Flake: 0]