UPSTREAM: <carry>: chore: add meaningful logs to client initialization.

[HumairAK]

Resolves: https://issues.redhat.com/browse/RHOAIENG-3970

Description of your changes:
It is annoying when users see a "Initializing client manager" log and it's just stuck, not knowing whether db or minio connection failed, these simple logs will go a long way in helping troubleshoot such issues.

testing instructions

1. deploy dspa
2. check pipeline server logs, and see whether new logs show up in the changes

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: HumairAK

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [HumairAK]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[dsp-developers]

A set of new images have been built to help with testing out this PR:
API Server: quay.io/opendatahub/ds-pipelines-api-server:pr-29
DSP DRIVER: quay.io/opendatahub/ds-pipelines-driver:pr-29
DSP LAUNCHER: quay.io/opendatahub/ds-pipelines-launcher:pr-29
Persistence Agent: quay.io/opendatahub/ds-pipelines-persistenceagent:pr-29
Scheduled Workflow Manager: quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-29
MLMD Server: quay.io/opendatahub/mlmd-grpc-server:latest
MLMD Envoy Proxy: registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2
UI: quay.io/opendatahub/ds-pipelines-frontend:pr-29

[dsp-developers]

An OCP cluster where you are logged in as cluster admin is required.

The Data Science Pipelines team recommends testing this using the Data Science Pipelines Operator. Check here for more information on using the DSPO.

To use and deploy a DSP stack with these images (assuming the DSPO is deployed), first save the following YAML to a file named dspa.pr-29.yaml:

apiVersion: datasciencepipelinesapplications.opendatahub.io/v1alpha1
kind: DataSciencePipelinesApplication
metadata:
  name: pr-29
spec:
  dspVersion: v2
  apiServer:
    image: "quay.io/opendatahub/ds-pipelines-api-server:pr-29"
    argoDriverImage: "quay.io/opendatahub/ds-pipelines-driver:pr-29"
    argoLauncherImage: "quay.io/opendatahub/ds-pipelines-launcher:pr-29"
  persistenceAgent:
    image: "quay.io/opendatahub/ds-pipelines-persistenceagent:pr-29"
  scheduledWorkflow:
    image: "quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-29"
  mlmd:  
    deploy: true  # Optional component
    grpc:
      image: "quay.io/opendatahub/mlmd-grpc-server:latest"
    envoy:
      image: "registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2"
  mlpipelineUI:
    deploy: true  # Optional component 
    image: "quay.io/opendatahub/ds-pipelines-frontend:pr-29"
  objectStorage:
    minio:
      deploy: true
      image: 'quay.io/opendatahub/minio:RELEASE.2019-08-14T20-37-41Z-license-compliance'

Then run the following:

cd $(mktemp -d)
git clone [email protected]:opendatahub-io/data-science-pipelines.git
cd data-science-pipelines/
git fetch origin pull/29/head
git checkout -b pullrequest a5ed7093ccada9ae62fca24c9922d612dd903e3d
oc apply -f dspa.pr-29.yaml

More instructions here on how to deploy and test a Data Science Pipelines Application.

[gmfrasca]

/lgtm

[DharmitD]

/lgtm