model migration credential check too restrictive
Bug #1850580 reported by
Ian Booth
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
High
|
Unassigned |
Bug Description
When migration a model, a check is done using reflect.
This is too restrictive and can cause a valid migration attempt to fail. In 2.7, k8s credentials gain a new attribute and so even though the target controller can access the k8s cluster just fine, a migration from a 2.6 model is aborted.
If the reason for checking the credential on the target controller is to ensure it can access the resources in the model being migrated, this needs to be done is a less naiive way.
Changed in juju: | |
milestone: | 2.7.1 → 2.7.2 |
Changed in juju: | |
milestone: | 2.7.2 → 2.7.3 |
Changed in juju: | |
milestone: | 2.7.3 → 2.7.4 |
Changed in juju: | |
milestone: | 2.7.4 → 2.7.5 |
Changed in juju: | |
milestone: | 2.7.5 → 2.7.6 |
Changed in juju: | |
milestone: | 2.7.6 → 2.8.1 |
Changed in juju: | |
milestone: | 2.8.1 → 2.8-next |
Changed in juju: | |
milestone: | 2.8-next → 2.8.10 |
Changed in juju: | |
milestone: | 2.8.10 → 2.8.11 |
Changed in juju: | |
milestone: | 2.8.11 → 2.9-next |
Changed in juju: | |
milestone: | 2.9-next → 3.2-beta1 |
Changed in juju: | |
milestone: | 3.2-beta1 → 3.2-rc1 |
Changed in juju: | |
milestone: | 3.2-rc1 → 3.2.0 |
Changed in juju: | |
milestone: | 3.2.0 → 3.2.1 |
Changed in juju: | |
milestone: | 3.2.1 → 3.2.2 |
Changed in juju: | |
milestone: | 3.2.2 → 3.2.3 |
Changed in juju: | |
milestone: | 3.2.3 → 3.2.4 |
To post a comment you must log in.
Also related to https:/ /bugs.launchpad .net/juju/ +bug/1850579