Loading...

XML

Word

Printable

Type: Story
Resolution: Done
Priority: Normal
Fix Version/s: 2024-09-04 - API
Affects Version/s: None
Component/s: None
Labels:
- QE

Story Points:
5
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
True
Epic Link:
billable-usage-retries-status
Intelligence Requested:
Market:

Original story points:
5

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

Swatch-producer-azure should update the BillableUsageAggregate being processed with `status`, `error_code` and `billed_on`, and then emit it back to the platform.rhsm-subscriptions.billable-usage.status topic

Done:

`GET /internal/remittance/accountRemittances` should reflect the actual status of a given billable usage remittance record
QE should verify the fields for positive and negative test cases. (Specifically testing an inactive sub for the negative case).
Dev to write a happy path IQE test. Can also extend https://gitlab.cee.redhat.com/insights-qe/iqe-rhsm-subscriptions-plugin/-/blob/master/iqe_rhsm_subscriptions/tests/tally/test_remitance.py?ref_type=heads#L29

blocks

SWATCH-2611 Update existing billable_usage_remittances status to unknown

Closed

depends on

SWATCH-2288 Capture billable usage uuids in billable usage hourly aggregates

Closed

is blocked by

SWATCH-2503 Adjust GetTotalRemitted calculation to exclude fatal remittance failures

Closed

SWATCH-2290 Have swatch-producer-aws emit status

Closed

is depended on by

SWATCH-2803 Directly handle usages to be retried in the status consumer

Closed

Assignee:: Alex Wood

Reporter:: Kevin Howell

QA Contact:: Aurobinda Nayak

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2024/03/11 3:29 PM

Updated:: 2024/09/12 9:28 AM

Resolved:: 2024/08/28 5:56 PM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates