[2.1] Rack(relay) Controller is rejected after upgrade to 2.1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Mike Pontillo |
Bug Description
Update
======
After upgrading a MAAS with 2 rack (relay) controllers, the Rack (relay) Controller running in the same machine as the Region, is being rejected and it is unable to connect to the region:
==> /var/log/
2016-09-01 10:33:44 [ClusterClient,
2016-09-01 10:33:44 [ClusterClient,
==> /var/log/
2016-09-01 10:33:44 [RegionServer,
2016-09-01 10:33:44 [RegionServer,
Also, maas.log doesn't show a message of it being rejected, it only shows:
Aug 27 17:06:01 maas maas.rpc.
That said, the second Rack (relay) Controller that is running standalone is successfully connected to the Region (although, service tracking is not working, which is a known bug for alpha 1).
Original Report
===============
Upon upgrade to 2.1a1 I see repeated errors like this in the logs (every two seconds by the looks of it):
Aug 27 17:06:01 maas maas.rpc.
Related branches
- LaMont Jones (community): Approve
-
Diff: 67 lines (+23/-10)2 files modifiedsrc/maasserver/models/node.py (+14/-10)
src/maasserver/models/tests/test_node.py (+9/-0)
summary: |
- Repeated log errors about an existing rack controller + [2.1] Rack Controller is rejected after upgrade to 2.1 |
summary: |
- [2.1] Rack Controller is rejected after upgrade to 2.1 + [2.1] Rack(relay) Controller is rejected after upgrade to 2.1 |
description: | updated |
Changed in maas: | |
milestone: | none → 2.1.0 |
importance: | Undecided → Critical |
status: | New → Confirmed |
description: | updated |
Changed in maas: | |
status: | Confirmed → Triaged |
assignee: | nobody → Mike Pontillo (mpontillo) |
status: | Triaged → In Progress |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
http:// pastebin. ubuntu. com/23120940/