TestWorkerDiscoversSpaces no subnets found
Bug #1545057 reported by
Curtis Hovey
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
Medium
|
Michael Foord | ||
Bug Description
As seen in
http://
worker_test.go:179:
c.Check(
... obtained int = 0
... expected int = 1
Revision history for this message
| Michael Foord (mfoord) wrote | #1 |
Revision history for this message
| Michael Foord (mfoord) wrote | #2 |
| Changed in juju-core: | |
| assignee: | nobody → Michael Foord (mfoord) |
| status: | Triaged → In Progress |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| milestone: | none → 2.0-beta3 |
| tags: | added: tech-debt |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
| tags: | added: 2.0-count |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.0-beta3 → none |
| milestone: | none → 2.0-beta3 |
To post a comment you must log in.
It looks like we can get the right number of spaces added before all the subnets have been added (subnets must be added following the space creation as the subnets reference the space). This means the test finds the spaces but not the subnets.
Instead that test should wait for discovery to complete instead of waiting until there are four spaces.