rhtyd commented on pull request #5017: URL: https://github.com/apache/cloudstack/pull/5017#issuecomment-847824952
@olivierlemasle can the acceptable solution be as simple as leave it as is because backups are first class citizen? As per your bug report, at least 1 backup is created/exists for the VM so ideally the usage records should continue to be created until that VM's backup is removed by the user explicitly. However, if even after removing the backups if it does create usage records then it's a real bug. (didn't check just speculating here) The only edge case is when VM is expunged with no backups but possible a backup external job such as for Veeam, in which case the solution can be simply to check and unassign the backup offering for the VM which has no backups (i.e. delete the Veeam job external which won't actually work anyway as the VM which was assigned to it does not exist anymore in Vmware). What do you think @Pearl1594 @olivierlemasle ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
