[BUG] Write-Error: Cannot add a member with the name "ControlPlane" even though its the first installation

[DenizYueksel98]

Describe the bug
When we have the .msi installed and call the "New-AksEdgeDeployment" for the first time, we receive the following Error Message:

At C:\Program Files\WindowsPowerShell\Modules\AksEdge\1.9.262\AksEdge.psm1:12222 char:37
+ ... LinuxNode | Add-Member -MemberType NoteProperty -Name "ControlPlane" ...
+                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (@{ControlPlant=...ssthough=True}:PSObject) [Add-Member], InvalidOperationException
+ FullyQualifiedErrorld: MemberAlreadyExists,Microsoft.PowerShell.Commands.AddMemberCommand

To Reproduce
Steps to reproduce the behavior:

1. Fresh Windows Installation
2. Installed AksEdge-K3s-1.29.6-1.9.262.0.msi as well as the Powershell Modules
3. Run command "New-AksEdgeDeployment" for an offline cluster deployment

Expected behavior
The execution of the command is successful and the offline cluster gets deployed as expected. However, an error is thrown indicating that a control plane already exists, which should not be the case on a fresh installation.

Screenshots

Environment (please complete the following information):

• AKS Edge Essentials Version 1.9.262.0
• Kubernetes version K3s 1.29.6
• Windows Host OS (please complete the following information):
  • Edition: Windows 10 IoT Enterprise LTSC
  • Version: 21H2 19044.1288
  • Virtual Machine: None

[jagadishmurugan]

@DenizYueksel98 can you run Get-AksEdgeLogs and share the logs? thanks!

[DenizYueksel98]

aksedgelogs-250217-1713.zip
I had removed the VM meanwhile and needed some time to reconstruct it, but the observed behaviour for an airgapped deployment stays the same.

[DenizYueksel98]

The Bug is still existing in the latest version of AKS Edge 1.10.868.0

[scholz]

@SummerSmith : could someone from the team take a look into this for the next version?
(From outside) It seems like a simple issue to fix but it causes problems in our automatic installation procedure as we cannot use our normal logging (which usually fails when errors occur) but must work around this "expected error".