juju status triggers some uninteresting DEBUG level messages
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
Low
|
Anastasia | ||
2.3 |
Fix Released
|
Low
|
Anastasia |
Bug Description
This seems to be the full context for 1 "juju status" in debug-log for a controller:
machine-0: 15:35:18 DEBUG juju.apiserver [251] API connection from 10.67.99.1:42938
machine-0: 15:35:18 DEBUG juju.apiserver <- [251] {"request-
machine-0: 15:35:18 DEBUG juju.apiserver model login: user admin has "superuser" for controller; "admin" for model 9b89c6e0-
machine-0: 15:35:18 DEBUG juju.apiserver model login: user-admin for 9b89c6e0-
machine-0: 15:35:18 DEBUG juju.apiserver -> [251] 25.793971ms {"request-
machine-0: 15:35:18 DEBUG juju.apiserver <- [251] user-admin {"request-
machine-0: 15:35:18 DEBUG juju.wrench couldn't read wrench directory: stat /var/lib/
machine-0: 15:35:18 DEBUG juju.apiserver.
machine-0: 15:35:18 DEBUG juju.apiserver.
machine-0: 15:35:18 DEBUG juju.apiserver.
machine-0: 15:35:18 DEBUG juju.apiserver.
machine-0: 15:35:18 DEBUG juju.apiserver.
machine-0: 15:35:18 DEBUG juju.apiserver.
machine-0: 15:35:18 DEBUG juju.apiserver -> [251] user-admin 12.610299ms {"request-
machine-0: 15:35:18 DEBUG juju.rpc error closing codec: write tcp 10.67.99.
machine-0: 15:35:18 DEBUG juju.apiserver [251] user-admin API connection terminated after 71.396946ms
The lines around Remote applications: map[], Offers: map[] and multiple NetworkInterfaces: map[... are probably not interesting to include normally.
summary: |
- juju status triggers some uninteresting DEBUG level mesasges + juju status triggers some uninteresting DEBUG level messages |
Changed in juju: | |
status: | Triaged → Fix Committed |
Changed in juju: | |
milestone: | none → 2.4-rc1 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
From the time when this bug was filed, to mentioning of the "controller" which is a Juju 2 terminology, I am guessing that this is not a Juju 1.25.x bug.
I am re-targeting this to "juju" project that tracks Juju 2 bugs.