-
Notifications
You must be signed in to change notification settings - Fork 552
Check for conflicting install #2190
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check for conflicting install #2190
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kevinrizza The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/lgtm |
scripts/install.sh
Outdated
@@ -14,6 +14,12 @@ if [[ ${#@} -lt 1 || ${#@} -gt 2 ]]; then | |||
exit 1 | |||
fi | |||
|
|||
openshift_install_check=$(kubectl get deployment olm-operator -n openshift-operator-lifecycle-manager -o=jsonpath='{.spec}' 2>/dev/null) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the string test necessary? kubectl get
should exit with a nonzero status code if it doesn't find the resource, IIRC.
Update the install script so that known conflicting downstream installations of OLM don't cause conflicts and hotloop
3497563
to
d7eead7
Compare
/hold cancel |
/lgtm |
I think we can fix this via my suggestion here: #2210 (comment) |
Update the install script so that known conflicting downstream installations of OLM don't cause conflicts and hotloop