Hi Dave,
I am assuming that you used "Add volume to vFiler" certified command for adding volume to the vfiler.
This command in WFA 2.0 supports self-imposed WFA cache updates for volume table and vfiler table. So, using this command updates the volume table with the association of volume to the vfiler. In general, the self-imposed WFA cache updates are specific to each command, and works only with certified commands. Moreover, updates done by each command inside a workflow are not visible to other commands of that workflow (in WFA 2.0). Those updates are visible only in next workflows.
1. In your test scenario 2, the error message "vfiler vfiler0 does not have storage on volume DavidTest02" is misleading as you said, and I checked that this is a bug with the "Remove Volume" certified command code. We will fix this.
2. For the test scenarios 2 and 3, have you done all of these operations (create, adding to vfiler and deletion) in the single workflow? If yes, cache updates by previous commands in the workflow are not seen by the other commands of that workflow. So the finder used in "remove volume" command details will not find the volume created by "Create volume" command. You could instead use the same volume object that is defined in "Create Volume" command details for "Remove volume" command, instead of finding it.
If you have done removal of the volume in a separate workflow, then ideally it should work. Finder should locate this volume within this workflow even though WFA cache is not refreshed, as self-imposed updates of the previous workflow should be visible in this workflow. I tried this in WFA 2.0, and works fine.
-Chaitanya