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
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.
Updated by Nicolas PERRON about 12 years ago
In the migration script, there is clearly a test missing: Do not act on git if we are not the good git branch (Rudder Technique Reference Library branch).
Updated by Nicolas PERRON about 12 years ago
Here are two problems:
- We are matching only rudder.ptlib.git.refs.path but in rudder 2.4, this attribute is renamed into rudder.techniqueLibrary.git.refs.path
- Easy: we will check the both of them
- These attributes can accept a lot of values: (refs/heads/master, refs/tags/mytag, master, mytag, bf46f65cdbba1fc175bd73a74e97c80275ae4339 (commit ID), etc...)
- We can't use all of these attributes with git checkout for example: refs/heads/master will be in a detached HEAD state contrary to master
- A first approach will be to remove all "/refs/heads/", "refs/tags/" and "refs/remote/origin/" to use git checkout.
Updated by Nicolas PERRON about 12 years ago
- Status changed from New to Pending technical review
- % Done changed from 0 to 100
Nicolas PERRON wrote:
Here are two problems:
- We are matching only rudder.ptlib.git.refs.path but in rudder 2.4, this attribute is renamed into rudder.techniqueLibrary.git.refs.path
- Easy: we will check the both of them
- These attributes can accept a lot of values: (refs/heads/master, refs/tags/mytag, master, mytag, bf46f65cdbba1fc175bd73a74e97c80275ae4339 (commit ID), etc...)
- We can't use all of these attributes with git checkout for example: refs/heads/master will be in a detached HEAD state contrary to master
- A first approach will be to remove all "/refs/heads/", "refs/tags/" and "refs/remote/origin/" to use git checkout.
We can consider the last commit as fixing this issue.
A new ticket is open for an enhancement about other conditions than having rudder.ptlib.git.refs.path set to "/refs/heads/*", "refs/tags/*" or "refs/remote/origin/*": #2804
Updated by Jonathan CLARKE almost 12 years ago
- Status changed from Pending technical review to Released
Looks good to me.
Updated by Nicolas PERRON over 11 years ago
- Project changed from Rudder to 34
- Category deleted (
11)
Updated by Benoît PECCATTE over 9 years ago
- Project changed from 34 to Rudder
- Category set to Packaging