[CLOUDSTACK-10259] Missing float part of secondary storage data when calculating secondary storage usage in listAccounts

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 4.12
• Security Level: Public (Anyone can view this level - this is the default.)
• Assignee: Rafael Weingärtner
• Reporter: Rafael Weingärtner
• Created: 30/Jan/18 21:50
• Updated: 09/May/18 10:00
• Resolved: 01/Mar/18 16:35

Description

There is a non-floating points division that is missing the floating part of the secondary storage usage. This will affect methods that use the following SET method org.apache.cloudstack.api.response.AccountResponse.setSecondaryStorageLimit(String).

It affects the listAccounts API method, making it differ from the updateResource count method, which is presented in bytes.

Issue Links

• links to: GitHub Pull Request #2439