Model Operator In Juju using incorrect controller namespace
Bug #1919442 reported by
Thomas Miller
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Thomas Miller | ||
Bug Description
With Juju 2.8+ the model operator is no longer operating correctly on the controller model. Other models are not affected.
This is due to how the Kubernetes provider processes model names for the controller when working out which namespace to use.
ERROR github.
| Changed in juju: | |
| status: | New → In Progress |
| importance: | Undecided → High |
| assignee: | nobody → Thomas Miller (tlmiller) |
| milestone: | none → 2.8.10 |
| no longer affects: | juju/2.9 |
| Changed in juju: | |
| milestone: | 2.8.10 → 2.9-rc7 |
Revision history for this message
| Thomas Miller (tlmiller) wrote | #1 |
| Changed in juju: | |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This bug turned out to be a permission issue with namespace list missing. The caas provider requires this to work.
PR: https:/