The MySQL server is running with the --read-only option so it cannot execute this statement
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MySQL InnoDB Cluster Charm |
Expired
|
Undecided
|
Unassigned |
Bug Description
Similar to https:/
s390x groovy deployment, nova-cloud-
https:/
Tl;DR
2020-10-29 10:15:16.616 1943 WARNING nova.scheduler.
juju status and cluster-status both look OK:
(tempest) jenkins@
unit-mysql-0:
UnitId: mysql/0
id: "107"
results:
cluster-status: '{"clusterName": "jujuCluster", "defaultReplica
"default", "primary": "10.13.3.196:3306", "ssl": "REQUIRED", "status": "OK",
"statusText": "Cluster is ONLINE and can tolerate up to ONE failure.", "topology":
{
{}, "replicationLag": null, "role": "HA", "status": "ONLINE", "version": "8.0.22"},
"
{}, "replicationLag": null, "role": "HA", "status": "ONLINE", "version": "8.0.22"},
"
{}, "replicationLag": null, "role": "HA", "status": "ONLINE", "version": "8.0.22"}},
"
status: completed
timing:
completed: 2020-10-29 10:36:03 +0000 UTC
enqueued: 2020-10-29 10:35:59 +0000 UTC
started: 2020-10-29 10:36:00 +0000 UTC
(tempest) jenkins@
Model Controller Cloud/Region Version SLA Timestamp
s390x-mosci-s390x s390x-mosci-s390x manual 2.8.5 unsupported 10:36:16Z
App Version Status Scale Charm Store Rev OS Notes
mysql 8.0.22 active 3 mysql-innodb-
Unit Workload Agent Machine Public address Ports Message
mysql/0 active idle 0/lxd/2 10.13.3.238 Unit is ready: Mode: R/O
mysql/1* active idle 1/lxd/3 10.13.3.223 Unit is ready: Mode: R/O
mysql/2 active idle 2/lxd/3 10.13.3.196 Unit is ready: Mode: R/W
I tried manually pointing the db connection string in nova.conf to the R/W host, but still got the same error.