Yuliia7-1 opened a new issue, #13734: URL: https://github.com/apache/cloudstack/issues/13734
### problem When a volume's disk offering is changed to another offering with the same size, CloudStack does not emit a VOLUME.RESIZE event in cloud.usage_event ### versions ACS version is 4.19.1.1 ### The steps to reproduce the bug Steps to reproduce: 1. Create Volume using Disk Offering A. 2. Resize Volume (for example, from 300 GB to 400 GB). 3. Change the disk offering from Disk Offering A to Disk Offering B (size 400 GB) without changing the volume size. Actual behaviour: CloudStack generates a `VOLUME.CHANGE.DISK.OFFERING` event in the `cloud.event` table, confirming that the operation completed successfully. However, no new `VOLUME.RESIZE` entry is created in the `cloud.usage_event` table. As a result, the usage records continue to reference the previous disk offering, and downstream billing continues to use the old offering information. Additional observations: - The volume is successfully updated to Disk Offering B. - The volume size remains unchanged. - The latest `cloud.usage_event` entry still references Disk Offering A. - Billing data derived from `cloud.usage_event` therefore continues to report the previous offering. ### What to do about it? Expected behaviour: A usage event should be generated (or the existing usage information updated) so that the billing system reflects the new disk offering, even though the volume size has not changed. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
