Versions Compared

Version Old Version 9 New Version Current
Changes made by

Manjunath Ranganathaiah (Deactivated)

Manjunath Ranganathaiah (Deactivated)

Saved on

Key

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

...

API Response code 202. Waiting...

Deployment in progress... Please Wait

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


Invalid apply status State.Since the orchestrator  went down, status GET call fails with connection refused message:

Get "http://172.16.16.150:30415/v2/projects/gmsproj1/composite-apps/gms-collection-composite-app/v1/deployment-intent-groups/gms-collection-deployment-intent-group/status?status=deployed": dial tcp 172.16.16.150:30415: connect: connection refused


Connection refused message  

...

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/terminate
Response Code: 202
API Response code 202. Waiting...Deployment deletion in progress... Please Wait
pod "emco-services-orchestrator-7d46d6f888-vcbxf" deleted
parse error: Invalid numeric literal at line 1, column 6
Invalid delete status State.

Since the orchestrator  went down, status GET call fails with connection refused message:

Get "http://172.16.16.150:30415/v2/projects/gmsproj1/composite-apps/gms-collection-composite-app/v1/deployment-intent-groups/gms-collection-deployment-intent-group/status?status=deployed": dial tcp 172.16.16.150:30415: connect: connection refused


Logical cloud Instantiation API call completes but status API fails

...

POST --> URL: http://172.16.16.150:30477/v2/projects/gmsproj1/logical-clouds/default/instantiate
Response Code: 202
API Response code 202. Waiting...Logical Cloud creation in progress... Please Wait
pod "emco-services-dcm-5f746d5db4-hpft7" deleted
parse error: Invalid numeric literal at line 1, column 6
Invalid apply status State.


Since the dcm  went down, status GET call fails with connection refused message:

Get " http://172.16.16.150:30477/v2/projects/gmsproj1/logical-clouds/default/status": dial tcp 172.16.16.150:30477: connect: connection refused


Logical cloud termination API call completes but status API fails

...

POST --> URL: http://172.16.16.150:30477/v2/projects/gmsproj1/logical-clouds/default/terminate
Response Code: 202
API Response code 202. Waiting...Logical Cloud deletion in progress... Please Wait
pod "emco-services-dcm-5f746d5db4-5scl9" deleted
parse error: Invalid numeric literal at line 1, column 6
Invalid delete status State.

Since the dcm  went down, status GET call fails with connection refused message:

Get " http://172.16.16.150:30477/v2/projects/gmsproj1/logical-clouds/default/status": dial tcp 172.16.16.150:30477: connect: connection refused

Logical cloud Termination API call in flight

...

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


Cluster provider creation with CLM restarting


In this case, cluster provider creation fails followed by logical cloud and deployment intent instantiation failure:

Post "http://172.16.16.150:30461/v2/cluster-providers": dial tcp 172.16.16.150:30461: connect: connection refused
Apply: cluster-providers Error: Post "http://172.16.16.150:30461/v2/cluster-providers": dial tcp 172.16.16.150:30461: connect: connection refused


logical cloud and deployment intent instantiation returns code 500

POST --> URL: http://172.16.16.150:30477/v2/projects/gmsproj1/logical-clouds/default/instantiate
Response Code: 500
Response: The server encountered an internal error and was unable to complete your request.

 POST --> URL: http://172.16.16.150:30477/v2/projects/gmsproj1/logical-clouds/default/instantiate
Response Code: 500
Response: The server encountered an internal error and was unable to complete your request.


Once the CLM comes backup, reissue the provider, cluster, logical cloud, DIG instantiation calls and the application instantiation should complete