Juju GUI not managing bundle import properly

Bug #1468849 reported by Samuel Cozannet
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
juju-gui
Triaged
High
Madison Scott-Clary

Bug Description

Hello,

I noticed the bundles that are exported by the GUI are now different from what they used to be. They now contain the list of machines along with constraints at the machine level, not the service level.

However, the bundles in the store itself do not contain this information (machines are not in the yaml file)

* When deploying a bundle from the store, there is an additional step (commit) to take to really deploy, that was not needed in the past
* But when drag'n'dropping a bundle or using import button:
  * if the bundle was exported by the current GUI, with machines references, it deploys OK
  * if format in the charm store or previous bundles (without machine constraints), the deployment fails and the GUI says

Error generating changeSet

There was an error generating the changeSet. See browser console for additional information

The console itself says:
Error: Invalid value for <g> attribute transform="translate(undefined,undefined)"

To reproduce:
* Take any bundle in the store and deploy + commit deployment.
* Then export
* Then edit the yaml file to remove the machines that are listed, and remove the "to: XXX" in service description.
* Then try to import again.

Some bundles that would also fail are available here : https://github.com/SaMnCo/bundle-sentiment-analysis

Revision history for this message
Samuel Cozannet (samuel-cozannet) wrote :
Revision history for this message
Richard Harding (rharding) wrote :

Since you removed the machine placement you've left in the -to flags so it's going to error as the bundle is no longer valid. You have placement directives, but no machines to place them on.

This describes the bundle transition that took place and has notes on the machine specification.
https://github.com/juju/charmstore/blob/v4/docs/bundles.md

Please let me know if I'm misunderstanding the problem or if this does not help.

Changed in juju-gui:
status: New → Invalid
Revision history for this message
Samuel Cozannet (samuel-cozannet) wrote :

Ah, I didn't notice the export had the "--to" as well.

This one is a classic bundle extracted from the charm store. It also fails.

I'll edit my initial bug to improve the process.

description: updated
Revision history for this message
Richard Harding (rharding) wrote :

Thanks Samuel, so I can confirm that the code we used to have to accept both v3 and v4 bundles has a regression in the last GUI release. The next release was going to be tomorrow, but we'll work to get this fix up before we do that release.

If you need something today, the best thing is to move to the v4 format, and eventually you'll want to do that anyway. However, it was not intended to break all the v3 ones at this time so we'll get an update out asap.

Changed in juju-gui:
status: Invalid → Confirmed
importance: Undecided → High
status: Confirmed → Triaged
assignee: nobody → Madison Scott-Clary (makyo)
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.