[2.0b4] external maas-rack-controller logs to syslog instead of maas.log
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Unassigned |
Bug Description
Connected an external rack controller, but it didn't log import of images:
ubuntu@
==> /var/log/
==> /var/log/
2016-05-03 22:41:04+0000 [Uninitialized] ClusterClient connection established (HOST:IPv4Addre
2016-05-03 22:41:04+0000 [Uninitialized] ClusterClient connection established (HOST:IPv4Addre
2016-05-03 22:41:05+0000 [ClusterClient,
2016-05-03 22:41:05+0000 [ClusterClient,
2016-05-03 22:41:05+0000 [ClusterClient,
2016-05-03 22:41:05+0000 [ClusterClient,
2016-05-03 22:41:34+0000 [-] Event-loop trusty-
2016-05-03 22:41:35+0000 [Uninitialized] ClusterClient connection established (HOST:IPv4Addre
2016-05-03 22:41:35+0000 [ClusterClient,
2016-05-03 22:41:35+0000 [ClusterClient,
Related branches
- Andres Rodriguez (community): Approve
- Brendan Donegan (community): Approve
-
Diff: 55 lines (+4/-5)3 files modifieddebian/control (+2/-3)
debian/maas-common.postinst (+2/-0)
debian/maas-region-api.postinst (+0/-2)
Changed in maas: | |
status: | New → Confirmed |
importance: | Undecided → High |
milestone: | none → 2.0.0 |
Changed in maas: | |
status: | Confirmed → Triaged |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
Looks like journalctl is stealing all the messages.