Cannot force update branch error is back about ruby_rbenv

[thr3a]

This problem is still occurring in my environment.
What is the progress of fixing this issue?

[ramereth]

Unfortunately not but this would be a great candidate for Hacktoberfest 2020.

[axelrtgs]

@thr3a So the issue at heart is a bug in chef built in git resource. i can confirm that newer versions of chef-client don't exhibit this behaviour in my testing. We use 16.4.41 in our env and we do not have this issue anymore (even with the removed workaround) and the testing running on latest did not exhibit this issue either.

The solution to this is to update to a more recent chef client with the bugfix theres not much that can be done in this cookbook. removed the workaround in the cookbook since its no longer needed on more recent versions.

[ramereth]

@axelrtgs is this only affecting Versions >= 16, < 16.4.41? with Chef?

[axelrtgs]

i can tell you for sure its affect some versions inside that range. i know we noticed it when first trying out 16 in the lab then found out the git resource got a rewrite and then when we went to prod with it we pinned to version 16.4.41 which seems to work fine now. it may have been fixed in a slightly earlier version. I can leave a not in the readme that theres a chef bug that affected the cookbook in that range and that we have confirmed >=16.4.41 to be working properly now

[thr3a]

@axelrtgs

Thank you for providing me with useful information.
I also updated my chef version (16.6.14) and the problem was resolved.