The problem is a little hard to diagnose with the current output.
1) are you able to rerun the tests with the following config?
logging-config=juju.container.lxc=TRACE
- you can either do this at bootstrap time like this:
juju bootstrap --logging-config=juju.container.lxc=TRACE;juju=DEBUG
- or on a running environment like this:
juju set-env 'logging-config=juju.container.lxc=TRACE;juju=DEBUG'
2) Has this ever passed before? If so, what other config settings have changed?
The problem is a little hard to diagnose with the current output.
1) are you able to rerun the tests with the following config? config= juju.container. lxc=TRACE config= juju.container. lxc=TRACE; juju=DEBUG config= juju.container. lxc=TRACE; juju=DEBUG'
logging-
- you can either do this at bootstrap time like this:
juju bootstrap --logging-
- or on a running environment like this:
juju set-env 'logging-
2) Has this ever passed before? If so, what other config settings have changed?
3) Can we also get the values from /etc/lxc ?