Skip to content

Add TSG to fix x509 authentication between NC and Hosts after Solution Update#275

Open
arudell wants to merge 12 commits intoAzure:mainfrom
arudell:tsg/networking/nchost-agent-apiservice-update
Open

Add TSG to fix x509 authentication between NC and Hosts after Solution Update#275
arudell wants to merge 12 commits intoAzure:mainfrom
arudell:tsg/networking/nchost-agent-apiservice-update

Conversation

@arudell
Copy link
Copy Markdown
Collaborator

@arudell arudell commented Apr 17, 2026

This pull request adds new troubleshooting documentation for a critical SDN Express issue where NcHostAgent is unable to connect to the ApiService after a solution update. The documentation outlines the problem, root causes, and provides step-by-step resolution guidance. The main changes are:

Documentation Additions:

  • Added a new troubleshooting guide: Troubleshoot-SDNExpress-NcHostAgent-Unable-To-Connect-ApiService-After-Solution-Update.md, which covers symptoms, root causes, and resolutions for the NcHostAgent connection issue following solution updates.
  • Updated README.md to include a link to the new troubleshooting document, making it easier to find and reference.

arudell and others added 5 commits April 17, 2026 15:12
…pdate

Add troubleshooting guide for NcHostAgent connectivity failure to Network
Controller ApiService following Azure Local solution updates. The issue is
caused by missing NetworkControllerNodeNames registry key on Hyper-V hosts,
which prevents certificate rotation from propagating to NC VMs.

Mitigation steps include:
- Validating and populating the registry key on all hosts
- Verifying local admin permissions on NC VMs
- Running Start-SdnServerCertificateRotation for short-term recovery

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Break the Root Cause into distinct sub-sections:
1. Missing NetworkControllerNodeNames registry key
2. HCI admin user not in Local Administrators on NC VMs
3. Code defect in certificate rotation logic (fix in progress)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI review requested due to automatic review settings April 17, 2026 21:20
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new Azure Local Networking (SDN Express / Network Controller) troubleshooting guide for a post–solution update failure where NcHostAgent cannot authenticate/connect to the NC ApiService, and links it from the Networking README so it’s discoverable.

Changes:

  • Added a new TSG documenting symptoms, root causes, and mitigation steps for x509/auth failures between NC and hosts after solution update certificate rotation.
  • Updated the Networking README to include the new TSG under the SDN Express section.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.

File Description
TSG/Networking/SDN-Express/Troubleshoot-SDNExpress-NcHostAgent-Unable-To-Connect-ApiService-After-Solution-Update.md New TSG describing the issue and providing diagnostic/resolution steps (including PowerShell guidance).
TSG/Networking/README.md Adds a TOC entry linking to the new troubleshooting guide.

arudell and others added 6 commits April 17, 2026 16:23
…-Unable-To-Connect-ApiService-After-Solution-Update.md

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
…-Unable-To-Connect-ApiService-After-Solution-Update.md

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants