microsoft / microsoft/SdnDiagnostics
Improve detection if missing AzureStackCertificationAuthority certificate
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 34
- Forks
- 6
- Avg merge
- 5d 14h
- Merged PRs (30d)
- 5
Description
For Azure Local deployments, if we do not have connectivity from NCHostAgent to NC API service, look at the certs present on the system to see if the AzureStackCertificationAuthority cert was recently generated and provide advise to install the cert to trusted root on each of the NC VMs
Copy-SdnFileToComputer -Path 'C:\ClusterStorage\Infrastructure_1\Shares\SU1_Infrastructure_1\AzureStackCertificateAuthority\AzureStackCertificationAuthority.cer' -Destination (Get-SdnWorkingDirectory) -ComputerName 'NC1','NC2','NC3'
Invoke-SdnCommand -ComputerName 'NC1','NC2','NC3' -ScriptBlock {
$cert = Get-ChildItem -Path "$(Get-SdnWorkingDirectory)\AzureStackCertificationAuthority.cer"
Import-SdnCertificate -FilePath $cert.FullName -CertStore 'Cert:\LocalMachine\Root'
}
Contributor guide
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.
Research direction
Start by locating the PowerShell diagnostic path for Azure Local connectivity between NCHostAgent and the NC API service, then review the AzureStackCertificationAuthority.cer workflow and the shown Copy-SdnFileToComputer and Invoke-SdnCommand commands. Done means missing connectivity triggers detection of a recently generated certificate and actionable advice to install it in Cert:\LocalMachine\Root on each NC VM.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100