From: OSCAR P. <no...@op...> - 2007-12-20 19:30:00
|
#444: F8 - Inconsistent database state due to aborted installtion -----------------------------+---------------------------------------------- Reporter: abbyz | Owner: dikim = Type: bug | Status: assigned = Priority: major | Milestone: OSCAR 5.1 = Component: core - Testing | Version: crispy_5.1 Resolution: | Keywords: = -----------------------------+---------------------------------------------- Comment (by dikim): OK, abbyz, can you please clarify what differences you can get between fresh oscar installation and after start_over in terms of the OSCAR database? (Assuming that you don't have this error when this is an oscar fresh installation.) Looks like I need to reproduce this error on my test in order to crack this problem. Otherwise, it is very difficult for me to get closer to the problem. If anyone want to take over the RHEL4-x86 support, I would be happy to support F8-x86. Regards, -- = Ticket URL: <http://svn.oscar.openclustergroup.org/trac/oscar/ticket/444#co= mment:3> OSCAR Project <http://svn.oscar.openclustergroup.org/> OSCAR | Open Source Cluster Application Resources |