systemd broadcast message spam during test run
Bug #1456258 reported by
Michael Foord
on 2015-05-18
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | juju-core |
Medium
|
Unassigned | ||
| | 1.23 |
Medium
|
Unassigned | ||
| | 1.24 |
Medium
|
Unassigned | ||
Bug Description
During a full test run on vivid there is systemd broadcast message spam (in one large chunk) to all open terminal windows.
e.g.
ok github.
Broadcast message from systemd-
[6231]: 2015-05-18 15:21:57 DEBUG juju.apiserver apiserver.go:273 <- [7] machine-1 {"RequestId"
| Eric Snow (ericsnowcurrently) wrote : | #1 |
| Changed in juju-core: | |
| milestone: | none → 1.25.0 |
| milestone: | 1.25.0 → none |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| Eric Snow (ericsnowcurrently) wrote : | #2 |
The message implies that some log entries are getting written to stdout, which systemd catches and writes to its log (and stdout).
Anastasia (anastasia-macmood)
on 2016-09-02
| tags: | removed: unit-tests |
Anastasia (anastasia-macmood)
on 2016-10-17
| Changed in juju-core: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.


Note that this only happens when running the juju test suite on a host running systemd. Normal use of juju does not appear to manifest the "stdout spam".