Exporting an un-committed bundle results in broken bundle
Bug #1446789 reported by
Charles Butler
on 2015-04-21
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | juju-gui |
High
|
Jeff Pihach | ||
Bug Description
When exporting an incomplete bundle from the GUI (services are added, but un-committed - complete with relations) - clicking export sends a broken bundle export to the user
envExport:
services: {}
relations:
- - "63169405$
- "92038280$
- - "9574579$:client"
- "81769329$:etcd"
- - "92038280$:network"
- "63169405$:network"
- - "9574579$:client"
- "63169405$:db"
- - "81769329$
- "92038280$:api"
series: precise
| Jeff Pihach (hatch) wrote : | #1 |
| Changed in juju-gui: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| Richard Harding (rharding) wrote : | #2 |
Jeff can you check if the WIP has this corrected and can be marked fix committed?
| Changed in juju-gui: | |
| assignee: | nobody → Jeff Pihach (hatch) |
| Jeff Pihach (hatch) wrote : | #3 |
Yes this was fixed. I created a duplicate bug earlier for this https:/
| Changed in juju-gui: | |
| status: | Triaged → Fix Committed |
Richard Harding (rharding)
on 2015-07-23
| Changed in juju-gui: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Thanks for this report. We should be ignoring any 'ghost' models when generating bundles.