startup of machines updates container support on every startup
Bug #1812981 reported by
John A Meinel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
John A Meinel | ||
| 2.4 |
Won't Fix
|
High
|
Unassigned | ||
| 2.5 |
Fix Released
|
High
|
John A Meinel | ||
Bug Description
During a restart of a controller, we started to see messages like this:
2019-01-23 07:40:08 ERROR juju.state machine.go:2027 cannot update supported containers of machine 13: read tcp 10.25.2.
That would indicate that we are making a db write request for every machine to record that "yes, we still have exactly lxd+kvm support".
We should turn that record of information into "only write to the database if it is different than the current value".
That should improve some of the startup load.
Revision history for this message
| John A Meinel (jameinel) wrote | #1 |
| Changed in juju: | |
| milestone: | none → 2.6-beta1 |
| assignee: | nobody → John A Meinel (jameinel) |
| status: | Triaged → In Progress |
Revision history for this message
| John A Meinel (jameinel) wrote | #2 |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
https:/