We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I don't know if this is reproducible, but I observed the following on an OpenStack environment
The juju status output is https://pastebin.canonical.com/p/s2qsq37Z83/ and log output from the unit that was primary is https://pastebin.canonical.com/p/pybWV6vV4T/
Two units are added okay.
See above
Operating system: jammy
Juju CLI: 2.9.44
Juju agent: 2.9.44
Charm revision: 196
LXD: N/A, this was on openstack
Juju debug log: see above
The text was updated successfully, but these errors were encountered:
https://warthogs.atlassian.net/browse/DPE-2722
Sorry, something went wrong.
also, as a note, the mysqld error logs on the primary unit are captured here: https://pastebin.canonical.com/p/g7r6MMJ5RV/
No branches or pull requests
Steps to reproduce
I don't know if this is reproducible, but I observed the following on an OpenStack environment
The juju status output is https://pastebin.canonical.com/p/s2qsq37Z83/ and log output from the unit that was primary is https://pastebin.canonical.com/p/pybWV6vV4T/
Expected behavior
Two units are added okay.
Actual behavior
See above
Versions
Operating system: jammy
Juju CLI: 2.9.44
Juju agent: 2.9.44
Charm revision: 196
LXD: N/A, this was on openstack
Log output
Juju debug log: see above
Additional context
The text was updated successfully, but these errors were encountered: