Bug 2013157
| Summary: | subctl diagnose firewall intra-cluster - failed VXLAN checks | ||
|---|---|---|---|
| Product: | Red Hat Advanced Cluster Management for Kubernetes | Reporter: | Noam Manos <nmanos> |
| Component: | Submariner | Assignee: | Sridhar Gaddam <sgaddam> |
| Status: | CLOSED ERRATA | QA Contact: | Noam Manos <nmanos> |
| Severity: | low | Docs Contact: | Christopher Dawson <cdawson> |
| Priority: | unspecified | ||
| Version: | rhacm-2.4 | CC: | nyechiel |
| Target Milestone: | --- | Flags: | ming:
rhacm-2.4+
|
| Target Release: | rhacm-2.4 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-11-11 18:33:54 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
Noam Manos
2021-10-12 09:12:18 UTC
G2Bsync 941083357 comment nyechiel Tue, 12 Oct 2021 14:47:56 UTC G2Bsync This issue has nothing to do with the addon nor ACM. It's being tracked here: https://github.com/submariner-io/submariner-operator/issues/1614 @qiujian16 can you please close this issue (or let me know how can I get the required permissions to do so myself)? Thanks! @nmanos fix is merged both in upstream and downstream. Please verify and close this BZ. Thanks Sridhar, it works good on d/s now: https://qe-jenkins-csb-skynet.apps.ocp4.prod.psi.redhat.com/job/ACM-2.4-Submariner-0.11-AWSx2-SDN/246/Test-Report/ subctl version: v0.11.0 COMPONENT REPOSITORY VERSION submariner registry.redhat.io/rhacm2-tech-preview v0.11.0 submariner-operator registry.redhat.io/rhacm2-tech-preview 08d185eea8ee48a service-discovery registry.redhat.io/rhacm2-tech-preview v0.11.0 $ oc config get-contexts CURRENT NAME CLUSTER AUTHINFO NAMESPACE admin nmanos-aws-devcluster-c admin default default-api-nmanos-aws-devcluster-a-devcluster-openshift-com-6443-master api-nmanos-aws-devcluster-a-devcluster-openshift-com:6443 master/api-nmanos-aws-devcluster-a-devcluster-openshift-com:6443 test-submariner default-api-nmanos-aws-devcluster-c-devcluster-openshift-com-6443-master api-nmanos-aws-devcluster-c-devcluster-openshift-com:6443 master/api-nmanos-aws-devcluster-c-devcluster-openshift-com:6443 test-submariner ocm/api-nmanos-aws-devcluster-a-devcluster-openshift-com:6443/master api-nmanos-aws-devcluster-a-devcluster-openshift-com:6443 master/api-nmanos-aws-devcluster-a-devcluster-openshift-com:6443 ocm * submariner-operator/api-nmanos-aws-devcluster-a-devcluster-openshift-com:6443/master api-nmanos-aws-devcluster-a-devcluster-openshift-com:6443 master/api-nmanos-aws-devcluster-a-devcluster-openshift-com:6443 submariner-operator submariner-operator/api-nmanos-aws-devcluster-c-devcluster-openshift-com:6443/master api-nmanos-aws-devcluster-c-devcluster-openshift-com:6443 master/api-nmanos-aws-devcluster-c-devcluster-openshift-com:6443 test-submariner test-submariner/api-nmanos-aws-devcluster-a-devcluster-openshift-com:6443/master api-nmanos-aws-devcluster-a-devcluster-openshift-com:6443 master/api-nmanos-aws-devcluster-a-devcluster-openshift-com:6443 test-submariner test-submariner/api-nmanos-aws-devcluster-c-devcluster-openshift-com:6443/master api-nmanos-aws-devcluster-c-devcluster-openshift-com:6443 master/api-nmanos-aws-devcluster-c-devcluster-openshift-com:6443 test-submariner $ subctl diagnose firewall intra-cluster --validation-timeout 120 Cluster "api-nmanos-aws-devcluster-a-devcluster-openshift-com:6443" • Checking the firewall configuration to determine if VXLAN traffic is allowed ... ✓ Checking the firewall configuration to determine if VXLAN traffic is allowed ✓ The firewall configuration allows VXLAN traffic Cluster "api-nmanos-aws-devcluster-a-devcluster-openshift-com:6443" • Checking the firewall configuration to determine if VXLAN traffic is allowed ... ✓ Checking the firewall configuration to determine if VXLAN traffic is allowed ✓ The firewall configuration allows VXLAN traffic Cluster "api-nmanos-aws-devcluster-a-devcluster-openshift-com:6443" • Checking the firewall configuration to determine if VXLAN traffic is allowed ... ✓ Checking the firewall configuration to determine if VXLAN traffic is allowed ✓ The firewall configuration allows VXLAN traffic Cluster "nmanos-aws-devcluster-c" • Checking the firewall configuration to determine if VXLAN traffic is allowed ... ✓ Checking the firewall configuration to determine if VXLAN traffic is allowed ✓ The firewall configuration allows VXLAN traffic Cluster "api-nmanos-aws-devcluster-a-devcluster-openshift-com:6443" • Checking the firewall configuration to determine if VXLAN traffic is allowed ... ✓ Checking the firewall configuration to determine if VXLAN traffic is allowed ✓ The firewall configuration allows VXLAN traffic Cluster "api-nmanos-aws-devcluster-c-devcluster-openshift-com:6443" • Checking the firewall configuration to determine if VXLAN traffic is allowed ... Cluster "api-nmanos-aws-devcluster-c-devcluster-openshift-com:6443" ✓ Checking the firewall configuration to determine if VXLAN traffic is allowed ✓ The firewall configuration allows VXLAN traffic • Checking the firewall configuration to determine if VXLAN traffic is allowed ... Cluster "api-nmanos-aws-devcluster-c-devcluster-openshift-com:6443" ✓ Checking the firewall configuration to determine if VXLAN traffic is allowed ✓ The firewall configuration allows VXLAN traffic • Checking the firewall configuration to determine if VXLAN traffic is allowed ... ✓ Checking the firewall configuration to determine if VXLAN traffic is allowed ✓ The firewall configuration allows VXLAN traffic 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 (Important: Red Hat Advanced Cluster Management 2.4 images and security updates), 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:4618 |