Renovate: bug(bitbucket-server): ERROR: Repository has unknown error

[viceice]

What Renovate type are you using?
Renovate CLI 14.20.0, Bitbucket Server 6.0

Describe the bug
Renovate is trying to update an onboarding pr and gets a 409 Conflict.
It has rebased and pushed the onboarding commit before.
Looks like a caching problem?

Did you see anything helpful in debug logs?
You are attempting to modify a pull request based on out-of-date information.

 "currentVersion": 12,
 "expectedVersion": 11,

To Reproduce
Steps to reproduce the behavior:

1. Create repository with multiple Docker, Angular and Dotnet projects
2. Wait for onboarding pr

Expected behavior
Should update the pr title and description.

[viceice]

I have a debug log, but that should not be public. 😉

[rarkins]

What causes the PR to need updating? Can you try to flesh out the reproduction steps so I can reproduce it on my local BB server? I assume it's not necessarily related to the exact type of projects or even related to whether you have 2 or more.

[viceice]

Ok, i found something. I've changed the onboardingConfig, thats why renovate will update the commit, but does push the old config.

{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":20,"repository":"owner/repo","msg":"Onboarding PR already exists","time":"2019-02-19T07:14:12.353Z","v":0}
{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":20,"repository":"owner/repo","msg":"Checking if onboarding branch needs rebasing","time":"2019-02-19T07:14:12.353Z","v":0}
{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":20,"repository":"owner/repo","msg":"getBranchPr(renovate/configure)","time":"2019-02-19T07:14:12.353Z","v":0}
{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":20,"repository":"owner/repo","msg":"findPr(renovate/configure)","time":"2019-02-19T07:14:12.353Z","v":0}
{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":20,"repository":"owner/repo","msg":"findPr(renovate/configure, \"null\", \"open\")","time":"2019-02-19T07:14:12.354Z","v":0}
{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":20,"repository":"owner/repo","msg":"getPrList()","time":"2019-02-19T07:14:12.354Z","v":0}
{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":20,"repository":"owner/repo","msg":"returning cached PR list","time":"2019-02-19T07:14:12.354Z","v":0}
{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":20,"repository":"owner/repo","msg":"Found PR #1","time":"2019-02-19T07:14:12.354Z","v":0}
{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":20,"repository":"owner/repo","msg":"getPr(1)","time":"2019-02-19T07:14:12.354Z","v":0}
{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":20,"repository":"owner/repo","msg":"getFile(renovate.json, renovate/configure)","time":"2019-02-19T07:14:12.354Z","v":0}
{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":20,"repository":"owner/repo","msg":"Checking for greenkeeper config","time":"2019-02-19T07:14:12.404Z","v":0}
{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":20,"repository":"owner/repo","msg":"getFile(package.json, undefined)","time":"2019-02-19T07:14:12.405Z","v":0}
{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":20,"repository":"owner/repo","msg":"No greenkeeper config migration","time":"2019-02-19T07:14:12.429Z","v":0}
{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":20,"repository":"owner/repo","config":{"extends":["config:base",":automergePatch",":automergeDigest",":assignAndReview(kriese)"]},"msg":"onboarding config","time":"2019-02-19T07:14:12.430Z","v":0}
{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":30,"repository":"owner/repo","msg":"Rebasing onboarding branch","time":"2019-02-19T07:14:12.432Z","v":0}
{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":20,"repository":"owner/repo","msg":"commitFilesToBranch({\n  \"branchName\": \"renovate/configure\",\n  \"filesLength\": 1,\n  \"message\": \"Add renovate.json\",\n  \"parentBranch\": \"master\"\n})","time":"2019-02-19T07:14:12.433Z","v":0}
{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":20,"repository":"owner/repo","msg":"Setting baseBranch to renovate/configure","time":"2019-02-19T07:14:14.409Z","v":0}
{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":20,"repository":"owner/repo","msg":"getFileList(renovate/configure)","time":"2019-02-19T07:14:14.434Z","v":0}
{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":20,"repository":"owner/repo","msg":"Found renovate.json config file","time":"2019-02-19T07:14:14.487Z","v":0}
{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":20,"repository":"owner/repo","msg":"getFile(renovate.json, undefined)","time":"2019-02-19T07:14:14.487Z","v":0}
{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":30,"repository":"owner/repo","configFile":"renovate.json","config":{"extends":["config:base"]},"msg":"Repository config","time":"2019-02-19T07:14:14.513Z","v":0}
{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":20,"repository":"owner/repo","msg":"migrateAndValidate()","time":"2019-02-19T07:14:14.513Z","v":0}
{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":20,"repository":"owner/repo","msg":"No config migration necessary","time":"2019-02-19T07:14:14.514Z","v":0}
{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":20,"repository":"owner/repo","config":{"extends":["config:base"]},"msg":"massaged config","time":"2019-02-19T07:14:14.514Z","v":0}
{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":20,"repository":"owner/repo","config":{"extends":["config:base"]},"msg":"migrated config","time":"2019-02-19T07:14:14.514Z","v":0}
{"name":"renovate","hostname":"41202ec0f0df","pid":26,"level":20,"repository":"owner/repo","msg":"checkBaseBranch()","time":"2019-02-19T07:14:15.613Z","v":0}

[rarkins]

Changing onboardingConfig is not something I've looked at in a long time. I know there were some difficult edge cases that caused me to change its behaviour but I forget exactly what! Also, gitFs is new since then so that's another factor.

[viceice]

@rarkins I'll delete the pr and branch, this will maybe fix the problem for now.

[renovate-bot]

:tada: This issue has been resolved in version 14.26.2 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: