Currently whenever debug logging is turned on for juju, such as when running unit tests, we log the full contents of every lxd response:
<http://reports.vapour.ws/releases/3943/job/run-unit-tests-xenial-s390x/attempt/119>
With GIANT CLOUD CONFIG FILE and GIANT CERT BLOCK chopped out, it's still a lot of data:
[LOG] 0:03.523 DEBUG lxd Raw response: {"type":"sync","status":"Success","status_code":200,"metadata":[{"architecture":"s390x","config":{"user.juju-controller-uuid":"60194204-8034-45a8-86f5-068d239cffa3","user.juju-is-controller":"true","user.juju-model-uuid":"60194204-8034-45a8-86f5-068d239cffa3","user.user-data":"#cloud-config\n... GIANT CLOUD CONFIG FILE ...","volatile.base_image":"995321b9835c02947b8279bba7d4f8650fd113b02500ba201a3aea311611d208","volatile.eth0.hwaddr":"00:16:3e:5c:9c:8e","volatile.last_state.idmap":"[{\"Isuid\":true,\"Isgid\":false,\"Hostid\":100000,\"Nsid\":0,\"Maprange\":65536},{\"Isuid\":false,\"Isgid\":true,\"Hostid\":100000,\"Nsid\":0,\"Maprange\":65536}]"},"expanded_devices":{"eth0":{"name":"eth0","nictype":"bridged","parent":"lxdbr0","type":"nic"},"root":{"path":"/","type":"disk"}},"name":"juju-60194204-8034-45a8-86f5-068d239cffa3-machine-0","profiles":["default","juju-admin"],"stateful":false,"status":"Running","status_code":103}]}
[LOG] 0:03.539 WARNING juju.cmd.jujud.reboot Waiting for containers to shutdown: [lxd:juju-60194204-8034-45a8-86f5-068d239cffa3-machine-0]
[LOG] 0:04.546 DEBUG juju.tools.lxdclient connecting to LXD remote "local": ""
[LOG] 0:04.553 DEBUG lxd Raw response: {"type":"sync","status":"Success","status_code":200,"metadata":{"api_extensions":[],"api_status":"stable","api_version":"1.0","auth":"trusted","config":{"core.https_address":"[::]","core.proxy_ignore_hosts":"cloud-images.ubuntu.com"},"environment":{"addresses":["10.13.6.5:8443","10.0.3.1:8443","192.168.122.1:8443","10.0.8.1:8443"],"architectures":["s390x"],"certificate":"-----BEGIN CERTIFICATE-----... GIANT CERT BLOCK ...-----END CERTIFICATE-----\n","driver":"lxc","driver_version":"2.0.0","kernel":"Linux","kernel_architecture":"s390x","kernel_version":"4.4.0-17-generic","server":"lxd","server_pid":230810,"server_version":"2.0.0","storage":"dir","storage_version":""},"public":false}}
This comes from github.com/lxc/lxd client.go l102:
func ParseResponse(r *http.Response) (*Response, error) {
...
shared.Debugf("Raw response: %s", string(s))
...
}
Either that could be lowered to trace, or juju should poke the logging of the lxd client code.
This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.