Bug 1785419

Summary: The sctp feature is not available in the LatencySensitive featureset
Product: OpenShift Container Platform Reporter: Neelesh Agrawal <nagrawal>
Component: NetworkingAssignee: Juan Luis de Sousa-Valadas <jdesousa>
Networking sub component: openshift-sdn QA Contact: Weibin Liang <weliang>
Status: CLOSED ERRATA Docs Contact:
Severity: urgent    
Priority: urgent CC: aos-bugs, augol, fpaoline, mfojtik, nagrawal, scuppett, sttts, xxia, zzhao
Version: 4.3.0   
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1784492 Environment:
Last Closed: 2020-01-23 11:19:28 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1784492    
Bug Blocks: 1771572    

Comment 2 Xingxing Xia 2019-12-20 02:29:19 UTC
Different feature gates involve different teams. Though they all are defined in above repos, per https://github.com/openshift/api/pull/550/files#diff-a5a3801c705742637eeef3b8e7d76bb8R134 it is sig-network, therefore moving to Networking component accordingly (it requires Subcomponent not sure which one is OK)

Comment 5 zhaozhanqi 2019-12-30 09:05:59 UTC
verified this bug on 4.3.0-0.nightly-2019-12-29-173422

 oc get featuregates -o yaml
apiVersion: v1
- apiVersion: config.openshift.io/v1
  kind: FeatureGate
      release.openshift.io/create-only: "true"
    creationTimestamp: "2019-12-30T08:10:58Z"
    generation: 2
    name: cluster
    resourceVersion: "22532"
    selfLink: /apis/config.openshift.io/v1/featuregates/cluster
    uid: ba5dd10a-11fc-4354-8675-81e041cb4a7b
    featureSet: LatencySensitive
kind: List
  resourceVersion: ""
  selfLink: ""

 oc get svc
NAME         TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)      AGE
sctpserver   ClusterIP   <none>        30100/SCTP   43s

Comment 7 errata-xmlrpc 2020-01-23 11:19:28 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, and where to find the updated
files, follow the link below.

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