[release-4.18]: OCPBUGS-54807: skip tests on platform type External #2268
Conversation
Skip service LoadBalancer for UDP protocol on platform type External as it is permanent failure on OpenShift clusters triggered by openshift/conformance suite. The following tests are affected by the skip: ~~~ [sig-network] LoadBalancers [Feature:LoadBalancer] should be able to preserve UDP traffic when server pod cycles for a LoadBalancer service on the same nodes [Skipped:alibabacloud] [Skipped:aws] [Skipped:baremetal] [Skipped:ibmcloud] [Skipped:kubevirt] [Skipped:nutanix] [Skipped:openstack] [Skipped:ovirt] [Skipped:vsphere] [Suite:openshift/conformance/parallel] [Suite:k8s] [sig-network] LoadBalancers [Feature:LoadBalancer] should be able to preserve UDP traffic when server pod cycles for a LoadBalancer service on different nodes [Skipped:alibabacloud] [Skipped:aws] [Skipped:baremetal] [Skipped:ibmcloud] [Skipped:kubevirt] [Skipped:nutanix] [Skipped:openstack] [Skipped:ovirt] [Skipped:vsphere] [Suite:openshift/conformance/parallel] [Suite:k8s] ~~~ https://issues.redhat.com/browse/OCPBUGS-53249 https://issues.redhat.com//browse/OCPBUGS-54807 (backport 4.18) Added to other platform type on: https://issues.redhat.com/browse/OCPBUGS-38840
openshift-ci-robot
added
the
backports/unvalidated-commits
openshift-ci
bot
added
the
do-not-merge/work-in-progress
|
Skipping CI for Draft Pull Request. |
openshift-ci
bot
added
kind/cleanup
|
@mtulio: 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:
Comment |
mtulio
changed the title
openshift-ci-robot
added
jira/valid-reference
|
@mtulio: This pull request references Jira Issue OCPBUGS-54807, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
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. |
Skip service LoadBalancer for UDP protocol on platform type External as it is permanent failure on OpenShift clusters triggered by openshift/conformance suite. The following tests are affected by the skip: ~~~ [sig-network] LoadBalancers [Feature:LoadBalancer] should be able to preserve UDP traffic when server pod cycles for a LoadBalancer service on the same nodes [Skipped:alibabacloud] [Skipped:aws] [Skipped:baremetal] [Skipped:ibmcloud] [Skipped:kubevirt] [Skipped:nutanix] [Skipped:openstack] [Skipped:ovirt] [Skipped:vsphere] [Suite:openshift/conformance/parallel] [Suite:k8s] [sig-network] LoadBalancers [Feature:LoadBalancer] should be able to preserve UDP traffic when server pod cycles for a LoadBalancer service on different nodes [Skipped:alibabacloud] [Skipped:aws] [Skipped:baremetal] [Skipped:ibmcloud] [Skipped:kubevirt] [Skipped:nutanix] [Skipped:openstack] [Skipped:ovirt] [Skipped:vsphere] [Suite:openshift/conformance/parallel] [Suite:k8s] ~~~ https://issues.redhat.com/browse/OCPBUGS-53249 https://issues.redhat.com//browse/OCPBUGS-54807 (backport) Added to other platform type on: https://issues.redhat.com/browse/OCPBUGS-38840
mtulio
force-pushed
the
OCPBUGS-54807-backport-OCPBUGS-53249
branch
from
10d87e2 to
d656a89
Compare
|
@mtulio: 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:
Comment |
|
/lgtm |
|
/jira-refresh |
|
openshift/origin#29666 merged, now openshift-tests must support provider /test e2e-aws-external-ccm |
|
@mtulio: The specified target(s) for The following commands are available to trigger optional jobs: Use In response to this:
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. |
Oops, typo: /test e2e-external-aws-ccm |
|
@mtulio: The specified target(s) for The following commands are available to trigger optional jobs: Use In response to this:
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. |
Added e2e external jobs on 4.18 release branch on openshift/kubernetes repository to validate skips added on openshift/kubernetes#2268
Added e2e external jobs on 4.18 release branch on openshift/kubernetes repository to validate skips added on openshift/kubernetes#2268
openshift/release#63771 merged, now we should have the job here: /test e2e-external-aws-ccm |
|
Test drastically failed, looks like cloud variability/ infra issues. Retrying: /test e2e-external-aws-ccm |
|
e2e-external-aws-ccm is now passing. I am converting to a regular PR to trigger all required jobs for readiness. |
openshift-ci
bot
removed
the
backports/unvalidated-commits
|
/jira refresh |
openshift-ci-robot
added
jira/valid-bug
|
@mtulio: This pull request references Jira Issue OCPBUGS-54807, which is valid. 7 validation(s) were run on this bug
In response to this:
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. |
|
/test e2e-aws-ovn-serial |
|
/retest-required |
I didn't see this was required, holding until it is reporting as passing: /hold |
openshift-ci
bot
added
the
do-not-merge/hold
|
@mtulio: all tests passed! 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. |
|
All tests are passing. /hold cancel |
openshift-ci
bot
removed
the
do-not-merge/hold
sdodson
added
cherry-pick-approved
openshift-ci
bot
assigned duanwei33, gangwgr, kasturinarra, wangke19, xingxingxia and zhouying7780
openshift-merge-bot
bot
merged commit 0b8a681
into
openshift:release-4.18
|
@mtulio: Jira Issue OCPBUGS-54807: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-54807 has been moved to the MODIFIED state. In response to this:
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. |
|
[ART PR BUILD NOTIFIER] Distgit: openshift-enterprise-pod |
|
[ART PR BUILD NOTIFIER] Distgit: kube-proxy |
|
[ART PR BUILD NOTIFIER] Distgit: openshift-enterprise-hyperkube |
|
[ART PR BUILD NOTIFIER] Distgit: ose-installer-kube-apiserver-artifacts |
…shift#63771) Added e2e external jobs on 4.18 release branch on openshift/kubernetes repository to validate skips added on openshift/kubernetes#2268
…shift#63771) Added e2e external jobs on 4.18 release branch on openshift/kubernetes repository to validate skips added on openshift/kubernetes#2268
What type of PR is this?
/kind cleanup
/kind failing-test
What this PR does / why we need it:
Backport #2247 to OCP 4.18.
--
This PR introduce test skips to the platform type
External. The skipped tests are not configured properly (when trying to use UDP service LB on AWS, for instance), and those are permanent failing on that platform, also in others added in 4.18 (previously provider=external was not supported by the test framework, this PR will keep the synchrony) .OpenShift CI exercises platform type External on AWS and vSphere providers, both requires additional configuration to CCM created correctly the service LoadBalancer using UDP protocol, such requirements is not implemented by upstream k8stest. Those tests are also skipped by AWS and vSphere.
Which issue(s) this PR fixes:
Fixes #
https://issues.redhat.com//browse/OCPBUGS-54807
Special notes for your reviewer:
This PR is blocked by openshift/origin#29666 change adding support to
provider=Externalto theopenshift-tests.Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: