@Udara
Great. Once you finish the tests, let us know the results.
@Akila
I know you are facing some merge conflict issues when you try to push your
changes. Please let us know once you are done.I think we can start the
4.1.3 release work after that.
Thanks,
Gayan
On Sun, Sep 20, 2015 at 6:14 AM,
Hi Gayan,
I performed a quick smoke test with two clusters and it was successful.
I will do some more tests and let you know the results.
On Sat, Sep 19, 2015 at 10:47 AM, Gayan Gunarathne wrote:
> Additionally we have removed the kubernetesClusterId from the
> ClusterContext and added the kube
Additionally we have removed the kubernetesClusterId from the
ClusterContext and added the kubernetesClusterId to the
kuberentesServices.Idea behind that is we can't have kubernetesClusterId in
ClusterContext as there can be one or more Kubernetes clusters in the case
of multi-region deployment.But
I had an offline discussion on this with Gayan. It looks like the root
cause of this problem is that we have added Kubernetes Cluster ID to the
Cluster Context. This seems to be incorrect. A cluster can have multiple
Kubernetes Clusters if its a multi-region deployment.
We need to remove the prope
We might need to use cluster id and network partition id as the key of this
map.
Once we are done with this fix shall we do 4.1.3 release build?
Thanks
On Friday, September 18, 2015, Gayan Gunarathne wrote:
> When we try to un-deploy the application in a multi region deployment, It
> will thro
When we try to un-deploy the application in a multi region deployment, It
will throw the following exception.
javax.ws.rs.WebApplicationException: HTTP 404 pods "tomcatr1-pod-1" not
found
Issue seems like,in a topology service clusterIdClusterMap has only one
value even there is two clusters in t
