Azure / Azure/AzureLocal-Supportability
Readiness Check Fails if certain PSGallery Powershell Modules are installed
- Dominant language
- PowerShell
- Stars
- 78
- Forks
- 60
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 5
Description
**Bug description**
Readiness check completely fails to run if there are extra powershell modules installed, preventing any kind of update from running. The error produced from this failure doesn't provide any useful diagnostic information.
For example, running get-solution update results in this line:
HealthCheckResult : {Error reading readiness results for System}
**Repro steps**
Steps to reproduce the behavior:
1. Install VMFleet Powershell module on any node. (Or "cluster" powershell module from the PSGallery)
2. Attempt to run a readiness check
**Expected behavior**
1. Readiness check fails with an error that describes conflicting powershell modules that are installed.
2. When updates are run, there should be a prompt asking to uninstall the conflicting modules first.
**Environment (please complete the following information):**
- Azure Local 12.2509 (Currently being upgraded now)
- 4 node cluster
- Production
- East US Region
Contributor guide
Research direction
Reproduce the failure by installing the VMFleet or cluster PowerShell module, then run a readiness check and get-solution update. Trace the readiness-check and update entry points to identify where the generic System error is produced; done means conflicting modules are named clearly and updates prompt for their removal.
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
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100