Submariner 0.12.0 not able to establish connection between sites. Error: The detected CNI network plugin ("") is not supported by Submariner. #3042
Comments
|
A. You can read how Submariner detects if CNI is OVN-K8S here (in 0.12 release) B. I can see that OVN-K8S was detected successfully for site2 , both site1 and site2 are running OCP 4.10, is there any difference in OVN-K8S configuration between these clusters ? |
|
FYI, SubM 0.12 is a very old version that's long since not supposed to be supported. If you get a chance to update, that would likely be a very good idea. |
|
@yboaron
On both sites, it is the same output Site 2
Site 2
Site 2
Site 2 |
|
@dfarrell07 |
Did you mean oc get pods -A -l name=ovnkube-db ? |
|
@yboaron
Yes |
You had created #2955 a while back where you were using Submariner 0.16.x and OCP 4.15 so I'm curious why you would now be using much older versions of each (which are no longer supported).... |
|
A.
Hmm, that's weird, b/c if no pod with ovnkube-db label is found Submariner shouldn't recognize CNI plugin as OVN-K8S, and OVN-K8S was detected successfully for site2 B. What version of subctl do you use ? C. Also think it is better to upgrade Submariner, for OCP 4.10 you can upgrade to Submariner 0.14. D. If you decide to stay with version 0.12, and still hit this issue please upload subctl gather from both clusters. |
|
@tpantelis This is a different cluster setup @yboaron C. Any version of 0.14.x would work on OCP 4.10? D. Sure, will try to get the subctl gather from both clusters, it might take some time. Meanwhile, I have found some error log statements in submariner-operator logs of Site 1, Please check this out. |
Yep. |
|
@yboaron There is a concern about sharing all the logs. Could you let me know if you want any specific logs to look for the exact error? |
|
Please share the output of oc get submariner submariner -n submariner-operator -o yaml , from site1 , couldn't see the status section in the ^^ you attached above. |
|
The output of the command Here are the submariner-operator pod logs you asked |
|
According to the site1 logs, submariner-operator failed to reconcile due to [1] error, and therefore does not update submariner.status section. Please address this issue and let us know how it goes. [1]
|
This looks like an incompatibility with the K8s version your using, ie the K8s version is newer than what's supported by Submariner 0.12. As mentioned earlier, 0.12 is no longer maintained so I strongly suggest upgrading Submariner. |
|
In the past when we had an issue with Submariner 0.12.0 and OCP 4.10, then it was said by your team that the OCP version must be 4.11+ for the submariner 0.13. Also in the same ticket, it was mentioned that the Submariner does not support OVN on OCP 4.9 and 4.10 |
|
You're better off upgrading both Submariner and OCP to supported versions. |
|
We upgraded the Submariner to 0.14.6 version, and even after the upgrade its the same error message we are seeing and some add on errors Site 1 Site 2 On site2 there is a difference from previous version output |
|
First of all sorry I wasn't clear in my previous answer, Submariner 0.14.x can work with OCP 4.10 but with CNI other than OVN-K. As suggested, please upgrade also OCP to version 4.11+, as |
|
@yboaron we have some concerns about updating the OCP 4.10 to 4.11, we want to get the submariner issue fixed through which a component that is dependent on the submariner will be fixed and then only we can proceed to the OCP upgrade. @tpantelis said that it looks like an incompatibility issue
So, which K8s version is compatible with Submariner 0.12.0? Another point I see is that the Submariner 0.12. and also 0.14. versions are trying to fetch a pod that has the label And we don't have any pods like that on both sites, But the Site 2 is able to detect the plugin Here I want to mention a point on what happened before this issue |
|
Well, I'm afraid it's a chicken and egg problem here, Submariner doesn't support OCP 4.10 with OVN-K as cni and you want to upgrade OCP after Submariner issue resolved. I think the best thing would be to uninstall Submariner, upgrade OCP, reinstall Submariner (of course upgrading submariner version). Maybe you can try resolve Submariner issue before upgrading OCP using the following workaround:
[1]
[2] |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ISSUE:
The Submariner is not able to establish the connection between the sites.
The error we are seeing in the diagnose all command is
Error Message:
The detected CNI network plugin ("") is not supported by Submariner. Supported network plugins: [generic canal-flannel weave-net OpenShiftSDN OVNKubernetes calico]SETUP:
Site 1: OCP 4.10
Site 2: OCP 4.10
Submariner version: v0.12.0
We are using OVNKubernetes
From the output of
oc get network/cluster -o yamlWe can see network type as this
networkType: OVNKubernetesOutputs of show all and diagnose all commands
Show all for Site 1
Show all for Site 2
Diagnose all for Site 1
Diagnose all for Site 2
The text was updated successfully, but these errors were encountered: