Once the rate calculation for EBS changes were merged in IQE, I added 3 EBS disks uncorrelated to OCP, nor using resource matching neither using csi_volume_handle report attribute

https://gitlab.cee.redhat.com/insights-qe/iqe-cost-management-plugin/-/blob/master/iqe_cost_management/data/aws/aws_static_report_basic_template.yml#L596

Still, the costs of such disk is being added to the ocp on aws storage path

To reproduce, pull latest iqe and run    

test_api_ocp_on_aws_source_raw_calc

Not sure atm if this was introduced when modifying the OCP on AWS resource matching SQL