Troubleshooting Data Product Hub

Flight service URL fails to generate for a subscription

• Symptom: You chose Flight service for your delivery method, but the URL does not generate for your subscriptions.
• Possible Cause: An external Flight service route was not configured for your IBM Software Hub project on your cluster before Data Product Hub was installed. For details about configuring an external route, see Configuring an external route to the Flight service in the IBM Software Hub documentation.
• Solution: Configure an external route following the steps described in Configuring an external route to the Flight service in the IBM Software Hub documentation. Then bind the external route to Data Product Hub. If you prefer to use the OpenShift console, see How to configure an external Flight URL route to deliver data products with Data Product Hub.

Steps for binding the external Flight service URL route to Data Product Hub from the command line:

1. Open the terminal and log into the cluster where the Data Product Hub service is deployed. Execute:

sudo su -

2. Find the podname:

kubectl get pods -n <<operator-namespace>>| grep "data-product-operator"

Two pod names are returned: ibm-cpd-data-product-operator-xxxxx and ibm-cpd-data-product-operator-catalog-xxxxx. You will access the pod that does NOT contain "catalog".

3. Access the operator pod:

kubectl exec -it <ibm-cpd-data-product-operator-xxxxx> -n <<operator-namespace>> /bin/bash

4. Locate the update_fcrouteurl.yaml script in the /opt/ansible/installed-version/roles/data-product directory where installed-version is the Cloud Pak for Data version.

5. Execute the update_fcrouteurl.yaml script:

ansible-playbook update_fcrouteurl.yaml -e "fcservicens=wkc fcservicename=wdp-connect-flight"

Ensure that fcservicens is the correct namespace for the wdp-connect-flight service.

6. Restart the dataproduct-api service to bind the new external routeURL:

kubectl rollout restart deployment dataproduct-api -n wkc