Description of problem: For fresh installation with 4.3 nightly build, pvc is always in pending status and pc cannot be created, when checking pvc info, it reports: Failed to provision volume with StorageClass "thin": No VM found As we met storage issue in upgrade env yesterday(Bug #1776773), when checking kubelet process, we see '--cloud-provider=', but after modification, it still doesn't work. Also we see kubelet log as below, seems config file not specified, so add --cloud-provider in kubelet process doesn't work. Nov 26 08:11:24 compute-0 hyperkube[1723]: I1126 08:11:24.311085 1723 plugins.go:100] No cloud provider specified. Nov 26 08:11:24 compute-0 hyperkube[1723]: I1126 08:11:24.311108 1723 server.go:533] No cloud provider specified: "" from the config file: "" Version-Release number of selected component (if applicable): 4.3.0-0.nightly-2019-11-25-153929 How reproducible: Steps to Reproduce: 1. create pod with pvc using default sc "thin" 2. check pod/pvc status Actual results: pod is pending pvc is pedning Expected results: pod should be running and pvc should be bounded. Master Log: Node Log (of failed PODs): from kubelet: Nov 26 08:11:24 compute-0 hyperkube[1723]: I1126 08:11:24.311085 1723 plugins.go:100] No cloud provider specified. Nov 26 08:11:24 compute-0 hyperkube[1723]: I1126 08:11:24.311108 1723 server.go:533] No cloud provider specified: "" from the config file: "" PV Dump: PVC Dump: Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning ProvisioningFailed 4m5s (x41 over 79m) persistentvolume-controller Failed to provision volume with StorageClass "thin": No VM found StorageClass Dump (if StorageClass used by PV/PVC): Additional info: