juju-gui fails to parse exported bundle in beta-16

[Charles Butler]

I've used juju-gui to export this bundle, upon re-importing the bundle to re-deploy on another controller (moving from lxd to aws for example)

Screenshot of the error modal in the gui:
https://www.evernote.com/l/AX4GdEg57uZERY3ERHi8zSapcGgaDuMr4qAB/image.png

Error Modal Text:
The following errors occurred while retrieving bundle changes: cannot read bundle YAML: cannot unmarshal bundle data: yaml: unmarshal errors: line 1: cannot unmarshal !!str `xenial` into charm.legacyBundleData

The bundle in question:
http://paste.ubuntu.com/23120903/

Reproduceable by just attempting to import the bundle from the pastebin

[Anastasia (anastasia-macmood)]

@Charles
I wonder if it's GUI or juju bug :D
Could you please pastebin the content of original bundle definition you've deployed as well as the result of export operation? It will be helpful to compare the two for *interesting* characters...

[Anastasia (anastasia-macmood)]

Created juju-gui issue: https://github.com/juju/juju-gui/issues/2031

[Jeff Pihach (hatch)]

This is caused by an outdated bundle parsing library which is used with Juju 1. We're in the process of updating this library so this issue will be resolved once updated, likely next week.