Canonical Juju

  1. Bug #2007535
  2. Comment #2

Comment 2 for bug 2007535

Revision history for this message
Andrew Liaw (aliaw) wrote (last edit ):

I deployed the same version of charm on a different juju controller hosted on an openstack instance.

The `juju debug-log` was showing the unit logs, for example:

unit-runner-0: 12:37:57 INFO unit.runner/0.juju-log Download of runner binary from https://github.com/actions/runner/releases/download/v2.301.1/actions-runner-linux-x64-2.301.1.tar.gz return status code: 200

It seems this only happens on that controller/server, I have redeployed multiple times, but the unit log never shows up there.

I have also started up a tiny-bash charm on that controller/server, and that units log is not showing up in `juju debug-log` either. The unit log are present on the machine as well.

I think we can focus on using the tiny-bash charm as the charm for testing this bug as the other charm is in active development.