Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Renovate from Azure DevOps Started Generating Git Error #6846

Closed
MikeKenyon opened this issue Jul 24, 2020 · 5 comments
Closed

Renovate from Azure DevOps Started Generating Git Error #6846

MikeKenyon opened this issue Jul 24, 2020 · 5 comments
Labels
platform:azure Azure DevOps platform

Comments

@MikeKenyon
Copy link

What Renovate type are you using?

Running Renovate through the RenovateMe task on Azure DevOps. This is running from a Linux Build Agent.

Describe the bug

Prior till Tuesday, Renovate was running fine. Since then, the tool generates an error while attempting to create pull requests. It does the comparison and makes branches fine.

  • TFS hasn't been updated
  • Permissions haven't been updated
  • RenovateMe (the task runner) hasn't been updated
  • The build structure hasn't versioned
  • The underlying code hasn't versioned in the repo being updated.

The only thing that has versioned is Renovate.

Relevant debug logs

To Reproduce

DEBUG: getBranchStatus(renovate/microsoft.aspnetcore.mvc.testing-3.x) (repository=EWB/api.widgets, branch=renovate/microsoft.aspnetcore.mvc.testing-3.x)
DEBUG: Creating PR (repository=EWB/api.widgets, branch=renovate/microsoft.aspnetcore.mvc.testing-3.x)
       "prTitle": "chore(deps): update dependency microsoft.aspnetcore.mvc.testing to v3.1.6"
DEBUG: Pull request creation error (repository=EWB/api.widgets, branch=renovate/microsoft.aspnetcore.mvc.testing-3.x)
       "err": {
         "statusCode": 400,
         "result": {
           "$id": "1",
           "innerException": null,
           "message": "TF401398: The pull request cannot be activated because the source and/or the target branch no longer exists, or the requested refs are not branches",
           "typeName": "Microsoft.TeamFoundation.Git.Server.GitPullRequestCannotBeActivated, Microsoft.TeamFoundation.Git.Server",
           "typeKey": "GitPullRequestCannotBeActivated",
           "errorCode": 0,
           "eventId": 3000
         },
         "message": "TF401398: The pull request cannot be activated because the source and/or the target branch no longer exists, or the requested refs are not branches",
         "stack": "Error: TF401398: The pull request cannot be activated because the source and/or the target branch no longer exists, or the requested refs are not branches\n    at RestClient.<anonymous> (/home/buildagent/.npm/_npx/90347/lib/node_modules/renovate/node_modules/typed-rest-client/RestClient.js:202:31)\n    at Generator.next (<anonymous>)\n    at fulfilled (/home/buildagent/.npm/_npx/90347/lib/node_modules/renovate/node_modules/typed-rest-client/RestClient.js:6:58)\n    at process._tickCallback (internal/process/next_tick.js:68:7)"
       }
DEBUG: Removing any stale branches (repository=EWB/api.widgets)
DEBUG: config.repoIsOnboarded=true (repository=EWB/api.widgets)

Additional context

@rarkins
Copy link
Collaborator

rarkins commented Jul 24, 2020

Can you work out which version of Renovate it last worked on, and which it failed on? e.g. did it work in v21 but then start failing for v22?

And does the branch exist?

@rarkins rarkins added the platform:azure Azure DevOps platform label Jul 24, 2020
@sleeuwen
Copy link

I'm having the same problem, renovate runs fine and the logs don't indicate any errors but the pull request is never created while the branch with the changes exists. Only when I set the log level to debug it shows the pull request couldn't be created, but I would have expected that to be of log level error?

I have done some testing, and it seems to have started from build 21.33.13. My system ran this morning version 22.3.3 and is still experiencing the problem.

@renovate-release
Copy link
Collaborator

🎉 This issue has been resolved in version 22.3.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

@rarkins
Copy link
Collaborator

rarkins commented Jul 27, 2020

Thanks for your help reporting and narrowing down the problem. Once you have the chance to test 22.3.4 or later, please confirm here if it's fixed as I hope.

@zleight1
Copy link
Contributor

zleight1 commented Jul 27, 2020

I was having the same issue with on-premises Azure DevOps with whatever was the "latest" version on July 23, and can confirm it is now working in 22.3.4

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
platform:azure Azure DevOps platform
Projects
None yet
Development

No branches or pull requests

5 participants