Cluster members not added to Cluster, probably because port number is incorrect

soverbosch commented 5 years ago

BUG REPORT

Master

Environment:

Kubernetes version (use kubectl version): Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.3", GitCommit:"d2835416544f298c919e2ead3be3d0864b52323b", GitTreeState:"clean", BuildDate:"2018-02-09T21:51:54Z", GoVersion:"go1.9.4", Compiler:"gc", Platform:"darwin/amd64"} Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.8", GitCommit:"7eab6a49736cc7b01869a15f9f05dc5b49efb9fc", GitTreeState:"clean", BuildDate:"2018-09-14T15:54:20Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"} s

What happened?

Set up a cluster with tree members as described in tutorial

What you expected to happen?

I expected a cluster with three members, but it only has one member

How to reproduce it (as minimally and precisely as possible)?

Just follow the tutorial

Anything else we need to know?

Look at the portnumber of the REPLICATION_GROUP_SEEDS and XCom!?!?!? I suspect that the value given inpkg/resources/statefulsets/statefulset.go: replicationGroupPort = 13306 should be changed to 33061?

mysql-agent: Container ID:
Image: iad.ocir.io/oracle/mysql-agent:0.3.0 Image ID: docker-pullable://iad.ocir.io/oracle/mysql-agent@sha256:f86427ca0b65c004a5c00fbbe78dee7964e1acf7638238e27ef9a9c4082f1595 Port: Args: --v=4 State: Running Started: Thu, 01 Nov 2018 11:45:52 +0100 Ready: False Restart Count: 0 Liveness: http-get http://:10512/live delay=0s timeout=1s period=10s #success=1 #failure=3 Readiness: http-get http://:10512/ready delay=0s timeout=1s period=10s #success=1 #failure=3 Environment: MYSQL_CLUSTER_NAME: mysql POD_NAMESPACE: some-namespace (v1:metadata.namespace) REPLICATION_GROUP_SEEDS: mysql-0.mysql:13306,mysql-1.mysql:13306,mysql-2.mysql:13306

2018-11-01T10:45:38.153114Z 0 [Note] [MY-011735] [Repl] Plugin group_replication reported: '[GCS] XCom initialized and ready to accept incoming connections on port 33061'

soverbosch commented 5 years ago

After we changed the hard coded port in statefulset.go we got another problem, it concerns the whitelisting. The whitelist only contains the 10.X.X.X but this looks to be the ip address range of the pods but when the second members tries to become part of the cluster is has an ip address in another range (looks to be the node address).

tarlov commented 5 years ago

we are experiencing exactly the same issue. Do you expect the issue to be fixed soon?

oracle / mysql-operator