search

sreckoj / IBM-CP4I-CLI-based-installation

0 stars 0 forks source link

PVC error #1

Closed mninawa closed 2 years ago

mninawa commented 2 years ago

Hi Srecko, after running this `cat << EOF | oc apply -f -

apiVersion: integration.ibm.com/v1beta1 kind: PlatformNavigator metadata: name: integration-navigator namespace: cp4i spec: license: accept: true license: L-RJON-CD3JKX storage: class: nfs-client mqDashboard: true replicas: 1 version: 2022.2.1 EOF i get the following:platformnavigator.integration.ibm.com/integration-navigator created which is fine, the platform ui runs and later i get the following: Time out waiting for user-home-pvc to be bound at 2022-07-14_19:16:21. unknown playbook failure Reason: Failed Status: False Type: Failure Last Transition Time: 2022-07-14T19:16:24Z Message: Running reconciliation Reason: Running Status: True Type: Running`

what is it that i might be doing wrong?

mninawa commented 2 years ago

lastly what is the script that was used to provision the following storages: NAME PROVISIONER managed-nfs-storage icpd-nfs.io/nfs rook-ceph-block (default) rook-ceph.rbd.csi.ceph.com

sreckoj commented 2 years ago

Those are storage classes that I already had in the available OpenShift environment. The aim was to show the CP4I installation process using CLI assuming that there are already available classes. The class names in your environment will be probably different. What you need for CP4I is one file type (RWX) storage class and one block type (RWO). Most of the customers use OpenShift Data Foundation for on-prem OpenShift installations. The cloud providers that offer OpenShift (IBM Cloud, AWS, Azure) typically offer some default storage classes based on the storage solutions in their clouds. For PoC installations, I offten use Rook-Ceph. I will prepare a separate document about that.