-
Sub-task
-
Resolution: Done
-
Blocker
-
None
-
None
-
None
-
False
-
-
False
-
subs-swatch-thunder
-
-
-
Swatch Thunder Sprint 2
AssertionError: Recorded tally: 184 does not match expected tally: 192
self = <iqe_rhsm_subscriptions.tests.longrun.test_verify_rosa.TestRosaLongrun object at 0x7ff22b20ef90> application = <iqe.base.application.Application object at 0x7ff22b2ada30> longrun_rosa_cluster_setup = {'billing_provider': 'aws', 'display_name': 'automation', 'instance_id': 'fake_cluster', 'metric_data': {'cores': 2976, 'instance-hours': 744}, ...} def test_rosa_get_account_and_product_tally_report( self, application, longrun_rosa_cluster_setup ): """Verify the tally report for the ROSA Longrun cluster. metadata: assignee: tmcknigh negative: false importance: critical level: system requirements: longrun test_steps: 1. Call Tally Report /v1/tally/products/{product_id}/{metric_id} endpoint 2. For each metric, evaluate data matches the expected value. expected_results: 1. Tally data[0] (yesterday's usage) should match the expected value """ for metric, expected_value in self.expected_metrics_daily.items(): tally = application.rhsm_subscriptions.get_tally_report( product_id=longrun_rosa_cluster_setup["product_id"], metric_id=metric, beginning=self.beginning_of_day, ending=self.end_of_day, granularity="Daily", ) logging.info(f"{metric} Tally Report:\n{tally}") > assert tally.data[0].value == expected_value, ( f"Recorded tally: {tally.data[0].value} does not" f" match expected tally: {expected_value}" ) E AssertionError: Recorded tally: 184 does not match expected tally: 192 E assert 184 == 192 E + where 184 = {'date': datetime.datetime(2025, 10, 5, 0, 0, tzinfo=tzlocal()),\n 'has_data': True,\n 'value': 184}.value /iqe_venv/lib/python3.12/site-packages/iqe_rhsm_subscriptions/tests/longrun/test_verify_rosa.py:201: AssertionError
We think this is related to a missing Event record (see https://redhat-internal.slack.com/archives/C09BCH0GRT7/p1760098787929349?thread_ts=1760049585.701799&cid=C09BCH0GRT7) for the 2025-10-05T20:00:00Z timestamp.
There is NOT a missing datapoint in Prometheus.
There's evidence in Splunk that swatch-tally did receive a message for that timestamp/instance.
- relates to
-
SWATCH-3836 Long run test get wrong remittance report at the start of the month
-
- Release Pending
-