Juju 1.25.10 non-HA cpu/ram usage spike (can't apply changes to env)
Bug #1667419 reported by
Alvaro Uria
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
This bug is related to bug 1587644. It happened in previous versions and continues to happen in Juju 1.25.10 (running on Xenial).
Juju state server runs in non-HA mode (a single juju-db instance).
https:/
https:/
Agents shows "dependency not available": https:/
* any action to services affected does nothing (ie. upgrade-charm, juju set)
* juju run --unit .. returns no socket to dial
By restarting jujud-machine-0, juju env goes back to normal.
This happens in a daily basis (sometimes, more than once a day).
Please let me know if you'd need more information. Thank you!
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #1 |
| Changed in juju-core: | |
| status: | New → Won't Fix |
To post a comment you must log in.
@Alvaro Uría,
With our current capacity as well as focus on Juju 2.1+, we will not be able to address this. I am marking it as Won't Fix since regular restart of jujud allows you to workaround this issue.