My favorites | Sign in
Project Home Downloads Wiki Issues Source
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 1287: Problem upgrading 2.1.8 to 2.2.2.1
3 people starred this issue and may be notified of changes. Back to list
Status:  New
Owner:  ----


Sign in to add a comment
 
Reported by r...@rensnel.nl, Mar 12, 2012
I'm upgrading a 2.1.8 install to 2.2.2.1, but directly after answering all configuration questions I get the following error:

Upgrading database schema from version 52 to 53 ...
Exception in thread "main" com.google.gwtorm.client.OrmException: Cannot create repository Some/Repository/Name
	at com.google.gerrit.server.schema.Schema_53.exportProjectConfig(Schema_53.java:163)
	at com.google.gerrit.server.schema.Schema_53.migrateData(Schema_53.java:101)
	at com.google.gerrit.server.schema.SchemaVersion.upgradeFrom(SchemaVersion.java:95)
	at com.google.gerrit.server.schema.SchemaVersion.check(SchemaVersion.java:77)
	at com.google.gerrit.server.schema.SchemaVersion.upgradeFrom(SchemaVersion.java:86)
	at com.google.gerrit.server.schema.SchemaVersion.check(SchemaVersion.java:77)
	at com.google.gerrit.server.schema.SchemaVersion.upgradeFrom(SchemaVersion.java:86)
	at com.google.gerrit.server.schema.SchemaVersion.check(SchemaVersion.java:77)
	at com.google.gerrit.server.schema.SchemaVersion.upgradeFrom(SchemaVersion.java:86)
	at com.google.gerrit.server.schema.SchemaVersion.check(SchemaVersion.java:77)
	at com.google.gerrit.server.schema.SchemaVersion.upgradeFrom(SchemaVersion.java:86)
	at com.google.gerrit.server.schema.SchemaVersion.check(SchemaVersion.java:77)
	at com.google.gerrit.server.schema.SchemaVersion.upgradeFrom(SchemaVersion.java:86)
	at com.google.gerrit.server.schema.SchemaVersion.check(SchemaVersion.java:77)
	at com.google.gerrit.server.schema.SchemaVersion.upgradeFrom(SchemaVersion.java:86)
	at com.google.gerrit.server.schema.SchemaVersion.check(SchemaVersion.java:77)
	at com.google.gerrit.server.schema.SchemaUpdater.update(SchemaUpdater.java:64)
	at com.google.gerrit.pgm.Init$SiteRun.upgradeSchema(Init.java:181)
	at com.google.gerrit.pgm.Init.run(Init.java:79)
	at com.google.gerrit.pgm.util.AbstractProgram.main(AbstractProgram.java:76)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at com.google.gerrit.launcher.GerritLauncher.invokeProgram(GerritLauncher.java:165)
	at com.google.gerrit.launcher.GerritLauncher.mainImpl(GerritLauncher.java:89)
	at com.google.gerrit.launcher.GerritLauncher.main(GerritLauncher.java:47)
	at Main.main(Main.java:25)
Caused by: org.eclipse.jgit.errors.RepositoryNotFoundException: repository not found: Invalid name: Some/Repository/Name
	at com.google.gerrit.server.git.LocalDiskRepositoryManager.createRepository(LocalDiskRepositoryManager.java:117)
	at com.google.gerrit.server.schema.Schema_53.exportProjectConfig(Schema_53.java:161)
	... 27 more
	

I already found this post: https://code.google.com/p/gerrit/issues/detail?id=500 and followed the instructions about the missing indexes from the 2.0.x installation, but this didn't fix the issue (I indeed missed the next_val index). I also set the site_path in the system_config as this was also not set.

But this is all not solving the problem... Any other steps I can do to get this working?
Mar 12, 2012
#1 r...@rensnel.nl
For now I've updated the schema to 53 by hand and restarted the init, and this works... Any idea how I can see what the migration between those 2 versions actually is?
Aug 14, 2012
#2 lash...@gmail.com
I've updated the schema to 53 by hand

Help~~I'm working on this issue
how did you update the schema to 53 by hand???
Aug 15, 2012
#3 r...@rensnel.nl
I just installed a new copy of the next version, and compared the database structure by hand. Pretty dirty, but it worked ;)
Oct 11, 2012
#4 l13uw3hu...@gmail.com
Rens, had the repository name a trailing slash? I did some RTFC based on the class names and line nrs in your exception stack trace and came into method isUnreasonableName() of class LocalDiskRepositoryManager where the project name is being checked on a trailing slash among a few other things.
In my lab environment, I upgraded successfully to rev 64. 

Note 1: I used https://docwhat.org/gerrit-rename-a-project/ to rename the affected projects.
Note 2: some users might also check table submodule_subscriptions, but that was empty in my case
Sign in to add a comment

Powered by Google Project Hosting