it doesn't seem unreasonable to expect that if a charm uses a tool it ensures it is installed beforehand. The alternative is that end users are left trawling through logs for random error messages in the form of uncaught python exceptions and trying to figure out the intersect between the tools the charm writers decided to use and what their cloud provider decided to remove for their own undisclosed reasons. Essentially at the moment we put the load on our customers when the developers already have this knowledge, and in the process we expand our range of supported platforms from the narrow "known good" providers to any box with ubuntu installed. On 27 March 2018 at 20:40, Ryan Beisner