Skip to content
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

Going from one to three units put the charm in an error state #335

Open
mthaddon opened this issue Oct 6, 2023 · 2 comments
Open

Going from one to three units put the charm in an error state #335

mthaddon opened this issue Oct 6, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@mthaddon
Copy link

mthaddon commented Oct 6, 2023

Steps to reproduce

I don't know if this is reproducible, but I observed the following on an OpenStack environment

  1. Deployed one unit.
  2. Related wordpress-k8s to it via cross-model relations
  3. Confirmed the application was working as expected
  4. Added two units to mysql
  5. Charm went into error status.

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

@mthaddon mthaddon added the bug Something isn't working label Oct 6, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Oct 6, 2023

@shayancanonical
Copy link
Contributor

also, as a note, the mysqld error logs on the primary unit are captured here: https://pastebin.canonical.com/p/g7r6MMJ5RV/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants