model will not migrate - volumeAttachmentPlanInfo schema check failed

Bug #1834115 reported by james beedy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical Juju
Fix Released
High
Joseph Phillips
2.6
Fix Released
High
Joseph Phillips

Bug Description

Trying to migrate a model that houses an application which uses juju storage, I get this message telling me that model migration was aborted:

migrating: aborted, removing model from target controller: model data transfer failed, failed to import model into target controller: volumes: volume 0: volumeAttachmentPlan 0: volumeAttachmentPlanInfo schema check failed: volumePlanInfo schema check failed: device-attributes: expected map, got nothing

juju status - https://paste.ubuntu.com/p/qRypk2M36z/

Here is another juju status from another model with applications using juju storage - https://paste.ubuntu.com/p/nB4xRhkQs4/

Not really sure if there is anything I can provide that may lend further insight, or if this is just the current state of model migrations?

thanks

james beedy (jamesbeedy)
description: updated
Revision history for this message
Joseph Phillips (manadart) wrote :

This appears to be an omission from the juju/description logic.

For that type, defaults need to be supplied with "schema.Omit" when coercing fields that have "omitempty" tags.

Changed in juju:
importance: Undecided → High
status: New → Triaged
Changed in juju:
status: Triaged → In Progress
Revision history for this message
Joseph Phillips (manadart) wrote :
Changed in juju:
assignee: nobody → Joseph Phillips (manadart)
milestone: none → 2.7-beta1
Revision history for this message
Joseph Phillips (manadart) wrote :
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 report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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