Verify workflow failure

You can view the workflow failure logs to verify the reason for workflow failure. You can view logs of the remote worker pod on which workflow is executed.

Problem

Workflow fails because of different reasons.

Solution

• ♦ Run the following command to verify the remote worker pod on which the workflow is executed.

  kubectl logs vmware-bma-remote-worker-pliant-worker-7bb567f897-lqg2h -n bma-remote-worker

  Error from Logs

  action trigger-flow e5cd6c0e-dcff-448c-97ee-3690b6e1db2b
  status R e5cd6c0e-dcff-448c-97ee-3690b6e1db2b
  process e5cd6c0e-dcff-448c-97ee-3690b6e1db2b executing system
  process e5cd6c0e-dcff-448c-97ee-3690b6e1db2b executing Redfish/request
  process e5cd6c0e-dcff-448c-97ee-3690b6e1db2b error "RequestError: Error: self signed certificate" "RequestError: Error: self signed certificate\n    at new RequestError (/usr/src/app/node_modules/request-promise-core/lib/errors.js:14:15)\n    at Request.plumbing.callback (/usr/src/app/node_modules/request-promise-core/lib/plumbing.js:87:29)\n    at Request.RP$callback [as _callback] (/usr/src/app/node_modules/request-promise-core/lib/plumbing.js:46:31)\n    at self.callback (/usr/src/app/node_modules/request/request.js:189:22)\n    at Request.emit (node:events:369:20)\n    at Request.onRequestError (/usr/src/app/node_modules/request/request.js:887:8)\n    at ClientRequest.emit (node:events:369:20)\n    at TLSSocket.socketErrorListener (node:_http_client:462:9)\n    at TLSSocket.emit (node:events:369:20)\n    at emitErrorNT (node:internal/streams/destroy:188:8)\n    at emitErrorCloseNT (node:internal/streams/destroy:153:3)\n    at processTicksAndRejections (node:internal/process/task_queues:81:21)"