Versions Compared

Version Old Version 3 New Version 4
Changes made by

Manjunath Ranganathaiah

Manjunath Ranganathaiah

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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


Example:

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/terminate": dial tcp 172.16.16.150:30415: connect: connection refused

 

Termination API call in flight

If the termination 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/terminate": EOF

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