Azure-docs: Is it "InProgress" or "In Progress" for "status" field

Created on 19 Sep 2019  Â·  9Comments  Â·  Source: MicrosoftDocs/azure-docs

As per documentation it shall be "InProgress" (no space), yet actual data for event spells as "In Progress". In addition it was "In progress" for quite sometime now untill recently.
Error when you try to create alert with space is belo

      "message": "{\r\n  \"Code\": \"ConditionValueInvalid\",\r\n  \"Message\": \"Invalid value In Progress for condition status\"\r\n}"
    }

Actual event is below

    },
    "resourceId": "/subscriptions/<>/resourceGroups/USEASTPROD/providers/Microsoft.Compute/virtualMachines/AUEGLBLVTRNDP01",
    "status": {
        "value": "In Progress",
        "localizedValue": "In Progress"
    },
    "subStatus": {
        "value": "",
        "localizedValue": ""
    },
    "submissionTimestamp": "2019-09-19T09:40:05.2811188Z",
    "subscriptionId": "<>",
    "properties": {
        "title": "We're sorry, your virtual machine isn't available because an unexpected failure on the host server",
        "details": null,
        "currentHealthStatus": "Unavailable",
        "previousHealthStatus": "Unknown",
        "type": "Downtime",
        "cause": "PlatformInitiated"
    },
    "relatedEvents": []

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Pri2 cxp product-bug service-healtsvc triaged

All 9 comments

@artisticcheese good catch. I too am able to repro the above.
@stephbaron can you confirm this is a recent change? is it possible to change the actual event output to match the recent change?

Checking...

@stephbaron - any update on this pls?

We think we've identified the issue and will be preparing a fix. The proper value is "In Progress". I do not have a firm ETA at this point, but it should be near term.

Thanks @stephbaron. would appreciate if you can post an update on here once the fix is released.
@artisticcheese
We will now close this issue. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.

This fix has been deployed to production, I'll get the documentation updated as well.

OMG, guys you are incredible. You fix one thing and break another. Now resourceType is misspelled
"equals": "Microsoft.Compute/virtualMachines"
Actual event is below

    "resourceType": {
        "value": "MICROSOFT.COMPUTE/VIRTUALMACHINES",
        "localizedValue": "MICROSOFT.COMPUTE/VIRTUALMACHINES"
    },

Can you elaborate what you mean by resourceType is misspelled?

Documentation specifies that resourceType for Virtual Machine shall be Microsoft.Compute/virtualMachines while actual event have it spelled with all capital letters like below

"resourceType": {
        "value": "MICROSOFT.COMPUTE/VIRTUALMACHINES",
        "localizedValue": "MICROSOFT.COMPUTE/VIRTUALMACHINES"
    },
Was this page helpful?
0 / 5 - 0 ratings