Be more explicit when keeping existing infrastructure in sync with config
Bug #1897933 reported by
Kenneth Koski
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Won't Fix
|
High
|
Unassigned | ||
Bug Description
A follow-up to https:/
It would be really nice if Juju was much more verbose when it attempts to keep existing infrastructure in sync with the pod spec. Right now, it periodically applies the existing pod spec, and from what I can tell, blindly updating what's there. It would help diagnose situations like the linked one much more quickly if Juju was smarter and had some logging like:
INFO - Found changing in existing infrastructure
INFO - Diff of existing and expected infrastructure:
INFO - <diff>
INFO - Reapplying expected infrastructure
| Changed in juju: | |
| milestone: | none → 2.9-beta1 |
| tags: | added: k8s |
| Changed in juju: | |
| importance: | Undecided → High |
| status: | New → Triaged |
| Changed in juju: | |
| milestone: | 2.9-beta1 → 2.9-rc1 |
| tags: | added: bitesize |
| Changed in juju: | |
| milestone: | 2.9-rc1 → 2.9.1 |
| Changed in juju: | |
| milestone: | 2.9.1 → 2.9.2 |
| Changed in juju: | |
| milestone: | 2.9.2 → 2.9.3 |
| Changed in juju: | |
| milestone: | 2.9.3 → 2.9.5 |
| Changed in juju: | |
| milestone: | 2.9.5 → 2.9-next |
Revision history for this message
| Harry Pidcock (hpidcock) wrote | #1 |
| Changed in juju: | |
| milestone: | 2.9-next → none |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
We are unlikely to make this improvement to the soon to be deprecated pod spec charming.