Reported by Mark Dunnett:

I'm running zsh shell on a mac. The install script does not like zsh. I tried several workarounds to invoke it with bash. The problem was how the logging uses tee. I finally used ./scripts/deploy-rhods.sh to get it installed, but I don't get any logging that way. This is what you see when you work around the rhods install scripting:

...
operatorgroup.operators.coreos.com/self-managed-redhat-product-og created
subscription.operators.coreos.com/self-managed-rhods created
utils.sh: command substitution: line 193: syntax error near unexpected token `>'
utils.sh: command substitution: line 193: `$cmd &>>/dev/null'
NAME                    DISPLAY NAME   STATUS
redhat-ods-monitoring                  Active
utils.sh: command substitution: line 193: syntax error near unexpected token `>'
utils.sh: command substitution: line 193: `$cmd &>>/dev/null'
NAME                    DISPLAY NAME   STATUS
redhat-ods-monitoring                  Active
utils.sh: command substitution: line 193: syntax error near unexpected token `>'
utils.sh: command substitution: line 193: `$cmd &>>/dev/null'
NAME                    DISPLAY NAME   STATUS
redhat-ods-monitoring                  Active
utils.sh: command substitution: line 193: syntax error near unexpected token `>'
utils.sh: command substitution: line 193: `$cmd &>>/dev/null'

Here is what line 193 does:

token=$($cmd &>>/dev/null) && returncode=$? || returncode=$?

My setup is similar to how many people have their laptops setup. I'm not sure what assumptions engineering is making when they use bash scripting that pipes stdout/stderr to logs using tee, but it didn't work for me. If you are not using zsh shell I'm sure it works fine. I'm not sure if engineering wants to put some verbiage around the fact that they are assuming you are using bash, but I would. Many customers would see that it's not working and move on (at least the customers I deal with).