Azure / Azure/Microsoft.AVS.Management
Disconnect ISCSI Target should check for VMs on datastore before continuing.
Open
- Dominant language
- PowerShell
- Stars
- 13
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
Before disconnecting or removing an iscsi target there should be a check to validate that there are no VMs currently registered and using the datastore. This causes orphaned objects and run command failures/timeouts.
Contributor guide
Research direction
Start by locating the PowerCLI entry point that disconnects or removes an iSCSI target, then trace how its datastore and registered VMs are represented. Done means the operation checks for VMs using the datastore before continuing and prevents the orphaned-object and command-failure behavior described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100