Bug #3531
closed
Backport the git lock erase promise if older than 5 minutes from 2.5 to 2.4
Added by Matthieu CERDA over 11 years ago.
Updated about 11 years ago.
Category:
System techniques
Description
As seen in #3526, we introduced a fix to nuke the git lock file in the configuration-repository in case it was older than X minutes.
Il should be backported into 2.4 when tested enough.
- Target version changed from 2.4.5 to 2.4.6
- Target version changed from 2.4.6 to 2.4.7
- Target version changed from 2.4.7 to 2.4.8
- Status changed from New to Discussion
- Assignee set to Matthieu CERDA
Shouldn't have it already be made ?
- Target version changed from 2.4.8 to 2.4.9
I'm taking a look at this.
- Status changed from Discussion to 13
- Status changed from 13 to Pending release
Applied in changeset policy-templates:commit:25f466a83a1c086654f83ef5e0729dc9d1bf73f4.
Applied in changeset policy-templates:commit:af824ba8737d37b62fe156bd5a732238017f2b86.
- Target version changed from 2.4.9 to 2.4.8
- Tracker changed from User story to Bug
This is more a bug than a user story but I still keep the implementation ticket.
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.4.8, which was released today.
Check out:
Also available in: Atom
PDF