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

[SURE-9775] vsphere provider and missing credentials_keys #1109

Open
thehejik opened this issue Feb 27, 2025 · 1 comment · Fixed by #1110
Open

[SURE-9775] vsphere provider and missing credentials_keys #1109

thehejik opened this issue Feb 27, 2025 · 1 comment · Fixed by #1110
Assignees
Labels
JIRA must shout kind/bug Something isn't working
Milestone

Comments

@thehejik
Copy link
Collaborator

thehejik commented Feb 27, 2025

What steps did you take and what happened?

Latest Turtles v0.17.0-rc.0 and capi-ui 0.8.2 on local rancher:v2.10-head

There is a Credential keys missing message in vsphere CAPIProvider resource after providing vsphere secret when provisioning vsphere provider over capi-ui.

$ k get capiproviders.turtles-capi.cattle.io  -n capv-system vsphere -o yaml
apiVersion: turtles-capi.cattle.io/v1alpha1
kind: CAPIProvider
spec:
  configSecret:
    name: vsphere-credentials-rctrb
  credentials:
    rancherCloudCredentialNamespaceName: cattle-global-data:cc-rc28p
  features:
    clusterResourceSet: true
    clusterTopology: true
    machinePool: true
  name: vsphere
  type: infrastructure
  variables: {}
status:
  conditions
  - lastTransitionTime: "2025-02-26T16:25:27Z"
    message: 'Credential keys missing: [key not found: vmwarevsphere-password, key
      not found: vmwarevsphere-username]'
    reason: RancherCredentialKeyMissing
    severity: Error
    status: "False"
    type: RancherCredentialsSecretMapped
  contract: v1beta1
  installedVersion: v1.12.0
  name: vsphere
  observedGeneration: 2
  phase: Ready
  variables:
    CLUSTER_TOPOLOGY: "true"
    EXP_CLUSTER_RESOURCE_SET: "true"
    EXP_MACHINE_POOL: "true"

Seems RancherCredentialsSecretMapped is expecting vmwarevsphere-password and vmwarevsphere-username but the credentials secret we create when provisioning the vsphere provider consists of:

apiVersion: v1
data:
  vmwarevspherecredentialConfig-password: XXX
  vmwarevspherecredentialConfig-username: XXX
  vmwarevspherecredentialConfig-vcenter: XXX
  vmwarevspherecredentialConfig-vcenterPort: XXX
kind: Secret
...

Also secret capv-manager-bootstrap-credentials is empty then:
Image

Anyway vsphere provider is Ready and I could provision a capv cluster but most probably due to my custom resources where credentials are passed in a different way and not using the secret.

@thehejik thehejik added kind/bug Something isn't working JIRA must shout labels Feb 27, 2025
@kkaempf kkaempf added this to the March 2025 milestone Feb 27, 2025
@kkaempf kkaempf moved this to Team Backlog in CAPI / Turtles Feb 27, 2025
@thehejik
Copy link
Collaborator Author

Fix successfully validated here #1110 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
JIRA must shout kind/bug Something isn't working
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants