Install-AksHci fails on latest server 2022 in powershell and windows admin center

keith siilats 1 Reputation point
2021-11-04T21:00:11.99+00:00

Hi in Powershell following step 5
https://learn.microsoft.com/en-us/azure-stack/aks-hci/kubernetes-walkthrough-powershell
senthiPS C:\Users\Administrator> Install-AksHci
VERBOSE: [11/04/2021 16:13:54] [Kva] Uninstalling KVA without Azure Connection may result in leaked Arc Connected
Clusters, Please clean up resources in portal.
create --configfile "f:\clusterstorage\volume1\ImageStore\1.0.5.11028\yaml\appliance.yaml" --outfile
"f:\clusterstorage\volume1\ImageStore\1.0.5.11028\kubeconfig-mgmt" --azure-creds-stdin returned a non zero exit code
1 [Error: unable to reconcile group: rpc error: code = Unavailable desc = connection closed]
At C:\Program Files\WindowsPowerShell\Modules\Kva\1.0.13\Kva.psm1:3629 char:9

  • throw "$command $arguments returned a non zero exit code $LAS ...

And If i follow the Windows Administrator version on installing aks-hci i get:
ErrorWe cannot display the changes right now.: The following commands are already available on this system:'Find-Package,Install-Package,Uninstall-Package'. This module 'PackageManagement' may override the existing commands. If you still want to install this module 'PackageManagement', use -AllowClobber parameter.

I ran this command successfully:
Install-Module -Name PackageManagement -Repository PSGallery -AllowClobber

can you push maybe new version of the windows admin center that has a checkbox to add AllowClobber?
or tell me how i can remove Find-Package,Install-Package,Uninstall-Package

Thank you!

Azure Stack HCI
Azure Stack HCI
A hyperconverged infrastructure operating system delivered as an Azure service that provides security, performance, and feature updates.
269 questions
Azure Kubernetes Service (AKS)
Azure Kubernetes Service (AKS)
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
1,864 questions
0 comments No comments
{count} votes

8 answers

Sort by: Newest
  1. MattMcSpirit-MSFT 561 Reputation points
    2021-11-15T20:15:56.683+00:00

    Hi,

    Thanks for the extra information. Your hardware looks fine - more than enough to evaluate AKS-HCI on a single node.

    I'd suggest using PS 5.x for the time being.

    PowerShellGet will be important to install the other modules - on my local machine, i have versions 2.2.5 and 3.0.11 as well as the initial 1.0.0.1. I believe it needs to be 2.2.3 or newer. PowerShellGet will also be in C:\Program Files\WindowsPowerShell\Modules\PowerShellGet, if you want to check.

    Now that you have started again, at what stage are the errors happening?

    Thanks,
    Matt

    0 comments No comments

  2. keith siilats 1 Reputation point
    2021-11-13T23:14:39.353+00:00

    I think I made some progress, when I updated to vNext looks like some packages are in
    C:\Program Files (x86)\WindowsPowerShell\Modules
    the x86 is bad
    In particular PowerShellGet was there and did not get updated
    If you delete it from both places its no good, just delete the PowerShellGet folder from
    C:\Program Files (x86)\WindowsPowerShell\Modules

    0 comments No comments

  3. keith siilats 1 Reputation point
    2021-11-13T19:51:04.887+00:00

    Hi I tried to start again:
    https://learn.microsoft.com/en-us/azure-stack/aks-hci/kubernetes-walkthrough-powershell
    Windows updated the .net meanwhile
    Now I get nuget package version errors and IPAddress not found errors.

    1. Do you need to use powershell 5 or 7?
    0 comments No comments

  4. keith siilats 1 Reputation point
    2021-11-13T17:36:30.37+00:00

    Thank you very much. Its a simple Dell R630 with the latest vnext installed clean with 200GB of ram. I have F drive for the SSD raid and I made a folder clusterstorage there based on the AKS tutorial. Raid is 6 2TB SSD drives in RAID5 on the standard Dell storage controller.

    There is no domain, no workgroup.

    Command returned:
    CommandType Name Version Source


    Alias Initialize-AksHciNode 1.1.14 AksHci
    Function Add-AksHciGMSACredentialSpec 1.1.14 AksHci
    Function Add-AksHciNode 1.1.14 AksHci
    Function Disable-AksHciArcConnection 1.1.14 AksHci
    Function Disable-AksHciPreview 1.1.14 AksHci
    Function Enable-AksHciArcConnection 1.1.14 AksHci
    Function Enable-AksHciPreview 1.1.14 AksHci
    Function Get-AksHciBillingStatus 1.1.14 AksHci
    Function Get-AksHciCluster 1.1.14 AksHci
    Function Get-AksHciClusterNetwork 1.1.14 AksHci
    Function Get-AksHciClusterUpdates 1.1.14 AksHci
    Function Get-AksHciConfig 1.1.14 AksHci
    Function Get-AksHciCredential 1.1.14 AksHci
    Function Get-AksHciEventLog 1.1.14 AksHci
    Function Get-AksHciKubernetesVersion 1.1.14 AksHci
    Function Get-AksHciLogs 1.1.14 AksHci
    Function Get-AksHciNodePool 1.1.14 AksHci
    Function Get-AksHciProxySetting 1.1.14 AksHci
    Function Get-AksHciRegistration 1.1.14 AksHci
    Function Get-AksHciStorageContainer 1.1.14 AksHci
    Function Get-AksHciUpdates 1.1.14 AksHci
    Function Get-AksHciVersion 1.1.14 AksHci
    Function Get-AksHciVmSize 1.1.14 AksHci
    Function Install-AksHci 1.1.14 AksHci
    Function Install-AksHciAdAuth 1.1.14 AksHci
    Function Install-AksHciCsiNfs 1.1.14 AksHci
    Function Install-AksHciCsiSmb 1.1.14 AksHci
    Function Install-AksHciGMSAWebhook 1.1.14 AksHci
    Function Install-AksHciMonitoring 1.1.14 AksHci
    Function New-AksHciCluster 1.1.14 AksHci
    Function New-AksHciClusterNetwork 1.1.14 AksHci
    Function New-AksHciContainerRegistry 1.1.14 AksHci
    Function New-AksHciNetworkSetting 1.1.14 AksHci
    Function New-AksHciNodePool 1.1.14 AksHci
    Function New-AksHciProxySetting 1.1.14 AksHci
    Function New-AksHciStorageContainer 1.1.14 AksHci
    Function Remove-AksHciCluster 1.1.14 AksHci
    Function Remove-AksHciClusterNetwork 1.1.14 AksHci
    Function Remove-AksHciGMSACredentialSpec 1.1.14 AksHci
    Function Remove-AksHciNode 1.1.14 AksHci
    Function Remove-AksHciNodePool 1.1.14 AksHci
    Function Repair-AksHciCerts 1.1.14 AksHci
    Function Repair-AksHciClusterCerts 1.1.14 AksHci
    Function Restart-AksHci 1.1.14 AksHci
    Function Set-AksHciCluster 1.1.14 AksHci
    Function Set-AksHciConfig 1.1.14 AksHci
    Function Set-AksHciNodePool 1.1.14 AksHci
    Function Set-AksHciRegistration 1.1.14 AksHci
    Function Sync-AksHciBilling 1.1.14 AksHci
    Function Uninstall-AksHci 1.1.14 AksHci
    Function Uninstall-AksHciAdAuth 1.1.14 AksHci
    Function Uninstall-AksHciCsiNfs 1.1.14 AksHci
    Function Uninstall-AksHciCsiSmb 1.1.14 AksHci
    Function Uninstall-AksHciGMSAWebhook 1.1.14 AksHci
    Function Uninstall-AksHciMonitoring 1.1.14 AksHci
    Function Update-AksHci 1.1.14 AksHci
    Function Update-AksHciCluster 1.1.14 AksHci

    0 comments No comments

  5. MattMcSpirit-MSFT 561 Reputation points
    2021-11-10T18:12:24.147+00:00

    Thanks for this extra information.

    Please could you describe your physical Windows Server 2022 environment a little more? The reason I ask is, Windows Admin Center doesn't normally need to ask to use the -AllowClobber flag, so something else must be causing this. Putting Windows Admin Center to one side for a moment, that doesn't explain why you can't successfully deploy with PowerShell.

    • Is it domain joined or in a workgroup?
    • Your storage path above shows: **f:\clusterstorage\volume1**ImageStore\1.0.5.11028\kubeconfig-mgmt - :\ClusterStorage\Volume# is typically found when deploying Cluster Shared Volumes, as part of a Windows Server Cluster, but you stated above that your system is a single physical node - could you please clarify?
    • Could you run Import-Module AksHci and then Get-Command -Module AksHci and let us know the version that is returned? Should be 1.1.14 or newer.

    Also, in terms of Azure:

    Thanks,
    Matt

    0 comments No comments