Actions
Bug #2802
closedRudder can't start after a migration if the Rudder Technique Reference Library branch is not the same than the /var/rudder/configuration-repository branch
Status:
Released
Priority:
1 (highest)
Assignee:
Nicolas PERRON
Category:
Packaging
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
If in rudder-web.properties, the Rudder Technique Reference Library branch is not the same than the /var/rudder/configuration-repository branch, after a migration from 2.3 to 2.4.0~beta3, Rudder is broken.
in rudder-web.properties:
rudder.ptlib.git.refs.path=refs/heads/master
in /var/rudder/configuration-repository :
root@server:/var/rudder/configuration-repository# git branch * brokenbranch master
Rudder can't start with this error message:
[...] [2012-08-13 14:46:33] INFO application - Use configuration file defined by JVM property -Drudder.configFile : /opt/rudder/etc/rudder-web.properties [2012-08-13 14:46:34] INFO application - Use configuration file defined by JVM property -Drudder.authFile : /opt/rudder/etc/rudder-users.xml [2012-08-13 14:46:35] ERROR org.springframework.web.context.ContextLoader - Context initialization failed [...] Caused by: java.lang.RuntimeException: Missing techniques root category in Git, expecting category descriptor for Git path: '/var/rudder/configuration-repository/techniques/category.xml' at scala.sys.package$.error(package.scala:27) [...]
Even if I try to reapply rudder-upgrade script to the good branch, Rudder still can't be started with the same error message.
Actions