[2.1] please cleanup log format for new interface monitoring state
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Medium
|
Mike Pontillo |
Bug Description
When rackd starts, it generates a log entry that looks like the below. It should not look like an error log.
2016-09-30 17:33:12 [ClusterClient,
{'eth0': {'active': False, 'mdns': False, 'neighbour': False, 'params': None},
'eth1': {'active': False, 'mdns': False, 'neighbour': False, 'params': None},
'eth2': {'active': False, 'mdns': False, 'neighbour': False, 'params': None},
'eth3': {'active': False, 'mdns': False, 'neighbour': False, 'params': None},
'eth4': {'active': False, 'mdns': False, 'neighbour': False, 'params': None},
'eth5': {'active': False, 'mdns': False, 'neighbour': False, 'params': None}}
Related branches
- Blake Rouse (community): Approve
-
Diff: 38 lines (+5/-7)1 file modifiedsrc/provisioningserver/utils/services.py (+5/-7)
Changed in maas: | |
assignee: | nobody → Mike Pontillo (mpontillo) |
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → 2.1.0 |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |