Comment 3 for bug 1891076

New theory about this. Speculative, but based on troubleshooting we did today, it is possible that the scripts that bootstrap the juju agent on a machine can get into a state where they stall out, without exiting, while downloading the charm. Running juju sosreport seems to unstick things, which might have to do with it restarting some dbus related services.

We might need more timeouts, or otherwise better error detecting when something goes wrong with comms in the underlying system, and the early stages of downloading and dropping the agents and charm in place runs into trouble.