search

synopsys-sig / synopsys-action

Synopsys Action consuming Synopsys scanning tools
Apache License 2.0
23 stars 16 forks source link

Unexpected response from Connect API #54

Open bond- opened 1 year ago

bond- commented 1 year ago

We have Coverity installation in place in my corporate workspace.

Can you please provide more informational logs or document steps to debug this 500 error? When running this action in our corporate environment, I need to find out what's happening behind the scenes.

I am using the action.yaml provided here: https://github.com/synopsys-sig/synopsys-action#synopsys-github-action---coverity-cloud-deployment-with-thin-client

2023-01-04 11:06:15.5226 EST [Check pull request] INFO: Starting Adapter
2023-01-04 11:06:15.5281 EST [Check pull request] INFO: Adapter finished
2023-01-04 11:06:15.0000 EST [Connect Workflow Controller] ERROR: failed to find the coverity version supported: Received unexpected response status code '500 ' from Connect API
2023-01-04 11:06:15.7101 EST [Coverity Connect Controller] ERROR: Adapter failed: exit status 1
2023-01-04 11:06:15.7131 EST [Default Blackduck Scan Mode] INFO: Adapter finished
2023-01-04 11:06:15.7334 EST [Coverity connect post scan] INFO: Adapter finished
Synopsys Action workflow execution completed
Error: Workflow failed! Exit Code: 2 Error from adapter end
cswanson-crestron commented 1 year ago

We have Coverity installation in place in my corporate workspace.

Can you please provide more informational logs or document steps to debug this 500 error? When running this action in our corporate environment, I need to find out what's happening behind the scenes.

I am using the action.yaml provided here: https://github.com/synopsys-sig/synopsys-action#synopsys-github-action---coverity-cloud-deployment-with-thin-client

2023-01-04 11:06:15.5226 EST [Check pull request] INFO: Starting Adapter
2023-01-04 11:06:15.5281 EST [Check pull request] INFO: Adapter finished
2023-01-04 11:06:15.0000 EST [Connect Workflow Controller] ERROR: failed to find the coverity version supported: Received unexpected response status code '500 ' from Connect API
2023-01-04 11:06:15.7101 EST [Coverity Connect Controller] ERROR: Adapter failed: exit status 1
2023-01-04 11:06:15.7131 EST [Default Blackduck Scan Mode] INFO: Adapter finished
2023-01-04 11:06:15.7334 EST [Coverity connect post scan] INFO: Adapter finished
Synopsys Action workflow execution completed
Error: Workflow failed! Exit Code: 2 Error from adapter end

We are running into the same issue. Did you find a solution?

bond- commented 1 year ago

The GH action doesn't work because our installation isn't installed using Kubernetes and thin client isn't installed.

The 500 error is unintuitive, the error should be tuned to a better message.

cswanson-crestron commented 1 year ago

The GH action doesn't work because our installation isn't installed using Kubernetes and thin client isn't installed.

The 500 error is unintuitive, the error should be tuned to a better message.

We don't use K8s for it either. The error message, agreed, is not helpful.

When I read it, it seems like the thin-client was automatic to some degree. Clearly some client is installed in the error message.

I am tying to open a ticket directly with Synopsys since they are not responding to this.

lejouni commented 1 year ago

Thin-client is currently supporting only Cloud Native Coverity (CNC). If you have on-prem installation of Coverity Connect, this GH action will not work for you. If you want to integrate Coverity Connect with GH pipeline, you need to create your own action. I have created some examples here:

cswanson-crestron commented 1 year ago

Thank you @lejouni. This is exactly what I wanted to confirm before I went down the path of doing it similar to the above links.