debug-log does not work with local provider on xenial + 1.25.0

[Ryan Harper]

Broken for me on Xenial amd64 with 1.25.0

I'm in a Xenial lxd container:

apt-get install juju-local
su - ubuntu
juju init
juju switch local
juju bootstrap
juju debug-log

ERROR

ubuntu@nestc1:~$ juju init
A boilerplate environment configuration file has been written to /home/ubuntu/.juju/environments.yaml.
Edit the file to configure your juju environment and run bootstrap.
ubuntu@nestc1:~$ juju switch local
-> local
ubuntu@nestc1:~$ juju bootstrap
Bootstrapping environment "local"
Starting new instance for initial state server
Building tools to upload (1.25.0.1-xenial-amd64)
Installing Juju agent on bootstrap instance
sudo: unable to resolve host nestc1
Logging to /home/ubuntu/.juju/local/cloud-init-output.log on remote host
Installing package: curl
Installing package: cpu-checker
Installing package: bridge-utils
Installing package: rsyslog-gnutls
Installing package: cloud-utils
Installing package: cloud-image-utils
Installing package: tmux
Bootstrapping Juju machine agent
Starting Juju machine agent (juju-agent-ubuntu-local)
Bootstrap agent installed
Waiting for API to become available
Waiting for API to become available
Bootstrap complete
ubuntu@nestc1:~$ juju status
environment: local
machines:
  "0":
    agent-state: started
    agent-version: 1.25.0.1
    dns-name: localhost
    instance-id: localhost
    series: xenial
    state-server-member-status: has-vote
services: {}
ubuntu@nestc1:~$ juju deploy ubuntu
Added charm "cs:trusty/ubuntu-5" to the environment.
ubuntu@nestc1:~$ juju debug-log
ERROR cannot open log file: open /var/log/juju-ubuntu-local/all-machines.log: no such file or directory

[Cheryl Jennings (cherylj)]

Looks to be a regression of bug #1464335

[Ursula Junque (ursinha)]

I can confirm this problem in wily with juju 1.25.3-wily-amd64, can reproduce consistently with the exact same steps as OP.

[Anastasia (anastasia-macmood)]

1.25 is in Critial-bugs only mode.

Juju 2.0 has had considerable improvements in the area. This bug is no longer applicable there.