• Locate the issues
• Remediate issues
• Run manual upgrade of MOC ARB
• Error: Unable to find file release: mariner-2-0

I got this from Microsoft Premium Support. I was working on a Azure Local stack that would not update the MOC ARB to latest version doing the solution update. We ended up skipping the update from the solution update so the rest of the solution update would pass and then work on the MOC ARB afterwards. (I talk about how to skip certain sections of the solution update here: (Use with caution) /blog/wp/azure-local-update-issue-evalcauretryapplicability/)

Locate the issues

---

We will be using a PowerShell module to test the AKS configuration and remediate issues afterwards. To use Test-SupportAksArcKnownIssues, you must first install and import the Support.AksArc PowerShell module:

Install-Module -Name Support.AksArc
Import-Module Support.AksArc

Then you can run:

Test-SupportAksArcKnownIssues

Output from running the command showed me issues about the image being stuck in “deleting state”:

TestName                                                   Status Message

——–                                                   —— ——-

Validate Failover Cluster Service Responsiveness           Passed Failover Cluster service is responsive.

Validate Missing MOC Cloud Agents                          Passed No missing MOC cloud agents found.

Validate MOC Cloud Agent Running                           Passed MOC Cloud Agent is running

Validate MOC Admin Token Expiry                            Passed MOC admin token is valid. Expiry: 11/16/2025 13:17…

Validate Missing MOC Node Agents                           Passed All MOC nodes have the Node Agent service installe…

Validate Missing MOC Host Agents                           Passed All nodes have MOC host agents installed and healthy.

Validate MOC is on Latest Patch Version                    Failed MOC is not on the latest patch version. Current: 1…

Validate Expired Certificates                              Passed No expired certificates found.

Validate MOC Nodes Not Active                              Passed All MOC nodes are in the ‘Active’ state.

Validate MOC Nodes Sync with Cluster Nodes                 Passed All MOC nodes are in sync with cluster nodes.

Validate Multiple MOC Cloud Agent Instances                Passed No multiple instances of MOC Cloud Agent found.

Validate MOC Powershell Not Stuck in Updating              Passed MOC Powershell is not stuck in updating state.

Validate Windows Event Log Running                         Passed Windows Event Log is running

Validate Gallery Image Stuck In Deleting                   Failed The gallery images are stuck in deleting state and...

Validate Virtual Machine Stuck In Pending                  Passed No virtual machines are stuck in pending state.

Validate Virtual Machine Management Service Responsiveness Passed Virtual Machine Management service is responsive.

Validate Empty MOC Identity Tokens                         Passed No empty MOC identity tokens found.

Validate MOC PowerShell Configuration                      Passed MOC PowerShell configuration is valid.

Remediate issues

I then used this command to start the remediation:

Invoke-SupportAksArcRemediation

After running the command which took about 5 minutes, I ran the test again and it showed no errors now.

Run manual upgrade of MOC ARB

Now that no errors was present, I could then start manuel upgrade of the MOC ARB:

Note that the config file must exist, so you may need to change the path to fit your setup

az login --use-device-code
az arcappliance upgrade hci --config-file "C:\ClusterStorage\Infrastructure_1\Shares\SU1_Infrastructure_1\MocArb\WorkingDirectory\Appliance\hci-appliance.yaml"

Error: Unable to find file release: mariner-2-0

Error: Unable to find file release: ^mariner-2-0-(.*)-vhdx-rpm-(.*)$ with version:  in product release: arc-appliance-stable-releases.

This error was sadly still present even after fixing the issues with the AKS configuration.

This could be about the fact that Microsoft is retiring Azure Linux 2.0 (formerly mariner): https://techcommunity.microsoft.com/blog/azurearcblog/eol-of-azure-linux-2-0-on-azure-kubernetes-service-enabled-by-azure-arc/4434242

It should not be removed yet, since it should be supported the rest of 2025 (still waiting for Microsoft to confirm).

Azure Local 2507 and newer ships with Azure Linux 3.0 and my customers Azure Local stack was at 2504 (20th of september 2025, so it was behind on patching).

I’m currently working with Microsoft to fix the issue and will update this article once we get a valid fix for the issue.

UPDATE 21th september 2025: 2504 can update directly to 2508. And doing this update the MOC ARB got updated from 1.3 to 1.5 and the above error got resolved.