fix rbd device works at block mode not get mapped to container

[wenlxie]

In my environment, restart docker will caused all of the container restart(our kernel is a bit old).
Kubelet will also be restart.
After the container up , I checked the container and find the RBD block device is not mapped to container.
When I inspect the container, its {HostConfig.Devices[]} field is empty.
I did some debug, then find that at code https://github.com/kubernetes/kubernetes/blob/master/pkg/kubelet/kubelet_pods.go#L113
The volName is empty.

Fix issues for block device not mapped to container.

[wenlxie]

@mkimuram @mtanino @sbezverk @wgliang PTAL

[wgliang]

/ok-to-test

[wgliang]

@wenlxie Please add unit test case for it. You'd better submit one detail issue about it.

[mkimuram]

I confirmed that it's the similar fix discussed for Azure in #63841 and fixed in the same way as below commit(541edb7)

[wgliang]

/skip

[wgliang]

/assign @rootfs

[sjenning]

/uncc

[wenlxie]

UT case had been added
@wgliang @rootfs PTAL

[wgliang]

/test pull-kubernetes-e2e-kops-aws

[wenlxie]

@wgliang Test had all passed

[wgliang]

/lgtm

[wenlxie]

@dims Can you have the look?
It is pending for a long time
Thanks

[dims]

@kubernetes/sig-storage-pr-reviews

[dims]

/sig storage

[jsafrane]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jsafrane, wenlxie, wgliang

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:

• pkg/volume/rbd/OWNERS [jsafrane]

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

[k8s-github-robot]

Automatic merge from submit-queue (batch tested with PRs 65254, 64837, 64782, 64555, 64850). If you want to cherry-pick this change to another branch, please follow the instructions here.