Skip to content

Commit 9e526da

Browse files
jmazzitellibenluddy
authored andcommitted
install.sh should not abort if openshift olm is not installed
fixes: operator-framework/operator-lifecycle-manager#2210 Signed-off-by: John Mazzitelli <[email protected]> Upstream-repository: operator-lifecycle-manager Upstream-commit: fb6e5e759952c76d9e8a21d203da6d1fd231f1c8
1 parent 5188bb4 commit 9e526da

File tree

1 file changed

+1
-2
lines changed
  • staging/operator-lifecycle-manager/scripts

1 file changed

+1
-2
lines changed

staging/operator-lifecycle-manager/scripts/install.sh

+1-2
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,7 @@ if [[ ${#@} -lt 1 || ${#@} -gt 2 ]]; then
1414
exit 1
1515
fi
1616

17-
kubectl get deployment olm-operator -n openshift-operator-lifecycle-manager -o=jsonpath='{.spec}' > /dev/null 2>&1
18-
if [[ $? -eq 0 ]]; then
17+
if kubectl get deployment olm-operator -n openshift-operator-lifecycle-manager -o=jsonpath='{.spec}' > /dev/null 2>&1; then
1918
echo "OLM is already installed in a different configuration. This is common if you are not running a vanilla Kubernetes cluster. Exiting..."
2019
exit 1
2120
fi

0 commit comments

Comments
 (0)