Project

General

Profile

Actions
Copy link

Bug #2805

closed

After a migration from 2.3 to 2.4.0~beta3, if a migration has been made with a wrong git branch on /var/rudder/configuration-repository it is impossible to return in a normal state

Added by Nicolas PERRON over 11 years ago. Updated about 9 years ago.

Status:
Rejected
Priority:
5
Assignee:
Nicolas PERRON
Category:
Packaging
Target version:
2.4.2
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

Before #2802 fix, it was possible to initiate an upgrade with a wrong git branch and it was resulting in a broken state. Besides, there was no possibility to return in a functional state even if we try to reuse the right branch or to delete the attribute techniqueLibraryVersion in techniqueCategoryId=Active Techniques,ou=Rudder,cn=rudder-configuration.

Related issues 2 (0 open — 2 closed)

Related to Rudder - Bug #2802: Rudder can't start after a migration if the Rudder Technique Reference Library branch is not the same than the /var/rudder/configuration-repository branchReleasedNicolas PERRON2012-08-13Actions
Related to Rudder - Bug #2804: In rudder upgrade, the Rudder Technique Reference Library attribute in rudder-wbe.properties should be checked with a more flexbile wayRejectedNicolas PERRON2012-08-13Actions
Actions
Copy link

Also available in: Atom PDF