unclear error message when adding model with same name on different controller
Bug #1993518 reported by
Pietro Pasotti
This bug report is a duplicate of:
Bug #1994454: `add-model` for existing k8s namespace returns strange error message.
Edit
Remove
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
I just bootstrapped a new 3.0-rc2 controller and it won't let me create a model called 'secrets'. It fails with a super unclear error:
`ERROR failed to open kubernetes client: annotations map[...] for namespace "secrets" not valid must include map[...]`
Presumably this arises because I already have an identically-called model in another local microk8s controller (which uses 3.0-rc1, if that's relevant).
I can add models with other names without issues.
| Changed in juju: | |
| importance: | Undecided → Medium |
| milestone: | none → 3.2-beta1 |
| status: | New → Triaged |
| Changed in juju: | |
| milestone: | 3.2-beta1 → 3.2-rc1 |
Revision history for this message
| Jordan Barrett (barrettj12) wrote | #1 |
To post a comment you must log in.
Marked this as a duplicate of
https:/
Juju models ~= k8s namespaces, so Juju doesn't support having multiple models of the same name on one cluster, even if they are different controllers. The error message could definitely be improved though.