The cluster takes a long time to connect to the region.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Gavin Panella | ||
1.5 |
Fix Released
|
High
|
Gavin Panella | ||
maas (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Trusty |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
On a new MAAS instance, it can take up to a minute for the local cluster to connect to the region. Until the cluster is connected, MAAS is very much unusable because it doesn't have any architecture or power type registered.
[Impact]
* Longer than necessary downtime to wait for connection from cluster to region is changed to faster frequency rather than a random range.
* Means users need not wait as long to initially connect and run useful services
[Test Case]
* Start region and cluster on two separate machines, wait for the two to actaully connect to eachother
[Regression Potential]
* Minimal, both maas-CI integration and unit tests running, only effects timers for frequency of rpcs
Related branches
- Raphaël Badin (community): Approve
-
Diff: 189 lines (+89/-46)2 files modifiedsrc/provisioningserver/rpc/clusterservice.py (+42/-12)
src/provisioningserver/rpc/tests/test_clusterservice.py (+47/-34)
- Gavin Panella (community): Approve
-
Diff: 189 lines (+89/-46)2 files modifiedsrc/provisioningserver/rpc/clusterservice.py (+42/-12)
src/provisioningserver/rpc/tests/test_clusterservice.py (+47/-34)
Changed in maas: | |
assignee: | nobody → Gavin Panella (allenap) |
Changed in maas: | |
status: | Triaged → Fix Committed |
description: | updated |
Changed in maas (Ubuntu): | |
status: | New → Fix Released |
branch which fixes this and other 1.5.2 release bugs is linked to bug #1325038