cross network rules cause configure network to fail when source named-network doesn't exist
Bug #357440 reported by
chris grzegorczyk
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Eucalyptus |
Fix Released
|
High
|
chris grzegorczyk | ||
Bug Description
1. Create group A and group B.
2. Authorize ingress from B to A.
3. Run instances on network A (and none on B).
Ingress rules fail to be applied because network B is not actually running.
| Changed in eucalyptus: | |
| assignee: | nobody → chris-grze |
| importance: | Undecided → High |
| status: | New → Confirmed |
| Changed in eucalyptus: | |
| status: | Confirmed → Fix Committed |
| Changed in eucalyptus: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
