Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only
Back to discussions
Expand all | Collapse all

MAS9 SNO Bare Metal Install - Failed! One of more storage classes are not defined for Manage!

  • 1.  MAS9 SNO Bare Metal Install - Failed! One of more storage classes are not defined for Manage!

    Posted Wed August 21, 2024 04:21 PM

    I am doing a bare metal SNO install and up to point that MANAGE is installing. I am getting the following error and need guidance how to resolve...

    I only had a Storage Class of lvms-vg1  which this did not use...

    I get the following:

    TASK [ibm.mas_devops.suite_app_config : Assert Manage related storage classes are defined] ***
fatal: [localhost]: FAILED! => changed=false 
  assertion: mas_app_settings_doclinks_pvc_storage_class != ''
  evaluated_to: false
  msg:
  - Failed! One of more storage classes are not defined for Manage!
  - It was not possible to auto detect a valid storage class as none of the defaulted options were found ....................... ['ibmc-file-gold-gid', 'ocs-storagecluster-cephfs', 'azurefiles-premium', 'efs']
  - Storage Classes available in your cluster .................................................................................. ['lvms-vg1']
  - ''
  - 'Please, ensure you define a valid storage class for the following:'
  - ''
  - mas_app_settings_doclinks_pvc_storage_class' property ...................................................................... Undefined!
  - mas_app_settings_bim_pvc_storage_class' property ........................................................................... Undefined!
  - mas_app_settings_jms_queue_pvc_storage_class' property ..................................................................... Undefined!

NO MORE HOSTS LEFT *************************************************************

    Please advise what I need to do with my Storage Class, PV, PVC and/or VS, VSC tro give it a clas that apparently the Attach Docs wants to use, BIM and JMS.

    I saw nothing in documentation that explained I need to do something other then the LVM that I created as for the above needed storage classes?

    I did make a storage class with the value of the default it was looking for just as a test and it got further ion the install but still breaks as I expected

    [ibmmas/cli:10.7.3]mascli$ oc describe pvc inst1-work1-manage-bim
Name:          inst1-work1-manage-bim
Namespace:     mas-inst1-manage
StorageClass:  ocs-storagecluster-cephfs
Status:        Pending
Volume:
Labels:        app.kubernetes.io/instance=inst1
               app.kubernetes.io/managed-by=ibm-mas-manage
               app.kubernetes.io/name=ibm-mas-manage
Annotations:   volume.beta.kubernetes.io/storage-provisioner: topolvm.io
               volume.kubernetes.io/selected-node: eipdemo
               volume.kubernetes.io/storage-provisioner: topolvm.io
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:
Access Modes:
VolumeMode:    Filesystem
Used By:       inst1-work1-manage-maxinst-686f965d5d-rmknx
Events:
  Type     Reason                Age                   From                                                                               Message
  ----     ------                ----                  ----                                                                               -------
  Normal   WaitForFirstConsumer  16m (x145 over 52m)   persistentvolume-controller                                                        waiting for first consumer to be created before binding
  Normal   Provisioning          2m57s (x12 over 16m)  topolvm.io_topolvm-controller-bfd4d6c7-phwfs_d2caa2a5-8a3e-482d-9f1d-8e7809c5a442  External provisioner is provisioning volume for claim "mas-inst1-manage/inst1-work1-manage-bim"
  Warning  ProvisioningFailed    2m57s (x12 over 16m)  topolvm.io_topolvm-controller-bfd4d6c7-phwfs_d2caa2a5-8a3e-482d-9f1d-8e7809c5a442  failed to provision volume with StorageClass "ocs-storagecluster-cephfs": rpc error: code = InvalidArgument desc = unsupported access mode: MULTI_NODE_MULTI_WRITER
  Normal   ExternalProvisioning  109s (x62 over 16m)   persistentvolume-controller                                                        waiting for a volume to be created, either by external provisioner "topolvm.io" or manually created by system administrator





    ------------------------------
    David Miller
    Managing Partner - Maximo Consultant
    Enterprise Integration Partners LLC
    ------------------------------


  • 2.  RE: MAS9 SNO Bare Metal Install - Failed! One of more storage classes are not defined for Manage!

    Posted Wed August 21, 2024 04:47 PM
    Edited by David Miller Wed August 21, 2024 04:48 PM

    Is it possible that I needed to tell it the ReadWriteMany Storage Class should have also been my lvms-vg1? All guides always have us just specify the ReadWriteOnce Storage Class   ?????   Just looking at my parameters...

    21.1) OpenShift Container Platform
      Storage Class Provider .................. custom
      ReadWriteOnce Storage Class ............. lvms-vg1
      ReadWriteMany Storage Class ............. Default
      Certificate Manager ..................... redhat
      Cluster Ingress Certificate Secret ...... Default


    Or should I create an entirely new lvms-vg2  to be the RWM and specify it for the RWM?
    ------------------------------
    David Miller
    Managing Partner - Maximo Consultant
    Enterprise Integration Partners LLC
    ------------------------------

    Original Message


  • 3.  RE: MAS9 SNO Bare Metal Install - Failed! One of more storage classes are not defined for Manage!

    Posted Thu August 22, 2024 02:40 AM

    Hi David,

    SNO will accept only the RWO storage class, which you have correctly defined as lvms-vg1. You shouldn't worry about the RWM because the Ansible scripts check whether your cluster is an SNO and initially define all parameters to RWO.

    My question now is, what method are you using to install it? Ansible scripts or mas-cli?

    If using Ansible scripts, you may have to define the variable mas_app_settings_persistent_volumes_flag to true (https://ibm-mas.github.io/ansible-devops/roles/suite_app_config/#mas_app_settings_persistent_volumes_flag) manually.

    Using mas-cli, I faced a similar issue when not proceeding to execute the pipeline and executing the generated command line later.

    Let us know if this variable makes any difference for you.

    Cheers.



    ------------------------------
    If this post helps, please consider accepting it as a solution to help other members find it more quickly.

    Maycon Belfort
    Consultant
    BPD Zenith
    Melbourne
    ------------------------------

    Original Message


  • 4.  RE: MAS9 SNO Bare Metal Install - Failed! One of more storage classes are not defined for Manage!

    Posted Thu August 22, 2024 04:15 AM

    This is a MAS CLI bug that is tracked https://github.com/ibm-mas/cli/issues/1192

    Like in other parts of the code, it needs to understand it is deploying on a SNO and should never ask for a RWX storage class.

    @Sarika Budhiraja FYI



    ------------------------------
    Alex Donatelli
    IBM
    ------------------------------

    Original Message


  • 5.  RE: MAS9 SNO Bare Metal Install - Failed! One of more storage classes are not defined for Manage!

    Posted Thu August 22, 2024 08:15 AM
    Edited by David Miller Thu August 22, 2024 09:07 AM

    Yes indeed I am doing the install by way of the MAS CLI. So, I guess I will do my install and not install Manage  in the CLI and see if I can get past this. So when I install Manage through the App Suite will we get the Attached Docs to work in a SNO env or is this issue going to prevent Attach Docs from being able to work if they need a RWM and SNO only support RWO ??? Will attach docs always need a RWM Storage Class definition? Even if I try to do something with NFS will I not still need to access it through a storage class definition where I am needing to pick a Provisioner and PVC with RWM?



    ------------------------------
    David Miller
    Managing Partner - Maximo Consultant
    Enterprise Integration Partners LLC
    ------------------------------

    Original Message


  • 6.  RE: MAS9 SNO Bare Metal Install - Failed! One of more storage classes are not defined for Manage!

    Posted Thu August 22, 2024 08:51 AM

    It is probably helpful to go back and review the RWX definition for a storage class. A RWX storage class support the sharing of storage among nodes. Given here we are talking about a single node, the RWO is perfectly able to support Manage and all its features.

    In a multi-node cluster, you'll need a RWX storage to make sure all the Manage pods sees and can interact with the same storage area independently where OpenShift located them. You also appreciate that the use of node affinity may support additional scenarios.



    ------------------------------
    Alex Donatelli
    IBM
    ------------------------------

    Original Message


  • 7.  RE: MAS9 SNO Bare Metal Install - Failed! One of more storage classes are not defined for Manage!

    Posted Thu August 29, 2024 09:33 AM
    Edited by David Miller Thu August 29, 2024 09:33 AM

    IBM Solution .... "DO NOT USE MAS CLI"  .. LOL


    https://www.ibm.com/mysupport/s/defect/aCIKe000000bnSh/dt395072?language=en_US



    ------------------------------
    David Miller
    Managing Partner - Maximo Consultant
    Enterprise Integration Partners LLC
    ------------------------------

    Original Message


  • 8.  RE: MAS9 SNO Bare Metal Install - Failed! One of more storage classes are not defined for Manage!

    Posted Thu August 29, 2024 10:00 AM

    No, actually the contrary, David, use the MAS CLI because that issue is already fixed and delivered.

    Every SW code may have bugs, the key for IBM is to quickly resolve them when they appear and we do our best to follow that rule.



    ------------------------------
    Alex Donatelli
    IBM
    ------------------------------

    Original Message


  • 9.  RE: MAS9 SNO Bare Metal Install - Failed! One of more storage classes are not defined for Manage!

    Posted Thu April 03, 2025 08:48 AM

    Hello, here, year 2025 and facing same issue with SNO option using mas install in podman.



    ------------------------------
    Abdallah Chebib
    ------------------------------

    Original Message


  • 10.  RE: MAS9 SNO Bare Metal Install - Failed! One of more storage classes are not defined for Manage!

    Posted Fri August 30, 2024 05:16 AM

    Hi David

    If the CLI issue not fix, you can try to add a NFS or other storage class is allow create RreaWriteMany before install manage, and using this during installation

    Regards,

    Jason



    ------------------------------
    Jason Pun
    Technical Consulant
    ------------------------------

    Original Message


  • 11.  RE: MAS9 SNO Bare Metal Install - Failed! One of more storage classes are not defined for Manage!

    Posted Sun September 01, 2024 07:30 PM

    Hi David,

    Faced the same issue, solved it by not installing LVM operator, but rather setting up NFS storage (as Jason mentioned above) and then following this link: https://www.ibm.com/support/pages/how-do-i-create-storage-class-nfs-dynamic-storage-provisioning-openshift-environment

    Encountered further issues with external SQL Server database, but that's a story for another day.

    Ended up installing MAS + Manage 9.02 on my Windows laptop using crc 4.15, dropped the mike and rode off into the sunset    :)



    ------------------------------
    Dejan Matijas
    ------------------------------

    Original Message


  • 12.  RE: MAS9 SNO Bare Metal Install - Failed! One of more storage classes are not defined for Manage!

    Posted Mon September 02, 2024 02:08 AM

    You can always use MAS CLI and run Ansible playbooks from there. It gives You all the install options without some of the bugs that are there in Tekton approach.

    Using NFS for SNO is really not a great idea, unless You need it for specific use case (like shared storage with external service). Using NFS for internal OCP components is highly discouraged by Red Hat: https://access.redhat.com/solutions/3428661



    ------------------------------
    Witold Wierzchowski
    ------------------------------

    Original Message