PowerStore REST API bug in 3.2+ on GET file_system?

Hey all,

NetApp guy here. We have a mutual customer where when trying to discover a few Dell/EMC PowerStore 3.2.1.0 firmware arrays, we are seeing this REST API call:

/api/rest/file_system?offset=0&limit=2000&select=access_policy%2Caccess_policy_l10n%2Caccess_type%2Caccess_type_l10n%2Ccreation_timestamp%2Ccreator_type%2Ccreator_type_l10n%2Cdefault_hard_limit%2Cdefault_soft_limit%2Cdescription%2Cexpiration_timestamp%2Cfile_tree_quotas%2Cfile_user_quotas%2Cfilesystem_type%2Cfilesystem_type_l10n%2Cfolder_rename_policy%2Cfolder_rename_policy_l10n%2Cgrace_period%2Cid%2Cis_async_MTime_enabled%2Cis_modified%2Cis_quota_enabled%2Cis_smb_no_notify_enabled%2Cis_smb_notify_on_access_enabled%2Cis_smb_notify_on_write_enabled%2Cis_smb_op_locks_enabled%2Cis_smb_sync_writes_enabled%2Clast_refresh_timestamp%2Clast_writable_timestamp%2Clocking_policy%2Clocking_policy_l10n%2Cname%2Cnas_server%28id%2Cname%2Ccurrent_node_id%29%2Cnas_server_id%2Cnfs_exports%2Cparent_id%2Cprotection_policy%2Cprotection_policy_id%2Csize_total%2Csize_used%2Csmb_notify_on_change_dir_depth%2Csmb_shares 

Return:

....

"size_total":null,

"size_used":null,

....

We believe this is only occurring when these file systems are some type of disaster recovery / replication *destination* - when this occurs, we see this happening for all of the file_systems belonging to a given nas_server.

Is this expected behavior for these 2 attributes' values to be null in this configuration? If this is a bug, is there a firmware release where it is fixed?

Thanks,

Matt