ArtifactVersionNotFound – No version found in the artifact repository – Microsoft.WindowsAzure.GuestAgent – CRPProd

QuestionsCategory: QuestionsArtifactVersionNotFound – No version found in the artifact repository – Microsoft.WindowsAzure.GuestAgent – CRPProd
vtcode1 Staff asked 2 weeks ago

Facing this issue for the past 3 hours for Windows 10 Pro Azure VM. Any updates?

No version found in the artifact repository that satisfies the requested version ” for VM extension with publisher ‘Microsoft.WindowsAzure.GuestAgent’ and type ‘CRPProd’.

jd Staff replied 2 weeks ago

Impact Statement from Microsoft Azure: Starting as early as 05:12 UTC on 13 Oct 2021, a subset of customers using Windows Virtual Machines may experience failure notifications when performing service management operations – such as start, create, update, delete. Deployments of new VMs and any updates to extensions may fail. Non-Windows Virtual Machines, and existing running Windows Virtual Machines should not be impacted by this issue. Services with dependencies on Windows VMs may also experience similar failures when creating resources.

2 Answers
jd Staff answered 2 weeks ago

Current Status from Microsoft Azure: We have identified that calls made during service management operations are failing due to a required artifact version not returning as expected during query. The failure shows that that a required extension cannot be located. We are currently implementing a mitigation option to force a refresh of the extension and are seeing signs of recovery where mitigation has been deployed. We expect recovery to be observed as the mitigation progresses across regions. The next update will be provided within 60 minutes, or as events warrant.

This message was last updated at 11:03 UTC on 13 October 2021

Current Status from Microsoft Azure: We have identified that calls made during service management operations are failing due to a required artifact version not returning as expected during query. The failure shows that that a required extension cannot be located. We are currently implementing a mitigation option to force a refresh of the extension. The next update will be provided within 60 minutes, or as events warrant.

This message was last updated at 10:28 UTC on 13 October 2021

Current Status from Microsoft Azure: We have identified that calls made during service management operations are failing as required artifact version data cannot be queried. We are currently focusing our investigation on the backend compute resource provider to determine why the calls are failing. The next update will be provided within 60 minutes, or as events warrant
This message was last updated at 09:45 UTC on 13 October 2021

jd Staff answered 2 weeks ago

Virtual Machines – Mitigated (Tracking ID 0NC_-L9G)
Summary of impact: Between 05:12 UTC and 11:45 UTC on 13 Oct 2021, a subset of customers using Windows Virtual Machines may have received failure notifications when performing service management operations – such as start, create, update, delete. Deployments of new VMs and any updates to extensions may have failed. Non-Windows Virtual Machines, and existing running Windows Virtual Machines should not have been impacted by this issue. Additionally, services with dependencies on Windows VMs may have also experienced similar failures when creating resources.
Preliminary root cause: We identified that calls made during service management operations were failing as a required artifact version data could not be queried. Our investigation focused on the backend compute resource provider (CRP) to determine why the calls were failing, and identified that a required VMGuestAgent could not be queried from the repository. The VM Guest Agent Extension publishing architecture was being migrated (as part of a migration of legacy service management backend systems) to a new platform which leverages the latest Azure Resource Manager (ARM) capabilities.
Mitigation: We mitigated impact by marking the appropriate extensions to the correct expected level (in this case, public). Engineers proactively verified the return to full success rate for operations after the updates were completed.
Next Steps: We will continue to investigate to establish the full root cause and prevent future occurrences. A full Root Cause Analysis (RCA) will be published within 72 hours.

Up ↑

%d bloggers like this: