Install-SfbLabRequirements fails - incorrect function called
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- powershell
- Domain
- devops
Research direction
Start at SfBAutomatedLab.psm1 around lines 314-315 and reproduce the failure through Install-SfbLabRequirements. Check the reported Get-LabMachine call and its use as the ComputerName argument. Done means the reported command-not-found error and resulting null-argument error no longer occur.
Written by the indexing model from the issue text.
Description
Install-SfbLabRequirements fails with multiple message like this one:
Get-LabMachine : The term 'Get-LabMachine' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included,
verify that the path is correct and try again.
At C:\Program Files\WindowsPowerShell\Modules\SfBAutomatedLab\0.6\SfBAutomatedLab.psm1:314 char:17
+ $machines = Get-LabMachine
+ ~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Get-LabMachine:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Install-LabWindowsFeature : Cannot validate argument on parameter 'ComputerName'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command
again.
At C:\Program Files\WindowsPowerShell\Modules\SfBAutomatedLab\0.6\SfBAutomatedLab.psm1:315 char:45
+ Install-LabWindowsFeature -ComputerName $machines -FeatureName NE ...
+ ~~~~~~~~~
+ CategoryInfo : InvalidData: (:) [Install-LabWindowsFeature], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationError,Install-LabWindowsFeature
This is because Get-LabMachineDefinition should be used instead of Get-LabMachine.
- Dominant language
- PowerShell
- Stars
- 14
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AutomatedLab/SfBAutomatedLab
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
AutomatedLab/SfBAutomatedLab#12 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 15/100
All issues in AutomatedLab/SfBAutomatedLab
Similar issues
-
agent/sec-check hive/hosted-available-lke648397-260827-5n31 security
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
agentic-workflows documentation workflow-editor
Difficulty 1/5 1-3 hours Newbie friendliness 65/100
githubnext/gh-aw-workshop#4246 ·
Maintainers usually reply within 1 day
-
sync-en
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 3 days
-
documentation good first issue
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day