Skip to content
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

issues with vcenter fqdns that contains uppercase #351

Closed
yastij opened this issue Jul 2, 2020 · 5 comments
Closed

issues with vcenter fqdns that contains uppercase #351

yastij opened this issue Jul 2, 2020 · 5 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.
Milestone

Comments

@yastij
Copy link
Member

yastij commented Jul 2, 2020

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug

it seems like we are lower casing the vcenter fqdn before storing in the cache

credentialKey = strings.ToLower(credentialKey)
if strings.HasSuffix(credentialKey, "password") {
vcServer := strings.Split(credentialKey, ".password")[0]
if _, ok := config[vcServer]; !ok {
config[vcServer] = &Credential{}
}
config[vcServer].Password = string(credentialValue)
} else if strings.HasSuffix(credentialKey, "username") {
vcServer := strings.Split(credentialKey, ".username")[0]
if _, ok := config[vcServer]; !ok {
config[vcServer] = &Credential{}
}
config[vcServer].User = string(credentialValue)
, but when trying to access credentials we are using vcenter fqdn as is, see:

credentials, err := credMgr.GetCredential(vcInstance.Cfg.VCenterIP)
,

/assign @dvonthenen

What happened:

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

  • vsphere-cloud-controller-manager version:
  • OS (e.g. from /etc/os-release):
  • Kernel (e.g. uname -a):
  • Install tools:
  • Others:
@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Jul 2, 2020
@frapposelli frapposelli added this to the v1.18.0 milestone Jul 2, 2020
@davidvonthenen
Copy link
Contributor

Thanks @yastij for catching this!

@vuil
Copy link

vuil commented Jul 8, 2020

@dvonthenen is this an issue that will be addressed soon? Look for guidance on whether we need to address TKG-2098.

@davidvonthenen
Copy link
Contributor

The PR (above) to fix this was opened the same day the issue was filed. Just waiting for feedback or a merge on this PR in order to close this out.

@davidvonthenen
Copy link
Contributor

/close

@k8s-ci-robot
Copy link
Contributor

@dvonthenen: Closing this issue.

In response to this:

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

5 participants