[2.3b2] Rack and region controller versions still not updated
Bug #1721743 reported by
Mark Shuttleworth
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Unassigned | ||
Bug Description
Previously I reported a bug which resulted in unknown rack and region controller versions, and I commented on the proposed patch saying that it could not be the root cause since the issues it addressed were not relevant in my case.
Sure enough, the issue is still present in 2.3b2. Controller versions are not being updated correctly.
Please dig a little deeper.
Related branches
~blake-rouse/maas:fix-1722646
- Mike Pontillo (community): Approve
- MAAS Lander: Pending (unittests) requested
-
Diff: 36 lines (+14/-0)2 files modifiedsrc/metadataserver/api.py (+1/-0)
src/metadataserver/tests/test_api.py (+13/-0)
~mpontillo/maas:startup-race-conditions--bug-1730474
- MAAS Lander: Needs Fixing
- Blake Rouse (community): Approve
-
Diff: 209 lines (+71/-32)4 files modifiedsrc/maasserver/eventloop.py (+27/-2)
src/maasserver/plugin.py (+0/-5)
src/maasserver/tests/test_eventloop.py (+44/-2)
src/maasserver/tests/test_plugin.py (+0/-23)
Revision history for this message
| Mike Pontillo (mpontillo) wrote | #1 |
| Changed in maas: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| assignee: | nobody → Mike Pontillo (mpontillo) |
| milestone: | none → 2.3.0beta3 |
Revision history for this message
| Mike Pontillo (mpontillo) wrote | #2 |
Revision history for this message
| Mike Pontillo (mpontillo) wrote | #3 |
| Changed in maas: | |
| assignee: | Mike Pontillo (mpontillo) → nobody |
| Changed in maas: | |
| milestone: | 2.3.0beta3 → 2.3.0rc1 |
| Changed in maas: | |
| milestone: | 2.3.0rc1 → 2.3.0rc2 |
| importance: | High → Critical |
| Changed in maas: | |
| status: | Triaged → Fix Released |
To post a comment you must log in.
I thought maybe the pre-release of beta2 you're using didn't have the fix yet. We've actually landed two fixes for this issue so far, but I think I just found a third issue. So we'll dig a little deeper. ;-)