-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Charm stuck in Initialising mysqld
#310
Comments
Another run with debug logs: relation data: jhack show-relation mysql:database-peers --format json
{
"type": "peer",
"endpoints": [
{
"url": "mysql:database-peers",
"relation_id": 8,
"meta": {
"scale": 1,
"units": [
0
],
"leader_id": 0
},
"application_data": {
"cluster-name": "cluster-58a3017b136b545d62e8d3b9fb03c6eb",
"cluster-set-domain-name": "cluster-set-58a3017b136b545d62e8d3b9fb03c6eb",
"secret-id": "secret://4cad2829-f96b-45b8-8277-47786a891317/ck8o22698o8tjbgj5gtg"
},
"units_data": {
"mysql/0": {
"unit-status": "alive"
}
},
"model": null,
"other_model": null
}
]
} |
@gboutry thanks for the report. Did you saw that on other juju version? |
I haven't, but I can try more |
I was using microk8s 1.24/stable with Juju 3.1.6, and kept facing this issue. Moving to microk8s 1.26/stable or 1.26-strict/stable worked. |
I have unfortunately moved to 1.26 microk8s ... will update if I manage to get something running somewhere. |
I have not seen this error for weeks now, seems fixed from my side. |
I have found something weird ... this problem occurs every time if I enable the |
Dear all
|
Duplicates #535 |
Steps to reproduce
Expected behavior
Charm should become ready
Actual behavior
Charm has an unhandled exception and never becomes ready
Versions
Operating system: Ubuntu 22.04.3 LTS
Juju CLI: 3.2.3-genericlinux-amd64
Juju agent: 3.2.3
Charm revision: 99 (8.0/candidate)
microk8s: MicroK8s v1.26.8 revision 5883
Log output
Status log:
Additional context
I does not happen at every run, only some of them, but if it happens, mysql never become ready.
The text was updated successfully, but these errors were encountered: