Bug #970

onedb: opennebula 2.0 upgrade to 3.0

Added by kan wenxiao over 9 years ago. Updated over 9 years ago.

Status:ClosedStart date:11/10/2011
Priority:HighDue date:
Assignee:-% Done:


Target version:-
Resolution:invalid Pull request:
Affected Versions:OpenNebula 3.0



While upgrading to 3.0 I found a fault:"Database schema does not look to be created by OpenNebula: table user_pool is missing or empty."can you tell me how to solve it? thank you!!!!


#1 Updated by Carlos Martín over 9 years ago

  • Status changed from New to Closed
  • Resolution set to invalid

This is probably a configuration issue, not a bug. Maybe the sqlite DB isn't readable, or one of the mysql connection parameters is not correctly set...
Please use the mailing list [1] for support.

[1] http://www.opennebula.org/community:mailinglists

Also available in: Atom PDF