bosh logs -f returns tail errors with zookeeper-release

[drnic]

I have a default https://github.com/cppforlife/zookeeper-release deployment but bosh logs -f is only showing tail errors:

> bosh -v
version 2.0.38-98d425d-2017-09-11T23:18:53Z
> bosh -d zookeeper logs -f

returns tail errors for each instance:

zookeeper/6e8b7728-88fd-4da1-8191-66546a80a8f6: stdout | tail: cannot open ‘/var/vcap/sys/log/**/*.log’ for reading: No such file or directory
zookeeper/6e8b7728-88fd-4da1-8191-66546a80a8f6: stdout | tail: cannot open ‘/var/vcap/sys/log/*.log’ for reading: No such file or directory
zookeeper/6e8b7728-88fd-4da1-8191-66546a80a8f6: stdout | tail: cannot watch parent directory of ‘/var/vcap/sys/log/**/*.log’: No such file or directory
zookeeper/6e8b7728-88fd-4da1-8191-66546a80a8f6: stdout | tail: inotify cannot be used, reverting to polling

The logs available on a zookeeper vm are:

$ cd /var/vcap/sys/log/zookeeper
$ tree
.
├── pre-start.stderr.log
├── pre-start.stdout.log
├── stderr.log
├── stdout.log
└── version-2

1 directory, 4 files

Restricting to --job zookeeper (which is a different code path in bosh-cli) gives a similar but diff error:

$ bosh logs -f --job zookeeper
...
zookeeper/b5923bcf-3106-4b7f-8eb4-212b5877ef81: stdout | tail: cannot open ‘/var/vcap/sys/log/zookeeper/*.log’ for reading: No such file or directory

Running tail -f /var/vcap/sys/log/zookeeper/*.log inside the VM as root or vcap user works as expected.

[belinda-liu]

Fixed in #446