-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
consider failing earlier when no device is provided #63
Comments
here is the output it generated: ` TASK [linux-system-roles.storage : define an empty list of volumes to be used in testing] ************************************* TASK [linux-system-roles.storage : include the appropriate backend tasks] ***************************************************** TASK [linux-system-roles.storage : get a list of rpm packages installed on host machine] ************************************** TASK [linux-system-roles.storage : make sure blivet is available] ************************************************************* TASK [linux-system-roles.storage : initialize internal facts] ***************************************************************** TASK [linux-system-roles.storage : Apply defaults to pools and volumes [1/6]] ************************************************* TASK [linux-system-roles.storage : Apply defaults to pools and volumes [2/6]] ************************************************* TASK [linux-system-roles.storage : Apply defaults to pools and volumes [3/6]] ************************************************* TASK [linux-system-roles.storage : Apply defaults to pools and volumes [4/6]] ************************************************* TASK [linux-system-roles.storage : Apply defaults to pools and volumes [5/6]] ************************************************* TASK [linux-system-roles.storage : Apply defaults to pools and volumes [6/6]] ************************************************* TASK [linux-system-roles.storage : debug] ************************************************************************************* TASK [linux-system-roles.storage : debug] ************************************************************************************* TASK [linux-system-roles.storage : manage the pools and volumes to match the specified state] ********************************* PLAY RECAP ******************************************************************************************************************** ` |
I accidentally executed a playbook using the storage role where I did not have a device defined. Would it be good to detect very early that a device name is NULL or invalid before executing so much of the logic? Below is the snippet from my playbook:
The text was updated successfully, but these errors were encountered: