Open vvaldez opened 8 years ago
I'd suggest that we create a specific task / role that does all the "pre-checks" up front to avoid having to run 1/3 through the execution before getting the info - this should include all "prereqs" that we are aware of that is needed - including "access to the hosting env", "necessary subscriptions", etc. etc.
When testing PR #168 end-to-end provisioning using a Fedora VM, I got this error:
I propose this be checked before starting the main playbook tasks/roles.