-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Helm Test Intermittent failure with 'Generic ID not found' #2925
Comments
Hey team! Please add your planning poker estimate with Zenhub @mdebarros @sri-miriyala @vijayg10 @kleyow |
After running the tests for multiple hours I have not observed the specific error labeled in this story. I've added failed reports that stem mostly from 5xx errors. mojaloop/testing-toolkit-test-cases#91 may have resolved this issue. Moving to blocked. |
WIl re-open this if there's a repro, but closed for now as it is not reproducible |
Issue seems to present as "Id not found" and not "Generic ID not found". |
PartyId that is missing from the testfsp4's backend (i.e. mojaloop/mojaloop-simulator:v13.0.1):
Log from
Request to backend to list all parties
Response with missing
Log from moja4-sim-testfsp4-backend-9db946c89-49v5h:
|
Re-running the API operation to create the Party on the Mojaloop-Simulator after a restart:
|
Unable to determine the cause of the missing participant, except that it is seems to be occuring during the onboarding setup... The provisioning script hub/provisioning/CGS_Specific/add-users-to-new-sims-and-als-registration.json still shows the operation as being successful:
Will need to re-look at this once mojaloop-simulator/releases/tag/v13.1.0 or later is packaged in a release. This version will also include audits for incoming repository requests which will help identify the cause of the issue. |
Summary:
Helm Test Intermittent failure with 'Generic ID not found' when executing transfers via the Mojaloop-Simulator's API for
POST /scenarios
requests related tests, failing with below error; possibly indicating an issue with lookup (either a provisioning issue or bug - after some investigation the source of the issue seems to occur at the Mojaloop-Simulator){ errorCode: '3200', errorDescription: 'Generic ID not found' }
Example reports:
Work-around:
Re-run the
helm test
, specifically re-run the following Test Collections:$DEPLOYMENT_NAME-ml-ttk-test-setup
<-- Re-provisioning script to re-create MISSING Party data on Mojaloop-Simulators$DEPLOYMENT_NAME-ml-ttk-test-val-gp
<-- Golden Path Test CollectionSeverity:
Low
Priority:
Low
Expected Behavior
helm tests
should consistently pass without theID not found
with the Parties being correctly provisioned on the Mojaloop Simulators.Steps to Reproduce
watch -n 300 helm test moja2 --filter "name=moja2-ml-ttk-test-setup,name=moja2-ml-ttk-test-val-gp"
watch
command to stop running further testsSpecifications
Dependency:
Tasks for fix:
Note: If issue not found move to closed or blocked until issue re-occurs and then revive the story
Notes:
The text was updated successfully, but these errors were encountered: