PureStorage Flash Blade Discovery

[Gus1]

We've been working on configuring FlashBlade discovery by following the documentation presented here:
https://docs.servicenow.com/bundle/washingtondc-it-operations-management/page/product/service-mappin...

We've confirmed that we are meeting the prerequisites and that the FlashBlade is on version 4.
We've configured the SSH credential and the applicative credentials. 
We've opened ports 22 and 443 for this. 

It seems the way this should work is the shazzam probe will identify port 22 is open and kick off the unix classify multiprobe, this multiprobe has 7 child probes one of which is the PureBlade probe. The PureBlade probe has a probe parameter that contains a shell script, the shell script out of box is the following:

#!/bin/sh
echo `pureblade list 2>&1`

The other parameter we have is the allow_unsupported_shells and we've set this to "true". 

This probe is supposed to run this shell script from the parameter above and help identify the FlashBlade, with the PureBladeByName unix classification which launches the pattern for FlashBlade Pure Storage. 

The problem we're having is the FlashBlade is unable to run echo shell command. Discovery logs show this error:

The `pureman` command displays information about the Purity//FB CLI. To display
CLI syntax and usage guidelines, run `pureman pureman`. To display information
about a Purity//FB CLI command, run the `pureman` command with the Purity//FB
CLI command name. For example, run `pureman purefs` to display the man page for
the `purefs` command.

Error: Arguments may not contain line breaks
Error: Unknown command - #!/bin/sh

Error: Unknown command - echo

Error: Unknown command - }

Error: Unknown command - snc_func_1 - Exit status: 127

We've spoken with the Pure vendor a couple of times and they've pushed back on running echo on FlashBlades, they've stated that isn't something they support. Does anyone have any other suggestions or has anyone been able to resolve a similar issue before?

[Gus1]

Wasn't able to get the vendors to meet but ServiceNow Support did escalate the case to their dev team. We've not had much luck and the latest update was confirming they've had others contact them about this issue. They've created a problem record.

[Charlotte Pakes]

Thanks, I've raised a Case too now referencing this thread.

[Alexey7]

I have the same issue.. Anyone able to make progress on it? Thanks!