| Case | Step | Event | uss1 | ||
|---|---|---|---|---|---|
| Setup | Cleanup OIRs | 1 | 🌐 |
|
🌐 |
| 2 | 🛑 |
Operational intent references can be searched for
[1]
Failed OIR search with HTTP code 401 Failed to query operational intent references: Received code 401 when attempting to find operational intents in {'volume': {'outline_polygon': {'vertices': [{'lat': 37.1853, 'lng': -80.614}, {'lat': 37.2148, 'lng': -80.614}, {'lat': 37.2148, 'lng': -80.544}, {'lat': 37.1853, 'lng': -80.544}]}, 'altitude_lower': {'value': 0.0, 'reference': |
🛑 | ||
| Cleanup | 3 | 🌐 |
|
🌐 | |
| 4 | ⚠️ |
Operational intent references can be searched for
[3]
Failed OIR search with HTTP code 401 Failed to query operational intent references: Received code 401 when attempting to find operational intents in {'volume': {'outline_polygon': {'vertices': [{'lat': 37.1853, 'lng': -80.614}, {'lat': 37.2148, 'lng': -80.614}, {'lat': 37.2148, 'lng': -80.544}, {'lat': 37.1853, 'lng': -80.544}]}, 'altitude_lower': {'value': 0.0, 'reference': |
⚠️ | ||
| 5 | 🌐 |
|
🌐 | ||
| 6 | ⚠️ |
Operational intent references can be queried by ID
[5]
OIR Get query returned code different from 200 or 404 Received code 401 when attempting to retrieve operational intent reference 00000191-e36d-40be-8d38-beca6ca30000; error message: `Invalid access token audience: dss.stage.iart.software (E:d3e6f56d-dcd0-4a10-94c0-c94bc98ffc2d)` |
⚠️ | ||
| 7 | 🌐 |
|
🌐 | ||
| 8 | ⚠️ |
Successful subscription search query
[7]
Could not query subscriptions When attempting to query subscriptions from the DSS, received 401 |
⚠️ | ||
| 9 | 🌐 |
|
🌐 | ||
| 10 | ⚠️ |
Subscription can be queried by ID
[9]
Could not query subscription 00000192-e36d-40be-8d38-beca6ca30000 When attempting to query subscription 00000192-e36d-40be-8d38-beca6ca30000 from the DSS, received 401: Invalid access token audience: dss.stage.iart.software (E:85dd58be-0910-4606-9e44-a763fd54d5b9) |
⚠️ | ||
monitoring.uss_qualifier.scenarios.scenario.ScenarioDidNotStopError at 2026-05-21T21:19:57.072077ZMessage: Scenario did not stop as expected upon failed check: 'Subscription can be queried by ID check' (Medium severity involving for participants uss1) documented at , doc: https://github.com/interuss/monitoring/blob/d1166f192120200e60d4a63515b6847f6e2311e6/monitoring/uss_qualifier/scenarios/astm/utm/dss/clean_workspace_subs_during_cleanup.md#subscription-can-be-queried-by-id-check)
Stack trace:
Traceback (most recent call last):
File "/app/monitoring/uss_qualifier/suites/suite.py", line 172, in _run_test_scenario
scenario.cleanup()
~~~~~~~~~~~~~~~~^^
File "/app/monitoring/uss_qualifier/scenarios/astm/utm/dss/oir_explicit_sub_handling.py", line 438, in cleanup
self._clean_all_subs()
~~~~~~~~~~~~~~~~~~~~^^
File "/app/monitoring/uss_qualifier/scenarios/astm/utm/dss/oir_explicit_sub_handling.py", line 422, in _clean_all_subs
test_step_fragments.cleanup_sub(self, self._dss, self._sub_id)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/monitoring/uss_qualifier/scenarios/astm/utm/dss/test_step_fragments.py", line 94, in cleanup_sub
raise ScenarioDidNotStopError(check)
monitoring.uss_qualifier.scenarios.scenario.ScenarioDidNotStopError: Scenario did not stop as expected upon failed check: 'Subscription can be queried by ID check' (Medium severity involving for participants uss1) documented at , doc: https://github.com/interuss/monitoring/blob/d1166f192120200e60d4a63515b6847f6e2311e6/monitoring/uss_qualifier/scenarios/astm/utm/dss/clean_workspace_subs_during_cleanup.md#subscription-can-be-queried-by-id-check)