`juju export-bundle` lacks information
Bug #1802599 reported by
james beedy
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Ian Booth | ||
| 2.4 |
Fix Released
|
High
|
Ian Booth | ||
Bug Description
It seems the `export-bundle` command lacks machine constraints, application constraints, application options.
bundle I deployed https:/
juju export-bundle | https:/
| description: | updated |
Revision history for this message
| Ian Booth (wallyworld) wrote | #1 |
| Changed in juju: | |
| milestone: | none → 2.5-beta1 |
| status: | New → Triaged |
| importance: | Undecided → High |
Revision history for this message
| Ian Booth (wallyworld) wrote | #2 |
Revision history for this message
| Ian Booth (wallyworld) wrote | #3 |
| Changed in juju: | |
| assignee: | nobody → Ian Booth (wallyworld) |
| status: | Triaged → In Progress |
| 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 has been fixed as per this bug 1802033
When I fixed it, I tested with application constraints but I think it's the case the machine constraints may be missing. If so, that can be fixed against this bug.