TestProvisionerObservesMachineJobs fails intermittently
Bug #1552589 reported by
John A Meinel
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Medium
|
John A Meinel | ||
juju-core |
Fix Released
|
Medium
|
Anastasia | ||
1.25 |
Fix Released
|
Medium
|
Anastasia |
Bug Description
I ran into this today. I spent some time debugging it, and it looks like sometimes it takes long enough for the NewProvisionerTask to start, that by the time it starts up, the configuration has already changed. So the task starts is HarvestAny mode and never sends the signal (there is never a change).
So we need the test to wait until NewProvisionerTask has started before it changes the configuration.
Changed in juju-core: | |
status: | In Progress → Fix Committed |
milestone: | none → 2.0-beta2 |
Changed in juju-core: | |
status: | Fix Committed → Fix Released |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.0-beta2 → none |
milestone: | none → 2.0-beta2 |
Changed in juju-core: | |
assignee: | nobody → Anastasia (anastasia-macmood) |
importance: | Undecided → Medium |
status: | New → Fix Released |
To post a comment you must log in.
I've been able to reproduce this on multiple machines by just doing it in parallel:
for i in `seq 4`; do go test -v -check.v -check.f ProvisionerObserves & done ; time wait