Closed pbaity closed 1 year ago
@vsnyc Can you please review/merge this PR and publish it. Thanks! (@nathsen FYI)
/do-e2e-tests
@vsnyc Is /do-e2e-tests
supposed to update this issue once the tests complete?
Yes, in case of a successful run. I'll check the logs and post back what didn't go right.
/do-e2e-tests
@git4rk - I checked our CI and looks like we are getting some errors picking up the code change. I'll work on it Wednesday. Any chance you have the taskcat_outputs dir from a successful test run that you could zip and attach as a comment here? I can use that to approve and merge this faster. Thanks!
@vsnyc Here is the output from taskcat run: taskcat_outputs.zip
Thanks @git4rk , I'll merge the change.
Issue #, if available:
closes #35 closes #36
Description of changes:
First, I noticed a problem after installing OLM on the cluster, adding the IBM Operator Catalog, and installing the WebSphere Liberty Operator. The operator never started running and the installation script eventually times out. This was due to a known issue in OLM v0.23.0 where any operators installed from the community catalog source (for OperatorHub) would also fail to run. This was patched in v0.23.1 by simply setting
spec.grpcPodConfig.securityContextConfig
torestricted
on the catalog source. So I applied the same change to the IBM Operator Catalog source, and the problem was fixed - WLO installed and runs successfully after that change.Second, I switched the "working directory" used as the location for scripts, templates, and log files from
/tmp
to/opt/ibm
in order to make sure these files don't get deleted when/tmp
is cleared.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.