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 12 years ago. Updated over 9 years ago.

Status:
Rejected
Priority:
5 (lowest)
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
 #1

Updated by Jonathan CLARKE about 12 years ago

  • Assignee deleted (Nicolas PERRON)
  • Priority changed from 1 (highest) to 4
  • Target version changed from 2.4.0~beta4 to 2.4.0~rc1

This is a corner case, unlikely to happen... Degrading priority.

Actions
Copy link
 #2

Updated by Jonathan CLARKE about 12 years ago

  • Assignee set to Nicolas PERRON
Actions
Copy link
 #3

Updated by Jonathan CLARKE about 12 years ago

  • Priority changed from 4 to 5 (lowest)
Actions
Copy link
 #4

Updated by Jonathan CLARKE about 12 years ago

  • Target version changed from 2.4.0~rc1 to 2.4.0~rc2
Actions
Copy link
 #5

Updated by Nicolas PERRON about 12 years ago

  • Target version changed from 2.4.0~rc2 to 2.4.0~rc1
Actions
Copy link
 #6

Updated by Nicolas PERRON about 12 years ago

  • Target version changed from 2.4.0~rc1 to 2.4.0~rc2

This ticket have to be postponed at least to 2.4.0~rc2 (if not rejected by the fact that this is a corner case)

Actions
Copy link
 #7

Updated by François ARMAND almost 12 years ago

  • Target version changed from 2.4.0~rc2 to 61
Actions
Copy link
 #8

Updated by François ARMAND almost 12 years ago

  • Status changed from New to Discussion

NPE, it seems that there is a workaround for that bug? Could you please give some more information and close it if it should be closed.

Actions
Copy link
 #9

Updated by Nicolas PERRON almost 12 years ago

  • Assignee changed from Nicolas PERRON to François ARMAND

A workaround has been made here: #2802
This is a situation which should not be able to reproduce since like the description said: a migration should be made with a wrong git branch in the /var/rudder/configuration-repository but the workaround prevent from that.

Actions
Copy link
 #10

Updated by François ARMAND almost 12 years ago

  • Assignee changed from François ARMAND to Nicolas PERRON

So, I propose to close that one to "rejected", as it seems to be an artifact of tests done during development phases.

Actions
Copy link
 #11

Updated by François ARMAND almost 12 years ago

  • Target version changed from 61 to 2.4.2
Actions
Copy link
 #12

Updated by Nicolas PERRON almost 12 years ago

  • Status changed from Discussion to Rejected

François ARMAND wrote:

So, I propose to close that one to "rejected", as it seems to be an artifact of tests done during development phases.

Agreed

Actions
Copy link
 #13

Updated by Nicolas PERRON almost 12 years ago

  • Project changed from Rudder to 34
  • Category deleted (11)
Actions
Copy link
 #14

Updated by Benoît PECCATTE over 9 years ago

  • Project changed from 34 to Rudder
  • Category set to Packaging
Actions
Copy link

Also available in: Atom PDF