kubernetes-sigs/cluster-api-provider-vsphere

Possible Deadlock scenario when permissions are not set correctly

Open

#1,176 opened on Apr 30, 2021

View on GitHub
 (5 comments) (0 reactions) (0 assignees)Go (320 forks)auto 404
area/govmomihelp wantedkind/buglifecycle/frozen

Repository metrics

Stars
 (417 stars)
PR merge metrics
 (PR metrics pending)

Description

/kind bug

What steps did you take and what happened: if you have created a cluster on resources that you dont have permissions for you are not able to delete if without manually patching finalizers

    Last Transition Time:  2021-04-30T10:26:54Z
    Message:               error finding object by uuid "f027dece-38b9-4b78-998c-3e14b5a95d9e": ServerFaultCode: Permission to perform this operation was denied.
    Reason:                DeletionFailed
    Severity:              Warning
    Status:                False
    Type:                  VMProvisioned

What did you expect to happen: the vsperemachine and thus the cluster get deleted properly Anything else you would like to add: [Miscellaneous information that will assist in solving the issue.]

Environment:

  • Cluster-api-provider-vsphere version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):

Contributor guide

Research direction
Investigate the deletion logic in the vsphere machine controller, focusing on how finalizers are handled and why the deletion fails when permissions are insufficient. Look at the error handling for the 'DeletionFailed' reason and trace the code path that leads to the deadlock.
Tech stack
go
Domain
backendinfrastructure
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
KubernetesvSphere
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40