unable to initiate network scanning
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
New
|
Critical
|
Unassigned |
Bug Description
I see this in my regiond log every 5 minutes:
2018-05-06 16:19:25 maasserver: [error] Error while calling ScanNetworks: Unable to get RPC connection for rack controller 'scylla' (8tsb7m).
2018-05-06 16:19:25 maasserver: [error] Error while calling ScanNetworks: Unable to get RPC connection for rack controller 'maas' (4y3h7n).
2018-05-06 16:19:25 maasserver: [error] Error while calling ScanNetworks: Unable to get RPC connection for rack controller 'charybdis' (fbgtn8).
2018-05-06 16:19:25 maasserver: [error] Error while calling ScanNetworks: Unable to get RPC connection for rack controller 'lapsi' (4nqs36).
2018-05-06 16:19:25 maasserver.
Of these controllers, all but Lapsi report they are healthy.
Changed in maas: | |
status: | New → Triaged |
status: | Triaged → In Progress |
importance: | Undecided → High |
importance: | High → Critical |
assignee: | nobody → Blake Rouse (blake-rouse) |
milestone: | none → 2.4.0rc1 |
summary: |
- [2.4b3] unable to initiate network scanning + unable to initiate network scanning |
Changed in maas: | |
assignee: | Blake Rouse (blake-rouse) → nobody |
status: | In Progress → New |
tags: | added: bug-council |
I don't think this is a duplicate of bug #1768575.
The string "ScanNetworks" doesn't even appear in that other bug report, and RPC is barely mentioned.
That thread is all about controllers being in a "degraded" state. My controller is marked as healthy, yet I still get the exact same problem as listed in this bug report.