[OCP] Using the olm script manually to apply does not work in OpenShift environment (no marketplace namespace)

[whowutwut]

Describe the bug

Trying to follow this instruction:

Results in this error:

clusterrolebinding.rbac.authorization.k8s.io/olm-crb created
Error from server (NotFound): error when creating "deploy/olm-scripts/operator-source.yaml": namespaces "marketplace" not found
Error from server (NotFound): error when creating "deploy/olm-scripts/operator-source.yaml": namespaces "marketplace" not found
Error from server (NotFound): error when creating "deploy/olm-scripts/operator-source.yaml": namespaces "marketplace" not found
No resources found.

To Reproduce

In Openshift environment, run oc apply -f deploy/olm-scripts/operator-source.yaml

Expected behavior

Operator comes up?

Environment

Running this code:

[root@c943f4n01-pvt csi-operator-ansible]# cd ~/go/src/github.com/IBM/ibm-spectrum-scale-csi-operator/
[root@c943f4n01-pvt ibm-spectrum-scale-csi-operator]# git remote -v
origin	https://github.com/IBM/ibm-spectrum-scale-csi-operator.git (fetch)
origin	https://github.com/IBM/ibm-spectrum-scale-csi-operator.git (push)
[root@c943f4n01-pvt ibm-spectrum-scale-csi-operator]# git branch
* dev
[root@c943f4n01-pvt ibm-spectrum-scale-csi-operator]# git  log -1
commit be2ca36225d6fc5760b69a0595c4a709be7eaf7e
Merge: 3303227 9b1057c
Author: John Dunham <JFDBEar1@gmail.com>
Date:   Thu Nov 21 17:22:08 2019 -0500

    Merge pull request IBM/ibm-spectrum-scale-csi-operator#60 from mew2057/csv-vet

    Cluster Service Version Cleanup

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

[whowutwut]

@mew2057 just for kicks....

I did the following:

1. search/replace for marketplace to ibm-spectrum-scale-csi-driver in the deploy/olm-scripts/operator-source.yaml
2. applied namespace/secret/olm yamls 👇

[root@c943f4n01-pvt ibm-spectrum-scale-csi-operator]# oc apply -f deploy/namespace.yaml
namespace/ibm-spectrum-scale-csi-driver created
[root@c943f4n01-pvt ibm-spectrum-scale-csi-operator]# oc apply -f /root/csi-operator-ansible/secrets.json -n ibm-spectrum-scale-csi-driver
secret/spectrum-scale-gui-secret created
[root@c943f4n01-pvt ibm-spectrum-scale-csi-operator]# oc apply -f deploy/olm-scripts/operator-source.yaml
clusterrolebinding.rbac.authorization.k8s.io/olm-crb configured
operatorsource.operators.coreos.com/ibm-spectrum-scale-csi-operator-app created
operatorgroup.operators.coreos.com/operator-group created
subscription.operators.coreos.com/oper-sub created

But nothing happened:

[root@c943f4n01-pvt csi-operator-ansible]# oc get pods  -n ibm-spectrum-scale-csi-driver
No resources found.
[root@c943f4n01-pvt csi-operator-ansible]#

Any pointers?

[mew2057]

So this was a documentation gap on my part. In OpenShift you don't need operator-source.yaml, you need deploy/olm-scripts/operator-source-oc.yaml.

The operator-source-oc.yaml file does one thing, subscribe to the CSV. After that you need to access the GUI and set up the operator for use:
https://github.com/IBM/ibm-spectrum-scale-csi-operator/issues/25#issuecomment-557251170

Alternatively, follow this guide https://github.com/operator-framework/community-operators/blob/master/docs/testing-operators.md

[mew2057]

Here's the Revised documentation:

Option B: Using Operator Lifecycle Manager (OLM)

NOTE: This will be the prefered method. However, work is ongoing.

NOTE: Installing OLM is out of the scope of this document, please refer to the official documentation. If you're still having trouble, this guide goes even deeper.

The following will subscribe the quay.io version of the operator assuming OLM is installed.

cd ${OPERATOR_DIR}/stable/ibm-spectrum-scale-csi-operator-bundle/operators/ibm-spectrum-scale-csi-operator

kubectl apply -f deploy/olm-scripts/operator-source.yaml

NOTE: Kubernetes use kubectl command, replace with oc if deploying in OpenShift.

cd ${OPERATOR_DIR}/stable/ibm-spectrum-scale-csi-operator-bundle/operators/ibm-spectrum-scale-csi-operator

oc apply -f deploy/olm-scripts/operator-source-oc.yaml

[mew2057]

Also, until we're in OperatorHub this documentation is actually not terribly accurate, this is just a for example. I don't know if we should actually support OLM officially until we're there, because the current model is pointing to a bundle I made by hand that isn't even up to date?

[smitaraut]

This should have been addressed with the GA. OLM instructions here-
https://www.ibm.com/support/knowledgecenter/STXKQY_5.0.4/com.ibm.spectrum.scale.csi.v5r04.doc/bl1csi_install_usingOLM.html

[deeghuge]

Following document provide the mechanism for OLM pre release test.
https://github.com/IBM/ibm-spectrum-scale-csi/blob/dev/tools/ansible/olmupgrade.md

Please reopen if above document is not sufficient