rancher: Rancher database migrations fail on clean install on MySQL cluster setup.
Rancher versions: rancher/server: stable: v1.6.2 and latest: v1.6.3 rancher/agent: v1.2.2
Infrastructure Stack versions: healthcheck: ipsec: network-services: scheduler: kubernetes (if applicable):
Docker version: (docker version,docker info preferred)
core@p1 ~ $ docker info
Containers: 1
Running: 1
Paused: 0
Stopped: 0
Images: 29
Server Version: 1.12.6
Storage Driver: overlay
Backing Filesystem: extfs
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: null host bridge overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options: seccomp selinux
Kernel Version: 4.11.9-coreos
Operating System: Container Linux by CoreOS 1409.6.0 (Ladybug)
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.788 GiB
Name: p1.packet.nlze.nl
ID: M2OK:UBUZ:HFJV:4EKZ:BJCW:6H5E:NA4X:5JNJ:2QNV:TLTV:JEL3:ETFQ
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Insecure Registries:
127.0.0.0/8
Operating system and kernel: (cat /etc/os-release, uname -r preferred)
4.11.9-coreos
Type/provider of hosts: (VirtualBox/Bare-metal/AWS/GCE/DO)
Baremetal (Packet)
Setup details: (single node rancher vs. HA rancher, internal DB vs. external DB)
HA (an attempt to)
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Steps to Reproduce:
action
docker run -d --restart=unless-stopped -p 8080:8080 \
-p 9345:9345 \
--name rancher_server \
rancher/server \
--db-host ${DB_HOST} \
--db-port ${DB_PORT} \
--db-user admin --db-pass ${DB_PASS} \
--db-name ${DB_NAME} \
--advertise-address ${ADVERTISE_ADDRESS}
results
The problem is that on a clean install; connecting to a remote MySQL database on compose.io fails with what seems to errors on migrations.
Yes, compose.io is a hosted, managed, HIghly availble MySQL database (cluster). But the database in question seems to confirm to all requirements.
https://gist.github.com/dhrp/4ce9c5cd7f52921f77253333437e33d6
After I run script command to start rancher below; connecting to this remote MySQL database, it stops with many errors. See gist below. In the database this is created, so it fails on creating the account table.
mysql details
mysql> show tables;
+--------------------------+
| Tables_in_rancher_packet |
+--------------------------+
| DATABASECHANGELOG |
| DATABASECHANGELOGLOCK |
| account |
+--------------------------+
3 rows in set (0.01 sec)
mysql> show variables;
InnoDB with Barracuda and dynamic tables is set. See all details in the following gist:
https://gist.github.com/dhrp/d034cba2999c51596faaf5169ba814b7
Results:
Here is the logoutput: https://gist.github.com/dhrp/4ce9c5cd7f52921f77253333437e33d6
I don’t know or understand what goes wrong here. When I let rancher start with it’s local database it works fine. But obviously I want at HA setup.
like #9279, but with a clean install
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 22 (7 by maintainers)
Compose support got back to me with the comment that they see this in the logs:
'./application.log.1:2017-07-11T15:05:45.000+00:00 gcp-europe-west1-data mysql375: mysql.22 | 2017-07-11T15:05:45.564857Z 8011 [ERROR] Plugin group_replication reported: ‘Table DATABASECHANGELOG does not have any PRIMARY KEY. This is not compatible with Group Replication’
@superseb, here you go.