search

Azure / aksArc

# Welcome to the Azure Kubernetes Service enabled by Azure Arc (AKS Arc) repo This is where the AKS Arc team will track features and issues with AKS Arc. We will monitor this repo in order to engage with our community and discuss questions, customer scenarios, or feature requests. Checkout our projects tab to see the roadmap for AKS Arc!
MIT License
111 stars 45 forks source link

Install-MOC - GetRelease error returned by API call - Received unexpected response code: 404 #276

Closed mahoncj closed 1 year ago

mahoncj commented 1 year ago

Reference issue: #194 and #202

Module: AksHCI Version: 1.1.49

Attempting to perform an AKS deployment on Azure Stack HCI and receiving the following error:

Install-Moc failed. Exception [GetRelease error returned by API call: Post "https://msk8s.api.cdp.microsoft.com/api/v1.1/contents/default/namespaces/default/names/mocstack-stable/versions/1.0.15.11104/files?action=generateDownloadInfo&ForegroundPriority=True": POST https://msk8s.api.cdp.microsoft.com/api/v1.1/contents/default/namespaces/default/names/mocstack-stable/versions/1.0.15.11104/files?action=generateDownloadInfo&ForegroundPriority=True giving up after 6 attempt(s): Received unexpected response code: 404]

MOC validation was successful via the Set-AksHciConfig cmdlet.

image

To Reproduce Steps to reproduce the behavior:

  1. Run Install-Akshci
  2. See error

Expected behavior

Environment: OS: Azure Stack HCI (22H2) GA Release

HassanAlmanasrah commented 1 year ago

got the same issue for the URL , and tested two different versions for AKS.

strickos9 commented 1 year ago

Getting the same error on different hosts, was working fine yesterday

Elektronenvolt commented 1 year ago

I've seen 404 responses as well at a cluster update in the last 36 to 48 hours. I've asked @baziwane about it Wednesday and he confirmed an outage on some files. I've started the update again a few hours ago, it works now - try again, looks like it's fixed.

mahoncj commented 1 year ago

I've seen 404 responses as well at a cluster update in the last 36 to 48 hours. I've asked @baziwane about it Wednesday and he confirmed an outage on some files. I've started the update again a few hours ago, it works now - try again, looks like it's fixed.

Thanks! Confirmed it is now working for me as well.