-
Bug
-
Resolution: Done
-
Critical
-
None
-
None
Checking the remittances that are stuck at pending from '2024-09-04':
| Product | Metric | Count |
|---|---|---|
| rhacs | Cores | 17 |
| rhel-for-x86-els-payg | Cores | 16 |
| rhel-for-x86-els-payg | Instance-hours | 40 |
| rhel-for-x86-els-payg | Sockets | 16 |
| rhel-for-x86-els-payg | vCPUs | 245 |
| rhel-for-x86-els-payg-addon | Cores | 468 |
| rhel-for-x86-els-payg-addon | Instance-hours | 934 |
| rhel-for-x86-els-payg-addon | Sockets | 468 |
| rhel-for-x86-els-payg-addon | vCPUs | 6303 |
| rosa | Cores | 3829 |
| rosa | Instance-hours | 3809 |
Where some metrics are correct (for ex: the product "rhel-for-x86-els-payg-addon" supports the metric "vCPUs"), others not like the product "rhel-for-x86-els-payg-addon" and metrics "Sockets" or "Cores".
The consequences of this issue are that the billable usage remittance kept indefinetely on pending state.
Acceptance Criteria
- Investigate and fix why the billable usage remittance are being created with a wrong metric
- Update the aws/azure consumers to send a message to the status topic with the error "unsupported metric"
- mentioned on
