Comment 2 for bug 1943738

To make the point another way.

While it's valid that we can install megacli separately, I'm not sure we should approve use of random paths to megacli found on the system to be run by a root cronjob this charm creates. We should consider longer term if this is still a requirement of our charm to use a determinate path for megacli to ensure we've vetted it through the checksums. If checksum checking is required, the path to megacli should be hard-coded only to where we install that binary, instead of using any copy of megacli in the $PATH.