Cloud Pak for Data

 View Only
  • 1.  The Result of Uninstall Watson Discovery 2.1.1

    Posted Mon May 11, 2020 09:23 PM
    Hello, 

    Did someone try to uninstall Watson Discovery 2.1.1?
    After the uninstallation, some pods got problems and did not find out the cause yet.

    If there is someone did the uninstallation, could you tell me that result?

    Kind regards,
    Chris


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

    #CloudPakforDataGroup


  • 2.  RE: The Result of Uninstall Watson Discovery 2.1.1

    Posted Tue May 12, 2020 06:15 AM
    Hi,

    Didn't do 2.1.1, but the previous versions and the result was that all the elements of WD were removed, so no pods related to WD were failing.

    Thanks

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



  • 3.  RE: The Result of Uninstall Watson Discovery 2.1.1

    Posted Wed May 13, 2020 09:21 PM
    Edited by System Fri January 20, 2023 04:22 PM
    Hi,

    Thank you for your reply.

    I got the outut below. Some components related to Watson Discovery remain.

    # oc get all |grep disco
    pod/dataconn-engine-opdiscovery-8599f5f8dc-ghhgk 1/1 Running 1 1d
    pod/metadata-discovery-646f87ccdf-7cwcq 1/1 Running 2 1d

    service/dataconn-engine-opdiscovery ClusterIP 172.30.245.202 <none> 443/TCP 105d
    service/metadata-discovery ClusterIP 172.30.170.99 <none> 443/TCP 105d
    service/rabbitmq-ha-discovery ClusterIP None <none> 15672/TCP,5672/TCP,4369/TCP,5671/TCP 107d

    deployment.apps/dataconn-engine-opdiscovery 1 1 1 1 105d
    deployment.apps/metadata-discovery 1 1 1 1 105d

    replicaset.apps/dataconn-engine-opdiscovery-8599f5f8dc 1 1 1 105d
    replicaset.apps/metadata-discovery-646f87ccdf 1 1 1 105d

    imagestream.image.openshift.io/disco-ranker-server docker-registry.default.svc:5000/icp4d/disco-ranker-server 20200109-164717-3-0c09f21 3 months ago
    imagestream.image.openshift.io/discovery-ranker-rest-service docker-registry.default.svc:5000/icp4d/discovery-ranker-rest-service 20200113-150050-2-d1527c2 3 months ago


    Do you think it is the right result?

    Regards,
    Chris

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



  • 4.  RE: The Result of Uninstall Watson Discovery 2.1.1

    Posted Thu May 14, 2020 04:49 AM

    Hi,

    That doesn't look right.

    Can you please describe few of these objects ?

    oc describe deployment.apps/metadata-discovery 

    oc describe service/rabbitmq-ha-discovery

    Thanks



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



  • 5.  RE: The Result of Uninstall Watson Discovery 2.1.1

    Posted Thu May 14, 2020 09:09 PM
    Edited by System Fri January 20, 2023 04:09 PM
    Hello,

    Thank you for your reply.

    Here is output.
    # oc describe deployment.apps/metadata-discovery
    Name: metadata-discovery
    Namespace: icp4d
    CreationTimestamp: Wed, 29 Jan 2020 10:59:32 +0900
    Labels: app=metadata-discovery
    chart=metadata-discovery-1.0.792
    release=0075-wkc-lite
    Annotations: deployment.kubernetes.io/revision=1
    Selector: app=metadata-discovery
    Replicas: 1 desired | 1 updated | 1 total | 1 available | 0 unavailable
    StrategyType: RollingUpdate
    MinReadySeconds: 0
    RollingUpdateStrategy: 25% max unavailable, 25% max surge
    Pod Template:
    Labels: app=metadata-discovery
    wkc=wkc
    Annotations: productID=ICP4D-WKCLite-Prod-00000
    productId=wkc
    productName=Watson Knowledge Catalog Common Services
    productVersion=3.0
    Containers:
    metadata-discovery:
    Image: cp.icr.io/cp/cpd/metadata-discovery:1.0.792
    Port: 9443/TCP
    Host Port: 0/TCP
    Limits:
    cpu: 1
    memory: 1Gi
    Requests:
    cpu: 100m
    memory: 400Mi
    Liveness: http-get https://:9443/v2/heartbeat delay=120s timeout=10s period=60s #success=1 #failure=3
    Readiness: http-get https://:9443/v2/heartbeat delay=60s timeout=30s period=60s #success=1 #failure=3
    Environment:
    cloudant_username: <set to the key 'username' in secret 'wdp-cloudant-creds'> Optional: false
    cloudant_password: <set to the key 'password' in secret 'wdp-cloudant-creds'> Optional: false
    cloudant_url: <set to the key 'cloudant-url.txt' in secret 'wdp-cloudant-url'> Optional: false
    rabbitmq_uri_1: <set to the key 'rabbitmq-url.txt' in secret 'rabbitmq-url'> Optional: false
    rabbitmq_ca_certificate: <set to the key 'cacertb64.pem' in secret 'rabbitmq-ha-cert'> Optional: false
    openwhisk_enabled: false
    ENABLE_NEWRELIC: false
    base_url: <set to the key 'host-url' of config map 'wdp-config'> Optional: false
    catalogs_url: $(base_url)
    connections_url: $(base_url)
    entitlements_url: $(base_url)
    discovery_create_asset: discovery_create_asset
    discovery_runs: discovery_runs
    discovery_update_progress: discovery_update_progress
    discovery_create_asset_thread_count: 20
    environment: icp4data
    environment_type: WKC
    notifications_url: $(base_url)
    projects_url: $(base_url)
    monitoring_enabled: false
    check_entitlement: true
    WDP_SERVICE_ID_CREDENTIAL: <set to the key 'service-id-credentials' in secret 'wdp-service-id'> Optional: false
    service_id: <set to the key 'service-id' in secret 'wdp-service-id'> Optional: false
    enable_icp4d_auth: true
    enforce_wkc_permission: true
    icp4d_usermgmt_url: <set to the key 'icp4d-host-url' of config map 'wdp-config'> Optional: false
    redis_url: <set to the key 'redis-url.txt' in secret 'redis-url'> Optional: false
    cache_service_factory_impl: com.ibm.wdp.discovery.common.redis.OptimisticLockingRedisCacheServiceFactory
    relative_url: true
    Mounts:
    /etc/wdp_certs from wdp-certs (ro)
    Volumes:
    wdp-certs:
    <unknown>
    Conditions:
    Type Status Reason
    ---- ------ ------
    Progressing True NewReplicaSetAvailable
    Available True MinimumReplicasAvailable
    OldReplicaSets: <none>
    NewReplicaSet: metadata-discovery-646f87ccdf (1/1 replicas created)
    Events: <none>


    # oc describe service/rabbitmq-ha-discovery
    Name: rabbitmq-ha-discovery
    Namespace: icp4d
    Labels: app=wdp-rabbitmq
    chart=wdp-rabbitmq-3.7.16-57
    heritage=Tiller
    release=0022-wkc-base-prereqs
    Annotations: service.alpha.kubernetes.io/tolerate-unready-endpoints=true
    Selector: app=wdp-rabbitmq,release=0022-wkc-base-prereqs
    Type: ClusterIP
    IP: None
    Port: http 15672/TCP
    TargetPort: http/TCP
    Endpoints: <none>
    Port: amqp 5672/TCP
    TargetPort: amqp/TCP
    Endpoints: <none>
    Port: epmd 4369/TCP
    TargetPort: epmd/TCP
    Endpoints: <none>
    Port: amqps 5671/TCP
    TargetPort: amqps/TCP
    Endpoints: <none>
    Session Affinity: None
    Events: <none>

    I wonder I delete the components related to Watson Discovery (oc get all |grep disco) before installing WD 2.1.2.

    Regards,
    Chris

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