-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Minor
-
Component/s: _unsorted
See the attached screenshot. I'm not sure how I ended up getting into this state.
Here's what I do know:
- There are not 16 VMs provisioned in this environment despite the System Log claiming there are.
- There have been recent ARM deployment errors for one of my VM templates:
{
"status": "Failed",
"error": {
"code": "ResourceDeploymentFailure",
"message": "The resource operation completed with terminal provisioning state 'Failed'.",
"details": [
{
"code": "VMExtensionProvisioningTimeout",
"message": "Provisioning of VM extension 'customScriptwin2012-110340' has timed out. Extension installation may be taking too long, or extension status could not be obtained."
}
]
}
}
{
"error": {
"code": "ResourceNotFound",
"message": "The Resource 'Microsoft.Compute/virtualMachines/win2012-a13100/extensions/customScriptwin2012-a13100' under resource group 'jenkinsinfra-vmagents' was not found."
}
}
{
"error": {
"code": "NotFound",
"target": "vmName",
"message": "The entity was not found."
}
}
My theory is that the template failed to fully initialize, but was counted as a provisioned VM within the plugin's tracking of these things.
