Test runner failing at S47E55 for 'che_uspace_flightauth' with "ValueError: At state: 'Flying' is not a valid OperationalIntentState"

[srikarBudda]

Observed behavior
We are executing this scenario S47: Data Validation of GET operational intents by USS, in which at Event 55(uss1) the test runner is failing with: ValueError: At state: 'Flying' is not a valid OperationalIntentState
This is causing the test to stop executing further but we don't see any failed test indicators in the report. We have set the stop_fast flag to false, that didnt help continue to test either.

• A zip file of a sequence view artifact
• A zip file of report.json

Other acceptable means might include:

• Codebase version: ((interuss/monitoring/v0.20.0))

Test check
Scenario 47 - Event 55
Data Validation of GET operational intents by USS

Difference from expected behavior
The test report has that test as passed but the test runner itself is failing with the above mentioned error which is blocking the test execution. We think the test runner is not handling this exception properly.

[BenjaminPelletier]

This was fixed by #1238 and can be resolved by using monitoring v0.23.0 or later.

[srikarBudda]

A couple of weeks ago, we had executed our test runs using a later monitoring image version. However, based on the instructions in here, FOCA had requested that we alight to version v.0.20.0 for these runs.

Given that the recent fix (1238) mentions compatibility starting from v.0.23.0, we wanted to double-check whether we should continue using v0.20.0 as per FOCA's guidance, or move to the newer version to pick up the fix.

@barroco, could you please confirm what's preferred in this case so we can proceed accordingly?