adds log when gpuManager.start() failed

[x1957]

If gpuManager.start() returns error, there is no log.

We confused with scheduler do not schedule any pod(with gpu) to one node.
kubectl describe node xxx shows there is no gpu on that node, because the gpu driver do not work on that node, gpuManager.start() failed, but we can not see anything in log.

[k8s-reviewable]

This change is 

[k8s-ci-robot]

Hi @x1957. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with @k8s-bot ok to test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[cmluciano]

Possible dup of #44463

[xiangpengzhao]

SGTM:)

[xiangpengzhao]

@cmluciano I find your that PR doesn't include what this PR does. Since that PR is WIP, did you ever plan to include this? :)

[cmluciano]

The linked PR does log here. It then retries the GPU initiate process in a go routine.

[vishh]

/lgtm
/approve

It's better to surface errors. I agree with @cmluciano. The issue might be that of parallel driver installation.

[vishh]

@k8s-bot ok to test

[k8s-github-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vishh, x1957

Needs approval from an approver in each of these OWNERS Files:

• pkg/kubelet/OWNERS [vishh]

You can indicate your approval by writing /approve in a comment
You can cancel your approval by writing /approve cancel in a comment

[vishh]

Thanks for the patch @x1957

[x1957]

@cmluciano nice work #

[x1957]

@k8s-bot kops aws e2e test this

[xiangpengzhao]

Submit Queue — PR is missing CLA label; needs one of cla: yes, cncf-cla: yes or cla: human-approved

@x1957 check your CLA status, please.

[x1957]

@xiangpengzhao How to check CLA status? Thanks

[xiangpengzhao]

cla/linuxfoundation — x1957 authorized This check shows that your CLA was ok. I don't know why the label was missed and how to check again. You may need @vishh to label it manually if your CLA signature can be confirmed.

@fejta any thoughts? Do we have some manual way to check and label cncf-cla:yes ?

[dankohn]

@emsearcy I believe this may be an after-effect of the CLAbot bug from a couple weeks ago. Could you please trigger a re-run?

[x1957]

@dankohn @emsearcy thanks

[emsearcy]

@dankohn our CLA tool doesn't touch the labels: it's only responsible for the cla/linuxfoundation status check result. There is another Kubernetes-specific bot that uses the cla/linuxfoundation status to set labels.

[dankohn]

@caniszczyk ???

[madhusudancs]

@k8s-bot pull-kubernetes-federation-e2e-gce test this

[foxish]

Added label manually. May have been a github glitch. The label automation is on our end. cc @kubernetes/test-infra-maintainers

[k8s-github-robot]

Automatic merge from submit-queue