TRT-2068: Skip specific LoadBalancer test for "none" platform

[smg247]

This was done in #2247, but only using the external platform. I am not entirely sure if that is still necessary, but it is safer to also add this for the none platform as that is what MicroShift reports itself as. This is the only test that is failing in the microshift job run, after merging #2331

[openshift-ci-robot]

@smg247: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• e6d8189|UPSTREAM: : skip specific LoadBalancer test for "none" platform: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[pacevedom]

/lgtm
/hold
Hold in case you want more reviews, from MicroShift's POV this is correct.

[stbenjam]

/hold cancel
/lgtm
/remove-label backports/unvalidated-commits

[p0lyn0mial]

lgtm, just one question.

[p0lyn0mial]

FYI ci/prow/configmap-scale is perma failing, potential fix in openshift/release#67662

[smg247]

/override ci/prow/configmap-scale

[openshift-ci]

@smg247: Overrode contexts on behalf of smg247: ci/prow/configmap-scale

Details

In response to this:

/override ci/prow/configmap-scale

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.

[p0lyn0mial]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: p0lyn0mial, pacevedom, smg247, stbenjam

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:

• DOWNSTREAM_OWNERS [p0lyn0mial]

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

[openshift-ci-robot]

@smg247: This pull request references Jira Issue OCPBUGS-59956, which is invalid:

• expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This was done in #2247, but only using the external platform. I am not entirely sure if that is still necessary, but it is safer to also add this for the none platform as that is what MicroShift reports itself as. This is the only test that is failing in the microshift job run, after merging #2331

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]

@smg247: This pull request references TRT-2068 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "4.20.0" version, but no target version was set.

Details

In response to this:

This was done in #2247, but only using the external platform. I am not entirely sure if that is still necessary, but it is safer to also add this for the none platform as that is what MicroShift reports itself as. This is the only test that is failing in the microshift job run, after merging #2331

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]

/retest-required

Remaining retests: 0 against base HEAD c42ba29 and 2 for PR HEAD e6d8189 in total

[smg247]

/override ci/prow/configmap-scale

[openshift-ci]

@smg247: Overrode contexts on behalf of smg247: ci/prow/configmap-scale

Details

In response to this:

/override ci/prow/configmap-scale

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.

[smg247]

/label backports/vaidated-commits

[openshift-ci]

@smg247: The label(s) /label backports/vaidated-commits cannot be applied. These labels are supported: acknowledge-critical-fixes-only, platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, ux-approved, no-qe, downstream-change-needed, rebase/manual, cluster-config-api-changed, run-integration-tests, approved, backport-risk-assessed, backports/unvalidated-commits, backports/validated-commits, bugzilla/invalid-bug, bugzilla/valid-bug, cherry-pick-approved, jira/invalid-bug, jira/valid-bug, jira/valid-reference, stability-fix-approved, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

Details

In response to this:

/label backports/vaidated-commits

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.

[smg247]

/label backports/validated-commits

[smg247]

/override ci/prow/configmap-scale

[openshift-ci]

@smg247: Overrode contexts on behalf of smg247: ci/prow/configmap-scale

Details

In response to this:

/override ci/prow/configmap-scale

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.

[openshift-ci]

@smg247: 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	e6d8189	link	false	/test e2e-aws
ci/prow/e2e-aws-single-node	e6d8189	link	false	/test e2e-aws-single-node
ci/prow/e2e-metal-ipi-ovn-ipv6	e6d8189	link	false	/test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-openstack-csi-cinder	e6d8189	link	false	/test e2e-openstack-csi-cinder
ci/prow/okd-scos-e2e-aws-ovn	e6d8189	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-disruptive	e6d8189	link	false	/test e2e-aws-disruptive
ci/prow/e2e-metal-ipi-ovn-dualstack	e6d8189	link	false	/test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-openstack-csi-manila	e6d8189	link	false	/test e2e-openstack-csi-manila

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-bot]

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-pod
This PR has been included in build openshift-enterprise-pod-container-v4.20.0-202507302114.p0.g80b82ba.assembly.stream.el9.
All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: kube-proxy
This PR has been included in build kube-proxy-container-v4.20.0-202507302114.p0.g80b82ba.assembly.stream.el9.
All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-hyperkube
This PR has been included in build openshift-enterprise-hyperkube-container-v4.20.0-202507302114.p0.g80b82ba.assembly.stream.el9.
All builds following this will include this PR.

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: ose-installer-kube-apiserver-artifacts
This PR has been included in build ose-installer-kube-apiserver-artifacts-container-v4.20.0-202507302114.p0.g80b82ba.assembly.stream.el9.
All builds following this will include this PR.