deploy does not add relations transactionally
Bug #1072750 reported by
William Reade
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| juju-core |
Fix Released
|
High
|
William Reade | ||
Bug Description
If (eg) the connection fails mid-deploy, it is possible for us to add a service which *should* have a peer relation, but doesn't (because the relations are added after the service is created). This will be extremely confusing if it ever happens, and there's no way to rectify it from the UI. It would be much better if AddService were to check possible relations itself, and add all peer relations in the same transaction.
Revision history for this message
| William Reade (fwereade) wrote | #1 |
| Changed in juju-core: | |
| importance: | Undecided → High |
| status: | New → Triaged |
| Changed in juju-core: | |
| assignee: | nobody → William Reade (fwereade) |
| Changed in juju-core: | |
| status: | Triaged → In Progress |
| Changed in juju-core: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
(note that this is no longer theoretical: I had a power cut mid-deploy yesterday)