4 Replies Latest reply on Mar 9, 2020 4:11 AM by ZeevEisenbergCHS

    Discrepancy in vRA Reservation Storage Details between GUI and API

    jmedd Enthusiast
    vExpert

      vRA 7.3

       

      I'm seeing a discrepancy in vRA Reservation Storage details between what is reported in the GUI and what is returned via the API. Here's an example.

       

      These are the storage figures in the GUI for my reservation:

       

      StorageReservation.png

       

      and the data returned by the API:

      key                                  value

      ---                                  -----

      storageReservedSizeGB                @{type=integer; value=20}

      storageReservationPriority           @{type=integer; value=0}

      permissible_value_selected           @{type=boolean; value=True}

      storageAllocatedSizeGB               @{type=integer; value=0}

      computeResourceStorageTotalSizeGB    @{type=integer; value=48}

      isStorageCluster                     @{type=boolean; value=False}

      storagePath                          @{type=entityRef; classId=Storage; id=44d5a6b3-f899-4900-8a0e-15017e4e2630; componentId=; label=NFS01}

      storageEnabled                       @{type=boolean; value=True}

      computeResourceStorageReservedSizeGB @{type=integer; value=10}

      isSDRSEnabled                        @{type=boolean; value=False}

      computeResourceStorageFreeSizeGB     @{type=integer; value=33}

      diskCost                             @{type=integer; value=0}

       

      In easier to read form:

      1) Total Computer Resource Storage space is: 48 
      2) Free Computer Resource Storage space is: 33
      3) Computer Resource Storage Reserved space is: 10
      4) StorageReservedSize is: 20
      5) storageAllocatedSize is: 0

      So there definitely seems to be an issue with 2, 3 and 5.

      The API call was made to /reservation-service/api/reservations/$($ReservationId)

       

      and the storage figures returned via the ExtensionData property of the result.

       

      There are more details with another example over in an issue on our PowervRA repo: Not fetching correct data from VRA · Issue #172 · jakkulabs/PowervRA · GitHub

       

      Anyone else having the same problem?