[2.3] Failure on controller refresh seem to be causing version to not get updated
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Blake Rouse |
Bug Description
I have 4 controllers:
- 2 Region Rack
- 2 Rack Controllers
The first even region/rack that was installed, successfully reports the version. All the other controllers didn't report the version and it continued to be shown as unknown, even though I did upgrades or restart. However, I noticed something interesting:
- On the second Region/Rack, I noticed that refresh was failing on 00-maas-
- On the two rack controllers, I noticed that the version was still not reported. Also noticed that the script in question (00-maas-
Another unrelated issue I've noticed, is that controllers would be be on a degraded state constantly. After I upgraded to the version of MAAS that disables 00-maas-
Related branches
- Andres Rodriguez (community): Approve
-
Diff: 38 lines (+4/-0)2 files modifiedsrc/provisioningserver/rpc/cluster.py (+1/-0)
src/provisioningserver/rpc/tests/test_clusterservice.py (+3/-0)
Changed in maas: | |
milestone: | none → 2.3.0beta2 |
importance: | Undecided → Critical |
status: | New → Triaged |
summary: |
[2.3] Failure on controller refresh seem to be causing version to not - get update + get updated |
Changed in maas: | |
status: | Triaged → In Progress |
assignee: | nobody → Blake Rouse (blake-rouse) |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |