Skip to end of banner
Go to start of banner

Resilience testing with GMS application

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 2 Next »

Instantiation API call in flight

If the instantiation API call is in flight and the orchestrator goes down, the API call will get the following error:


Post "http://172.16.16.150:30415/v2/projects/gmsproj1/composite-apps/gms-collection-composite-app/v1/deployment-intent-groups/gms-collection-deployment-intent-group/instantiate": EOF

 

API call can be reissued once the service comes backup and application instantiation should complete


Instantiation API call completes but status API fails

In this case the orchestrator went down after the API call succeeded, but before the status was updated, status API will return error, but the instantiation will succeed after the orchestrator comes back up

POST  --> URL: http://172.16.16.150:30415/v2/projects/gmsproj1/composite-apps/gms-collection-composite-app/v1/deployment-intent-groups/gms-collection-deployment-intent-group/instantiate

Response Code: 202

API Response code 202. Waiting...

Deployment in progress... Please Wait

parse error: Invalid numeric literal at line 1, column 6

Invalid apply status State.


Connection refused message

 

If the API call is made after the emco microservice goes down, API call fails with connection refused message. API call needs to be reissued after the microservice comes backup

 

  • No labels