We saw this on the Canonistack BOS01 JAAS controllers, they're running Bionic. No nested lxd containers.
Running the command above works:
| ubuntu@juju-3e49f3-controller-1:~$ /bin/systemctl list-unit-files --no-legend --no-page -l -t service | grep -o -P '^\w[\S]*(?=\.service)' | wc -l | 224
Could it be related to load at the time? Is that 'Connection timed out' from systemctl itself? Or Juju waiting from output and timing out (Go channels/goroutine or whatever it is)?
We saw this on the Canonistack BOS01 JAAS controllers, they're running Bionic. No nested lxd containers.
Running the command above works:
| ubuntu@ juju-3e49f3- controller- 1:~$ /bin/systemctl list-unit-files --no-legend --no-page -l -t service | grep -o -P '^\w[\S] *(?=\.service) ' | wc -l
| 224
Could it be related to load at the time? Is that 'Connection timed out' from systemctl itself? Or Juju waiting from output and timing out (Go channels/goroutine or whatever it is)?