Azure-rest-api-specs: Recovery Service missed value in response of list method

[00Kai0]

I got a different response from swagger in Recovery Services:
my response:

- request:
    body: null
    headers:
      Accept:
      - application/json
      Accept-Encoding:
      - gzip, deflate
      Connection:
      - keep-alive
      User-Agent:
      - azsdk-python-mgmt-recoveryservices/1.0.0b1 Python/3.6.9 (Linux-4.9.184-linuxkit-x86_64-with-Ubuntu-18.04-bionic)
    method: GET
    uri: https://management.azure.com/Subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/test_mgmt_recoveryservices_test_retrieve_vault_usages5812162c/providers/Microsoft.RecoveryServices/vaults/PythonSDKTestResource/replicationUsages?api-version=2016-06-01
  response:
    body:
      string: '{"monitoringSummary":{"unHealthyVmCount":0,"unHealthyProviderCount":0,"eventsCount":0,"deprecatedProviderCount":0,"supportedProviderCount":0,"unsupportedProviderCount":0},"jobsSummary":{"failedJobs":0,"suspendedJobs":0,"inProgressJobs":0},"protectedItemsSummary":{"irInProgressProtectedItemsCount":0,"testFailoverInProgressProtectedItemsCount":0,"testFailoverWaitingProtectedItemsCount":0,"failoverInProgressProtectedItemsCount":0,"failedOverProtectedItemsCount":0,"changePitInProgressProtectedItemsCount":0,"failoverCommitInProgressProtectedItemsCount":0,"failoverCommittedProtectedItemsCount":0,"testFailoverApplicableProtectedItemsCount":0,"replicatingProtectedItemsCount":0,"hyperVToAzureProtectedItemsCount":0,"vmmToAzureProtectedItemsCount":0,"vmwareToAzureProtectedItemsCount":0,"azureToAzureProtectedItemsCount":0},"storageAccountsCountSummary":{"hyperVToAzureTotalStorageAccountsCount":0,"hyperVToAzureLogStorageAccountsCount":0,"hyperVToAzureRecoveryStorageAccountsCount":0,"vmwareToAzureStorageAccountsCount":0,"vmwareToAzureLogStorageAccountsCount":0,"vmwareToAzureRecoveryStorageAccountsCount":0,"azureToAzureRecoveryStorageAccountsCount":0,"azureToAzureStagingStorageAccountsCount":0},"protectedItemCount":0,"registeredServersCount":0,"recoveryPlanCount":0}'
    headers:
      cache-control:
      - no-cache
      content-length:
      - '1271'
      content-type:
      - application/json
      date:
      - Tue, 10 Nov 2020 06:01:34 GMT
      expires:
      - '-1'
      pragma:
      - no-cache
      server:
      - Microsoft-IIS/10.0
      - Kestrel
      strict-transport-security:
      - max-age=31536000; includeSubDomains
      transfer-encoding:
      - chunked
      vary:
      - Accept-Encoding
      x-content-type-options:
      - nosniff
    status:
      code: 200
      message: OK

in swagger:

{
  "value": [
    {
      "monitoringSummary": {
        "unHealthyVmCount": 0,
        "unHealthyProviderCount": 0,
        "eventsCount": 0,
        "deprecatedProviderCount": 0,
        "supportedProviderCount": 0,
        "unsupportedProviderCount": 0
      },
      "jobsSummary": {
        "failedJobs": 0,
        "suspendedJobs": 0,
        "inProgressJobs": 0
      },
      "protectedItemCount": 2,
      "registeredServersCount": 2,
      "recoveryPlanCount": 1
    }
  ]
}

[msftbot[bot]]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @pvrk.

Issue Details

Description:	I got a different response from swagger in Recovery Services: my response: - request: body: null headers: Accept: - application/json Accept-Encoding: - gzip, deflate Connection: - keep-alive User-Agent: - azsdk-python-mgmt-recoveryservices/1.0.0b1 Python/3.6.9 (Linux-4.9.184-linuxkit-x86_64-with-Ubuntu-18.04-bionic) method: GET uri: https://management.azure.com/Subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/test_mgmt_recoveryservices_test_retrieve_vault_usages5812162c/providers/Microsoft.RecoveryServices/vaults/PythonSDKTestResource/replicationUsages?api-version=2016-06-01 response: body: string: '{"monitoringSummary":{"unHealthyVmCount":0,"unHealthyProviderCount":0,"eventsCount":0,"deprecatedProviderCount":0,"supportedProviderCount":0,"unsupportedProviderCount":0},"jobsSummary":{"failedJobs":0,"suspendedJobs":0,"inProgressJobs":0},"protectedItemsSummary":{"irInProgressProtectedItemsCount":0,"testFailoverInProgressProtectedItemsCount":0,"testFailoverWaitingProtectedItemsCount":0,"failoverInProgressProtectedItemsCount":0,"failedOverProtectedItemsCount":0,"changePitInProgressProtectedItemsCount":0,"failoverCommitInProgressProtectedItemsCount":0,"failoverCommittedProtectedItemsCount":0,"testFailoverApplicableProtectedItemsCount":0,"replicatingProtectedItemsCount":0,"hyperVToAzureProtectedItemsCount":0,"vmmToAzureProtectedItemsCount":0,"vmwareToAzureProtectedItemsCount":0,"azureToAzureProtectedItemsCount":0},"storageAccountsCountSummary":{"hyperVToAzureTotalStorageAccountsCount":0,"hyperVToAzureLogStorageAccountsCount":0,"hyperVToAzureRecoveryStorageAccountsCount":0,"vmwareToAzureStorageAccountsCount":0,"vmwareToAzureLogStorageAccountsCount":0,"vmwareToAzureRecoveryStorageAccountsCount":0,"azureToAzureRecoveryStorageAccountsCount":0,"azureToAzureStagingStorageAccountsCount":0},"protectedItemCount":0,"registeredServersCount":0,"recoveryPlanCount":0}' headers: cache-control: - no-cache content-length: - '1271' content-type: - application/json date: - Tue, 10 Nov 2020 06:01:34 GMT expires: - '-1' pragma: - no-cache server: - Microsoft-IIS/10.0 - Kestrel strict-transport-security: - max-age=31536000; includeSubDomains transfer-encoding: - chunked vary: - Accept-Encoding x-content-type-options: - nosniff status: code: 200 message: OK in swagger: { "value": [ { "monitoringSummary": { "unHealthyVmCount": 0, "unHealthyProviderCount": 0, "eventsCount": 0, "deprecatedProviderCount": 0, "supportedProviderCount": 0, "unsupportedProviderCount": 0 }, "jobsSummary": { "failedJobs": 0, "suspendedJobs": 0, "inProgressJobs": 0 }, "protectedItemCount": 2, "registeredServersCount": 2, "recoveryPlanCount": 1 } ] }
Author:	00Kai0
Assignees:	pvrk, srinathvasireddy
Labels:	Recovery Services Backup, Service Attention
Milestone:	-

[jsntcy]

@pvrk, @srinathvasireddy, could you please help take a look this service issue?

[pvrk]

This seems to be replicationUsage. @sideeksh : Can you please take a look and assign accordingly?

[msftbot[bot]]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Sharmistha-Rai.

Issue Details

---

I got a different response from swagger in Recovery Services:
my response:

- request:
    body: null
    headers:
      Accept:
      - application/json
      Accept-Encoding:
      - gzip, deflate
      Connection:
      - keep-alive
      User-Agent:
      - azsdk-python-mgmt-recoveryservices/1.0.0b1 Python/3.6.9 (Linux-4.9.184-linuxkit-x86_64-with-Ubuntu-18.04-bionic)
    method: GET
    uri: https://management.azure.com/Subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/test_mgmt_recoveryservices_test_retrieve_vault_usages5812162c/providers/Microsoft.RecoveryServices/vaults/PythonSDKTestResource/replicationUsages?api-version=2016-06-01
  response:
    body:
      string: '{"monitoringSummary":{"unHealthyVmCount":0,"unHealthyProviderCount":0,"eventsCount":0,"deprecatedProviderCount":0,"supportedProviderCount":0,"unsupportedProviderCount":0},"jobsSummary":{"failedJobs":0,"suspendedJobs":0,"inProgressJobs":0},"protectedItemsSummary":{"irInProgressProtectedItemsCount":0,"testFailoverInProgressProtectedItemsCount":0,"testFailoverWaitingProtectedItemsCount":0,"failoverInProgressProtectedItemsCount":0,"failedOverProtectedItemsCount":0,"changePitInProgressProtectedItemsCount":0,"failoverCommitInProgressProtectedItemsCount":0,"failoverCommittedProtectedItemsCount":0,"testFailoverApplicableProtectedItemsCount":0,"replicatingProtectedItemsCount":0,"hyperVToAzureProtectedItemsCount":0,"vmmToAzureProtectedItemsCount":0,"vmwareToAzureProtectedItemsCount":0,"azureToAzureProtectedItemsCount":0},"storageAccountsCountSummary":{"hyperVToAzureTotalStorageAccountsCount":0,"hyperVToAzureLogStorageAccountsCount":0,"hyperVToAzureRecoveryStorageAccountsCount":0,"vmwareToAzureStorageAccountsCount":0,"vmwareToAzureLogStorageAccountsCount":0,"vmwareToAzureRecoveryStorageAccountsCount":0,"azureToAzureRecoveryStorageAccountsCount":0,"azureToAzureStagingStorageAccountsCount":0},"protectedItemCount":0,"registeredServersCount":0,"recoveryPlanCount":0}'
    headers:
      cache-control:
      - no-cache
      content-length:
      - '1271'
      content-type:
      - application/json
      date:
      - Tue, 10 Nov 2020 06:01:34 GMT
      expires:
      - '-1'
      pragma:
      - no-cache
      server:
      - Microsoft-IIS/10.0
      - Kestrel
      strict-transport-security:
      - max-age=31536000; includeSubDomains
      transfer-encoding:
      - chunked
      vary:
      - Accept-Encoding
      x-content-type-options:
      - nosniff
    status:
      code: 200
      message: OK

in swagger:

{
  "value": [
    {
      "monitoringSummary": {
        "unHealthyVmCount": 0,
        "unHealthyProviderCount": 0,
        "eventsCount": 0,
        "deprecatedProviderCount": 0,
        "supportedProviderCount": 0,
        "unsupportedProviderCount": 0
      },
      "jobsSummary": {
        "failedJobs": 0,
        "suspendedJobs": 0,
        "inProgressJobs": 0
      },
      "protectedItemCount": 2,
      "registeredServersCount": 2,
      "recoveryPlanCount": 1
    }
  ]
}

Author:	00Kai0
Assignees:	sideeksh
Labels:	`Recovery Services Site-Recovery`, `Service Attention`
Milestone:	-

[Sharmistha-Rai]

Hi @00Kai0 - thanks for bringing this up.
I tried out the request but I'm getting the same response with both browser and Swagger. Could you please check again? Meanwhile, I'll confirm if this is not an intermittent issue.

[Sharmistha-Rai]

@00Kai0 - we checked this internally and it's actually a bug. We will be tracking it as a fix for our future releases. For now, please avoid testing the requests using Swagger.

[Sharmistha-Rai]

Please feel free to reopen this query for any further questions.

[Sharmistha-Rai]

please-close

[pvrk]

@Sharmistha-Rai : Please close tag will only work for doc based bugs. You have to close the issue yourself by clicking the "close" button or "close with comment" button. Just FYI.

[00Kai0]

Thanks for your feedback, I will close it :)