juju-deployer bundlev4 format: numbering of machines not honoured
Bug #1507317 reported by
Darryl Weaver
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-deployer |
Won't Fix
|
Low
|
Unassigned | ||
Bug Description
juju-deployer 0.6.0
Using an openstack bundle with machines specified and machine placement does not work reliably.
The machines are listed in the bundle by machine number, but when juju-deployer deploys the new machines the order of deployment and hence machine number is not honoured, making numbered machine placement unreliable as the machines actually deployed do not match the numbering in the bundle.
For example, using a bundle that deploys a service to machine 4 and then additional services to LXC containers on machine 4, even though machine 4 is specified with constraints the deployment sometimes orders it as machine 5 and hence the service and containers end up on the wrong machine.
Example bundle included.
Revision history for this message
| Tom Haddon (mthaddon) wrote | #3 |
| Changed in juju-deployer: | |
| status: | New → Won't Fix |
| importance: | Undecided → Low |
To post a comment you must log in.
Marking as won't fix given the age of the bug and that native juju bundles would be used for this now