Canonical Juju

juju migrate on a JAAS model tries but then JAAS loses that info

Bug #1692721 reported by Jay R. Wren
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Expired
High
Unassigned

Bug Description

I'm not sure if `juju migrate` should work on a JAAS model, if it should then it should be an API call to `$JIMM_URL/'v2/model/evarlast/jctestmig5/migrate?controller=yellow/aws-us-east-2-jc3'`

But if `juju migrate` shouldn't work on a JAAS model then it should display a message to the user instead of trying and breaking.

Revision history for this message
Tim Penhey (thumper) wrote :

I don't see why it shouldn't work.

tags: added: model-migration
Changed in juju:
status: New → Triaged
importance: Undecided → High
Revision history for this message
Tim Penhey (thumper) wrote :

After chatting, I think that this is just a misunderstanding of the permissions required.

Model migration requires the user to be a superuser on both controllers, so in the JAAS case, normal users wouldn't have that permission so would not be able to migrate their models.

In JAAS, model migration will most likely be used by JAAS admins rather than normal users.

Changed in juju:
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for juju because there has been no activity for 60 days.]

Changed in juju:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.