Bug 1908677

Summary:	Reenable [sig-network] SCTP [Feature:SCTP] [LinuxOnly] should create a Pod with SCTP HostPort [Suite:openshift/conformance/parallel] [Suite:k8s]
Product:	OpenShift Container Platform	Reporter:	Tomáš Nožička <tnozicka>
Component:	Networking	Assignee:	Antonio Ojea <aojeagar>
Networking sub component:	openshift-sdn	QA Contact:	Weibin Liang <weliang>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	aconstan, anbhat, bbennett, danw, dcbw
Version:	4.7	Keywords:	Reopened
Target Milestone:	---
Target Release:	4.9.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-10-18 17:28:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tomáš Nožička 2020-12-17 10:26:18 UTC

[sig-network] SCTP [Feature:SCTP] [LinuxOnly] should create a Pod with SCTP HostPort [Suite:openshift/conformance/parallel] [Suite:k8s] 

is not working on the rebase to kube 1.20 and has been disabled. Please fix the test and reenable it.

I am not sure which subcomponent to choose, host network isn't openshift-sdn but nor are the other options. Please reassign if there is a more fitting component.

https://github.com/openshift/origin/pull/25764
https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/25764/pull-ci-openshift-origin-master-e2e-aws-fips/1339311087341801472

Comment 1 Antonio Ojea 2020-12-17 15:09:25 UTC

These tests need to be cleaned up upstream first

https://github.com/kubernetes/kubernetes/issues/96717

@DanWinship what is your opinion about these tests in Openshift?

Comment 2 Dan Winship 2020-12-17 16:04:04 UTC

While the test is going to be rewritten/removed in 1.21, it seems to me like it should pass in 1.20. CRI-O is using the upstream hostport manager code, which ought to set up iptables rules for SCTP hostports, which ought to be observed correctly by the test...

Oh. I bet it ends up using iptables-legacy to check the iptables rules. Sigh. We need to fix agnhost to use https://github.com/kubernetes-sigs/iptables-wrappers

Comment 3 Antonio Ojea 2020-12-17 17:43:30 UTC

The test was broken by a refactor, fix posted

https://github.com/kubernetes/kubernetes/pull/97371

Comment 4 Aniket Bhat 2021-01-28 14:38:36 UTC


*** This bug has been marked as a duplicate of bug 1861606 ***

Comment 5 Dan Winship 2021-01-28 14:44:06 UTC

oh, sorry, I misread this... 1861606 is about the [Feature:SCTPConnectivity] tests, not [Feature:SCTP].

Comment 6 Antonio Ojea 2021-01-28 15:40:21 UTC

I was confused too with another bug, I will backport the upstream change

Comment 7 Antonio Ojea 2021-01-28 16:57:06 UTC

PR for backporting upstream fix
https://github.com/openshift/kubernetes/pull/543
PR for enabling the test
https://github.com/openshift/origin/pull/25833

Comment 9 Weibin Liang 2021-09-07 17:44:37 UTC

pull-ci-openshift-origin-master-e2e-aws-fips passed in https://prow.ci.openshift.org/pr-history/?org=openshift&repo=origin&pr=25833

Comment 11 errata-xmlrpc 2021-10-18 17:28:58 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:3759