[keycloak-user] Still getting index error when upgrading to 1.3.1.Final

[Marek Posolda]

np, I've fixed the JSON import issue in latest master 
https://issues.jboss.org/browse/KEYCLOAK-1558 and also another related 
issue https://issues.jboss.org/browse/KEYCLOAK-1175 .

You should still be able to import the JSON in Keycloak 1.3.1.Final if 
you do not import the JSON through admin console but through the import 
mechanism. You need to:
- Start keycloak against clean database (to ensure master realm is created)
- Stop keycloak
- Start keycloak again with the system properties like: 
-Dkeycloak.migration.action=import 
-Dkeycloak.migration.provider=singleFile 
-Dkeycloak.migration.file=/tmp/abecorn-realm.json

In latest version you will be able to import directly into clean DB 
because of https://issues.jboss.org/browse/KEYCLOAK-1175 fix. But in 
1.3.1 it won't yet work, so you need to start+stop first to ensure 
master realm is initialized

Cheers,
Marek

On 11.7.2015 13:25, Dean Peterson wrote:
> Thank you very much!  I sent my JSON file to you in another e-mail too.
>
> On Sat, Jul 11, 2015 at 4:36 AM, Marek Posolda <mposolda at redhat.com 
> <mailto:mposolda at redhat.com>> wrote:
>
>     I've already created JIRA
>     https://issues.jboss.org/browse/KEYCLOAK-1548 with the reference
>     to the ML thread you created earlier. Will look into it to have
>     the fix for Keycloak 1.4 release.
>
>     Marek
>
>
>     On 10.7.2015 07:30, Dean Peterson wrote:
>>     I did a fresh install with mongodb 3.0 and everything worked fine
>>     running 1.3.1.Final.  However, I need to upgrade from 1.2.0.Beta1
>>     so I tried the same configuration with everything except this
>>     time migrating the old database data.  I get the following error:
>>
>>     at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
>>     at
>>     org.jboss.resteasy.core.ConstructorInjectorImpl.construct(ConstructorInjectorImpl.java:148)
>>     ... 19 more
>>     Caused by: java.lang.RuntimeException: Failed to update database
>>     at
>>     org.keycloak.connections.mongo.updater.impl.DefaultMongoUpdaterProvider.update(DefaultMongoUpdaterProvider.java:90)
>>     at
>>     org.keycloak.connections.mongo.DefaultMongoConnectionFactoryProvider.lazyInit(DefaultMongoConnectionFactoryProvider.java:99)
>>     ... 36 more
>>     Caused by: com.mongodb.CommandFailureException: { "serverUsed" :
>>     "kcdb/172.17.0.69:27017 <http://172.17.0.69:27017>" ,
>>     "nIndexesWas" : 1 , "ok" : 0.0 , "errmsg" : "index not found with
>>     name [realmId_1_name_1]"}
>>     at com.mongodb.CommandResult.getException(CommandResult.java:71)
>>     at com.mongodb.CommandResult.throwOnError(CommandResult.java:110)
>>     at com.mongodb.DBCollection.dropIndexes(DBCollection.java:847)
>>     at com.mongodb.DBCollection.dropIndex(DBCollection.java:1349)
>>     at
>>     org.keycloak.connections.mongo.updater.impl.updates.Update1_2_0_CR1.convertApplicationsToClients(Update1_2_0_CR1.java:33)
>>     at
>>     org.keycloak.connections.mongo.updater.impl.updates.Update1_2_0_CR1.update(Update1_2_0_CR1.java:23)
>>     at
>>     org.keycloak.connections.mongo.updater.impl.DefaultMongoUpdaterProvider.update(DefaultMongoUpdaterProvider.java:79)
>>     ... 37 more
>>
>>     01:17:00,691 ERROR [org.jboss.as.controller.management-operation]
>>     (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed -
>>     address: ([("deployment" => "keycloak-server.
>>
>>
>>     I mentioned this before and Stian was going to look into it; at
>>     the time he thought it might be due to using mongodb 3.0. 
>>     However, mongodb 3.0 works fine with a fresh install.
>>
>>
>>     _______________________________________________
>>     keycloak-user mailing list
>>     keycloak-user at lists.jboss.org  <mailto:keycloak-user at lists.jboss.org>
>>     https://lists.jboss.org/mailman/listinfo/keycloak-user
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/keycloak-user/attachments/20150711/e8f3b185/attachment.html