Cannot fetch provider configuration. Please contact your administrator
" is returned. This would be when the Kubernetes version is selected./root/cse.log
on the Container Service Extension (CSE) Server shows errors of the form:I0115 03:47:09.177567 23580 auth.go:50] Using VCD OpenAPI version [37.2]
E0115 03:47:09.179876 23580 auth.go:64] failed to authenticate using refresh token
panic: error logging into VCD: [unable to get swagger client from secrets: [unable to get bearer token from secrets: [failed to set authorization header: [error getting bearer token: error authorizing service account: Post "https://<VCD FQDN>/oauth/provider/token": dial tcp: lookup <VCD FQDN> on 127.0.0.53:53: server misbehaving]]]]
The CSE appliance lacks proper DNS configuration after deployment. This can be told from the logs on the CSE appliance.
To resolve this issue ensure that the CSE Server is configured with a valid DNS server.
Typically the DNS server configuration is taken at deployment from the Organization VDC Network to which the CSE Server VM is attached.
Example steps would be as follows:
root/vmware
but a custom or autogenerated password can also be set on deployment of the CSE Server using Guest OS Customization./root/cse.log
. In this situation it may look like:I0115 03:47:09.177567 23580 auth.go:50] Using VCD OpenAPI version [37.2]
E0115 03:47:09.179876 23580 auth.go:64] failed to authenticate using refresh token
panic: error logging into VCD: [unable to get swagger client from secrets: [unable to get bearer token from secrets: [failed to set authorization header: [error getting bearer token: error authorizing service account: Post "https://<VCD FQDN>/oauth/provider/token": dial tcp: lookup <VCD FQDN> on 127.0.0.53:53: server misbehaving]]]]
nslookup <VCD FQDN>
For more information on the prerequisites for deployment of the CSE Server see the documentation, VMware Cloud Director Container Service Extension Server Prerequisites.