Maximo

Maximo

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

 View Only

  • 1.  MAS Core Installation

    Posted Wed February 15, 2023 12:46 PM

    Hello!

    We trying to isntall MAS in our owen OCP cluster. 

    OCP 4.11.18

    We have installed ibm Cloud Pack For Data, all is good. 

    Now installing MAS Core using playbook from MAS Devops Collection. 

    Exported all variables, all is good, but installation faling on ibm.mas_devops.sls : Wait for LicenseService to be ready.

    Root case is that pod for sls-api-licensing faling to be created:

     oc get pods -n ibm-sls -o wide
    NAME                                                     READY   STATUS             RESTARTS   AGE   IP             NODE      NOMINATED NODE   READINESS GATES
    ibm-truststore-mgr-controller-manager-7d764954b4-l6nkt   1/1     Running            0          22m   10.129.2.106   worker2   <none>           <none>
    sls-api-licensing-647b75d866-glqc2                       0/1     ImagePullBackOff   0          15m   10.129.2.111   worker2   <none>           <none>
    sls-truststore-worker-rtsw5                              0/1     Completed          0          49m   10.129.2.101   worker2   <none>           <none>

    oc describe pod sls-api-licensing-647b75d866-glqc2 :

    Events:
      Type     Reason          Age                 From               Message
      ----     ------          ----                ----               -------
      Normal   Scheduled       16m                 default-scheduler  Successfully assigned ibm-sls/sls-api-licensing-647b75d866-glqc2 to worker2 by master3
      Normal   AddedInterface  16m                 multus             Add eth0 [10.129.2.111/23] from openshift-sdn
      Normal   Pulling         15m (x4 over 16m)   kubelet            Pulling image "cp.icr.io/cp/sls/api-licensing:5.8.1"
      Warning  Failed          15m (x4 over 16m)   kubelet            Failed to pull image "cp.icr.io/cp/sls/api-licensing:5.8.1": rpc error: code = Unknown desc = reading manifest 5.8.1 in cp.icr.io/cp/sls/api-licensing: denied: insufficient scope
      Warning  Failed          15m (x4 over 16m)   kubelet            Error: ErrImagePull
      Warning  Failed          14m (x6 over 16m)   kubelet            Error: ImagePullBackOff
      Normal   BackOff         94s (x64 over 16m)  kubelet            Back-off pulling image "cp.icr.io/cp/sls/api-licensing:5.8.1"

    entitlement key is valid. 

    So what it can be ?



    ------------------------------
    Andrey Ilinskiy
    ------------------------------

    #AssetandFacilitiesManagement
    #Maximo


  • 2.  RE: MAS Core Installation

    Posted Thu February 16, 2023 10:15 AM

    Please validate below things.

    1. Check Internet connectivity and allowing to connect to cp.icr.io portal.
    2. Network and Firewall settings. There is chance firewall scan trying to block during image download from  cp.icr.io/cp/sls/api-licensing:5.8.1 . For this try to run curl from your cluster.$curl cp.icr.io/cp/sls/api-licensing:5.8.1
    3. Check the your storage is supporting dynamic provisioning or not.
    4. Warning  Failed          15m (x4 over 16m)   kubelet            Failed to pull image "cp.icr.io/cp/sls/api-licensing:5.8.1": rpc error: code = Unknown desc = reading manifest 5.8.1 in cp.icr.io/cp/sls/api-licensing: denied: insufficient scope - This message saying trying to pull image from portal and denied by firewall or network.
    5. make sure you have valid key file and entitlement key.



    ------------------------------
    Ramakrishnudu Kayala
    ------------------------------

    Original Message


  • 3.  RE: MAS Core Installation

    Posted Thu February 16, 2023 02:20 PM

    If it is an network problem or entitlement key, why it is a problem only with that image, but all previous created pods haven't that problem? 



    ------------------------------
    Andrey Ilinskiy
    ------------------------------

    Original Message


  • 4.  RE: MAS Core Installation

    Posted Fri February 17, 2023 02:15 AM

    Every image has its own URL to pull from repository and network should allow to connect URL. Firewall scan will happen on individual images while pulling from repository.



    ------------------------------
    Ramakrishnudu Kayala
    ------------------------------

    Original Message


  • 5.  RE: MAS Core Installation

    Posted Fri February 17, 2023 09:29 AM

    Hi Andrey,

    I've had similar problem. OCP 4.11 is not supported by MAS 8.9. Downgrading to 4.10 solved that for me.



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

    Original Message


  • 6.  RE: MAS Core Installation

    Posted Fri February 17, 2023 09:41 AM

    OCP 4.11 will not support MAS 8.9. Due to unsupported version it has failed to pull image .

    OCP 4.10.46 will support MAS 8.9



    ------------------------------
    Ramakrishnudu Kayala
    ------------------------------

    Original Message


  • 7.  RE: MAS Core Installation

    Posted Mon February 20, 2023 11:15 AM

    There is a possiblity that something is wrong with your entitlement key. The reason why you can see other pods (ibm sls controller mgr operator and truststore operator pods) and not api-licensing is because api-licensing is from Entitled Registry meaning you need to have the right entitlement (for which you use your entitlement key). I found a guide here that may help . You could also try to pull the same image locally using your entitlement key via docker or podman. 



    ------------------------------
    Rawa Resul
    ------------------------------

    Original Message