search

forcedotcom / devops-center-feedback

61 stars 2 forks source link

Commit Changes Error -- Unable to perform operation #262

Open Jamie-Ivey opened 1 year ago

Jamie-Ivey commented 1 year ago

Describe the bug We are just in the process of getting set up with DevOps Center. We have managed to get as far as setting up a project with pipeline and we have a work item created. The work item has created the branch successfully in GitHub, so it appears as if things are connected correctly. If we make a change in the development org, the change is recognized in DevOps Center. So far, so good. The issue arises when we attempt to commit that change. The page shows that the commit was initiated and then it errors out and goes no further. It doesn't mention connecting with GitHub, so we're not sure whether the issue is with contacting GitHub or if it's on the Salesforce side before reaching out to GitHub. But, as we mentioned, the work item did successfully create the branch, so it appears as if Salesforce is speaking to GitHub properly. If we scour the debug logs the only thing that stands out is that at some point Salesforce tries to hit a named credential endpoint that results in a 404 -- not found. The named credential is the DevOpsCenter Service. We're not sure if that has something to do with it or not.

Expected behavior We are expecting that our changes be committed successfully so that we can then continue with the deployment process.

Screenshots image

Additional context We've gone through many setup guides and we think everything is set up properly in terms of the connected app, permissions, pipeline orgs etc.

tfirman-ehg commented 1 year ago

We are seeing the same thing. Is there any update?

aldoforce commented 11 months ago

How did you fixed this?

dvario-vi commented 11 months ago

I'm experiencing something similar to this right now. Getting a 404 error when attempting to commit. Check GH and I can see the branch was committed, but it shows as failed in DevOps. How did you resolve this?

prabhjeetbhatia commented 11 months ago

We are also getting this error today only 404 Error. If others started getting this error today it means something wrong with Salesforce side.

qkershner commented 11 months ago

Same. Three separate orgs, all failing with "Response Code 404 (Not Found)" error

prabhjeetbhatia commented 11 months ago

@dvario-vi @aldoforce you started getting it today?

prabhjeetbhatia commented 11 months ago

@qkershner We started getting today as well. So must be salesforce is having some problem connecting with GitHub I feel.

aldoforce commented 11 months ago

@prabhjeetbhatia well, yes this was a Salesforce <> GH issue. It fixed without any change from dev side. Right now (5:42am EST) everything is working as expected.

joostkarsten commented 5 months ago

We are experiencing the exact same problem. We have searched through the logs, and we encounter the following error:

12:36:29:594 NAMED_CREDENTIAL_RESPONSE NamedCallout[Named Credential Id=0XAIV0000000HSI, Named Credential Name=DevOps_Center_Service, Status Code=404, Content-Type=application/json, Response Size bytes=149, Overall Callout Time ms=895, Connect Time ms=446

It is trying to reach the following endpoint: 12:36:29:594 NAMED_CREDENTIAL_REQUEST NamedCallout[Named Credential Id=0XAIV0000000HSI, Named Credential Name=DevOps_Center_Service, Endpoint=https://devops-center.prod.repo-ops.sfdc.sh/doce-servicio, Method=POST, External Credential Type=EXTERNAL, HTTP Header Authorization=Method: Not set - Credential: Not set, Content-Type=application/json; charset=utf-8, Request Size bytes=827, Retry on 401=True]

I tried reaching this endpoint from outside Salesforce, with a rest client, and got the same error: NOT FOUND. It seems that this endpoint does not exist.