New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vCenter password with special characters locks down my vCenter user #102

Closed
frodenas opened this Issue Aug 20, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@frodenas
Contributor

frodenas commented Aug 20, 2017

I deployed this release using kubo-deployment on vSphere and the deployment failed when updating the worker/0 vm with this error message: Error: Unknown CPI error 'Unknown' with message 'Cannot complete login due to an incorrect user name or password.' in 'create_disk' CPI method. Redeploying again (several times) resulted in the same error. Weird that bosh was able to create vms on a previous step but failed at this point.

I logged into my vCenter console and saw a bunch of login errors. But when I used the same user/pwd combination used by the bosh properties I was able to login without any problems.

When I looked into the kubernetes-controller-manager job logs I saw this error multiple times: F0820 18:41:39.739969 7530 controllermanager.go:176] error building controller context: cloud provider could not be initialized: could not init cloud provider "vsphere": ServerFaultCode: Cannot complete login due to an incorrect user name or password.

After some debugging I discovered that the vsphere cloud provider does NOT enclose the password inside double quotes, and my vCenter password contains special characters (the ; sign). So what it is happening is that the controller-manager is NOT using the full password (only the characters until the ; sign), and as a result, it locks down my user periodically (each time monit restart the process).

@cf-gitbot

This comment has been minimized.

cf-gitbot commented Aug 20, 2017

We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story.

The labels on this github issue will be updated when the story is started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment