Hey guys,
I got a problem.
I deleted "default" hardware pool several days before. And I had
to
reinstall ovirt. I got a prompt "500 internal server error" today.
After
refreshing,I can not login to UI. It prompt "We're sorry,but something
went wrong." I think it may be caused by trying to rename the
"default"
hardware pool.
How can I fix this? Must I reinstall it?
Did this action just destroy UI or virtualization configuration ?
Some other peoples also met this problem. Would ovirt buddies give a
feature about resetting? :-)
Thanks,
Nikki
Jia Dong wrote:> Hey guys, > I got a problem. > I deleted "default" hardware pool several days before. And I had to > reinstall ovirt. I got a prompt "500 internal server error" today. > After refreshing,I can not login to UI. It prompt "We're sorry,but > something went wrong." I think it may be caused by trying to rename > the "default" hardware pool. > How can I fix this? Must I reinstall it? > Did this action just destroy UI or virtualization configuration ? > Some other peoples also met this problem. Would ovirt buddies give a > feature about resetting? :-)And there are messages in virt-viewer: EXT3-fs error (device sda2):etx3_add_entry : bad entry in directory in directory #1141426 : rec_len is smaller than minimal - offset=0 ,inode=0,rec_len=0,name_len=0> Thanks, > Nikki > > _______________________________________________ > Ovirt-devel mailing list > Ovirt-devel at redhat.com > https://www.redhat.com/mailman/listinfo/ovirt-devel
On Tue, Dec 2, 2008 at 10:08 AM, Jia Dong <jdong at redhat.com> wrote:> Alan Pevec wrote: >> This all looks like a bad corruption somewhere. As a sanity check, I'll do F9 build now. > I ran it on F9. > How did you install it on F10? I tried to install it on F10 this morning, and got a message that there was no packages for F10.Or you built sources on F10?Yeah, F10 was built from git. But in any case, I got the same issue on F9 and the culprit is the updated kvm-79. I'll downgrade back to 78-4 in ovirt.org repo and we'll use that for the 0.96 release we're wrapping up. After release is out, I'll bisect between 78 and 79 to find out what introduced this issue.