-
Bug
-
Resolution: Not a Bug
-
Normal
-
None
-
ACM 2.6.0, ACM 2.8.0, ACM 2.7.Z
-
False
-
None
-
False
-
-
-
Submariner Sprint 2023-7
-
Moderate
-
No
Description of problem:
ACM 2.8 / Submariner 0.15.0
When creating a clusterset, a broker associated with the clusterset created as well.
The broker configmap stores the globalnet metadata (clusterinfo) of each cluster submariner installed on:
cluster_id and global_cidr.
$ oc -n submariner-broker get configmap submariner-globalnet-info -o yaml apiVersion: v1 data: clusterinfo: "[\n\t{\n\t\t\"cluster_id\": \"mbabushk-gcp\",\n\t\t\"global_cidr\": [\n\t\t\t\"242.0.0.0/16\"\n\t\t]\n\t},\n\t{\n\t\t\"cluster_id\": \"mbabushk-azure\",\n\t\t\"global_cidr\": [\n\t\t\t\"242.1.0.0/16\"\n\t\t]\n\t},\n\t{\n\t\t\"cluster_id\": \"mbabushk-aws\",\n\t\t\"global_cidr\": [\n\t\t\t\"242.2.0.0/16\"\n\t\t]\n\t}\n]" globalnetCidrRange: '"242.0.0.0/8"' globalnetClusterSize: "65536" globalnetEnabled: "true" kind: ConfigMap metadata: creationTimestamp: "2023-06-04T07:48:26Z" labels: cluster.open-cluster-management.io/backup: submariner component: submariner-globalnet name: submariner-globalnet-info namespace: submariner-broker resourceVersion: "92975" uid: d104a6d4-c2a7-4164-b71e-523fcc1bcbc6
When submariner uninstalled from one of the clusters, the cluster_id of that cluster should be removed from the "clusterinfo" configmap metadata, but it's not removed.
The state of all installed clusters:
- lastTransitionTime: "2023-06-04T09:01:05Z" message: |- The connection between clusters "mbabushk-aws" and "mbabushk-gcp" is established The connection between clusters "mbabushk-aws" and "mbabushk-azure" is established reason: ConnectionsEstablished status: "False" type: SubmarinerConnectionDegraded
The state of the submarienr when one of the clusters removed:
- lastTransitionTime: "2023-06-04T09:01:05Z" message: The connection between clusters "mbabushk-aws" and "mbabushk-azure" is established reason: ConnectionsEstablished status: "False" type: SubmarinerConnectionDegraded
Submariner on cluster "mbabushk-gcp" has been uninstalled.
But the metadata still keep that cluster info:
$ oc -n submariner-broker get configmap submariner-globalnet-info -o yaml apiVersion: v1 data: clusterinfo: "[\n\t{\n\t\t\"cluster_id\": \"mbabushk-gcp\",\n\t\t\"global_cidr\": [\n\t\t\t\"242.0.0.0/16\"\n\t\t]\n\t},\n\t{\n\t\t\"cluster_id\": \"mbabushk-azure\",\n\t\t\"global_cidr\": [\n\t\t\t\"242.1.0.0/16\"\n\t\t]\n\t},\n\t{\n\t\t\"cluster_id\": \"mbabushk-aws\",\n\t\t\"global_cidr\": [\n\t\t\t\"242.2.0.0/16\"\n\t\t]\n\t}\n]" globalnetCidrRange: '"242.0.0.0/8"' globalnetClusterSize: "65536" globalnetEnabled: "true" kind: ConfigMap metadata: creationTimestamp: "2023-06-04T07:48:26Z" labels: cluster.open-cluster-management.io/backup: submariner component: submariner-globalnet name: submariner-globalnet-info namespace: submariner-broker resourceVersion: "92975" uid: d104a6d4-c2a7-4164-b71e-523fcc1bcbc6
The bug could lead into an issue when I'm uninstalling submariner from all the clusters within the clusterset and then re-installing it back on some of the clusters.
The connection agent will try to establish connection of all of the clusters including the cluster that I did not install submariner on, because its metadata exists within the broker globalnet info.
Attaching "submariner-addon" pod log.
