I am encountering unexpected behavior with the “Search or Define” command block when searching for an aggregate, AND using the “If…was not found” with “Fill-in attributes for… and execute the command.” I know this will be a little wordy - I’m just trying to convey relevant information (hopefully).
If I use the option to just disable the command (default behavior) if an aggregate meeting the criteria was not found, then things work exactly as expected. That being if an aggregate meeting the criteria was found, then it returns that, otherwise the command is disabled. However, as soon as I use the option to fill in attributes then the command appears to ALWAYS be disabled.
A difference in behavior can be observed in the Advanced tab (let’s assume “myaggr” is the variable name here):
When using the default behavior (disable command if a suitable aggregate was not found), then under the advanced tab we see “Execute this command: If the variable myaggr was found AND Always”
However, when using the fill-in attributes option then this reflects: “Execute this command: If the variable myaggr was not found AND Always.”
Since I haven’t stated what I expect to see yet, it would be that if I select the “fill-in attributes…” option then the command will search on the criteria given and return an aggregate meeting that criteria. If an aggregate was not found meeting that criteria, then it would return whatever aggregate that I have filled in.
I hope that all makes sense.
-WFA 4.0 on Server 2012 R2, WFA Pack for managing Clustered Data ONTAP v1.2.1, OnCommand Unified Manager 7.1-