Bug 1901675
| Summary: | [sig-network] multicast when using one of the plugins 'redhat/openshift-ovs-multitenant, redhat/openshift-ovs-networkpolicy' should allow multicast traffic in namespaces where it is enabled | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Lokesh Mandvekar <lsm5> | |
| Component: | Networking | Assignee: | Aniket Bhat <anbhat> | |
| Networking sub component: | openshift-sdn | QA Contact: | Weibin Liang <weliang> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | high | |||
| Priority: | medium | CC: | aconstan, dosmith, weliang | |
| Version: | 4.7 | |||
| Target Milestone: | --- | |||
| Target Release: | 4.7.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1902054 (view as bug list) | Environment: |
[sig-network] multicast when using one of the plugins 'redhat/openshift-ovs-multitenant, redhat/openshift-ovs-networkpolicy' should allow multicast traffic in namespaces where it is enabled
[sig-network] multicast when using one of the plugins 'redhat/openshift-ovs-multitenant, redhat/openshift-ovs-networkpolicy' should block multicast traffic in namespaces where it is disabled
|
|
| Last Closed: | 2021-02-24 15:35:50 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: | ||||
| Bug Depends On: | 1816812 | |||
| Bug Blocks: | 1902054 | |||
|
Description
Lokesh Mandvekar
2020-11-25 19:38:09 UTC
Same log URL for test: [sig-network] multicast when using one of the plugins 'redhat/openshift-ovs-multitenant, redhat/openshift-ovs-networkpolicy' should block multicast traffic in namespaces where it is disabled Still see the multicast failed in latest v4.7 CI: https://search.ci.openshift.org/?search=multicast+when+using+one+of+the+plugins+%27redhat%2Fopenshift-ovs-multitenant%2C+redhat%2Fopenshift-ovs-networkpolicy%27+should+allow+multicast+traffic+in+namespaces+where+it+is+enabled&maxAge=168h&context=1&type=bug%2Bjunit&name=4.7&maxMatches=5&maxBytes=20971520&groupBy=job https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-e2e-azure-4.7/1338330052495937536 https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ocp-4.7-e2e-aws-workers-rhel7/1338552052871073792 the azure error seems to be related to some permissions issue:
Dec 14 04:47:19.698: INFO: Error running /usr/bin/oc --namespace=e2e-test-multicast-qvbmb --kubeconfig=/tmp/configfile346677150 exec multicast-3 -- omping -c 5 -T 60 -q -q 10.131.0.188 10.131.0.189 10.128.2.182:
StdOut>
error: You must be logged in to the server (Unauthorized)
StdErr>
error: You must be logged in to the server (Unauthorized)
[AfterEach] [sig-network] multicast
github.com/openshift/origin/test/extended/util/client.go:138
STEP: Collecting events from namespace "e2e-test-multicast-qvbmb".
The aws error seems to be rhel7 specific and it is likely that the RHEL7 worker node is not set up correctly since the Multus readinessindicatorfile was not found, which likely means the sdn was not properly initialized.
Dec 14 20:00:46.397: INFO: At 2020-12-14 19:57:10 +0000 UTC - event for multicast-3: {kubelet ip-10-0-179-21.us-west-1.compute.internal} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_multicast-3_e2e-test-multicast-xdhf8_e32d5fb1-150a-4094-b18f-2a9f59c861ab_0(ce76b14dd92b45a4f69ba2402bcc4580c76cc50f58839fdfe58dc75f6e08ec6c): Multus: [e2e-test-multicast-xdhf8/multicast-3]: PollImmediate error waiting for ReadinessIndicatorFile: timed out waiting for the condition
Dec 14 20:00:46.397: INFO: At 2020-12-14 19:58:53 +0000 UTC - event for multicast-3: {kubelet ip-10-0-179-21.us-west-1.compute.internal} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_multicast-3_e2e-test-multicast-xdhf8_e32d5fb1-150a-4094-b18f-2a9f59c861ab_0(b352d3d09db7f57423b3a313955969f8d3e36c59a3f3a7c9556baf2b56e36b6e): Multus: [e2e-test-multicast-xdhf8/multicast-3]: PollImmediate error waiting for ReadinessIndicatorFile: timed out waiting for the condition
Dec 14 20:00:46.397: INFO: At 2020-12-14 20:00:35 +0000 UTC - event for multicast-3: {kubelet ip-10-0-179-21.us-west-1.compute.internal} FailedCreatePodSandBox: Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_multicast-3_e2e-test-multicast-xdhf8_e32d5fb1-150a-4094-b18f-2a9f59c861ab_0(18fb08e899765e33d85313fcddb94cc2a7e89e692764e5985e85fdc6c1c806ea): Multus: [e2e-test-multicast-xdhf8/multicast-3]: PollImmediate error waiting for ReadinessIndicatorFile: timed out waiting for the condition
The rhel7 worker issue seems to be related to: https://bugzilla.redhat.com/show_bug.cgi?id=1908616
Not see multicast failed log in e2e-azure-4.7 any more. 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.7.0 security, bug fix, and enhancement 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-2020:5633 |