Cloud Pak for Data

Cloud Pak for Data

Come for answers. Stay for best practices. All we’re missing is you.

 View Only
Back to discussions
Expand all | Collapse all

[Data Virtualization] Installation

  • 1.  [Data Virtualization] Installation

    Posted 04/14/20 01:48 AM
    Hello,

    I am trying to install Data virstualization,
    however it doesnt work well.


    [INFO] [2020-04-14 14:42:34-0991] Executing command oc secrets link dv-sa docker-pull-icp4d-cp-icr-io-cp-cpd-base-registry-registry --for=pull
    [ERROR] [2020-04-14 14:42:35-0212] Error from server (NotFound): serviceaccounts "dv-sa" not found
    [ERROR] [2020-04-14 14:42:35-0213] Failed applying secret docker-pull-icp4d-cp-icr-io-cp-cpd-base-registry-registry using: /ibm/cpd/bin/cpd-linux-workspace/YAML/docker-pull-icp4d-cp-icr-io-cp-cpd-base-registry-registry.yaml
    [ERROR] [2020-04-14 14:42:35-0215] Exiting due to error. Please check /ibm/cpd/bin/cpd-linux-workspace/Logs/CPD-2020-04-14T14-42-25.log for details


    As I deleted service account dv-sa for the unistallation before the installation,
    I do not have it.

    Could you help me with the installation?

    Warm regards,
    Chris

    ------------------------------
    Chris
    ------------------------------

    #CloudPakforDataGroup


  • 2.  RE: [Data Virtualization] Installation

    Posted 04/14/20 09:33 AM
    Hi Chris,
    Did you run adm command before running the dv installer?

    ./cpd-linux adm --repo repo.yaml --assembly dv --namespace <namespace> --apply


    Thanks,

    ------------------------------
    Sidrah Junaid
    ------------------------------



  • 3.  RE: [Data Virtualization] Installation

    Posted 04/15/20 02:51 AM
    Hello,

    Thank you for your cooperation.
    I runned the command you suggested, and then I tried to install again after uninstalling it as the instruction says(https://www.ibm.com/support/knowledgecenter/SSQNUZ_2.5.0/cpd/svc/dv/uninstall-dv.html).

    However it does not seem to work well.
    I attch the event log.
    Is there anything I have to fix before the installation?

    Thank you,
    Chris





    ------------------------------
    Chris
    ------------------------------

    Original Message


  • 4.  RE: [Data Virtualization] Installation

    Posted 04/15/20 02:54 AM
    Here is the log.
    Thank you.

    [xxxx@master01 ~]# oc get ev |grep dv
    1h 6h 67 dv-1-1586763487932-ibm-unified-console-58f8999848.1605d622578085de ReplicaSet Warning FailedCreate replicaset-controller Error creating: pods "dv-1-1586763487932-ibm-unified-console-58f8999848-" is forbidden: error looking up service account icp4d/dv-sa: serviceaccount "dv-sa" not found
    1h 6h 67 dv-3-1586763487932-ibm-dv-api-7979f79854.1605d622554f4c16 ReplicaSet Warning FailedCreate replicaset-controller Error creating: pods "dv-3-1586763487932-ibm-dv-api-7979f79854-" is forbidden: error looking up service account icp4d/d -sa: serviceaccount "dv-sa" not found
    1h 1h 1 dv-1-1586763487932-ibm-unified-console-58f8999848-9cfwn.1605e4db707d5fb1 Pod Normal Scheduled default-scheduler Successfully assigned icp4d/dv-1-1586763487932-ibm-unified-console-58f8999848-9cfwn to wkr01
    1h 1h 1 dv-3-1586763487932-ibm-dv-api-7979f79854-x8gft.1605e4db70fabc76 Pod Normal Scheduled default-scheduler Successfully assigned icp4d/dv-3-1586763487932-ibm-dv-api-7979f79854-x8gft to wkr01
    1h 1h 1 dv-3-1586763487932-ibm-dv-api-7979f79854.1605e4db6fa2ac68 ReplicaSet Normal SuccessfulCreate replicaset-controller Created pod: dv-3-1586763487932-ibm-dv-api-7979f79854-x8gft
    1h 1h 1 dv-1-1586763487932-ibm-unified-console-58f8999848.1605e4db6f86fd7b ReplicaSet Normal SuccessfulCreate replicaset-controller Created pod: dv-1-1586763487932-ibm-unified-console-58f8999848-9cfwn
    1h 1h 1 dv-3-1586763487932-ibm-dv-api-7979f79854-x8gft.1605e4dc4567bcaf Pod spec.containers{ibm-dv-api} Normal Pulled kubelet, wkr01 Container image "cp.icr.io/cp/cpd/dv-api:v1.3.0.0-301" already present on machine
    1h 1h 1 dv-1-1586763487932-ibm-unified-console-58f8999848-9cfwn.1605e4dc47b56058 Pod spec.containers{uc} Normal Pulled kubelet, wkr01 Container image "cp.icr.io/cp/cpd/dv-unifiedconsole:v1.3.0.0-301" already present on machine
    1h 1h 1 dv-3-1586763487932-ibm-dv-api-7979f79854-x8gft.1605e4dc8f9a1a62 Pod spec.containers{ibm-dv-api} Normal Started kubelet, wkr01 Started container
    1h 1h 1 dv-3-1586763487932-ibm-dv-api-7979f79854-x8gft.1605e4dc8d321a0c Pod spec.containers{ibm-dv-api} Normal Created kubelet, wkr01 Created container
    1h 1h 1 dv-1-1586763487932-ibm-unified-console-58f8999848-9cfwn.1605e4dcb5ad3f05 Pod spec.containers{uc} Normal Created kubelet, wkr01 Created container
    1h 1h 1 dv-1-1586763487932-ibm-unified-console-58f8999848-9cfwn.1605e4dcca111a46 Pod spec.containers{uc} Normal Started kubelet, wkr01 Started container
    1h 1h 1 dv-1-1586763487932-ibm-unified-console-58f8999848-9cfwn.1605e4f926aef038 Pod spec.containers{uc} Warning Unhealthy kubelet, wkr01 Readiness probe failed: INACTIVE
    1h 1h 24 dv-1-1586763487932-ibm-unified-console-58f8999848-9cfwn.1605e4fc2aa3424d Pod spec.containers{uc} Warning Unhealthy kubelet, wkr01 Readiness probe errored: rpc error: code = Unknown desc = command error: command timed out, stdout: , stderr: , exit code -1
    1h 1h 1 dv-caching-58cbc87c6c-jmq98.1605e650c6d832d7 Pod Normal Scheduled default-scheduler Successfully assigned icp4d/dv-caching-58cbc87c6c-jmq98 to wkr03
    1h 1h 1 dv-caching-58cbc87c6c.1605e650c62870a5 ReplicaSet Normal SuccessfulCreate replicaset-controller Created pod: dv-caching-58cbc87c6c-jmq98
    1h 1h 1 dv-caching-58cbc87c6c-jmq98.1605e65230d2ea9a Pod spec.initContainers{init-caching} Normal Pulled kubelet, wkr03 Container image "cp.icr.io/cp/cpd/dv-caching:v1.3.0.0-301" already present on machine
    1h 1h 1 dv-caching-58cbc87c6c-jmq98.1605e652803fad74 Pod spec.initContainers{init-caching} Normal Created kubelet, wkr03 Created container
    1h 1h 1 dv-caching-58cbc87c6c-jmq98.1605e6528754ab81 Pod spec.initContainers{init-caching} Normal Started kubelet, wkr03 Started container
    1h 1h 20 dv-1-1586763487932-ibm-unified-console-58f8999848-9cfwn.1605e5f5100571ce Pod spec.containers{uc} Warning Unhealthy kubelet, wkr01 Liveness probe errored: rpc error: code = Unknown desc = command error: command timed out, stdout: , stderr: , exit code -1
    1h 1h 1 dv-1-1586763487932-ibm-unified-console.1605e708925730dd Deployment Normal ScalingReplicaSet deployment-controller Scaled up replica set dv-1-1586763487932-ibm-unified-console-58f8999848 to 1
    1h 1h 1 dv-1-1586763487932-ibm-unified-console-58f8999848.1605e708941ce775 ReplicaSet Normal SuccessfulCreate replicaset-controller Created pod: dv-1-1586763487932-ibm-unified-console-58f8999848-f6k2t
    1h 1h 1 dv-3-1586763487932-ibm-dv-api-7979f79854.1605e70a8ebbdf1f ReplicaSet Normal SuccessfulCreate replicaset-controller Created pod: dv-3-1586763487932-ibm-dv-api-7979f79854-dk44l
    1h 1h 1 dv-3-1586763487932-ibm-dv-api-7979f79854-x8gft.1605e70a99608b3b Pod spec.containers{ibm-dv-api} Normal Killing kubelet, wkr01 Killing container with id cri-o://ibm-dv-api:Need to kill Pod
    1h 1h 1 dv-3-1586763487932-ibm-dv-api.1605e70a8d487011 Deployment Normal ScalingReplicaSet deployment-controller Scaled up replica set dv-3-1586763487932-ibm-dv-api-7979f79854 to 1
    1h 1h 1 dv-caching.1605e70bfb19909e Deployment Normal ScalingReplicaSet deployment-controller Scaled up replica set dv-caching-58cbc87c6c to 1
    1h 1h 1 dv-caching-58cbc87c6c.1605e70bfc83d7f8 ReplicaSet Normal SuccessfulCreate replicaset-controller Created pod: dv-caching-58cbc87c6c-s4pjr
    1h 1h 25 dv-1-1586763487932-ibm-unified-console-58f8999848-f6k2t.1605e708941b92a2 Pod Warning FailedScheduling default-scheduler persistentvolumeclaim "dv-pvc" is being deleted
    1h 1h 1 dv-1-1586763487932-ibm-unified-console-58f8999848-9cfwn.1605e70f9bcc339e Pod spec.containers{uc} Warning Unhealthy kubelet, wkr01 Liveness probe errored: rpc error: code = Unknown desc = container is not created or running
    1h 1h 23 dv-3-1586763487932-ibm-dv-api-7979f79854-dk44l.1605e70a8ed1d79f Pod Warning FailedScheduling default-scheduler persistentvolumeclaim "dv-pvc" is being deleted
    1h 1h 17 dv-caching-58cbc87c6c-s4pjr.1605e70bfc7c959c Pod Warning FailedScheduling default-scheduler persistentvolumeclaim "dv-pvc" is being deleted
    1h 1h 195 dv-1-1586763487932-ibm-unified-console-58f8999848-f6k2t.1605e71089de8dcd Pod Warning FailedScheduling default-scheduler persistentvolumeclaim "dv-pvc" not found
    1h 1h 203 dv-3-1586763487932-ibm-dv-api-7979f79854-dk44l.1605e7108930cd83 Pod Warning FailedScheduling default-scheduler persistentvolumeclaim "dv-pvc" not found
    1h 1h 209 dv-caching-58cbc87c6c-s4pjr.1605e710898de8d7 Pod Warning FailedScheduling default-scheduler persistentvolumeclaim "dv-pvc" not found
    58m 58m 1 dv-caching-58cbc87c6c.1605e7798a1044c4 ReplicaSet Normal SuccessfulCreate replicaset-controller Created pod: dv-caching-58cbc87c6c-mbm7s
    58m 58m 13 dv-caching-58cbc87c6c-mbm7s.1605e7798a022d50 Pod Warning FailedScheduling default-scheduler persistentvolumeclaim "dv-pvc" not found
    58m 58m 1 dv-caching-58cbc87c6c-mbm7s.1605e77d51e9c4c2 Pod Warning FailedScheduling default-scheduler skip schedule deleting pod: icp4d/dv-caching-58cbc87c6c-mbm7s
    58m 58m 1 dv-caching-58cbc87c6c.1605e77d536bf848 ReplicaSet Normal SuccessfulCreate replicaset-controller Created pod: dv-caching-58cbc87c6c-b7z85
    57m 58m 25 dv-caching-58cbc87c6c-b7z85.1605e77d5367991c Pod Warning FailedScheduling default-scheduler persistentvolumeclaim "dv-pvc" not found
    57m 58m 15 dv-1-1586763487932-ibm-unified-console-58f8999848.1605e7761a915a96 ReplicaSet Warning FailedCreate replicaset-controller Error creating: pods "dv-1-1586763487932-ibm-unified-console-58f8999848-" is forbidden: error looking up service account icp4d/dv-sa: serviceaccount "dv-sa" not found
    57m 58m 15 dv-3-1586763487932-ibm-dv-api-7979f79854.1605e778162427f7 ReplicaSet Warning FailedCreate replicaset-controller Error creating: pods "dv-3-1586763487932-ibm-dv-api-7979f79854-" is forbidden: error looking up service account icp4d/dv-sa: serviceaccount "dv-sa" not found
    56m 6h 571 dv.1605d62270337003 StatefulSet Warning FailedCreate statefulset-controller create Pod dv-0 in StatefulSet dv failed error: pods "dv-0" is forbidden: error looking up service account icp4d/dv-sa: serviceaccount "dv-sa" not found
    56m 6h 571 dv-worker.1605d62271636da7 StatefulSet Warning FailedCreate statefulset-controller create Pod dv-worker-0 in StatefulSet dv-worker failed error: pods "dv-worker-0" is forbidden: error looking up service account icp4d/dv-sa: serviceaccount "dv-sa" not found
    52s 1h 223 dv-worker.1605e48b4829e7fe StatefulSet Warning FailedCreate statefulset-controller create Pod dv-worker-0 in StatefulSet dv-worker failed error: pods "dv-worker-0" is forbidden: unable to validate against any security context constraint: [provider dv-scc: .spec.securityContext.hostIPC: Invalid value: true: Host IPC is not allowed to be used spec.containers[0].securityContext.hostIPC: Invalid value: true: Host IPC is not allowed to be used fsGroup: Invalid value: []int64{43999}: 43999 is not an allowed group provider restricted: .spec.securityContext.hostIPC: Invalid value: true: Host IPC is not allowed to be used spec.containers[0].securityContext.securityContext.runAsUser: Invalid value: 1000322824: must be in the ranges: [1000090000, 1000099999] capabilities.add: Invalid value: "IPC_OWNER": capability may not be added spec.containers[0].securityContext.hostIPC: Invalid value: true: Host IPC is not allowed to be used provider ibm-discovery-prod-scc: .spec.securityContext.hostIPC: Invalid value: true: Host IPC is not allowed to be used capabilities.add: Invalid value: "IPC_OWNER": capability may not be added spec.containers[0].securityContext.hostIPC: Invalid value: true: Host IPC is not allowed to be used spec.containers[0].securityContext.allowPrivilegeEscalation: Invalid value: true: Allowing privilege escalation for containers is not allowed]
    52s 1h 223 dv.1605e48b4648e965 StatefulSet Warning FailedCreate statefulset-controller create Pod dv-0 in StatefulSet dv failed error: pods "dv-0" is forbidden: unable to validate against any security context constraint: [provider dv-scc: .spec.securityContext.hostIPC: Invalid value: true: Host IPC is not allowed to be used spec.containers[0].securityContext.hostIPC: Invalid value: true: Host IPC is not allowed to be used spec.containers[1].securityContext.hostIPC: Invalid value: true: Host IPC is not allowed to be used spec.containers[2].securityContext.hostIPC: Invalid value: true: Host IPC is not allowed to be used fsGroup: Invalid value: []int64{43999}: 43999 is not an allowed group provider restricted: .spec.securityContext.hostIPC: Invalid value: true: Host IPC is not allowed to be used spec.containers[0].securityContext.hostIPC: Invalid value: true: Host IPC is not allowed to be used spec.containers[1].securityContext.securityContext.runAsUser: Invalid value: 1000322824: must be in the ranges: [1000090000, 1000099999] capabilities.add: Invalid value: "IPC_OWNER": capability may not be added spec.containers[1].securityContext.hostIPC: Invalid value: true: Host IPC is not allowed to be used spec.containers[2].securityContext.securityContext.runAsUser: Invalid value: 1000322824: must be in the ranges: [1000090000, 1000099999] spec.containers[2].securityContext.hostIPC: Invalid value: true: Host IPC is not allowed to be used provider ibm-discovery-prod-scc: .spec.securityContext.hostIPC: Invalid value: true: Host IPC is not allowed to be used spec.containers[0].securityContext.hostIPC: Invalid value: true: Host IPC is not allowed to be used capabilities.add: Invalid value: "IPC_OWNER": capability may not be added spec.containers[1].securityContext.hostIPC: Invalid value: true: Host IPC is not allowed to be used spec.containers[1].securityContext.allowPrivilegeEscalation: Invalid value: true: Allowing privilege escalation for containers is not allowed spec.containers[2].securityContext.hostIPC: Invalid value: true: Host IPC is not allowed to be used spec.containers[2].securityContext.allowPrivilegeEscalation: Invalid value: true: Allowing privilege escalation for containers is not allowed]

    ------------------------------
    Chris
    ------------------------------

    Original Message


  • 5.  RE: [Data Virtualization] Installation

    Posted 04/15/20 04:04 AM
    Hi,

    I runned the installation command without the option "--override", then it finished.
    Is it right that data virtualization pods such as dv-0 are created when I provision on CP4D console?
    They are not seen now as I get the result of "oc get pods".

    Thank you,
    Chris

    ------------------------------
    Chris
    ------------------------------

    Original Message


  • 6.  RE: [Data Virtualization] Installation

    Posted 04/15/20 04:39 AM
    Yes, these get created when you provision an instance.

    Thanks

    ------------------------------
    TOMASZ HANUSIAK
    ------------------------------

    Original Message


  • 7.  RE: [Data Virtualization] Installation

    Posted 04/16/20 08:55 PM
      |   view attached
    Hi,

    I could not provison data virtualization on console in the end.
    It did not start, and I found the log saying something related to "security context constraint".
    I attached the log file this message.

    This time, I did not delete only svc(service) when uninstalling dv, and reinstalled dv.
    Should I have deleted svc as well as other elements?
    If so, should I remain dv-service-provider and ibm-dv-api as the instruction writes it?
    https://www.ibm.com/support/knowledgecenter/SSQNUZ_2.5.0/cpd/svc/dv/uninstall-dv.html

    *The result of oc get svc
    dv 
    dv-addon
    dv-caching
    dv-console-uc
    dv-internal 
    dv-server 
    dv-service-provider 
    ibm-dv-api 

    warm regards,
    Chris

    ------------------------------
    Chris
    ------------------------------

    Attachment(s)

    txt
    dverror_20200417.txt   19 KB 1 version
    Original Message


  • 8.  RE: [Data Virtualization] Installation

    Posted 04/21/20 05:07 AM
    Hi,

    Can you please open a support ticket ? We may need to invest more time to investigate this.

    Out of the top of my head:

    - please check your scc definitions
    - make sure that the dv-scc has

    allowHostIPC: true

    Thanks

    ------------------------------
    TOMASZ HANUSIAK
    ------------------------------

    Original Message


  • 9.  RE: [Data Virtualization] Installation

    Posted 04/22/20 12:27 AM
    Hi,

    Thank you  for your cooperation.
    Now I uninstalled Data Virualization, I cannot view dv-scc status.

    I am going to CP4D v3.0, so I put this case away.
    Thank you,

    Chris

    ------------------------------
    Chris
    ------------------------------

    Original Message


  • 10.  RE: [Data Virtualization] Installation

    Posted 04/22/20 09:09 AM

    Hi Chris, 

    The error showed DV statefulset couldn't run with hostIPC:true as its scc did not allow it. This can happen if your dv-scc does not match DV 1.3 build. Could you run `oc get dv-scc -o yaml` and paste here the content ?

    Also, could you run `oc get pods | grep -i dv` and past the results here ?



    ------------------------------
    DI LI
    ------------------------------

    Original Message


  • 11.  RE: [Data Virtualization] Installation

    Posted 04/22/20 09:10 AM

    Hi Chris,

    What is the full content of dv-scc ? "oc get scc dv-scc -o yaml"

    What is the result of "oc get pods  | grep -i dv "



    ------------------------------
    DI LI
    ------------------------------

    Original Message


  • 12.  RE: [Data Virtualization] Installation

    Posted 04/24/20 02:14 AM
    Hello,

    Is dv-scc created when I install data virtualization?
    Since I uninstalled it, I cannot see the status now.
    I wonder I try to install it again though...

    Thank you,
    Chris

    ------------------------------
    Chris
    ------------------------------

    Original Message


  • 13.  RE: [Data Virtualization] Installation

    Posted 04/24/20 11:49 AM

    Hi Chris, 

    On a fresh cluster ( aka never has had DV installed before), dv-scc is created when you run ./cpd-linux adm command to set up DV's security context, SA, roles, etc.  On a cluster that had DV previously installed, dv-scc would remain unless you manually remove it. 

    The error you showed to Tomasz looked like a mismatch between dv-scc and dv statefulset. That's why I wanted to check the content of dv-scc on your cluster.

    I shared with you the uninstall document in the DV KC. Please make sure you clean up your cluster before reinstalling DV. 



    ------------------------------
    DI LI
    ------------------------------

    Original Message


Related Content