Skip to content

Commit 031ea7a

Browse files
learn-build-service-prod[bot]sethmanheimLearn Build Service GitHub AppHaikoHertesCopilot
authored
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-stack-docs (branch main) (#21243)
* Update deployment-without-azure-arc-gateway.md When using multi-line PowerShell cmdlets, we need to mask the line-break, otherwise, first line would be used as-is, missing all the parameters. * Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> * Refactor Arc registration script for clarity and options I have replaced the line-breaks with splatting... * Update LTS end of life for 1.30 (#4337) * Update kubeconfig instructions for IP address usage (#4346) Clarify kubeconfig server address instructions to include port number. * Update Firmware versions in BOMs (#4335) Update Firmware versions in BOMs Components updated: iDRAC, BIOS, NVIDIA ConnectX‑6 Lx (2×25G), and Broadcom network. * Change Azure permissions assignment instructions (#4372) Updated instructions to assign Azure permissions for deployment from resource group instead of subscription. * Kbarilar updates (#4375) * this is a test * Known issues update * Updated known issues workaround * Removing test * Update azure-local/small-form-factor/small-form-factor-known-issues.md Co-authored-by: sipastak <61058798+sipastak@users.noreply.github.com> * Update azure-local/small-form-factor/small-form-factor-known-issues.md Co-authored-by: sipastak <61058798+sipastak@users.noreply.github.com> * Update azure-local/small-form-factor/small-form-factor-known-issues.md Co-authored-by: sipastak <61058798+sipastak@users.noreply.github.com> * Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: sipastak <61058798+sipastak@users.noreply.github.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> --------- Co-authored-by: Seth Manheim <sethm@microsoft.com> Co-authored-by: Learn Build Service GitHub App <Learn Build Service LearnBuild@microsoft.com> Co-authored-by: learn-build-service-prod[bot] <113403604+learn-build-service-prod[bot]@users.noreply.github.com> Co-authored-by: Haiko Hertes <HaikoHertes@users.noreply.github.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Co-authored-by: Regan Downer <v-rdowner@microsoft.com> Co-authored-by: Travis Neely <travisneely@gmail.com> Co-authored-by: Tony Joint <ajoint@gmail.com> Co-authored-by: sirajyasin <38433478+sirajyasin@users.noreply.github.com> Co-authored-by: PRATEEK PRASHER <prateekprshr@gmail.com> Co-authored-by: Kiana Harris <43056496+kianaharris4@users.noreply.github.com> Co-authored-by: sipastak <61058798+sipastak@users.noreply.github.com>
1 parent 3b776f9 commit 031ea7a

2 files changed

Lines changed: 4 additions & 4 deletions

File tree

‎azure-local/small-form-factor/small-form-factor-faq.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,4 +39,4 @@ Run:
3939
az provisionedmachine reset-os --name <NAME_OF_MACHINE> --resource-group <RESOURCE_GROUP_NAME>
4040
```
4141

42-
After the reset finishes, you can provision the machine again by using either the Azure portal or the Azure CLI.
42+
After the reset finishes, you can provision the machine again by using either the Azure portal or the Azure CLI.

‎azure-local/small-form-factor/small-form-factor-known-issues.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -19,13 +19,13 @@ The following known issues apply to Azure Local small form factor deployments ru
1919

2020
| Feature area | Issue | Impact | Workaround |
2121
|---|---|---|---|
22-
| Subscription setup | New required resource providers were added since the last release. | Deployment can fail if the required providers aren't registered. | Validate your subscription against the current required provider list before deployment. |
22+
| Subscription setup | New required resource providers were added since the last release. | Deployment can fail if the required providers aren't registered. | [Validate your subscription against the current required provider list before deployment](small-form-factor-subscription-setup.md#register-the-required-resource-providers). |
2323
| Subscription policy | Azure policies that restrict publicly accessible storage accounts can block deployment. | Provisioned machine creation can fail during storage account-related steps. | If you hit storage account errors, review subscription policies that restrict publicly accessible storage accounts. |
2424
| ROE install | NUC 15 Pro doesn't show status messages on the CLI during ROE install. | This behavior can be confusing during testing because the installation might appear stalled. | When you're testing on a NUC 15 Pro, treat a blank screen with a blinking cursor as a successful in-progress state. |
2525
| OS provisioning | During OS provisioning, the Azure portal may display the status **Action Required!** even though provisioning is progressing successfully. | Users may incorrectly assume that provisioning has failed and could file unnecessary support requests or ICMs. | No action is required. OS provisioning continues to run successfully despite the incorrect status message. Monitor the provisioning workflow until completion. |
26-
| OS provisioning | OS provisioning can intermittently fail because the `LinuxEdgeObservability` extension times out during deployment. The extension attempts to retrieve the GCS configuration file after observability tenant registration, which can take up to eight minutes. However, the Azure Arc extension manager imposes a five-minute timeout on the enable operation. | OS provisioning may intermittently fail during deployment. | Retry the OS provisioning operation. This issue is intermittent and occurs when the observability tenant registration exceeds the extension manager timeout window. |
26+
| OS provisioning | OS provisioning can intermittently fail because the `LinuxEdgeObservability` extension times out during deployment. The extension attempts to retrieve the GCS configuration file after observability tenant registration, which can take up to eight minutes. However, the Azure Arc extension manager imposes a five-minute timeout on the enable operation. | OS provisioning may intermittently fail during deployment. | [Retry the OS provisioning operation](../deploy/troubleshoot-simplified-machine-provisioning.md#reattempt-a-failed-os-provisioning). This issue is intermittent and occurs when the observability tenant registration exceeds the extension manager timeout window. |
2727
| Reset OS | After running `reset-os`, the provisioned machine state in the Azure portal may display as **Unknown** instead of a resetting state. | Users may be unsure whether the reset operation is progressing successfully. | This behavior is expected in version 2604. Reset status flows and reset operations are not yet fully supported in the Azure portal for small form factor deployments. The portal currently defaults unsupported states to **Unknown**. |
28-
| Retesting | TPM slot exhaustion can happen after repeated deployments, usually after about 15 runs. | Retesting can fail when no TPM slots remain. | Manually clear the TPM in BIOS before you retest. |
28+
| Retesting | TPM slot exhaustion can happen after repeated deployments, usually after about 15 runs. | Retesting can fail when no TPM slots remain. | [Manually clear the TPM in BIOS before you retest](small-form-factor-troubleshoot.md#tpm-isnt-writable-during-provisioning). |
2929

3030
## Related content
3131

0 commit comments

Comments
 (0)